Also helps prevent that port from wearing out from repeated usage. We wrote it purely because it was easier than digging around in the electrical board to unplug the USB drive. It’s not doing anything super fancy, just sequences the unix tools for SSH/SCP to find and copy all the files on the USB drive to the PC. Here’s a python script to get the files off of the roboRIO and onto your local computer. We use these low-profile drives to ensure there’s not a bunch of mass cantilevered off the USB port which might vibrate around, weaken the connection, come loose, etc. These files can get big and the RIO doesn’t have a ton of internal storage (literally, 0.5GB, and a good chunk of that is taken up by the OS). I definitely recommend implementing your csv creation such that it logs to an external USB drive (should mount to /U/ if you plug into the “outside” usb port). Even the mechanical and electrical teams like them - by logging current and voltages and speeds, SW team can often feed them info about loose connectors, hot motors, tight chain, etc. It’s particularly useful for debugging non-reproducible issues that were seen once on the field. The whole reason we log CSV files is to ensure we have detailed performance data for each match. Sorry, probably some more useful followup. How would you use a CSV file in this case?
0 Comments
Leave a Reply. |