Does anyone know anything about the “CAD66” BLE PCB that’s compatible with the CA66? Saw some pictures on Reddit but don’t know where to get one.

A tiny little bit, it's a dual mode replacement pcb that is bluetooth enabled and USB capable, replaces the LED strip with an LED matrix that is individually addressable, and is Alps comptible. the original group buy came with a pcb, carbon fiber replacement plate (to allow signal transmission), and a battery. original group buy was on taobao, and is over. there may be another buy in the near future...

Sad news- add me to the growing list of people with a bricked PCB. Here’s what happened and what I’ve tried:

1 - use CA66 happily for a couple of months,2 - watching full screen video on desktop computer running Windows 10, 3 - hear USB disconnect sound, lights on CA66 turn on and are all white (I had them turned off previously, they only lit when holding the function key) 4 - error message, "The last USB device you connected to this computer malfunctioned, and Windows does not recognize it."5 - each time I plug into a different computer I get the same error message,6 - attempt to re-flash with eeprom reset and ca66 hex files. Hold down “ESC” and plug in, no error message, but both boot loader and QMK toolbox software are unable to find a device to flash

Has anyone found a workaround or discovered the cause? I hope others can avoid these issues if we are able the identify what is going wrong.

Finally came around to build the CA66 and it really is super nice and beautiful! I will post pictures soon, want to customize a little first (since I just now finished it). Question: I want to "port" the board to QMK. But since I'm a beginner still with QMK, I wonder if the default TMK file is somewhere available for download? Or can I somehow download the Hex file from the keyboard? Just in case something is going wrong.One other thing: I built it with split spacebar and am using SA keycaps and I have the problem that the "right" spacebar (2.75U) is sometimes slightly touching the case. It's not too bad, but it doesn't feel all that well. Anyone with the same setup and problem?

Finally came around to build the CA66 and it really is super nice and beautiful! I will post pictures soon, want to customize a little first (since I just now finished it). Question: I want to "port" the board to QMK. But since I'm a beginner still with QMK, I wonder if the default TMK file is somewhere available for download? Or can I somehow download the Hex file from the keyboard? Just in case something is going wrong.One other thing: I built it with split spacebar and am using SA keycaps and I have the problem that the "right" spacebar (2.75U) is sometimes slightly touching the case. It's not too bad, but it doesn't feel all that well. Anyone with the same setup and problem?

Finally came around to build the CA66 and it really is super nice and beautiful! I will post pictures soon, want to customize a little first (since I just now finished it). Question: I want to "port" the board to QMK. But since I'm a beginner still with QMK, I wonder if the default TMK file is somewhere available for download? Or can I somehow download the Hex file from the keyboard? Just in case something is going wrong.One other thing: I built it with split spacebar and am using SA keycaps and I have the problem that the "right" spacebar (2.75U) is sometimes slightly touching the case. It's not too bad, but it doesn't feel all that well. Anyone with the same setup and problem?

Ah sorry, I used the wrong word ofc. What I meant was the bootloader thing: Don‘t I have to do something with it to be able to use QMK? I read something a few pages back, but I might not have read this correctly..

Finally came around to build the CA66 and it really is super nice and beautiful! I will post pictures soon, want to customize a little first (since I just now finished it). Question: I want to "port" the board to QMK. But since I'm a beginner still with QMK, I wonder if the default TMK file is somewhere available for download? Or can I somehow download the Hex file from the keyboard? Just in case something is going wrong.One other thing: I built it with split spacebar and am using SA keycaps and I have the problem that the "right" spacebar (2.75U) is sometimes slightly touching the case. It's not too bad, but it doesn't feel all that well. Anyone with the same setup and problem?

Ah sorry, I used the wrong word ofc. What I meant was the bootloader thing: Don‘t I have to do something with it to be able to use QMK? I read something a few pages back, but I might not have read this correctly..

No worries, go the first post >FEATURES OF PCB> Flashing Guide. Choose either Mac/Windows and that'll have all the info you need. All you need is a hex file.

If you don't have know how to compile a hex someone might be able to pass one along. Are you familiar with compiling?

Edit: Actually QMK configurator has the ca66 so you should just be able to use that:)

Sad news- add me to the growing list of people with a bricked PCB. Here’s what happened and what I’ve tried:

1 - use CA66 happily for a couple of months,2 - watching full screen video on desktop computer running Windows 10, 3 - hear USB disconnect sound, lights on CA66 turn on and are all white (I had them turned off previously, they only lit when holding the function key) 4 - error message, "The last USB device you connected to this computer malfunctioned, and Windows does not recognize it."5 - each time I plug into a different computer I get the same error message,6 - attempt to re-flash with eeprom reset and ca66 hex files. Hold down “ESC” and plug in, no error message, but both boot loader and QMK toolbox software are unable to find a device to flash

Has anyone found a workaround or discovered the cause? I hope others can avoid these issues if we are able the identify what is going wrong.

Same here. I have a second PCB, but I'm hesitant to build it up now unless the source for the problem is figured out. I don't want to brick another PCB.

I have had this happen to me, but I was able to recover the board by reflashing the firmware. Windows showed an error that a device (the keyboard) was using too much power. This makes me believe that the failure was due to a bad USB-C cable.

I have had this happen to me, but I was able to recover the board by reflashing the firmware. Windows showed an error that a device (the keyboard) was using too much power. This makes me believe that the failure was due to a bad USB-C cable.

that's a good guess. a bad cable can definitely fry an input device. i had a bad micro-usb fry my intuos tablet.