[GB] M65-A | Made with RAMA.WORKS (Complete)

[Atredl]

Put together my own M65-A build guide. Hope you enjoy! 

http://imgur.com/a/XpQOS

[mattijs]

Put together my own M65-A build guide. Hope you enjoy! 

http://imgur.com/a/XpQOS

Great build guide with lots of detail, thanks for posting it

[delivery]

Packed with details!

[robbles]

These pics look great and all but none feature that sweet underglow? Came someone deliver?

[kitchenace13]

Anyone have any tips/recommendations on what I need to do for LEDs? Maybe SIP sockets for now and decide later?  Not sure what everyone else is planning!

[Atredl]

Anyone have any tips/recommendations on what I need to do for LEDs? Maybe SIP sockets for now and decide later?  Not sure what everyone else is planning!

I plan on installing SIPs on mine eventually. Unless you're doing hotlites, SIPs are the way to go.

[Valaris]

Holtites don't fit on this PC iirc.

[Atredl]

TIL I guess SIPs really are the way to go on this board then.

[Arallu]

..

[MikeTheTiger]

Did I miss extras being posted?

[Corgi Butts]

Did I miss extras being posted?

Don't believe so.


Sent from my iPhone using Tapatalk

[pixelpusher]

We just have to be patient.  Not only are there people wanting extras of this board, but we still haven't seen extras of the XDA keycaps.  I have a feeling jchan is busy and the website will pop up with all of the extras soon enough. 

[Rumblehotep]

Nice pics everyone! I'm wondering, Mr. Chan, if those of us who opted-out of stabs are getting ours shipped out? I was hoping that by opting-out it would expedite the process, however I haven't seen an update since I started following the shipping progress.

Q: Can I get stabs later?
A: Unfortunately, I'll have to say no. I don't like shipping partial orders. That's a lot of upkeep for me.

Doesn't look like it, I opted out but have some waiting for it already.
Edit: Ah thought you were asking if the stabs were being shipped after, dunno if the m65's are expedited or not.

[kimusan]

So what are the chances of getting my hands on one of these amazing keebs?

[forevermadrigal]

So what are the chances of getting my hands on one of these amazing keebs?

If you read the op, you will know those chances.

[kimusan]

might just be me but I did not see anything mentioning this in the OP :-S

Edit: nevermind. See it now (completely overlooked it at first).

[evrydayzawrkday]

Put together my own M65-A build guide. Hope you enjoy! 

http://imgur.com/a/XpQOS

I love the guide.. and it even reminded me to screw in the sides (which took away my tiny wobble problem with the steel base).

[BAS1C]

Hey jchan, could you add a “more” button for all/all but a few of the pics in the first post when you get a chance? No rush. It eats all the datas everytime I check the first page for shipping updates. Don’t see an option tohide them, someone correct me if I am doing it wrong please!

[TheDisappointingGatsby]

Hey jchan, could you add a “more” button for all/all but a few of the pics in the first post when you get a chance? No rush. It eats all the datas everytime I check the first page for shipping updates. Don’t see an option tohide them, someone correct me if I am doing it wrong please!

Would be nice to hide them for more efficient F5'ing to check for shipping updates.

[KINGPIN]

I am being slightly upset because I filled the no stab form buy my keeb still haven't been shipped yet, I may as well not fill the form if that's what happend

[Atredl]

Put together my own M65-A build guide. Hope you enjoy! 

http://imgur.com/a/XpQOS

I love the guide.. and it even reminded me to screw in the sides (which took away my tiny wobble problem with the steel base).

Glad I could help 

[eyedrop]

Just send an email to jchan's support email.

I finally had a chance to open the box and I noticed I am missing the PCB as well.

I look everywhere, took out the foam piece, and it is not there.

Hopefully jchan can resolve this problem for me.

[imprevade]

So I got the QMK PCB, and I've been making good progress with the programming.. but a few of my RGBs won't cooperate. Sometimes they join the others in color and mode, other times they just get stuck on a color. Anyone have this problem or know of a solution?

edit: So I'm now seeing that if I play with hue or value while the color is stuck, it doesn't do anything. But if I mess with saturation, they will sometimes sync up with the rest.

Also note, if the colors are syncing when I toggle the RGB off, the stuck ones don't go off either.

