|
|
|
![]() |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
Logging
Is there a best practices for logging in LabVIEW?
The robot is a very busy system, and as we add more functionality (PID, State machines, State machines reacting to other state machines, etc) the complexity of debugging increases dramatically. Ideally, I'd like to be able to turn the robot on, operate it for a while, turn it off - and then be able to read from some file that can "tell a story" about what happened: TimeStamp1 - Autonomous Invoked TimeStamp2 - Entering Autonomous_RaiseArm TimeStamp3 - Arm Target changed to HighMiddlePeg TimeStamp4 - Arm raised to target height (HighMiddlePeg) TimeStamp5 - Entering Autonomous_DriveForward TimeStamp6 ...... Is there already a framework in LabVIEW I can use to do this? Have other teams implemented something similar? |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|