Jaguar Non-FRC Firmware

[drakesword]

Originally Posted by Al Skierkiewicz

This is the very reason, for FRC, you have to use the specified code. WE want all robots to stop at the end of a match or when disabled by the field controller.

In that case is there a way I can use the FRC firmware not on the cRio?

There appears to be a set of commands with trust appended to them. I tried useing these commands with FRC firmware 91 but no luck. Do I need to send the trusted heartbeat?

[Al Skierkiewicz]

Bryant,
I would defer to David for any advice on those issues. Clearly, the Jag series of products is intended to have a wider customer base than FIRST.

[dyanoshak]

Originally Posted by drakesword

In that case is there a way I can use the FRC firmware not on the cRio?

There appears to be a set of commands with trust appended to them. I tried useing these commands with FRC firmware 91 but no luck. Do I need to send the trusted heartbeat?

You can only use FRC firmware with the cRIO and/or the FRC version of BDC-COMM.

Yes, a trusted heartbeat is necessary to keep Jags with FRC Firmware alive.

If this project isn't intended for an FRC robot, I would recommend not using the FRC firmware. The source code for regular BDC-COMM and the non-FRC Jag firmware is in the firmware development package you have downloaded. Looking at the BDC-COMM source will help you understand what frames need to go out in order to control the Jaguar in various modes.

I am not sure what is going wrong when you switch to firmware version 91. More details would be nice. What does the Jaguar do when it works? What does it do when it doesn't work? What do you expect it to do and how does it differ? Take note of LED states, motor actions, values read off of the Jaguar, etc.

I have tested version 91 myself using BDC-COMM and I have had no trouble setting up and using the various modes. Since you are using the 2CAN adapter I would try contacting someone from Cross the Road, they might be able to help with their own hardware.

Originally Posted by drakesword

If I had a serial port I would. But cant until I have access to one.

USB to serial adapters are cheap and they work with BDC-COMM. If you happen to have a Vex programming cable laying around, the USB to serial cable works great. You just need to make sure you select the appropriate COM port (other than COM1) when using them.

-David

[drakesword]

I figured out what the problem was.

The firmware I was loading wasn't the proper one. sure it was in the directory but it didn't function. Recompiled but first running the make clean then make and the firmware works properly