search

FRC2706 / 2017-2706-Robot-Code

The main robot code for our 2017 Steamworks robot.
3 stars 3 forks source link

Data logging during events? #60

Open kevlam2706 opened 7 years ago

kevlam2706 commented 7 years ago

At some point (not for Toronto) it would be good to investigate how to strap an event logger to our code. Other teams do this (according to forum chatter) so it is definitely possible.

It would be nice to be able to review the system logs to determine sensor data. For example, understanding why autonomous modes did or didn't work, whether (and when) the vision system is detecting targets, what the ultrasonics and IRs are measuring, etc.

Questions I would love to have answered by going over match data logs:

A data logger on the driver station would be the easiest since that's where you'll want to keep logs for later review. You could have the RoboRio dumping logs directly onto its file system but that doesn't seem ideal to me.

georgetzavelas commented 7 years ago

Good idea @greyingjay Would this involve an application listening on a port and then logging packets sent to it? Is tshark too generic?

kevlam2706 commented 7 years ago

I have a suspicion that FRC/wpilib/driver station already provides some kind of framework, we just need to figure out how it works. I would be very surprised and disappointed if Smart Dashboard and Live Window didn't come with some kind of logging.

ryanlarkin commented 7 years ago

In Java Smart Dashboard, there's an option to log values to a file, and in Labview Smart Dashboard, there is a way to view log files, but I don't know what's saved there

ryanlarkin commented 7 years ago

@georgetzavelas, I took out some of the RIOLog code, and made it print all the output, and it works on Mergius but not our practice bot (probably something that was configured when the robot was first imaged).

georgetzavelas commented 7 years ago

@eandr127 that's good to know, thanks!