MASsoft and ESPsoft set up (continued)
The following information represents experience setting up communications between a Hiden instrument and a PC. Most problems have been found to be due to the set up of the PC, and thus are readily overcome. This is by no means a comprehensive list of all possible problems, but may provide some help. An attempt has been made to link solutions with problems, but some solutions apply to more than one problem, so you are advised to read the whole document if your problem resists a listed solution. Windows can sometimes be a tricky environment to set up (usually it's not), so if you initially get problems, don't worry too much, they can usually be solved fairly easily.
Specific problems - MASsoft or ESPsoft does not launch or gives errors on launch (6 possibilities).
- MASsoft starts up but most of the menu options are grey
- MASsoft starts but will not run a scan.
- MASsoft starts but the Mass Spectrometer is Unavailble
- ESPsoft starts but the instrument is “Not found”
 (you are here - this section covers 6 - 16)
- MASsoft fails to re-interrogate on a serial connection
- MASsoft fails to re-interrogate over a network
- MASsoft gives errors during re-interrogation
- MASsoft starts but gives “Unknown Logical Device” error when run.
- MASsoft or ESPsoft starts but gives “Comm Port Error” dialogue when run.
- MASsoft or ESPsoft starts but gives “Status Change” dialogue when run.
- MASsoft crashes frequently
- MASsoft won't acquire data
- The same Mass Spectrometer appears twice in the "MassSpecs" menu list
- RS232 communication doesn't work.
- LAN communication doesn't work.
- Using MASsoft with Windows 3.1
- Using MASsoft with Windows For Workgroups 3.11
- Using MASsoft with Windows 95
- Using MASsoft with Windows 98
- Using MASsoft with Windows Me ( Millennium Edition )
- Using MASsoft with Windows NT 4.0 or greater
- Windows fails to start up.
- Windows fails to shutdown.
- Gateway Colorbook2 known problems
- MSIU beeps - Toshiba Satelite 1620 CDS Known Problem
- Mitac computers and PCI cards.
- Using MASsoft V 2.3 or earlier with Microsoft Office
6. MASsoft fails to re-interrogate on a serial connection PROBLEM MASsoft fails to re-interrogate on a serial connection
CAUSE #1 The MSIU is switched off
SOLUTION Switch the MSIU on, if it will not switch on then check the fuses.
CAUSE #2 The MSIU is not connected
SOLUTION Ensure that the RS232 cable is connected from the RS232 port on MSIU to COM1 on the PC.
Use the cable provided by Hiden.
CAUSE #3 The MSIU is connected to the wrong Com port
SOLUTION Either connect the RS232 cable to COM1 on your PC or use the Comms Configuration Utility in Hiden Applications group to change the comms port.
CAUSE #4 The serial lead is plugged in to the RS422/RS485 connector.
SOLUTION Both the RS422/RS485 and RS232 connectors are 9 pin D connectors. Do NOT connect to the RS422/RS485 connector, which is in the middle, between the network BNC and the RS232 D connector.
CAUSE #5 The MSIU has new EPROMs whose name does not match the original exactly. This can occur if the EPROMs have been reconfigured to change the instrument type, or if, due to a change in the software used to configure EPROMs, the name differs by even a space.
SOLUTION Use the Comms Configuration Utility to force automatic re-interrogation, then re-start MASsoft.
CAUSE #6 There is a fault in the serial connection
SOLUTION See section 15,“RS232 communication doesn't work”.
[index]
7. MASsoft fails to re-interrogate over a network PROBLEM MASsoft fails to re-interrogate over a network
CAUSE #1 The MSIU is switched off
SOLUTION Switch the MSIU on, if it will not switch on then check the fuses.
CAUSE #2 The MSIU is not connected
SOLUTION Ensure that the network card on the PC is connected by 50 ohm coax to the 10base2 BNC connector on the MSIU. Do not confuse with the SEM HV out connector! Make sure the cable is terminated at both ends with 50ohm terminators.
Obey the Rules for Connecting an Ethernet Local area Network in your Operators Manual.
CAUSE #3 The network address is not correct. This can occur if you have connected the PC to another MSIU, if you installed the demo installation or if you used the wrong System Information floppy disc when you installed.
SOLUTION Use the Comms Configuration Utility to set the correct network address. The network address should be 0248410XXXXX where XXXXX represents the instrument’s 5 digit WR number. The WR number can be found on the serial number plate on the rear of the MSIU. The WR number is beneath the main serial number. If it is a 4 digit number add a leading 0. Then use the Comms Configuration Utility to force automatic re-interrogation and re-start MASsoft.
CAUSE #4 The DLC protocol parameters are not correctly set.
SOLUTION Ensure that the swap and UseDix parameters are set to 0.
CAUSE #5 There is a fault in the network connection
SOLUTION See section 16, "LAN communication doesn't work.”.
[index]
8. MASsoft gives errors during re-interrogation PROBLEM #1 MASsoft hangs during interrogation
CAUSE A communication error has occured during the interrogation.
SOLUTION Test the communication using TTY.EXE or HideNet as in the sections “” and “”
See the sections “” and “” below:- PROBLEM #2 MASsoft gives “Comm Port Error” dialogue during interrogation
CAUSE There are many possible causes of Comm Port errors. The problem is usually caused by the PC failing to keep up with data sent by the MSIU.
This can be caused by: - PC hardware configuration problems
- Virus scanners
- Programs running in the SysTray
- Device driver problems
SOLUTION see the section “”
PROBLEM #3 In Windows for Workgroups 3.11 MASsoft crashes while interrogating the mass spectrometer or as soon as it starts to down-load a scan and displays a message box such as:- *C001* Command Error 1 "Unknown Command" *C003* Command Error 3 "Command Truncated"
CAUSE There may be a problem with the version of COMMS.DRV used by Windows. The RS232 driver supplied with Windows for Workgroups 3.11 and Windows 95 has been found to cause problems when used with MASsoft as it generates a spurious character in the receive buffer when the comms port is opened. (See also the note about Gateway Colorbook2 RS232 link below).
SOLUTION edit the SYSTEM.INI file in the Windows folder. Find the line comm=comm.drv
and change it to read comm=PATH\comm.drv
where PATH is the path to the Hiden MASsoft home folder - normally C:\hiden for MASsoft 3.5.3 ( and for later versions if running on WFW ), or C:\Progra~1\Hidena~1\Common for MASsoft 3.7 or later running on Windows 95 NOTE this problem is fixed within MASsoft itself in the current version. NOTE: Do NOT make this change on Windows 98 - it will cause Comm Port Errors when running MASsoft.
[index]
9. MASsoft starts but gives “Unknown Logical Device” error when run. SYMPTOM #1 You have one ( or both ) of your auxiliary inputs configured as a temperature input, or some other custom configuration.
CAUSE You have opened an old file that still uses inputs auxiliary1 or auxiliary2, these no longer exists.
SOLUTION Re-create the file starting from File New. The new names for the input devices will now appear in the Input Selection dialogue box and this error will no longer occur.
SYMPTOM #2 You have configured your inputs and have been running with them configured for some time. Now when you open and run one of these files you get an Unknown Logical Device error.
CAUSE The MSIU has lost its configuration. This can occur if the unit is switched off for a long time, if the battery is not fully charged or faulty and sometimes if the MSIU crashes.
SOLUTION Re-configure your auxiliary inputs. Either run the aux1conf.exp file ( if provided ) or follow the procedure in the appendix “Configuring the Auxiliary Analogue Inputs” in your Operator’s Manual. Take care to use exactly the same name as before. Names are case dependant. Take care over the use of hyphens - and underscores _ .
SYMPTOM #3 You opened and ran a file
CAUSE The file was created on another instrument, or an older version of the current instrument, with different devices programd into the MSIU firmware.
SOLUTION Use File New to create a file and then run it. If this runs without error then the problem is with the file that you are openning. Files may not run correctly if used on an instrument with a different configuration from the one on which they were created.
SYMPTOM #4 You have just interrogated your MSIU
CAUSE A communication error has corrupted the interrogation.
SOLUTION Test the communication using TTY.EXE or HideNet as in the sections “” and “”
See the sections “” and “” below:- .
[index]
10. MASsoft or ESPsoft starts but gives “Comm Port Error” dialogue when run. PROBLEM MASsoft or ESPsoft starts but gives “Comm Port Error” dialogue when run
CAUSE There are many possible causes of Comm Port errors. The problem is usually caused by the PC failing to keep up with data sent by the MSIU. This can be caused by:
- PC hardware configuration problems
- Virus scanners
- Programs running in the SysTray
- Device driver problems
SOLUTION see the section “” below
[index]
11. MASsoft or ESPsoft starts but gives “Status Change” dialogue when run. PROBLEM You are running on Windows NT and are connected to the MSIU by a network.
MASsoft or ESPsoft starts but gives “Status Change” dialogue with a Status Code of 0040 at some point in a run
CAUSE Windows NT maintains statistics on network communications; it counts messages sent and received, errors etc. When a counter “overflows” it notifies the DLC protocol; when HALDLC32.DLL is notified it displays this message. Note. Status Change messages with other status codes can occur for other reasons. These can indicate a problem with the network ( i.e. very heavy traffic ) or with the configuration of the DLC protocol ( usually timer settings ).
SOLUTION The current version of HALDLC32.DLL now ignores statistics notofications. For an updated version of this file contact Hiden or install the latest version of the Hiden software. The correct version was shipped in CD versions 1.23 and later.
[index]
12. MASsoft crashes frequently SYMPTOM #1 Screen driver causes problems The problems can be anything from strange screen, mouse or keyboard effects to a full Windows crash or loss of functionality
CAUSE Some screen drivers can cause problems during acquisition using MASsoft (and also with other applications!).
SOLUTION install the generic VGA 16 colour driver and see if the problems still persist. If this driver gives better results, then other, more capable drivers from the list in Windows Setup can be tried until a suitable driver is found or the problems recur.
SYMPTOM #2 EMM386 causes problems
CAUSE Under some circumstances using EMM386 (or other expanded memory managers such as QEMM) to load drivers high can cause problems. If the manager does not correctly identify the areas used by I/O cards, it may load a driver into a card's buffer memory (or part of it), and this can cause unpredictable errors which may or may not cause a crash.
SOLUTION edit the file \CONFIG.SYS and temporarily disable the line which loads EMM386 (e.g. place the word "rem" - without the " characters - at the start of the line). Reboot DOS and Windows, and see if the problem(s) still exist. If they have disappeared, you need to locate the I/O card affected, and use the X= option in EMM386 to exclude the memory it uses from the memory manager's permissable range. The line device=EMM386.EXE NOEMS X=D000,DFFF
will cater for many systems. Check also that the EMMExclude entry in the [386Enh] section of your \WINDOWS\SYSTEM.INI file excludes the same addresses as in CONFIG.SYS.
SYMPTOM #3 Not enough file table space in DOS
CAUSE DOS allocates space for the maximum number of files that can be open simultaneously when it boots, using the FILES= command in CONFIG.SYS. If this number is too small, unpredictable errors can occur in Windows. A minimum of 50 should be allocated, more if possible.
SOLUTION edit \CONFIG.SYS and set the FILES= value to at least 50.
[index]
13. MASsoft won't acquire data PROBLEM If the Inhibit signal for the MSIU is disabling the instrument MASsoft will refuse to acquire data, and may give an alert box, thus: 
SOLUTION if there is no connector in the TRIPS socket, one should be provided, wired to a vacuum gauge so that the mass spectrometer is protected against vacuum accidents. If a connector is in place, check that the Inhibit signal has not been applied as a result of overpressure in the chamber.
[index]
.14. The same Mass Spectrometer appears twice in the "MassSpecs" menu list PROBLEM If the same Mass Spectrometer appears twice in the MassSpecs menu it may have been found twice during the launch interrogate or during "Explore", once by RS232 and once by network.
SOLUTION disconnect the machine from either RS232 or the network and re-interogate your mass spectrometer.
If not using the network then use the Comms Confguration Utility go to “Select addresses for use with MASsoft” and uncheck all the network adresses by clicking on Clear All Then go to the Alter Communication port settings dialogue and select your comms port . - Alternatively edit Hiden.ini and ensure that the value in the line NumOfAddresses in the [Network] section is 0.
If not using the serial port then use the Comms Configuration Utility to select the network as the means of communications. - Alternatively edit Hiden.ini and change the value of the line Serial= in the [Serial] section to None
[index]
15. RS232 communication doesn't work. PROBLEM By default MASsoft uses COM1: to link to the MSIU.
SOLUTION Ensure that the cable to the MSIU is connected to COM1: on the PC. If you are using COM2: use the Comms configuration utility in the Hiden Applications group to change the comms port.
PROBLEM #2 In Windows for Workgroups 3.11 MASsoft crashes while interrogating the mass spectrometer or as soon as it starts to down-load a scan and displays a message box such as:- *C001* Command Error 1 "Unknown Command" *C003* Command Error 3 "Command Truncated"
CAUSE There may be a problem with the version of COMMS.DRV used by Windows. The RS232 driver supplied with Windows for Workgroups 3.11 and Windows 95 has been found to cause problems when used with MASsoft as it generates a spurious character in the receive buffer when the comms port is opened. (See also the note about Gateway Colorbook2 RS232 link).
SOLUTION edit the SYSTEM.INI file in the Windows folder. Find the line comm=comm.drv
and change it to become comm=PATH\comm.drv
where PATH is the path to the hiden MASsoft home folder - normally C:\hiden for MASsoft 3.5.3 ( and for later versions if running on WFW ), or C:\Progra~1\Hidena~1\Common for MASsoft 3.7 or later running on Windows 95 NOTE this problem may be fixed within MASsoft itself in the version supplied. NOTE: Do NOT make this change on Windows 98 - it will cause Comm Port Errors when running MASsoft.
PROBLEM #3 The above is correct, but the RS232 link still doesn't work.
SOLUTION see the section “” below:-
[index]
16. LAN communication doesn't work. PROBLEM Network communication does not work when using Windows 3.1
CAUSE To use a LAN to communicate with the MSIU requires Windows for Workgroups 3.11 operating system, or later. It is not possible to use a LAN with 3.1.
SOLUTION install Windows for Workgroups 3.11. or upgrade to Windows 95, Windows 98 or NT
The Network in these operating systems must be set up to include Microsoft DLC protocol. See you manual for details. If your NOS is not mentioned in the manual, contact Hiden for help.
PROBLEM #2 Network communication does not work when using Windows Me ( Millennium Edition )
CAUSE Microsoft DLC is a 16 bit protocol which is accessed through the real-mode NetBIOS INT5C interrupt vector. It binds to real mode ( NDIS II ) network drivers. Windows Me does not support real mode drivers.
SOLUTION Install Windows 95, Windows 98 or NT instead of Windows Me
PROBLEM #3 The above points are correct, but the LAN still does not work.
SOLUTION See the section “”
[index]
  
| 
