Is the code that is on the master microprocessor (not the user one) in the RC included somewhere in the FRC default code (ie is it possible for me to look at and then change appropriately for my needs?)
Nope. This would be a safety hazard as then teams could modify the behavior of the master processor which is what controls things like shutting down the robot when it’s disabled, etc.
does anyone here then have a general idea of what it does and then i could jsut make it up myself. i’m not using it to change the RC i’m using it to migrate code i wrote for the RC to another PIC device.
What are you trying to do that only the master processor does? All it really does is handle the data that is coming over the radio and pass it on to the user in formatted packets and then take packets from the user and send them over the radio. It also enables/disables the user and sets the autonomous mode, but that’s only for competition.
thank you, that’s all i needed to know. that it really does nothing other than control some things i’m not interested in and all the code i really need to get a PIC working is in the FRC stuff (i just have to change it all)
Thanks
however there are a lot of function prototypes in the start up file (ifi_startup) that i can’t find code for ie the ifi_intialization that apparently “Configures registers and initializes the SPI RX/TX buffers.” which seems important to me
It’s probably just a call to some master RC stuff. (as you assumed) According to what you said, it sets up the registers on the processor, so if you have any low level direct register stuff, you’ll have to fix that, and it initializes the input and output buffers.
What fowlern said is basically correct. The master processor just sits there and receives all outside data. (from sensors, controls, etc) It then handles if appropriate (for instance, the disable signal) or passes it along to the user processor. For most output, the user proc sends it’s desired info to the master and the master then sets things correctly.
The way it’s setup is great for you because all you have to do is create some wrapper code which takes care of simulating the data transfer between your code and the nonexistent master.
The definitions for those functions are in the IFI library file. Unless you’re going to talk to another device using the SPI bus (the bus IFI uses to link the master with the user) there is no reason to call that function. As far configuring the registers, I’m not sure what all IFI does there, but you should be able to configure the registers you need with your own code.
yea, they could have made it a little easier for me to see what was going on but i figured it out. i’m writing my own now
thanks guys