Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Programming (http://www.chiefdelphi.com/forums/forumdisplay.php?f=51)
-   -   Dashboard - User Bytes (http://www.chiefdelphi.com/forums/showthread.php?t=46678)

DanDon 18-04-2006 16:10

Dashboard - User Bytes
 
Hi, I noticed that the User Bytes were sent in multiple dashboard frames. Is there any way to utilize this in order to send more information through the dashboard port?

Like, have

User_Byte2 = 5 in the Extended Frame (Frame 2)

and
User_Byte2 = 7 in the Status Frame (Frame 3)

?

Thanks,

BradAMiller 19-04-2006 06:33

Re: Dashboard - User Bytes
 
Quote:

Originally Posted by dhoizner
Hi, I noticed that the User Bytes were sent in multiple dashboard frames. Is there any way to utilize this in order to send more information through the dashboard port?
Thanks,

One way of sending extra information to the dashboard port is to load up all the unused PWM ports with values. If nothing is connected to the RC ports it doesn't seem to matter, but the values get sent.

TimCraig 19-04-2006 19:45

Re: Dashboard - User Bytes
 
Quote:

Originally Posted by BradAMiller
One way of sending extra information to the dashboard port is to load up all the unused PWM ports with values. If nothing is connected to the RC ports it doesn't seem to matter, but the values get sent.

If the PWM output port isn't connected, it won't have any effect on the robot. However, you probably should give a little thought as to how you do this. If you're sending purely arbitrary values in unused PWM bytes and the user bytes, you could end up with additional 0xFF, 0xFF byte pairs that could make your start of frame detection algorithm more complex or unreliable.

BradAMiller 20-04-2006 05:10

Re: Dashboard - User Bytes
 
Quote:

Originally Posted by TimCraig
If the PWM output port isn't connected, it won't have any effect on the robot. However, you probably should give a little thought as to how you do this. If you're sending purely arbitrary values in unused PWM bytes and the user bytes, you could end up with additional 0xFF, 0xFF byte pairs that could make your start of frame detection algorithm more complex or unreliable.

That's a good point. In our case, we were sending things like the camera confidence, and measured speeds from our ball pitcher. They were displayed graphically over a car dashboard, where the PC program turned the rendered dials on the screen. We were careful not to send values that would mess up the framing and in that case it didn't matter if a 254 was send instead of a 255.


All times are GMT -5. The time now is 03:21.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi