I got my CBT quite a few months ago. When it didn't work right away I put it aside until I had time to figure out what's going on. Now's the time, but I need some help.

When I plug in, it does not enumerate. I've now removed it from the box so I have access to what I assume is the reset button.

When I press the reset button. It enumerates and ttyACM0 shows up for a few seconds then disappears.
Here is my kernel log.
<code>Oct 6 12:42:20 gaussMint kernel: [71445.648891] usb 3-6: new full-speed USB device number 62 using xhci_hcd
Oct 6 12:42:20 gaussMint kernel: [71445.778199] usb 3-6: New USB device found, idVendor=2341, idProduct=0036
Oct 6 12:42:20 gaussMint kernel: [71445.778204] usb 3-6: New USB device strings: Mfr=2, Product=1, SerialNumber=0
Oct 6 12:42:20 gaussMint kernel: [71445.778206] usb 3-6: Product: CANBus Triple
Oct 6 12:42:20 gaussMint kernel: [71445.778208] usb 3-6: Manufacturer: The FDB
Oct 6 12:42:20 gaussMint kernel: [71445.778379] usb 3-6: ep 0x82 - rounding interval to 1024 microframes, ep desc says 2040 microframes
Oct 6 12:42:20 gaussMint kernel: [71445.778754] cdc_acm 3-6:1.0: ttyACM0: USB ACM device
Oct 6 12:42:28 gaussMint kernel: [71453.438967] usb 3-6: USB disconnect, device number 62
</code>

On this thread: http://forum.canb.us/discussion/57/basic-problems-with-start-up/p1 , Derek mentions that the bootloader will run and disconnect ... I assume this is what I'm seeing, but he also says that mail sketch will run and enumerate ... I don't think I'm seeing this.

Suggestions?

Thanks.

Update: on a different usb port, this is the log file output:
<code>Oct 6 16:00:31 gaussMint kernel: [83332.856036] usb 3-12: new full-speed USB device number 74 using xhci_hcd
Oct 6 16:00:31 gaussMint kernel: [83332.985458] usb 3-12: New USB device found, idVendor=2341, idProduct=0036
Oct 6 16:00:31 gaussMint kernel: [83332.985464] usb 3-12: New USB device strings: Mfr=2, Product=1, SerialNumber=0
Oct 6 16:00:31 gaussMint kernel: [83332.985468] usb 3-12: Product: CANBus Triple
Oct 6 16:00:31 gaussMint kernel: [83332.985471] usb 3-12: Manufacturer: The FDB
Oct 6 16:00:31 gaussMint kernel: [83332.985752] usb 3-12: ep 0x82 - rounding interval to 1024 microframes, ep desc says 2040 microframes
Oct 6 16:00:31 gaussMint kernel: [83332.986189] cdc_acm 3-12:1.0: ttyACM0: USB ACM device
Oct 6 16:00:39 gaussMint kernel: [83340.648078] usb 3-12: USB disconnect, device number 74
Oct 6 16:00:39 gaussMint kernel: [83340.917103] usb 3-12: new full-speed USB device number 75 using xhci_hcd
Oct 6 16:00:40 gaussMint kernel: [83341.029049] usb 3-12: device descriptor read/64, error -71
Oct 6 16:00:40 gaussMint kernel: [83341.244940] usb 3-12: device descriptor read/64, error -71
Oct 6 16:00:40 gaussMint kernel: [83341.460865] usb 3-12: new full-speed USB device number 76 using xhci_hcd
Oct 6 16:00:40 gaussMint kernel: [83341.572846] usb 3-12: device descriptor read/64, error -71
Oct 6 16:00:40 gaussMint kernel: [83341.788784] usb 3-12: device descriptor read/64, error -71
Oct 6 16:00:41 gaussMint kernel: [83342.004650] usb 3-12: new full-speed USB device number 77 using xhci_hcd
Oct 6 16:00:41 gaussMint kernel: [83342.004783] usb 3-12: Device not responding to setup address.
Oct 6 16:00:41 gaussMint kernel: [83342.208676] usb 3-12: Device not responding to setup address.
Oct 6 16:00:41 gaussMint kernel: [83342.412497] usb 3-12: device not accepting address 77, error -71
Oct 6 16:00:41 gaussMint kernel: [83342.524464] usb 3-12: new full-speed USB device number 78 using xhci_hcd
Oct 6 16:00:41 gaussMint kernel: [83342.524596] usb 3-12: Device not responding to setup address.
Oct 6 16:00:41 gaussMint kernel: [83342.728498] usb 3-12: Device not responding to setup address.
Oct 6 16:00:41 gaussMint kernel: [83342.932310] usb 3-12: device not accepting address 78, error -71
Oct 6 16:00:41 gaussMint kernel: [83342.932339] usb usb3-port12: unable to enumerate USB device
</code>

The most common diagnosis seems to indicate that this error:
<code>Oct 6 16:00:40 gaussMint kernel: [83341.029049] usb 3-12: device descriptor read/64, error -71</code>
is caused by too much power used by a usb device.
Is anyone else having power issues with the CBT?

Try another USB cable and report back, I'm willing to be you got a bad one. :(

I just tried 4 different cables on 2 computers (one with USB2 the other with USB3) with same results on all of them.

I am in a similar situation of yours. Did you found any solution?

My CBT blinks the blue LED once and then nothing. I tried the reset button without success.

Thanks.

Derek sent me a replacement which worked without any of the issues I had with the original one.

If you look at the /var/log/kern.log file after you have plugged in your device and have a look at the messages you might get some hints. If you post the relevant lines to this forum, I can try to help.

My solution.
I installed the bootloader with an USBtinyISP and now I can see the CBT.

I bricked mine into this state once somehow. What worked for me (on Debian):
1.) Download firmware from git (I used 0.6.0)
2.) Loaded it into the Arduino IDE, did a compile to make sure everything worked.
3.) Had it plugged in, had the right settings enabled.
4.) Hit the reset button and immediately hit compile/upload.

Seems to work, but you have at most a few seconds to get that upload going.

I've seen the bootloader get lost under low power situations, even tho it is rare. If this ever does happen I will gladly reflash your device if you don't have the hardware available to do it yourself.

LightningRod did indeed have a corrupt bootloader somehow.