[chancellorr]

I really wish I didn't need those damn stabs.

[Arallu]

..

[imprevade]

Worth the wait.

[yokken]

Wow, that is stunning. Excellent work.

[Gamecat]

Worth the wait.

(Attachment Link)

(Attachment Link)

Beautiful! 
Do you think there is enough room/screw thread to add a small washer between the plate/case mount point so that the keycaps sit slightly below level to the case top?

[pixelpusher]

Worth the wait.

(Attachment Link)

(Attachment Link)

Beautiful! 
Do you think there is enough room/screw thread to add a small washer between the plate/case mount point so that the keycaps sit slightly below level to the case top?

That's a good idea but I'm pretty sure that you would have to have a significantly thick washer and then the bottom section would not meet up with the top.  I really prefer to have the keycaps below the top of the case (one of the reasons I like the Fjell so much), but this design was chosen purposefully, and still looks nice.   I'm guessing people like this look so that they can see the switch housings?  Especially when they are clear and have leds

[Gamecat]

Worth the wait.

(Attachment Link)

(Attachment Link)

Beautiful! 
Do you think there is enough room/screw thread to add a small washer between the plate/case mount point so that the keycaps sit slightly below level to the case top?

That's a good idea but I'm pretty sure that you would have to have a significantly thick washer and then the bottom section would not meet up with the top.  I really prefer to have the keycaps below the top of the case (one of the reasons I like the Fjell so much), but this design was chosen purposefully, and still looks nice.   I'm guessing people like this look so that they can see the switch housings?  Especially when they are clear and have leds

Good point, it's hard to tell how big the gap is from pictures, will take a look once stabs arrive and mine ships out

[Fullcream]

Worth the wait.

(Attachment Link)

(Attachment Link)

Beautiful! 
Do you think there is enough room/screw thread to add a small washer between the plate/case mount point so that the keycaps sit slightly below level to the case top?

Finally. I'm not the only one. You probably could slightly lower the plate/pcb with washers but then I imagine the usb port will not line up properly with the hole anymore.

It looks as though the bottom of keycaps may indeed sit flush with the top surface of the case but it's that inner chamfer causing that gap. For me personally the idea of a solid thick case looks so good with absolutely no gap from the bottom of keycaps to the top of the case. The complete opposite of 'floating' design would be nice. Oh well. (that was all just my silly opinion)
Still love everything else about this!.

Btw jchan, I love waiting. You can ship mine last!

[Jason_IRL]

anybody else running into any issues with the PCB?
My arrow key cluster appears to be dead. I checked to make sure I didn't bridge any other contacts (I've also assembled at least 15-20 other keyboards before, so I'm pretty sure its not sloppy work on my end.)

I hope its not a bad PCB. Ideas of things to try? Every other key is recognized in the bootmapper client. It just the arrow cluster.

[delivery]

anybody else running into any issues with the PCB?
My arrow key cluster appears to be dead. I checked to make sure I didn't bridge any other contacts (I've also assembled at least 15-20 other keyboards before, so I'm pretty sure its not sloppy work on my end.)

I hope its not a bad PCB. Ideas of things to try? Every other key is recognized in the bootmapper client. It just the arrow cluster.

Arrows not functioning outside of bootmapper as well or just witin bootmapper?

[Jason_IRL]

anybody else running into any issues with the PCB?
My arrow key cluster appears to be dead. I checked to make sure I didn't bridge any other contacts (I've also assembled at least 15-20 other keyboards before, so I'm pretty sure its not sloppy work on my end.)

I hope its not a bad PCB. Ideas of things to try? Every other key is recognized in the bootmapper client. It just the arrow cluster.

Arrows not functioning outside of bootmapper as well or just witin bootmapper?

arrow keys are not working at all. up arrow is working, but left, right, down are not.
pressing those keys in bootmapper is like no keys are pressed. nothing is recognized by the application.

[delivery]

anybody else running into any issues with the PCB?
My arrow key cluster appears to be dead. I checked to make sure I didn't bridge any other contacts (I've also assembled at least 15-20 other keyboards before, so I'm pretty sure its not sloppy work on my end.)

I hope its not a bad PCB. Ideas of things to try? Every other key is recognized in the bootmapper client. It just the arrow cluster.

