[Mike Copioli]

Originally Posted by jwakeman

I tried through the web dash today and it also did not work. It said it did not receive an Ack.

I still had the BDC-comm from last year and I was able to update the firmware using that version of BDC-comm and the serial interface. The old version of the firmware that was on the troublesome jag was 8161 (not 8181). Now that all my jags are updated to v107 of the firmware everything is working great!

Oh boy, It sounds like your problem was the dreaded 500 kbps bug. Basically if you update a jag over CAN and the firmware does not boot-load correctly(corrupted, poor CAN cable connection). The Jag gets stuck in boot loader and sometimes enters the CAN bus off state, thus causing your did not receive ack error. The recommended procedure is to power cycle the Jag thus rebooting the device and enabling the CAN controller. However for some reason on last years version of the Black Jag and I suspect all recent versions, the device changes it's CAN bit rate to 500 Kbps. The device then appears to be "bricked"(no led). The 2CAN's default bit rate is 1 Mbps, if you try to boot load Jag firmware in this state you will also receive a did not get ack message.

There are two remedies for this:

1. Change the 2CAN's bitrate to 500 kbps, flash the update, power cycle the jag and then switch the 2CAN back to 1 Meg.

2. Or update the firmware using the serial interface.

The second option works because the serial bit rate is not affected by this bug.

Also the CAN controller BUS off state is addressed in version 100 and newer of the FRC Jaguar firmware but is not addressed in in any non FRC version of firmware. You can reproduce the problem for yourself by shorting CAN high and CAN low together several times until the Jag stops communication over CAN (flashing orange LED).