Quote:
Originally Posted by vinnie
Thanks for the replies. I didn't even think of something that sophisticated. However we are going to make our own DS and a networking library to read the data from the DS. So I was thinking like a microcontroller with serial communication? (the Happs interface definitely looks interesting and I will look at it more but I'm not entirely sure how I would implement it. Have you used it before?) Also, does anyone have suggestions for a networking framework for our custom dashboard? I was looking at OSC ( http://www.opensoundcontrol.org) or just straight TCP. Any recommendations? Things you've used in the past? |
As Alan stated, everything has to go through the provided DS app in competition.
That being said, if you are still interested in hacking up a custom control protocol, I would say go for it. FRC doesn't really expose students to network programming, so this could be a cool little project.
OSC would work fine for this (it's just a fancy layer on top of UDP). I would not reccomend using a TCP stream to drive the robot. Basically, it turns out TCP is pretty good at delivering data reliably, with the cost of reduced speed. UDP is quicker, with the cost of possible data loss. I'll leave it up to you to figure out why both of these things are bad, but one is worse than the other in terms of driving something real time.