Quote:
Originally Posted by virtuald
On the driver station, or on the robot? If it's on the driver station.. what address are you listening on? If you're listening on 127.0.0.1, the field setup couldn't interfere. We use localhost:8888 with no issues.
|
We wanted the Robot code to run REST calls with attached JSON data to the webserver on the Driver's Station. We tried DNS names and static IP's. It's for telemetry, not robot control. We followed as much of 1418's setup as we could in getting as far as we did, but Network Tables was the implementation for CHSChamps.
No one on my team uses Python, for better or worse. We have plenty of kids who eventually use it during Cyber stuff, but for FRC stuff we stick to either Java or (eventually) Web. I don't want to get into a language debate - it's just what our team knows and does. I'll check out the links you provided though.
Thanks for the correction on ntcore - some of my info is 2nd-hand since I'm not on the programming team. I took a look at a few things, but it'll take a bit more analysis to figure out where it puts the rate limitation in. If not, maybe next year we'll do something like
Pete Lawrey's OpenHFT and then dump the results to the web server.