[Kruuzr]

Originally Posted by BradAMiller

You caught me! I just put up a new version with the function definition included in the BuiltIns.h file.

There are a few functions in WPILib which are hard for programmers to use, but easy for EasyC to automatically generate. These are two of those functions.

The function:

InitializeCamera(CameraInitializationData *c);

that you can call passing the address of the camera initialization structure. This is probably easiest for you to use. The other function:

InitCamera(unsigned char cameraInitIndex);

was intended for EasyC. It assumes that there is an array of those structs and the argument is the index to the one you want to use.

My suggestion is to initialize a structure with the camera parameters you want to use and call InitializeCamera. It's actually called from inside of InitCamera anyway.

The other functions to use the camera data are:

CaptureTrackingData(...) - this is the one you described

and

TPacket *CopyTrackingData(void);

Is the function that I intended hand-coding programmers to use. This returns a pointer to a static structure containing a TPacket inside of WPILib. When you call the function, it turns off interrupts, grabs the most recent packet, and puts it into the static structure - then returns its address.

Then you can write code like this:

TPacket t = CopyTrackingData();
conf = t->confidence;

which seemed to be pretty convenient.

Thanks for the info Brad...
I think the time lag between coding and documentation is a law of physics.

Steve