Quote:
Originally Posted by Hugh Meyer
How do we get the packet timing? We are using C++.
|
The easiest most efficent way is to just take the summary from the DLink statistics page. At least that's what I prefer to use since the DLink is made to collect that kind of data. It's nice because it's also the point that divides the transmission statistics into wireless (DLink<->field router<->DS) and Ethernet (DLink<->cRIO). We actually get additional results that the FMS logger doesn't have. In the past I've been able to identify a specific bad pin on the cable between the bridge and the cRIO this way.
Either captured by a query script (maybe while disabled after Teleop is over), or just examined via a web browser after a match. To examine it after a match be sure to leave the robot powered to preserve the match data until you can hookup your laptop.
Of course, if your DLink is rebooting then the data does get lost, but at least you'll have proof that it's rebooting.
I'd hesitate to log too much data too quickly on the cRIO, because of the potential for overload
If you're running a more powerful laptop as the driver station, logging the majority of the data back there might have less system impact, as well as being more easily accessable.