How to turn off automatic error logging in LabVIEW

[Doug Norman]

In LabVIEW, FRC errors are automatically logged to a file on the robot at c:\WPI_Error.txt. This is the file that you see when you click "View Log File..." on the Driver Station. If you have not configured a Cypress board for Enhanced I/O, you may be getting errors constantly logged to file. This could affect the loop rates for Teleop etc. If you think this may be a problem, you can turn off the automatic error logging. It is easy to turn off, because it is controlled by a global variable.

To turn off error logging:

1. From your project, open the Begin.vi and switch to its diagram.

2. Click back on your project, then type Ctrl-F to bring up the Find Project Items dialog.

3. Type ErrorsGlobal into the dialog and hit Enter – it should highlight the ErrorsGlobal.vi in your project.

4. Drag ErrorsGlobal.vi from your project to the diagram of Begin.vi

5. It should drop on the diagram as "log errors to file?". If it does not, click on it and choose "log errors to file?"

6. This is a global variable. Wire a FALSE constant to it. To do this you can right-click on the terminal (along the left hand side) and choose Create>>Constant. Click on the T/F constant to change it from T to F.

The way this works is that when your Begin.vi runs, the global will be set to FALSE. Then down inside FRC error VIs the global is read. If an error occurs and the global is FALSE, nothing is written to the WPI_Error.txt file. Only FRC Errors from wired error terminals get logged. In our testing, the constant logging did not detrimentally affect our loop rates. However, if you have a lot of I/O happening in your loop, this might make a difference.

[mbone206]

Hi All

I am trying to access ErrorsGlobal as defined in this thread, search Find Projects Items... does not find it...

Anyone else have another way I can access this VI

BTW: I tried opening brand new project, Ctr F, search did not find it also

thanx
Mark

[Greg McKaskle]

That is a pretty old thread.

If you open RobotMain and locate the subVI StartCommunications. Open it and look to the left side of the diagram. You will see a label comment about init error logging. It passes in a constant of T for file logging in order to open the file. If you right click on the icon and choose to Find All Instances, you should find three. The one responsible for handling most is the ErrorManagementHandleRuntimeErrors, and it passes in no parameter, defaulting to FALSE, not logging the error.

Verify that this is the way your system looks.

Greg McKaskle

[mbone206]

Hi Greg

I right click and Find All Instances, there are 2 not 3.

1 FPGA_ErrorManagementHandleRuntimeErrors.vi
2 WPI_DriverStationStart Communication.vi


I opened _ErrorManagement, there is a label to VI ---
'always send to Driver Station when auto error handling'
That has a constant TRUE going into VI (send to driver station)..

Is this what should be set to FALSE?

That would mean default is TRUE since I did not change this when started a new project?

Thanx
Mark

[Greg McKaskle]

That VI takes two Booleans I think. One for file logging on the cRIO, and one for sending to the cRIO Dianostics window. I think the default for cRIO logging is false, but you can right click and reinit to default to make sure, and you can wire a constant if you like.

Greg Mckaskle