[Kruuzr]

Originally Posted by BradAMiller

That is correct. And in fact, you only need to include the 2 libraries that are on the WPILib web site (unless you have additional libraries of your own). Those two libraries include all the IFI stuff - like ifi_utilities.o, etc.

So you can do these things:

• include the IFI .h files (ifi_aliases.h, ifi_utilities.h, etc.) and write to the PWM, digital I/O, analog (may change in the future - post build season), and relay ports directly.
• Include you own object files that don't change interrupts - except using the WPILib interrupt handling functions

Things you should NOT do:

• Change the interrupt code. There is an interrupt handler built into WPILib and you can get interrupts delivered to your program. Check out the documentation if this is something you need.
• You can't use the hardware timers - currently WPILib is using timer 1 and all the associated interrupt handlers. You could use other timers (without interrupts) for now, but I can't guarantee that this will continue to work in future versions.
• Do not call get_data or put_data or any of the other IFI code to interact with the master processor. This is all done in the background in WPILib and making additional calls of this type will probably break your program.

If you have specific things that you want to do, please let me know and I'll tell you if it is safe.

Brad...
I've just started playing with WPILib (and I love it!!!) but I was hoping to use the dashboard program I've written which utilizes the six user bytes. Are these accessable via WPILib???

Steve