|
Re: Running GRIP Generated Code on Roborio
In general. I should note that running vision code on the roborio is resource intensive since it's basically pegging a CPU core, which basically precludes you from running another resource-intensive thread.
The latency estimate I gave was very pessimistic (assumed 100ms response time for NetworkTables and a slow image stream). Again, the actual processing only takes about 12ms for me, with all other latencies being due to the network.
The best solution would be to use a coprocessor for doing vision, if you can.
__________________
WPILib
GRIP, RobotBuilder
Last edited by SamCarlberg : 09-02-2017 at 00:12.
|