<< Click to Display Table of Contents >> Navigation:  User Guide > Handling lost COMMS

 

If for some reason communications to an instrument is lost, SpecView will not automatically 'flag up' these types of issues in an obvious way because instruments can be legitimately switched off for maintenance, etc.

 

So it's up to the designer of the project to get SpecView to do something appropriate.

 

For example, it is possible to put a warning message on the screen (GDW) that that is looked at most often, and use Color Dynamics so that the message is red when BadComms is not equal to zero, and hidden while BadComms was zero.

 

The message would tell the operator to click on a button to go to an 'Admin' screen.

 

The Admin screen would have the same (or similar) message together with the other comms error variables and a button to set BadComms back to zero.

 

Here is an example of what an 'Admin' screen might look like:

 

 

Note: some systems regularly see 'BadComms' increasing - and this should be investigated in full to understand the reason.

 

It is also possible to log the comms variables, but be aware of the logging rate, and hence disk space usage.

 

Also the LineWriter can be used for recording what is happening with Comms.