Arrows not functioning outside of bootmapper as well or just witin bootmapper?

arrow keys are not working at all. up arrow is working, but left, right, down are not.
pressing those keys in bootmapper is like no keys are pressed. nothing is recognized by the application.

I used to have those problems in bootmapper, only up arrow is working and some other keys wont recognized at all,  so i reset it to default, and never tried reprogramming them again.

If you found out how to fix, plz share!

[Jason_IRL]

anybody else running into any issues with the PCB?
My arrow key cluster appears to be dead. I checked to make sure I didn't bridge any other contacts (I've also assembled at least 15-20 other keyboards before, so I'm pretty sure its not sloppy work on my end.)

I hope its not a bad PCB. Ideas of things to try? Every other key is recognized in the bootmapper client. It just the arrow cluster.

Arrows not functioning outside of bootmapper as well or just witin bootmapper?

arrow keys are not working at all. up arrow is working, but left, right, down are not.
pressing those keys in bootmapper is like no keys are pressed. nothing is recognized by the application.

I used to have those problems in bootmapper, only up arrow is working and some other keys wont recognized at all,  so i reset it to default, and never tried reprogramming them again.

I got it working!

In case anyone else runs into this issue in the future...
I noticed the diodes near those keys did not have as much solder on them as all the other keys.
CAREFULLY adding a little bit more solder to the pads, and making sure everything was connected resolved the issue.

Beautiful board. Thanks Rama and Jchan for making this a reality.

[drgonzo]

Did anyone try to modify the existing underlight modes yet? I'd like to tie certain colours to various key presses. The only reference I found so far was the backlighting matrix for the infinity60.

[forevermadrigal]

Worth the wait.

(Attachment Link)

(Attachment Link)

Ugh, looking so good. Can't wait for my champagne to come rolling through

[frobrox]

I opted for the QMK version, even though I've never used it before, and I'm having some troubles with setting up the build environment.
It keeps failing when adding the driver Microsoft PnP Utility saying: Adding the driver package failed : Invalid INF passed as parameter.

Anything I can or should do about this?

[yokken]

I opted for the QMK version, even though I've never used it before, and I'm having some troubles with setting up the build environment.
It keeps failing when adding the driver Microsoft PnP Utility saying: Adding the driver package failed : Invalid INF passed as parameter.

Anything I can or should do about this?

Well, the INF file is part of the driver. I would try re-downloading it (possible it became corrupted) or try to let Windows decide which driver it wants to use, without you specifying the files/folders with the drivers. Short of that... I would try removing the device through Device Manager, then plug it into a different USB port. Then try the re-downloaded drivers. Any problems beyond this would require more troubleshooting that is tough to do on a forum, but you might as well give it a shot!

[kolashnikov]

I opted for the QMK version, even though I've never used it before, and I'm having some troubles with setting up the build environment.
It keeps failing when adding the driver Microsoft PnP Utility saying: Adding the driver package failed : Invalid INF passed as parameter.

Anything I can or should do about this?

Setting up the build environment? As in, you intend to modify and/or build the firmware from source? Does the PCB not come with a default map already flashed?

I have personally been frustrated with Windows as a development environment so take this with a grain of salt, but I'd set up the build environment in Linux if that's what you're trying to do. You could install Ubuntu on a bootable flash drive and work off of that.

[fine_italian_leather]

You could install Ubuntu on a bootable flash drive and work off of that.

Or use virtualbox.

[drgonzo]

Or install the Linux subsystem for windows.

[Gamecat]

I opted for the QMK version, even though I've never used it before, and I'm having some troubles with setting up the build environment.
It keeps failing when adding the driver Microsoft PnP Utility saying: Adding the driver package failed : Invalid INF passed as parameter.

Anything I can or should do about this?

Setting up the build environment? As in, you intend to modify and/or build the firmware from source? Does the PCB not come with a default map already flashed?

I have personally been frustrated with Windows as a development environment so take this with a grain of salt, but I'd set up the build environment in Linux if that's what you're trying to do. You could install Ubuntu on a bootable flash drive and work off of that.

If you have Win 10 this seems to work pretty well (lxrun /install bash or the Ubuntu app if you are on insider build): https://msdn.microsoft.com/en-us/commandline/wsl/install_guide

[frobrox]

