Quote:
Originally Posted by virtuald
That sounds like a reasonable flow of operations... If everything was a static IP, that should work... I bet they're blocking outbound connections on 443. Did you try different ports instead of 443?
Also, I misread what you said earlier, I read "4k hz" instead of "4hz". You should be able to get at least 10hz out of ntcore, and 20hz out of pynetworktables. I haven't really benchmarked either of them recently, sounds like something someone could do.
|
Initially the port was
5800, but since it was a web server someone thought it would make a difference to put it on 443. Not sure why 443 over 80, but I wasn't around for that decision so there may be more to it.
Around this time last week someone on the programming team said they clocked Network Tables at 4hz - it matters at the moment since that's how vision sends parameters back to the robot. I'll examine how they benchmarked in more detail then. 10Hz is more palatable for post-match analysis, but in the shop I'd like to bump it higher so we can track some of the sensor outputs better.
Thad, I'll look for the rate to remove it. Thanks for the tip!