Status of Sensoft Vision
Applies to
Sensoft Vision 2.2 and later
Specifications of Status
Status of Sensoft Vision is an indicator how the Sensoft Vision software is running, e.g. if it is able to perform measurements, and if not, which problems are preventing it. Status is published every 5 s to the OPC UA variable From Sensoft.Status, a UInt32 value.
The values are 0: Not running, 1: Running and ok, ≥ 2: Running with problems. The bits of the variable Status codify which problems the software has:
| Status bit | Problem | Description |
| 0 | No problem | Running, no problem. If this status bit is 1, all others are 0. If all status bits are 0 (i.e. Status = 0), Sensoft Vision is not running. |
| 1 | Camera: Overload | The system is struggling retrieving the photos of the defects, because there have been many defects in a short time. The system can continue measuring, but the next few defects may have no photo. |
| 2 | Camera: Connection loss | A camera that worked, cannot be reached anymore. |
| 3 | Camera: Error | A generic error involving a camera |
| 4 | Camera: No 2nd cam | The system is configured for two cameras, but only one of them is working. The system can measure, using the one working camera. |
| 5 | Camera: None | No camera was found. The system can measure, but cannot take photos of the defects. |
| 6 | More than 6 criteria | Sensoft Vision support only up to 6 criteria. User tried to add more. |
| 7 | Dialog window | A dialog window is open that does not block measurement start by OPC UA. |
| 8 | OPC UA: Retry | No connection to OPC UA server. Sensoft is client and will retry to connect every 5 s. |
| 9 | OPC UA: Error | No connection to OPC UA server. A user intervention is necessary. |
| 10 .. 15 | NA | Reserved for future use. |
| 16 | Focusing | The system is in Focusing mode, i.e. showing live video. |
| 17 | Factory config | The system is still unconfigured. Please load or create the correct configuration. |
| 18 | Calibration file missing | The calibration file for one of your sensors could not be found on disk. |
| 19 | Data folder not writable | The data folder is set on page Settings. This user account has to have write permission to that folder in order to measure. |
| 20 | RT: SV or NS error | At the specified IP address there is a system that responds to ping, but not to Shared Variables and/or Network Stream. The Sensystem could be still booting, or it could be another device. |
| 21 | RT: Set to PC's IP | The value of the Sensystem IP address field on page Settings is set to the IP address of the PC. Please set it to the IP address of the Sensystem box instead. |
| 22 | RT: Wrong version | The software on the Sensystem has the wrong version. The user was asked if he wanted to put the correct software and has chosen not to. |
| 23 | RT: Not on PC's subnet | The IP addresses of the PC and Sensystem are not on the same subnet. They cannot communicate. The details are given in the warning dialog that appears at the change of the IP address field on page Settings. |
| 24 | Error: Unhandled | A generic error that requires a reinitialization or closing of Sensoft. |
| 25 | Corrupt TDMS | Corrupt TDMS file (spool or report). Automatically corrected by defragging. |
| 26 .. 28 | NA | Reserved for future use. |
| 29 | RT: No ping | Cannot connect to the Sensystem (not even a ping), although an IP address or host name for the Sensystem is given. |
| 30 | RT: IP empty | The field IP address on page Settings is empty. For measuring, it must contain the IP address of the Sensystem. |
| 31 | Blocking dialog window | A dialog window is open that blocks measurement start. |
Example: The value of Status is decimal 327'680. In binary therefore Status = 00000000 00000101 00000000 00000000, i.e. the bit 16 and bit 18 are True. The software thus has two "problems", Problem 16 (it is in focusing mode, i.e. showing live video) and Problem 18 (a calibration file was not found).
Problems with status bit less than 16 allow measurements, problems with status bit ≥ 16 block measurements. In the previous example, with Status = 327'680, one would not be able to start a measurement. Upon clicking on the Start button a dialog would appear to indicate one of the problems (the one with the highest bit). For debugging purposes you can also see the list of problems in Sensoft Vision, by clicking Ctrl - D and going to the newly appeared Debug tab.
Warning by dialog box
When there is a problem that requires user action, Sensoft Vision by default displays by a dialog window explaining the problem. Many dialogs are 1-button OK messages, others ask the user for a choice. All of them are by default also logged to the Windows Event Log. Therefore there is the option to disable the dialog for the 1-button OK messages. This is done by changing the line
Sensoft.Show dialog = "TRUE"
in the configuration file or by using Ctrl - D in Sensoft to change it on the Debug page.
Logging
Sensoft Vision can write log entries to the Windows Event Log. The log entries are mostly equal to the dialog messages, but at times log also events that the user is not notified, e.g. if a corrupt TDMS file is automatically corrected. There is the option to disable the logging by changing the line
Sensoft.Log = "TRUE"
in the configuration file or by using Ctrl - D in Sensoft to change it on the Debug page.
View the log with Event Viewer
To view the log:
- Open the Event Viewer of Windows
- The first time, Create Custom view...
- In the field Event logs: click on Window Logs and then on Application
- In the field Event sources: Click on National Instruments Software
- Click OK, give a Name, e.g. Sensoft, and click OK
- In the left pane, click on your Custom View (step 4. in Figure 1)
- In the center pane, click on an event. The content will be shown in the lower part.
Save and send the log
If you want to send us a log:
- Open the Event Viewer
- Click with the right mouse button on the custom view Sensoft, and select Save All Events in Custom View As... Click Save and then OK
- Send us the .evtx file, best to Daniel Haertle.