Support Home Page
Cubix Home Page
Feedback Forms

BCVision
Chapter 5 - Troubleshooting


Continual Reset

If a BC processor connected to an IES Supervisory System is being reset continually, check for the following conditions.

  1. Verify that the appropriate control software is installed on the BC processor as described below. The control software is included on the BC Series Software Installation Diskette. For installation instructions, see the BC Series Software Installation Guide.

DOS and Windows Environments

If the BC processor is running DOS or Windows, verify that the BCSETUP.SYS device driver is loaded in the CONFIG.SYS file. Determine the interrupt configuration as follows:

device=bcsetup No command line parameters: IRQ 15

device=bcsetup -I=10 IRQ 10 configuration

device=bcsetup -int=10 IRQ 10 configuration

device=bcsetup -I=15 IRQ 15 configuration

device=bcsetup -int=15 IRQ 15 configuration

device=bcsetup -int=no No IRQ configuration

 

OS/2 Environments

If the BC processor is running OS/2, verify that the BCSETOS2.SYS device driver is loaded in the CONFIG.SYS file. Determine the interrupt configuration as follows:

device=bcsetos2 No command line parameters: IRQ 15

device=bcsetos2 -I=10 IRQ 10 configuration

device=bcsetos2 -int=10 IRQ 10 configuration

device=bcsetos2 -I=15 IRQ 15 configuration

device=bcsetos2 -int=15 IRQ 15 configuration

device=bcsetos2 -int=no No IRQ configuration

 

NetWare Environments

If the BC processor is running NetWare v3.x or v4.x, verify that the BCACTIVE.NLM is loaded in the AUTOEXEC.NCF file on the NetWare partition. Determine the interrupt configuration as follows:

bcactive 10 IRQ 10 configuration

bcactive 15 IRQ 15 configuration

Also verify that the CONFIG.SYS file on the DOS partition loads BCSETUP.SYS as previously described under DOS and Windows Environments. The interrupt configurations for BCSETUP.SYS and BCACTIVE.NLM should match.

2. Verify that the Supervisory System Interrupt Selection on the BC processor board is set to the same IRQ configured for the control software. Refer to the Installation Guide provided with the BC Series processor.

Note!  Older documentation may refer to this as the AC Fail Interrupt Selection.

3. If other processors in the same subsystem with the problem board are functioning properly, check the cables between the processor and the multiplexor panel.

4. If no processors in the subsystem are functioning, check the cable running from the IES to the multiplexor panel.

5. Another possible cause of the problem may be that the BC processors are taking more time to boot and load the control software than is provided by the reboot timeout. Increase the reboot timeout using BCVision. Select the Set Reboot Timeout option from the Functions Menu on the IES Status Screen.

 

BCVision Response Time

If the keyboard response time in BCVision is too slow, increase the refresh rate. This can be accomplished by selecting the Set BCVision Refresh Rate from the Supervisor Menu. Be aware that the refresh rate determines how often BCVision polls each IES for alarm and status conditions.

 

Unnecessary Resets

If the BC processors are sometimes being reset when they are not locked up, it is probably due to the way the application running on the BC processor is handling interrupts. To avoid this problem, use BCVision to increase the poll interval by selecting Set Poll Interval under the Functions Menu on the IES Status Screen.

If the BC processors are not always allowed to complete their boot sequence before they are reset, the reboot timeout might not be long enough to accommodate the amount of time the CONFIG.SYS is taking before BCSETUP.SYS, BCSETOS2.SYS, or BCACTIVE.NLM is loaded. Use BCVision to increase the reboot timeout by selecting Set Reboot Timeout under the Functions Menu on the IES Status Screen.

 

IES Not Found

While the BCMaster TSR is initializing on the BC Supervisor, it scans the data highway to locate all of the Intelligent Environmental Sensors (IES). If BCMaster does not locate one or more sensors, unload BCMaster. Determine the cause of the problem (data highway cabled improperly, data highway terminated improperly, interrupt conflict with the data highway COM port on the BC Supervisor, etc.), and then reload BCMaster. Refer to the appropriate hardware manual to aid in the troubleshooting process (if the subsystem is an ERS II, or ERS/FT II refer to the Series II Subsystem User’s Guide. If a SafeStor/FT, refer to the SafeStor/FT User’s Guide. For any other subsystem, refer to the IES Module Hardware Installation Guide). Verify that each IES appears in the displayed list of sensors found by BCMaster. Load BCVision only after BCMaster has found all of the sensors.