Download User Manual - Instrumentation Central

Troubleshooting
This section is designed to offer possible solutions should you encounter problems when using
Commander 4.1.
SYSTEM SPEED
Scan rate per loop is approximately equal to the value programmed in Setup Communications. Default
setting is 100mS (0.1 second) per loop. This allows the program to scan 128 loops in approximately 13
seconds. If a large number of graphs are opened or other Windows programs are using a large amount of
Windows resources, the system and thus the scan rate, may slow down. Slower computers may not be
able to scan at this rate as well. Slower computers need a larger Scan value. If the Scan value is too
small Windows has a difficult time performing required housekeeping functions and errors can result
particularly if RAM is low.
COMMANDER CRASHED WITH A GENERAL PROTECTION FAULT
Probably due to insufficient RAM memory installed in computer. 16 megabytes (16,000,000) of RAM is
required to reliably run Commander. Computer should be rebooted after such an error. Try not running
as many programs at the same time if system speed degrades or if General Protection Faults occur.
MESSAGE “NEED TO CONFIGURE LOOPS” APPEARS ON MAIN SCREEN
No loops have been defined. Must define loops before Commander will operate. Select Setup Menu from
Main Screen, then choose Define Loops. See: Defining Loops
MESSAGE “NOT A VALID COMMS PORT” APPEARS ON MAIN SCREEN
One or more of the Comms Ports, as defined in Communications Setup, is not a valid Comms Port.
See: Communications Setup
MESSAGE “LICENSE EXPIRED” APPEARS ON MAIN SCREEN
License to use Commander has expired. You must call your software supplier for the required access
number to continue using Commander. See: Software RegistrationMESSAGE “CHANNEL # XXX OFF
LINE” APPEARS ON MAIN SCREEN (WEST ASCII)
MESSAGE “MB CHANNEL # XXX (ERR-2)” MODBUS
Indicates that the identified loop is not responding to Commander’s transmissions. This could be caused
by:
Wrong channel being programmed in the instrument
Invalid entry in Define Loops.
Wrong Comms Port ID or other parameters in Communications Setup.
Bad wiring to control’s Comms Port
Interface converter not wired or configured properly, or not of the proper type
62