This UNC program communicates with the Medoc TSAII through an old Visual Basic 6 Medoc driver called "Shoval32.exe". When starting, this Medoc program attempts to communicate with the TSAII as shown at left.
Once communication has been established the UNC program: TSAII_UNC_2014.exe takes over as seen at right.
| Shoval32.exe reads the initialization file (Options.ini) located in the same folder as itself. From this file it gets, among other things, the thermode size and computer COM port to which the TSAII is supposed to be connected.
The UNC application (TSAII_UNC_2014.exe) also reads this same file to get the same data, some of which is displayed in the "Options" window accessible through the "Tools" menu
| Clicking the OK button will display the "Options" window as shown above right. Clicking the "COM port" combo box will display the list of serial ports currently available on the computer. Should the TSAII port not show on the list, make sure it is connected, give the PC a couple of seconds to re-enumerate the ports, and click the down arrow again.
Select the correct port by clicking on it then click "OK". The message at right will ask you whether you want to run in "Edit" mode. Clicking "No" will save the new COM port ID and Exit the program so it can be restarted with the correct COM port.
|In this case the UNC application starts in "Edit" mode and the Medoc's driver flags the "!!! COMMUNICATION FAILURE !!!" error message.
Unless the intent is to run in "Edit" mode, the normal course of action would be to open the "Options" window through the "Tools" menu, fix the COM port ID problem, and restart the application.
|Most of the time, this error message is caused by other activities on the computer that interfered with the initialization process. Restarting the application is usually the only action necessary.|
2014 February 05
Last updated 2014 February 05