View Single Post
  #1   Spotlight this post!  
Unread 14-02-2010, 01:42
kamocat's Avatar
kamocat kamocat is offline
Test Engineer
AKA: Marshal Horn
FRC #3213 (Thunder Tech)
Team Role: Mentor
 
Join Date: May 2008
Rookie Year: 2008
Location: Tacoma
Posts: 894
kamocat is just really nicekamocat is just really nicekamocat is just really nicekamocat is just really nicekamocat is just really nice
Send a message via AIM to kamocat Send a message via MSN to kamocat
logging DS messages

Last year I had some trouble in a couple of matches with the robot not having full communication in a couple of matches, and experienced no FMS data to help in diagnostics or in determining the error. (In some instances it was blamed on the code on the robot)

So one of my plans for this year was to create something to log the DS messages when the mode changes (from disabled to auto to teleop), and log the state when a message is not received (also useful in determining the frequency of messages received, and what else was happening when those messages were not received)

So here it is. I haven't fully tested it on the robot, but I've tested the storing part on my computer, so unless I'm making assumptions about the values of the DS message when there's a timeout, it will work. (or if the watchdog refnum name is something other than "watchdog")

"To log or not to log" is the main VI to be placed in that loop in Robot Main; it should be wired up to the "Robot Mode" VI, as demonstrated in the picture below:
Attached Files
File Type: zip comm status.zip (45.2 KB, 28 views)
__________________
-- Marshal Horn