Interrupts, Interrupts, and more Interrupts!

[dcbrown]

Originally Posted by Kevin Sevcik

It might be nice to warn people trying this that all their operations on the data received from GetData() and sent to PutData() need to be atomic.

All rx/tx data fields are byte sized and therefore access to each field is atomic by default.

[Alan Anderson]

Originally Posted by dcbrown

All rx/tx data fields are byte sized and therefore access to each field is atomic by default.

Right, but the entire data structure is not. Look at how the IFI default code works -- it treats some of the PWM outputs as temporary locations before finishing the single-joystick mixing. This works fine when the get/put is done explicitly. If you have a need to coordinate values, you have to consider the possibility that the EasyC magic communication might happen when you've started setting them but haven't completed setting them all.

[ManicMechanic]

New question related to interrupts. I use EasyCv2 for Vex and would like to know how to read the values of the 6 interrupt ports (similar to the way that you use GetDigitalInput(I) to read one of the digital input ports). Basically, I want to create something similar to the FVC/FTC competition template but not be limited by the 20 second/2 minute demarcations of the template the way it currently exists.

[dcbrown]

Originally Posted by Alan Anderson

Right, but the entire data structure is not. Look at how the IFI default code works -- it treats some of the PWM outputs as temporary locations before finishing the single-joystick mixing. This works fine when the get/put is done explicitly. If you have a need to coordinate values, you have to consider the possibility that the EasyC magic communication might happen when you've started setting them but haven't completed setting them all.

I keep forgetting about that. Doing stuff like that is just so foriegn to me, that is the rxdata as recieved data is "read only" in my mind.