I opted for the QMK version, even though I've never used it before, and I'm having some troubles with setting up the build environment.
It keeps failing when adding the driver Microsoft PnP Utility saying: Adding the driver package failed : Invalid INF passed as parameter.

Anything I can or should do about this?

Setting up the build environment? As in, you intend to modify and/or build the firmware from source? Does the PCB not come with a default map already flashed?

I have personally been frustrated with Windows as a development environment so take this with a grain of salt, but I'd set up the build environment in Linux if that's what you're trying to do. You could install Ubuntu on a bootable flash drive and work off of that.

It had worked the first night I had built, with it already being preflashed. And then the next morning, I went to go use it, and no keystroke registered. All I had done in the interim was weigh it on a kitchen scale.

So right now I'm just trying to get it reflashed and working. I had flashed it with a set up TADA 68 hex, but that only has Esc, 1-9 working correctly, and the QWERTY row is all off one key.

I'll see if using a VM will help. Otherwise, I've got an expensive paperweight on my hands.

[duynguyenle]

I opted for the QMK version, even though I've never used it before, and I'm having some troubles with setting up the build environment.
It keeps failing when adding the driver Microsoft PnP Utility saying: Adding the driver package failed : Invalid INF passed as parameter.

Anything I can or should do about this?

Setting up the build environment? As in, you intend to modify and/or build the firmware from source? Does the PCB not come with a default map already flashed?

I have personally been frustrated with Windows as a development environment so take this with a grain of salt, but I'd set up the build environment in Linux if that's what you're trying to do. You could install Ubuntu on a bootable flash drive and work off of that.

It had worked the first night I had built, with it already being preflashed. And then the next morning, I went to go use it, and no keystroke registered. All I had done in the interim was weigh it on a kitchen scale.

So right now I'm just trying to get it reflashed and working. I had flashed it with a set up TADA 68 hex, but that only has Esc, 1-9 working correctly, and the QWERTY row is all off one key.

I'll see if using a VM will help. Otherwise, I've got an expensive paperweight on my hands.

Do you mean you actually flashed it with a Hex generated by the TADA online keymapper (or generated using QMK's TADA68 repository)? Because I don't think the two PCBs are compatible in terms of row and column layout

[BAS1C]

Finishing up the customs clearance. It should be here Monday 

Hey Jchan, so if one opted out of stabs for quicker shipping, and stabs are there tomorrow but order hasn't shipped yet, will one be receiving stabs?

[obviouslygene]

i made the mistake of not having a keycap set on hand...
cant use it at all

[frobrox]

I opted for the QMK version, even though I've never used it before, and I'm having some troubles with setting up the build environment.
It keeps failing when adding the driver Microsoft PnP Utility saying: Adding the driver package failed : Invalid INF passed as parameter.

Anything I can or should do about this?

Setting up the build environment? As in, you intend to modify and/or build the firmware from source? Does the PCB not come with a default map already flashed?

I have personally been frustrated with Windows as a development environment so take this with a grain of salt, but I'd set up the build environment in Linux if that's what you're trying to do. You could install Ubuntu on a bootable flash drive and work off of that.

It had worked the first night I had built, with it already being preflashed. And then the next morning, I went to go use it, and no keystroke registered. All I had done in the interim was weigh it on a kitchen scale.

So right now I'm just trying to get it reflashed and working. I had flashed it with a set up TADA 68 hex, but that only has Esc, 1-9 working correctly, and the QWERTY row is all off one key.

I'll see if using a VM will help. Otherwise, I've got an expensive paperweight on my hands.

Do you mean you actually flashed it with a Hex generated by the TADA online keymapper (or generated using QMK's TADA68 repository)? Because I don't think the two PCBs are compatible in terms of row and column layout

Oh, I definitely realized that after I flashed it. I guess I've gotta just keep at it, or see if there's anyone out there with the same layout of M65-A, and see if I can get their hex file.

[lordzebu]

Oh, I definitely realized that after I flashed it. I guess I've gotta just keep at it, or see if there's anyone out there with the same layout of M65-A, and see if I can get their hex file.

I followed these instructions to set up the build environment on win 10 and had no problems at all. In the jc65 repository you'll find 2 ready to use keymaps. From there you can compile the hex file for flashing using either one or make your own keymap. This one here helped as well.