User_Bytes taken over by breakers?

[kwilliam]

Originally Posted by Alan Anderson

The breaker panel feedback isn't hardwired. It was a short bit of code (in Default_Routine(), I believe) in prior years. ... If the default code still refers to it, ignore it.

What made me think it might be hardwired is that it isn't referenced anywhere in the default code. Did they just forget to take the comments out? If that's the case, will I need to add ".allbits" to bytes 3 through 6 like bytes 1 and 2 have?

[seanwitte]

Originally Posted by kwilliam

What made me think it might be hardwired is that it isn't referenced anywhere in the default code. Did they just forget to take the comments out? If that's the case, will I need to add ".allbits" to bytes 3 through 6 like bytes 1 and 2 have?

I haven't looked at the code, but it might be an artifact from last year. The breaker panel sends updates over the serial port, so the code that handled that updated the user bytes. If you're not using the breaker panel code then you should be able to set the user bytes yourself.

[Alan Anderson]

The reference to "allbits" is only on the first two user bytes. I think it's that way because the Dashboard Viewer program can show each individual bit of those two user bytes, and there is an associated bit array in the user byte structure that you can use to set those bytes' bits one at a time if you want to.

Don't worry about it. Just set User_Byte1 through User_Byte6 the way you want, make sure nothing else in Default_Routine() is setting them to something you don't want, and everything should work fine.

[kwilliam]

Thanks! It works great.

	//Send camera data to the Dashboard.
	User_Byte1 = CENTROID_X;
	User_Byte2 = CENTROID_Y;
	User_Byte3 = UPPER_X;
	User_Byte4 = UPPER_Y;
	User_Byte5 = LOWER_X;
	User_Byte6 = LOWER_Y;

(We defined aliases for the camera data.)