Status of Sensoft Multiline
Applies to
Sensoft Multiline 2.4 and later
Specifications of Status
Status of Sensoft Multiline is an indicator how the Sensoft Multiline 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 | NA | Reserved for future use. |
| 2 | Camera: Connection loss | A camera that worked, cannot be reached anymore. It will be reconnected automatically when it can be reached again. |
| 3 | Camera: Error | A generic error involving a camera, raised at camera initialization. Usually because a camera is already used by another process. |
| 4 | Camera: Not all | The system is configured for two cameras, but only one of them is working. The system can measure, using the one working camera. The other will be connected automatically when it becomes possible. |
| 5 | NA | Reserved for future use. |
| 6 | Error: Handled, log only | A handled error: No dialog is shown, but the error is logged to the Windows Event log. This status bit is always False, as the error is already handled. |
| 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 | (Not implemented yet) 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 | Device name missing | The USB device name specified in the configuration does not exist on the pc. Open Hardware settings and set another Device name. |
| 21 | Data rate too high for DAQ | The total data rate, i.e. Data rate [Hz]*Active sensors*Axes, is too high for this Sensystem. |
| 22 | Data rate too high for Lump | Data rate [Hz] is too high for Lump, Neck-down, LU x and LU y, at the current velocity. Defects using these signals can be missed. |
| 23 | USB device disconnected | The most common cause for this is that the USB cable has a connector which is too loose, intermittently disconnecting and reconnecting the USB connection. Remedies: 1) Clean the plugs of USB cable with compressed air. 2) Connect to a different USB socket on the PC. 3) Replace the USB cable. |
| 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 .. 30 | NA | Reserved for future use. |
| 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 Multiline, 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 Multiline 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
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
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.