Troubleshooting Guides

For addressing common start-up problems with Associated Research Electrical Safety Testers

At AR we strive to offer instruments with thoughtful features and options for more thorough safety testing. Although we design our products to be as user-friendly as possible, we realize that some customers may still require troubleshooting assistance.

In response to customer feedback, AR has created this page to help customers address the most common problems they encounter. This page offer easy solutions so that customers can get their AR instruments up and running quickly.

As always, feel free to contact our customer service department if you require more information or have a question that these pages fail to answer.

Topics addressed in this guide include:

Hypot III Series (3605, 3665, 3670)

Common Error Messages

Interlock is Open

Background: All AR Hypot^® III models incorporate a remote interlock feature that was designed to provide an added measure of safety for our customers. This feature utilizes a set of contacts that must be closed in order for the instrument to enable an output voltage. Access to these contacts is provided on pins 4 and 5 of the DB9 connector labeled Signal Input located on the back of the hipot. If these contacts are open and the Test button is pushed, or if they become open during a test, the Hypot^® III will disable the output and the following error will be displayed on the screen:
interlock_is_open
Solution: AR supplies all of our customers with an interlock disable connector (38075 provided with the unit) that shorts pins 4 and 5 of the Signal Input connector on the back of the Hypot^® III for those customers who do not utilize interlocked enclosures. If the tester displays the Interlock is Open error either your test enclosure is open or the Interlock disable connector is not properly connected.

PLC Remote ON

Background: All AR Hypot^® III models incorporate a PLC (programmable logic control) Remote interface that allows the test operator to control the hipot remotely. When the PLC Remote feature is enabled, the front panel keys (excluding the Reset button) are disabled and the only way a test can be initiated is through the PLC interface located on the Signal Input connector on the back of the hipot. If the Test button is pushed while this feature is active, the hipot will display the following error:
plc_remote_on
Solution: In order to disable the PLC Remote feature use the following procedure:

Turn on the unit.
When the Perform Test screen appears press the Menu key.
When the Main Menu screen appears press the Menu key.
Press the System key.
Use the “v” key to scroll down to the PLC Remote parameter.
Press the “+” key to toggle from the ON condition to the OFF condition.
Press the Exit key to return to the Perform Test screen.

Why won’t the buttons on the front panel work?

Usually this is a result of the key lockout feature that is incorporated into all AR Hypot^® III models. This feature provides security and safety by disabling the front panel so that unauthorized users cannot program the instrument. To bypass this feature use the following procedure:

Power up the unit while holding down the top soft key button.
When the Perform Test screen appears press the Menu key.
When the Main Menu screen appears press the Menu key.
Press the System key.
Use the “v” to scroll down to the Lock parameter.
Press the “+” key to toggle the Lock parameter to OFF.
Press the Exit key to return to the Perform Test screen.

What is VERI-CHEK?

VERI-CHEK is a patented self-verification system that allows for quick and easy validation of an AR Hypot^® III. When enabled, this feature walks the user through a series of steps designed to verify that the product is functioning correctly.

VERI-CHEK can be used to verify the functionality of the Continuity, AC Hipot, DC Hipot, and Insulation Resistance tests.
hypot_iii_power_up_screen

In order to enable the VERI-CHEK feature press the Test button while the unit is displaying the power up screen (above). The VERI-CHEK feature will walk the user through the verification procedure with a series of prompts from the display.

What is CAL-ALERT?

CAL-ALERT is a patented feature that automatically alerts the user when the instrument is due to be calibrated. The user can enter both the calibration due date as well as the calibration alert date. In order to access the CAL-ALERT feature use the following procedure:

Power up the unit.
When the Perform Test screen appears, press the Menu key.
When the Main Menu screen appears press the Menu key.
Press the System key.
Use the “v” to scroll down to the parameter.
From this menu screen you can select and adjust several parameters: Cal Alert, Cal Date, Cal Due, and Alert.
Press the “v” to scroll between test parameters. Press the “>” key to select the month, day and year. Press the “+” key to edit the parameters.
After adjusting all necessary parameters, press the Exit key to return to the Perform Test screen.

Cal Alert: This parameter enables or disables the CAL-ALERT feature. Use the “+” key to toggle this feature ON and OFF.

Cal Date: This non-editable parameter indicates the last date of calibration. It will automatically be updated with each calibration that is performed.

Cal Due: This parameter indicates when the unit should be sent in for calibration. AR recommends that all units be calibrated once a year. The date is automatically set for 1 year after each calibration.

Alert: This is an editable parameter that can be used to alert the user of the impending calibration date. Once set, the unit will show a reminder on the display that the unit is scheduled to be calibrated. The user can set this parameter to any specific date in advance of the calibration due date to provide ample time to send the unit into AR. The default value of this parameter is automatically set to 11 months after each calibration is completed.
cal_alert_screen
*Note: The Cal. Alert screen will be displayed every time the unit is powered-up once the calibration alert date has been reached.

How do I connect memory steps? / Are my memory steps connected?

All AR Hypot^® III models come equipped with 10 programmable memory locations each capable of storing up to 3 steps. Depending on the features of the model, each step can be used to execute a specific test (AC/DC Withstand or IR). Using these steps and memory locations, a user can program the hipot to execute up to a 3 step test routine for each memory location. The hipot will display the memory and step status in the following manner: M8-2 (memory location 8, step 2). In order to connect multiple steps within a memory location follow this procedure:

Power up the unit.
When the Perform Test screen appears, press the Menu key
Press the Memory key to select the desired memory location (M0-9).
Press the Step key until the unit indicates Step 1 of the current memory location (i.e. M3-1).
Press the Menu key.
Press the Test key to enter the Test Menu.
After entering the test type and parameters for the current test, scroll down to the Connect parameter by pressing the “v” key.
Press the Edit key to select the Connect parameter.
Press the “+” key to toggle the Connect parameter to ON.
Press the Exit key two times to return to the Perform Test screen.
Step 1 is now connected to Step 2
Repeat the process to connect Step 2 to Step 3.

memory_and_step_location
*Note: The Hypot^® III will now display the memory and step location followed by an underscore (i.e. M3-2_). The underscore symbolizes that the current step is connected to the subsequent step. As each memory location is only capable of supporting 3 steps, the Connect parameter will not be available when editing Step 3 of any memory location.

Why does my Hypot® III fail to execute the entire test sequence when all my linked memory steps are connected?

This can occur for one of two reasons. First, if any one of the linked tests fails, the test sequence will stop and the user must push the reset button and begin the sequence again. Second, all AR Hypot^® III models come with a single step function that allows the user to run one step at a time from a sequence of connected steps. The single step command overrides the connect command. To disable the single step command use the following procedure:

Power up the unit.
When the Perform Test screen appears, press the Menu key.
When the Main Menu screen appears press the Menu key.
Press the System key.
Press the “v” to select the Single Step parameter.
Press the “+” key to toggle the Single Step command to ON.
Press the Exit key to return to the Perform Test screen.

What is the Min-Lmt setting on my AC/DC Withstand test?

Current will not flow through an open loop. Thus if the DUT isn’t properly connected during the AC/DC Withstand test, a PASS condition could be issued since there is no minimum current limit setting.

For this reason all AR Hypot^® III models come with a minimum limit feature that may be activated during an AC or DC Withstand test. The minimum limit (Min-Lmt) feature is a programmable minimum current threshold that triggers a failure when the metered current value does not exceed the programmed current value.

Enabling this feature (entering a Min-Lmt setting other than 0) ensures that the Hypot^® III is connected to the DUT thereby preventing false PASS conditions.

How do I determine the Max-Lmt setting on my AC/DC Withstand test?

As there is no official standard for this setting, safety agencies usually leave it up to the manufacturer of the DUT to determine the appropriate maximum leakage current trip-point (Max-Lmt) on a hipot test. Generally, AR recommends that a manufacturer perform a hipot test on a several known good DUT’s and average the leakage current measurements. The resulting average current measurement can then be used as a benchmark for the nominal leakage current of the DUT. By setting the Max-Lmt parameter of the hipot slightly higher than this average the manufacturer will ensure that a failure condition occurs when the leakage current exceeds the average value.

Why do I get a Max-Lmt failure on my DC Withstand test before I reach my test voltage?

The DC Withstand test can be prone to Max-Lmt failures when the DUT is a highly capacitive load. This is due to the momentary charging currents associated with applying a DC voltage to a capacitor. If the test voltage is ramped up too fast, the charging current might exceed the Max-Lmt threshold and cause a false failure to occur.

In order to compensate for this problem, two approaches can be used: 1.) slowly ramp up the voltage during the test; 2.) raise the Max-Lmt parameter. Ramping up the voltage over an extended period of time or raising the value of the Max-Lmt parameter will keep the charging currents from exceeding the Max-Lmt threshold.

What is the Max-Lmt setting on my Insulation Resistance test?

The resistance of an open circuit is infinite. Thus if the DUT isn’t properly connected during the Insulation Resistance test, a PASS condition could be issued since the calculated resistance exceeds the Min-Lmt setting.

For this reason the AR Hypot^® III model 3670 comes with a maximum limit feature that may be activated during an insulation resistance test. The maximum limit (Max-Lmt) feature is a maximum resistance threshold that triggers a failure when exceeded.

By enabling this feature (entering a Max-Lmt setting other than 0) the Hypot^® III will trigger a failure condition if the metered resistance exceeds the programmed Max-Lmt value. This feature ensures that the tester is connected to the DUT thereby preventing false PASS conditions.

Note: If the Insulation Resistance of your DUT is >10GΩ the Max limit should be set to zero to disable this feature.

Why does my Hypot® III display > 10GΩ on my Insulation Resistance test?

The AR Hypot^® III model 3670 has the capability to measure up to 9999 MΩ of resistance during the Insulation Resistance test. If the DUT’s insulation has a value greater than 9999 MΩ Hypot^® III will not display a measured value, but will display the following message: “>10GΩ”.

Interfacing a Hypot® III with a HYAMP III

All AR Hypot^® III models can be interfaced with HYAMP III models 3130, 3140 and 3160 to form a complete test system. The interconnect capability of these two instrument families provides for easy AC/DC Withstand, Insulation Resistance, and Ground Bond testing with only one connection to the DUT. The HYAMP III and Hypot^® III operate together in a master/slave configuration, allowing the user to automate the test sequence for quick and easy testing with the push of a button. To interconnect the Hypot^® III to the HYAMP III start by identifying which test system you have:

System 3100 – HYAMP III Model 3130 and any Hypot^® III model.
System 3400 – HYAMP III Model 3140 and any Hypot^® III model.
System 6000 – HYAMP III Model 3160 and any Hypot^® III model.

After making the necessary connections (see the following diagrams) follow this procedure to complete the system setup:

Turn on both instruments.
From the Hypot^® III Perform Test screen press the Menu key.
When the Main Menu screen appears, press the Menu key.
Press the System key.
Use the “v” to scroll down to the PLC Remote parameter. Press the “+” key to toggle the parameter to ON.

*Note: In this configuration, you will only be able to start and reset the Hypot^® III from the HYAMP III. It is possible to reset or abort the Hypot^® III from both instruments.

From the HYAMP III Perform Test screen press the Menu key.
When the Main Menu screen appears, press the Menu key.
Press the System key.
Use the “v” to scroll down to the <'More'> parameter.
From the menu select the Hipot Start parameter.
Use the “+” key to toggle to the appropriate mode.

*Note: The Hipot Start parameter controls whether the hipot test will run sequentially after the ground bond test, G→W, or simultaneously with the ground bond test, G+W. The Hipot Start parameter directly controls the Start output relay. Setting the Hipot Start parameter to G →W will momentarily close the Start output relay at the end of the ground bond test. Setting the Hipot Start parameter to G+W will momentarily close the Start output relay at the start of the Ground Bond test.

Press the Exit key to return to the Perform Test screen.
Program the appropriate test procedures on both units.
Execute the test procedure by pressing the Test button on the HYAMP III.

System 3100

The following illustration should be used to configure the Hypot^® III for integrated operation with 3130 HYAMP III:
system_3100_configuration

If you order the HYAMP III interconnect kit you will receive the following items.

Interconnect Kit
Part Number	Description	Qty.
HS-8-11	Cable Assembly Return	1
05030DT-21	Cable Assembly R/P Interface COM	1
05030DT-22	Cable Assembly R/P Interface SEQ	1
38142	Interlock Connector	2
36541	Adapter Box HV, HC Domestic	1

When connecting Hypot^® III to HYAMP III the 38075 Interlock connectors may no longer be used. The 38142 Interlock connectors provided with the kit will replace these parts.

System 3400

The following illustration should be used to configure the Hypot^® III for integrated operation with 3140 HYAMP III:
system_3140_configuration

If you order the 3140 HYAMP III interconnect kit you will receive the following items.

Interconnect Kit for 3140 Only, AR Part #260-03
Part Number	Description	Qty.
HS-8-11	Cable Assembly Return	1
05030DT-21	Cable Assembly R/P Interface COM	1
05030DT-22	Cable Assembly R/P Interface SEQ	1
38142	Interlock Connector	2
38482	Adapter Box HV, HC Domestic	1

When connecting Hypot^® III to HYAMP III the 38075 Interlock connectors may no longer be used. The 38142 Interlock connectors provided with the kit will replace these parts.

System 6000

The following illustration should be used to configure the Hypot^® III for integrated operation with 3160 HYAMP III:
system_3100_configuration

If you order the 3160 HYAMP III interconnect kit you will receive the following items.

Interconnect Kit for 3160 Only, AR Part #260-02
Part Number	Description	Qty.
HS-8-11	Cable Assembly Return	1
05030DT-21	Cable Assembly R/P Interface COM	1
05030DT-22	Cable Assembly R/P Interface SEQ	1
38142	Interlock Connector	2

When connecting Hypot^® III to HYAMP III the 38075 Interlock connectors may no longer be used. The 38142 Interlock connectors provided with the kit will replace these parts.

HypotULTRA III Series (7620, 7650) / Autoware S7600

RS-232 Error Messages

This trouble shooting guide offers explanations and solutions for the most common error messages that Autoware S7600 reports to the test operator while using an RS-232 communication interface. The table below contains a series of error codes. Scan these codes until you find the error that you are experiencing. Once you find the appropriate error message click on the code to read about why the error is occurring and how to fix it.

Error - 1073807343

Incorrect COM Port (Hipot)

Background: Automating your testing procedure requires that you interface a computer with your HypotULTRA III. In order to do this you can use the Autoware software to communicate with the Hipot tester in one of two ways: via an RS-232 interface or via a GPIB interface. If you have selected to use an RS-232 interface your computer uses a serial port, which it labels “COM” followed by a number from 0-x (i.e. COM1). If Autoware tries to communicate with the Hipot using the wrong COM port you will receive an error message.

Solution: In order to fix this problem you need to make sure that you have identified the correct COM port so that Autoware can talk successfully to the Hipot.

From the Main Menu select the Setup System Parameters Menu.
The first field asks you to select the communications protocol to use. Make sure that this parameter is set to Serial.
The next field asks you to select which number port to use. Make sure that you select the number that corresponds to the port you have the RS-232 cable plugged into. *NOTE: This may require some trial and error using different ports. If you are using a PC you can identify the correct COM port using Windows Device Manager.
Click OK to return to the Main Menu.

Error - 1073807360

Incorrect COM Port (Scanner/Hipot)

*NOTE: This error can occur due to an incorrect Scanner configuration or an incorrect Hipot configuration. If a Hipot configuration error is suspected, follow the steps outlined in Error – 1073807343 to solve the problem. If a Scanner configuration error is suspected, follow the steps below.

Background: Automating your testing procedure requires that you interface a computer with your remote Scanner (a scanner controlled through a direct connection to the PC). In order to do this you can use the Autoware software to communicate with the remote Scanner in one of two ways: via an RS-232 interface or via a GPIB interface. If you have selected to use an RS-232 interface, your computer uses a serial port, which it labels “COM” followed by a number from 0-x (i.e. COM1). If Autoware tries to communicate with the remote Scanner using the wrong COM port you will receive an error message.

Solution: In order to fix this problem you need to make sure that you have identified the correct COM port so that Autoware can talk successfully to the Scanner.

From the Main Menu select the Setup System Parameters Menu.
The first thing to do is disable the remote Scanner configuration. Click the hot button labeled “Remote Scanners” under the More Settings heading at the bottom of the screen.
Make sure that the “Communication Type” heading is set to Serial.
Using the mouse, scroll through the arrows beneath the heading “Address/Com Port” until the correct port address is chosen.
Click OK to return to the Setup System Parameters Menu.
Click the OK button to return to the Main Menu.

Error - 1073807339

Faulty Interface Cable Connection (Hipot/Scanner)

Background: In order for your Autoware software to communicate properly with the HypotULTRA III and/or SC6540 Scanner, a good connection needs to be made between the serial port of the PC and the interface connector on the instrument. If this cable becomes loose or isn’t properly connected at either end of the system, you will receive an error message.

Solution: In order to fix this problem you need to make sure that your cable is mating properly with both ends of the system and is in good working order.

Unplug your RS-232 cable from each end of the test system and make sure that there are no broken or bent pins.
Reconnect the cable to the PC and the Hipot/Scanner and make sure that it is making a good connection at each end.
Make sure that the Hipot/Scanner power switch is set to the ON position.
If this doesn’t fix the problem you may need to replace your cable.

Error - 1073807195

Incorrect Communications Protocol Selected

Background: Automating your testing procedure requires that you interface a computer with your HypotULTRA III. In order to do this you can use the Autoware software to communicate with the Hipot tester in one of two ways: via an RS-232 interface or via a GPIB interface. If you are using an RS-232 interface and you have configured Autoware to use a GPIB interface you will receive an error message.

Solution: In order to fix this problem you need to make sure that you have selected the Serial (RS-232) communication option. This selection allows Autoware to talk successfully to the Hipot.

From the Main Menu select the Setup System Parameters Menu.
The first field asks you to select the communications protocol to use. Make sure that this parameter is set to Serial.
The next field asks you to select which number port to use. Make sure that you select the number that corresponds to the port you have the RS-232 cable plugged into. *NOTE: This may require some trial and error using different ports. If you are using a PC you can identify the correct COM port using Windows Device Manager.
Once you have the proper COM port configured make sure that the proper “Instrument Under Control” is selected in the Main Menu. Use the arrow keys to scroll through the options until the model and COM port information for your Hipot is selected.

Error 1 occured at Error with Command "ADD..." - Event Register = 0

Incorrect Local Scanner Configuration

Background: The HypotULTRA III is capable of interfacing with several different local Scanner configurations (none, 1 x 4 internal, 1 x 8 internal, 1 x 8 external, and 1 x 8 internal with 1 x 8 external). All of these Scanner channels are controlled locally by the Hipot tester. When incorporating a Scanner into your testing procedure, it is important to define the correct configuration so that the Autoware software knows how many channels are present in the system. If you have selected fewer Scanner channels than are actually present (1 x 4 internal with a 1 x 8 internal, 1 x 8 internal with a 1 x 8 internal and 1 x 8 external, etc.), Autoware will still function properly without error. However, if you have selected a Scanner configuration with more channels than actually exist, or if there is no Scanner at all, Autoware will display an error message similar to the one above (depending on the scanner configuration).

Solution: In order to solve this problem you will need to reconfigure your Scanner settings.

From the Main Menu select the Setup System Parameters Menu.
From here you will need to select the appropriate Scanner configuration. The fourth field from the top edits the Scanner parameters.
Using the mouse, click on the up and down arrows to scroll through the different Scanner configurations until you have set the parameter to the correct number of channels (none, 1 x 4, 1 x 8, 2 x 8).
Click OK to return to the Main Menu.

Remote Scanner Set Up as Local Scanner

Background: The HypotULTRA III is capable of interfacing with both an internal and external Scanner controlled locally by the Hipot tester, or with a remote Scanner which is controlled by the Autoware software through a direct connection to the PC. When incorporating a Scanner into your testing procedure, it is important to define whether Autoware should treat the Scanner as a local Scanner or a remote Scanner. If you have selected that your Scanner is to be controlled locally and the Scanner is actually a remote Scanner that is controlled through Autoware directly, Autoware will display an error message similar to the one above (depending on the scanner configuration).

Solution: In order to solve this problem you will need to reconfigure your Scanner settings.

From the Main Menu select the Setup System Parameters Menu.
The first thing to do is disable the internal Scanner configuration. The fourth field from the top edits the Scanner parameters.
Using the mouse, click on the up and down arrows to scroll through the different Scanner configurations until you have set the parameter to “None.”
Next you must configure the remote Scanner parameter to match your current configuration.
Click the hot button labeled “Remote Scanners” under the More Settings heading at the bottom of the screen.
Using the mouse, scroll through the arrows next to the heading “Number of Remote Scanners.” Depending on your configuration, you can set up a total of 12 remote Scanners. Once you have selected the correct number of remote Scanners you must then edit each Scanner’s operating parameters.
Make sure that the “Scanner Type” matches your Scanner (SC6540 or HS-16).
Set your communication type to either Serial (RS-232) or GPIB.
Next configure the proper port/address for the current Scanner (for more information on this read the Background section under the Error – 1073807343). Finally, set the correct number of HV (high voltage) channels you have opted for with your Scanner.
Once all of the parameters for each Scanner have been set correctly click OK to return to the Setup System Parameters Menu.
Click the OK button to return to the Main Menu.

Local Scanner Set Up as Remote Scanner

Background: The HypotULTRA III is capable of interfacing with both an internal and external Scanner controlled locally by the Hipot tester, or with a remote Scanner which is controlled by the Autoware software through a direct connection to the PC. When incorporating a Scanner into your testing procedure, it is important to define whether Autoware should treat the Scanner as a local Scanner or a remote Scanner. If you have selected that your Scanner is to be controlled remotely and the Scanner is actually an internal or external Scanner that is controlled locally by the Hipot you will receive an error message.

Solution: In order to solve this problem you will need to reconfigure your Scanner settings.

From the Main Menu select the Setup System Parameters Menu.
The first thing to do is disable the remote Scanner configuration. Click the hot button labeled “Remote Scanners” under the More Settings heading at the bottom of the screen.
Using the mouse, scroll through the arrows next to the heading “Number of Remote Scanners” until the number is 0. You have now disabled the remote scanner configuration.
Click OK to return to the Setup System Parameters Menu.
Next you must enable the proper local Scanner configuration. The fourth field from the top edits the Scanner parameters.
Using the mouse, click on the up and down arrows to scroll through the different Scanner configurations until you find the one that corresponds to your Scanner configuration (none, 1 x 8 channel, 2 x 8 channel, 1 x 4 channel).
Click the OK button to return to the Main Menu.

Error 1 occured at Error with command "SAO" - Event Register = 0

Auto-Offset Error

Background: One of the features of the HypotULTRA III’s Continuity test is an Auto-offset feature that allows the tester to automatically record the test lead resistance and subtract it from the resistance measurement of the Continuity test itself. In order for the unit to make an accurate measurement, the test leads must be shorted together when the measurement is taken. If you attempt to click the “Send Parameters and Load to Memory” button with the Auto-offset feature selected in the Continuity Test Menu and the test leads aren’t connected together you will receive an error message.

Solution: In order to fix this error you will need to make sure that there is continuity in the circuit you are testing when you click the “Send Parameters and Load to Memory” button. This will allow the Hipot to record an accurate measurement. It will then use this measurement every time it performs this test sequence. Once the “Send Parameters and Load to Memory” button has been pressed in the Continuity Test Menu you may disconnect the test leads and continue with the test procedure setup.

Error 1 occured at Error with command "FL1" - Event Register = 0

PLC Implementation Error

Background: The Autoware software may be used with the HypotULTRA III explicitly to log data. In order to do this you need to set the software up in the correct configuration while using the PLC inputs on the back of the Hipot tester. If you attempt to use the PLC inputs while in the Run Test menu you will receive an error message.

Solution: If you are going to be using the Autoware software for remote data capture you cannot use the standard Run Test menu.

From the Main Menu, click the button labeled “Last Test Results/Remote Data Logging.”
From here you can load the correct setup file that corresponds to your test procedure.
You may now use the PLC inputs to control the test procedure. The Autoware software will record the test data as the procedure progresses.

GPIB (IEEE – 488) Error Messages

This trouble shooting guide offers explanations and solutions for the most common error messages that Autoware S7600 reports to the test operator while using an GPIB (IEEE – 488) communication interface. The table below contains a series of error codes. Scan these codes until you find the error that you are experiencing. Once you find the appropriate error message click on the code to read about why the error is occurring and how to fix it.

Error - 1073807302

Incorrect GPIB Port (Hipot)

Background: Automating your testing procedure requires that you interface a computer with your HypotULTRA III. In order to do this you can use the Autoware software to communicate with the Hipot tester in one of two ways: via an GPIB (IEEE – 488) interface or via a RS-232 interface. If you have selected to use a GPIB interface your computer uses a parallel port, which it labels “GPIB” followed by a number from 0-x (i.e. GPIB1). If Autoware tries to communicate with the Hipot using the wrong GPIB port you will receive an error message.

Solution: In order to fix this problem you need to make sure that you have identified the correct GPIB port so that Autoware can talk successfully to the Hipot.

From the Main Menu select the Setup System Parameters Menu.
The first field asks you to select the communications protocol to use. Make sure that this parameter is set to GPIB.
The next field asks you to select which number port to use. Make sure that you select the number that corresponds to the port you have the GPIB cable plugged into.
Click OK to return to the Main Menu.

Error - 1073807265

Incorrect GPIB Port (Scanner/Hipot)

*NOTE: This error can occur due to an incorrect Scanner configuration or an incorrect Hipot configuration. If a Hipot configuration error is suspected, follow the steps outlined in Error – 1073807302 to solve the problem. If a Scanner configuration error is suspected, follow the steps below.

Background: Automating your testing procedure requires that you interface a computer with your remote Scanner (a scanner controlled through a direct connection to the PC). In order to do this you can use the Autoware software to communicate with the remote Scanner in one of two ways: via an GPIB (IEEE – 488) interface or via a RS-232 interface. If you have selected to use a GPIB interface, your computer uses a parallel port, which it labels “GPIB” followed by a number from 0-x (i.e. GPIB1). If Autoware tries to communicate with the remote Scanner using the wrong GPIB port you will receive an error message.

Solution: In order to fix this problem you need to make sure that you have identified the correct GPIB port so that Autoware can talk successfully to the Scanner.

From the Main Menu select the Setup System Parameters Menu.
The first thing to do is disable the remote Scanner configuration. Click the hot button labeled “Remote Scanners” under the More Settings heading at the bottom of the screen.
Make sure that the “Communication Type” heading is set to GPIB.
Using the mouse, scroll through the arrows beneath the heading “Address/Com Port” until the correct port address is chosen.
Click OK to return to the Setup System Parameters Menu
Click the OK button to return to the Main Menu.

Faulty Interface Cable Connection

Background: In order for your Autoware software to communicate properly with the HypotULTRA III or SC6540 a good connection needs to be made between the parallel port of the PC and the interface connector on the instrument. If this cable becomes loose or isn’t properly connected at either end of the system you will receive an error message.

Solution: In order to fix this problem you need to make sure that your cable is mating properly with both ends of the system and is in good working order.

Unplug your GPIB cable from each end of the test system and make sure that there are no broken or bent pins.
Reconnect the cable to the PC and the instrument and make sure that it is making a good connection at each end.
Make sure that the Hipot or Scanner power switch is set to the ON position.
If this doesn’t fix the problem you may need to replace your cable.

Incorrect Master Scanner Address

Background: The Associated Research, Inc. SC6540 modular scanner can be configured in multiple ways. Each Scanner is either designated to operate as a master or a slave before it leaves the factory. Each master Scanner can control up to four slave Scanners. In order for your Autoware software to communicate properly with each SC6540, the Scanner’s address needs to be set manually. Each scanner must be addressed using the 8 DIP switches located on the rear panel. A master’s address must correspond to the GPIB address being used to control it by the computer.

Solution : In order to fix the problem you must make sure that the GPIB address being used to control the master SC6540 Scanner corresponds to the address of the Scanner (as set by the 8 DIP switches).

From the Main Menu select the System Parameters Menu.
The first field asks you to select the communications protocol to use. Make sure that this parameter is set to GPIB.
The next field asks you to select which number port to use. Make sure that you select the number that corresponds to the port you have the GPIB cable plugged into.
Once you have selected the correct GPIB port you must configure the DIP switches on the back of the Scanner to match this address. The Scanner’s address is set using switches 1-5. The address is set using a binary system. The DIP switch is set in the up position for ON (or 1) and in the down position for OFF (or 0). Refer to the SC6540 manual for more information on this. Use the following table to set the correct scanner address:

Bit 5	Bit 4	Bit 3	Bit 2	Bit 1	GPIB Address
0	0	0	0	0	0
0	0	0	0	1	1
0	0	0	1	0	2
0	0	0	1	1	3
0	0	1	0	0	4
0	0	1	0	1	5
0	0	1	1	0	6
0	0	1	1	1	7
0	1	0	0	0	8
0	1	0	0	1	9
0	1	0	1	0	10
0	1	0	1	1	11
0	1	1	0	0	12
0	1	1	0	1	13
0	1	1	1	0	14
0	1	1	1	1	15

Error - 1073807343

Incorrect Communications Protocol Selected

Background: Automating your testing procedure requires that you interface a computer with your HypotULTRA III. In order to do this you can use the Autoware software to communicate with the Hipot tester in one of two ways: via an GPIB (IEEE – 488) interface or via a RS-232 interface. If you are using a GPIB interface and you have configured Autoware to use a GPIB (IEEE – 488) interface you will receive an error message.

Solution: In order to fix this problem you need to make sure that you have selected the Parallel (GPIB) communication option. This selection allows Autoware to talk successfully to the Hipot.

From the Main Menu select the Setup System Parameters Menu.
The first field asks you to select the communications protocol to use. Make sure that this parameter is set to GPIB.
The next field asks you to select which number port to use. Make sure that you select the number that corresponds to the port you have the GPIB cable plugged into.
Once you have the proper GPIB port configured make sure that the proper “Instrument Under Control” is selected in the Main Menu. Use the arrow keys to scroll through the options until the model and GPIB port information for your Hipot is selected.

Error - 1073807339

Incorrect Communications Protocol Selected

*See Error – 1073807343 for explanation.

Error - 1073807360

Incorrect Communications Protocol Selected

*See Error – 1073807343 for explanation.

Error 1 occured at Error with command "HV..." - Event Register = 32

Redundant GPIB Port

Background: Automating your testing procedure requires that you interface a computer with your HypotULTRA III and accompanying remote Scanner. If you have selected to use a GPIB interface to control both your Hipot and Scanner you need to make sure that each device has a separate GPIB address. The computer uses a parallel port, which it labels “GPIB” followed by a number from 0-x (i.e. GPIB1). If you have set both your Hipot and Scanner to communicate with the same GPIB port the Autoware will display the above error message.

Solution: In order to fix this problem you need to make sure that you have identified the correct GPIB ports so that Autoware can talk successfully to the Hipot and Scanner.

From the Main Menu select the Setup System Parameters Menu.
The first field asks you to select the communications protocol to use for Hipot control. Make sure that this parameter is set to GPIB.
The next field asks you to select which number port to use. Make sure that you select the number that corresponds to the port you have the GPIB cable plugged into.
Next disable the remote Scanner configuration. Click the hot button labeled “Remote Scanners” under the More Settings heading at the bottom of the screen.
Make sure that the “Communication Type” heading is set to GPIB.
Using the mouse, scroll through the arrows beneath the heading “Address/Com Port” until the correct port address is chosen.
Click OK to return to the Setup System Parameters Menu.
Once you have the proper GPIB port configured for both the Hipot and Scanner make sure that the proper “Instrument Under Control” is selected in the Main Menu. Use the arrow keys to scroll through the options until the model and GPIB port information for your Hipot is selected.

Local Scanner Set Up as Remote Scanner

Background: The HypotULTRA III is capable of interfacing with both an internal and external Scanner controlled locally by the Hipot tester, or with a remote Scanner which is controlled by the Autoware software through a direct connection to the PC. When incorporating a Scanner into your testing procedure, it is important to define whether Autoware should treat the Scanner as a local Scanner or a remote Scanner. If you have selected that your Scanner is to be controlled remotely and the Scanner is actually an internal or external Scanner that is controlled locally by the Hipot you will receive an error message.

Solution: In order to solve this problem you will need to reconfigure your Scanner settings.

From the Main Menu select the Setup System Parameters Menu.
The first thing to do is disable the remote Scanner configuration. Click the hot button labeled “Remote Scanners” under the More Settings heading at the bottom of the screen.
Using the mouse, scroll through the arrows next to the heading “Number of Remote Scanners” until the number is 0. You have now disabled the remote scanner configuration.
Click OK to return to the Setup System Parameters Menu.
Next you must enable the proper local Scanner configuration. The fourth field from the top edits the Scanner parameters.
Using the mouse, click on the up and down arrows to scroll through the different Scanner configurations until you find the one that corresponds to your Scanner configuration (none, 1 x 8 channel, 2 x 8 channel, 1 x 4 channel).
Click the OK button to return to the Main Menu.

Error 1 occured at Error with command "ADD..." - Event Register = 16

Incorrect Local Scanner Configuration

Solution: In order to solve this problem you will need to reconfigure your Scanner settings.

From the Main Menu select the Setup System Parameters Menu.
From here you will need to select the appropriate Scanner configuration. The fourth field from the top edits the Scanner parameters.
Using the mouse, click on the up and down arrows to scroll through the different Scanner configurations until you have set the parameter to the correct number of channels (none, 1 x 4, 1 x 8, 2 x 8).
Click OK to return to the Main Menu.

Remote Scanner Set Up as Local Scanner

Solution: In order to solve this problem you will need to reconfigure your Scanner settings.

From the Main Menu select the Setup System Parameters Menu.
The first thing to do is disable the internal Scanner configuration. The fourth field from the top edits the Scanner parameters.
Using the mouse, click on the up and down arrows to scroll through the different Scanner configurations until you have set the parameter to “None”.
Next you must configure the remote Scanner parameter to match your current configuration.
Click the hot button labeled “Remote Scanners” under the More Settings heading at the bottom of the screen.
Using the mouse, scroll through the arrows next to the heading “Number of Remote Scanners”. Depending on you configuration, you can set up a total of 12 remote Scanners. Once you have selected the correct number of remote Scanners you must then edit each Scanner’s operating parameters.
Make sure that the “Scanner Type” matches your Scanner (SC6540 or HS-16).
Set you communication type to either Serial (RS-232) or GPIB.
Next configure the proper port/address for the current Scanner (for more information on this read the Background section under Error – 1073807302).
Finally, set the correct number of HV (high voltage) channels you have opted for with your Scanner.
Once all of the parameters for each Scanner have been set correctly click OK to return to the Setup System Parameters Menu.
Click the OK button to return to the Main Menu.

Error 1 occured at Error with command "SAO"

Auto Offset Error

Background: One of the features of the HypotULTRA III’s Continuity test is an Auto-offset feature that allows the tester to automatically record the test lead resistance and subtract it from the resistance measurement of the Continuity test itself. In order for the unit to make an accurate measurement, the test leads must be shorted together when the measurement is taken. If you attempt to click the “Send Parameters and Load to Memory” button with the Auto-Offset feature selected in the Continuity Test Menu and the test leads aren’t connected together you will receive an error message.

Error – 1073807202

Error - 1073807302

Old NI-VISA Error

Background: The Autoware program uses NI-VISA to enable communication with the instrument via the communication ports. The version of NI-VISA must be compatible with the PC’s operating system in order for the program to establish proper communication with the instrument. If the NI-VISA version on the PC is an older version, it may not be compatible with the current PC operating system. As a result, you will receive this error message if you are using Windows VISTA or Windows 7.

Solution: In order to fix this problem you need to update the current NI-VISA to a newer edition and uninstall the old NI-VISA. The Autoware updates on the Associated Research website include the new NI-VISA version.

Go to your PC’s control panel and locate the old NI-VISA runtime engine (the old version is 2.6.1).
Uninstall the old NI-VISA runtime engine.
Once the uninstall is completed, go to the Autoware Updates on the Associated Research website:
https://www.arisafety.com/products/software-solutions/software-updates/
The Autoware Updates have a new NI-VISA runtime engine built in. Run the update and the new NI-VISA will be installed.NOTE: If you are unable to update the version of Autoware, you will need to get the NI-VISA update directly from the National Instruments website. Select the version that matches with your PC’s operating system:
http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/catnav:du/q/NI-VISA/

OMNIA 8100 Series (8104, 8105, 8106) / Autoware S8456

RS-232 Error Messages

This trouble shooting guide offers explanations and solutions for the most common error messages that Autoware S8456 reports to the test operator while using an RS-232 communication interface. The table below contains a series of error codes. Scan these codes until you find the error that you are experiencing. Once you find the appropriate error message click on the code to read about why the error is occurring and how to fix it.

Error - 1073807343

Incorrect COM Port (OMNIA)

Background: Automating your testing procedure requires that you interface a computer with your OMNIA. In order to do this you can use the Autoware software to communicate with the OMNIA in one of two ways: via an RS-232 interface or via a GPIB interface. If you have selected to use an RS-232 interface your computer uses a serial port, which it labels “COM” followed by a number from 0-x (i.e. COM1). If Autoware tries to communicate with the OMNIA using the wrong COM port you will receive an error message.

Solution: In order to fix this problem you need to make sure that you have identified the correct COM port so that Autoware can talk successfully to the OMNIA.

From the startup screen select Setup System Parameters located in the Window Menu.
Under the Primary Unit tab, the first field asks you to select the communications protocol to use. Make sure that this parameter is set to “Serial.”
The next field asks you to select which number port to use. Make sure that you select the number that corresponds to the port you have the RS-232 cable plugged into. *NOTE: You can click the View Available Communications Connections button to determine which COM port is being used.
Select Save and Close located in the File Menu to return to the startup screen.

Error - 1073807360

Incorrect COM Port (Scanner/OMNIA)

*NOTE: This error can occur due to an incorrect Scanner configuration or an incorrect OMNIA configuration. If an OMNIA configuration error is suspected, follow the steps outlined in Error – 1073807343 to solve the problem. If a Scanner configuration error is suspected, follow the steps below.

Solution: In order to fix this problem you need to make sure that you have identified the correct COM port so that Autoware can talk successfully to the Scanner.

From the startup screen select Setup System Parameters located in the Window Menu.
Click the Remote Scanners tab at the top of the screen.
For each Remote Scanner being used, make sure that the Communication Type heading is set to “Serial.”
Using the mouse, scroll through the arrows beneath the Address heading until the correct port address is chosen for each Remote Scanner.
Make sure that the number of HV (high voltage) and GND (ground bond) channels are correct for each Remote Scanner.
Select Save and Close located in the File Menu to return to the startup screen.

Error - 1073807339

Faulty Interface Cable Connection (OMNIA/Scanner)

Background: In order for your Autoware software to communicate properly with the OMNIA and/or SC6540 Scanner a good connection needs to be made between the serial port of the PC and the interface connector on the instrument. If this cable becomes loose or isn’t properly connected at either end of the system you will receive an error message.

Solution: In order to fix this problem you need to make sure that your cable is mating properly with both ends of the system and is in good working order.

Unplug your RS-232 cable from each end of the test system and make sure that there are no broken or bent pins.
Reconnect the cable to the PC and the OMNIA/Scanner and make sure that it is making a good connection at each end.
Make sure that the OMNIA/Scanner power switch is set to the ON position.
If this doesn’t fix the problem you may need to replace your cable.

Error - 1073807195

Incorrect Communication Protocol Selected

Background: Automating your testing procedure requires that you interface a computer with your OMNIA. In order to do this you can use the Autoware software to communicate with the OMNIA in one of two ways: via an RS-232 interface or via a GPIB interface. If you are using an RS-232 interface and you have configured Autoware to use a GPIB interface you will receive an error message.

Solution: In order to fix this problem you need to make sure that you have selected the Serial (RS-232) communication option. This selection allows Autoware to talk successfully to the OMNIA.

From the startup screen select Setup System Parameters located in the Window Menu.
Under the Primary Unit tab, the first field asks you to select the communications protocol to use. Make sure that this parameter is set to “Serial.”
The next field asks you to select which number port to use. Make sure that you select the number that corresponds to the port you have the RS-232 cable plugged into. *NOTE: You can click the View Available Communications Connections button to determine which COM port is being used.
Select Save and Close located in the File Menu to return to the startup screen.

Error #1 - Error with command "ADD..." - Event Register = 0

Incorrect Local Scanner Configuration

Background: The OMNIA is capable of interfacing with several different local Scanner configurations (none, 1 x 8 internal, 1 x 8 external, and 1 x 8 internal with 1 x 8 external). All of these Scanner channels are controlled locally by the OMNIA tester. When incorporating a Scanner into your testing procedure, it is important to define the correct configuration so that the Autoware software knows how many channels are present in the system. If you have selected fewer Scanner channels than are actually present Autoware will still function properly without error. However, if you have selected a Scanner configuration with more channels than actually exist, or if there is no Scanner at all, Autoware will display an error message similar to the one above (depending on the Scanner configuration).

Solution: In order to solve this problem you will need to reconfigure your Scanner settings.

From the startup screen select Setup System Parameters located in the Window Menu.
From here you will need to select the appropriate Scanner configuration. Under the Primary Unit tab the bottom-most field edits the Scanner parameters.
Using the mouse, click on the up and down arrows to scroll through the different Scanner configurations until you have set the parameter to the correct number of channels (none, 1 x 8, 2 x 8).
Select Save and Close located in the File Menu to return to the startup screen.

Remote Scanner Set Up as Local Scanner

Background: The OMNIA is capable of interfacing with both an internal and external Scanner controlled locally by the OMNIA tester, or with a remote Scanner which is controlled by the Autoware software through a direct connection to the PC. When incorporating a Scanner into your testing procedure, it is important to define whether Autoware should treat the Scanner as a local Scanner or a remote Scanner. If you have selected that your Scanner is to be controlled locally and the Scanner is actually a remote Scanner that is controlled through Autoware directly, Autoware will display an error message similar to the one above (depending on the scanner configuration).

Solution: In order to solve this problem you will need to reconfigure your Scanner settings.

From the startup screen select Setup System Parameters located in the Window Menu.
The first thing to do is disable the internal Scanner configuration. Under the Primary Unit tab, the bottom-most field edits the Scanner parameters.
Using the mouse, click on the up and down arrows to scroll through the different Scanner configurations until you have set the parameter to “None.”
Next you must configure the remote Scanner parameter to match your current configuration.
Click the Remote Scanners tab at the top of the screen.
Using the mouse, scroll through the arrows next to the heading “Number of Remote Scanners.” Depending on your configuration, you can set up a total of 12 remote Scanners. Once you have selected the correct number of remote Scanners you must then edit each Scanner’s operating parameters.
Make sure that the “Scanner Type” matches the Scanner (SC6540 or HS-16).
Set your communication type to either Serial (RS-232) or GPIB.
Next configure the proper port/address for the current Scanner (for more information on this read the Background section under Error – 1073807343).
Finally, set the correct number of HV (high voltage) and GND (ground bond) channels you have opted for with your Scanner.
Once all of the parameters for each Scanner have been set correctly select Save and Close located in the File Menu to return to the startup screen.

Local Scanner Set Up as Remote Scanner

Background: The OMNIA is capable of interfacing with both an internal and external Scanner controlled locally by the OMNIA tester, or with a remote Scanner which is controlled by the Autoware software through a direct connection to the PC. When incorporating a Scanner into your testing procedure, it is important to define whether Autoware should treat the Scanner as a local Scanner or a remote Scanner. If you have selected that your Scanner is to be controlled remotely and the Scanner is actually an internal or external Scanner that is controlled locally by the OMNIA you will receive an error message.

Solution: In order to solve this problem you will need to reconfigure your Scanner settings.

From the startup screen select Setup System Parameters located in the Window Menu.
The first thing to do is disable the remote Scanner configuration. Click the Remote Scanners tab at the top of the screen.
Using the mouse, scroll through the arrows next to the heading “Number of Remote Scanners” until the number is 0. You have now disabled the remote scanner configuration.
Next you must enable the proper local Scanner configuration. Click the Primary Unit tab at the top of the screen. The bottom-most field edits the Scanner parameters.
Using the mouse, click on the up and down arrows to scroll through the different Scanner configurations until you find the one that corresponds to your Scanner configuration (none, 1 x 8 channel, 2 x 8 channel).
Select Save and Close located in the File Menu to return to the startup screen.

Error #1 - Error with command "FL1" - Event Register = 0

Incorrect DUT HV setup

Background: One of the features of OMNIA models 8105 and 8106 is the addition of a DUT output jack used to supply power to a DUT during Line Leakage and Run testing. This feature can be enabled from both the front panel of the OMNIA and the Autoware software. If there is a discrepancy between how the parameter is set in OMNIA’s hardware and Autoware’s software an error message will be displayed when attempting to save a file to the OMNIA.

Solution: In order to solve this problem you will need to make sure that the DUT-HV parameter is consistent in both OMNIA’s hardware and Autoware’s software.

From the startup screen select Setup System Parameters located in the Window Menu.
Under the Primary Unit tab, make sure that the box next to DUT-HV Setting is checked.
Select Save and Close located in the File Menu to return to the startup screen.
Exit the Autoware program by selecting Exit Autoware from the File Menu.
From the Main Menu on the OMNIA’s LCD screen, press the softkey corresponding to Setup System.
From the Setup System Menu press the softkey corresponding to Hardware.
Toggle the DUT-HV Setup parameter until it is set to ON.
Press the Exit key twice to return to the Main Menu.
Now that both the hardware and software DUT-HV Setting parameters are configured properly you may run the Autoware software normally.

Error #1 - Error with command "SAO" - Event Register = 0

Auto-Offset Error (GC/GB)

Background: One of the features of OMNIA’s Ground Continuity and Ground Bond tests is an Auto-offset feature that allows the tester to automatically record the test lead resistance and subtract it from the resistance measurement of the test itself. In order for the unit to make an accurate measurement, the test leads must be shorted together when the measurement is taken. If you attempt to save a File to the OMNIA with the Auto-offset feature selected in either a Ground Continuity or a Ground Bond test and the test leads aren’t connected together you will receive an error message.

Solution: In order to fix this error you will need to make sure that there is continuity in the circuit you are testing when you select Save from the File Menu in the Setup Test Parameters screen. This will allow the OMNIA to record an accurate measurement. It will then use this measurement every time it performs this test sequence. Once you have successfully loaded the File into the OMNIA’s memory you may disconnect the test leads and continue with the test procedure setup.

GPIB (IEEE – 488) Error Messages

This trouble shooting guide offers explanations and solutions for the most common error messages that Autoware S8456 reports to the test operator while using GPIB (IEEE-488) communication interface. The table below contains a series of error codes. Scan these codes until you find the error that you are experiencing. Once you find the appropriate error message click on the code to read about why the error is occurring and how to fix it.

Error - 1073807265

Incorrect GPIB Port (Scanner / OMNIA)

Background: Automating your testing procedure requires that you interface a computer with your OMNIA and Scanner. In order to do this you can use the Autoware software to communicate with the OMNIA and Scanner in one of two ways: via an RS232 interface or via a GPIB interface. If you have selected to use a GPIB interface your computer uses a parallel port, which it labels “GPIB” followed by a number from 0-x (i.e. GPIB1). If Autoware tries to communicate with the OMNIA or Scanner using the wrong GPIB port you will receive an error message.

Solution (OMNIA): In order to fix this problem you need to make sure that you have identified the correct GPIB port so that Autoware can talk successfully to the OMNIA.

From the startup screen select Setup System Parameters located in the Window Menu.
Under the Primary Unit tab, the first field asks you to select the communications protocol to use. Make sure that this parameter is set to “GPIB”
The next field asks you to select which number port to use. Make sure that you select the number that corresponds to the port you have the GPIB cable plugged into. *NOTE: You can click the View Available Communications Connections button to determine which GPIB port is being used.
Select Save and Close located in the File Menu to return to the startup screen.

Solution (Scanner): In order to fix this problem you need to make sure that you have identified the correct GPIB port so that Autoware can talk successfully to the Scanner.

From the startup screen select Setup System Parameters located in the Window Menu.
Click the Remote Scanners tab at the top of the screen.
For each Remote Scanner being used, make sure that the Communication Type heading is set to “GPIB.”
Using the mouse, scroll through the arrows beneath the Address heading until the correct port address is chosen for each Remote Scanner.
Make sure that the number of HV (high voltage) and GND (ground bond) channels are correct for each Remote Scanner.
Select Save and Close located in the File Menu to return to the startup screen.

Error - 1073807304

Faulty Interface Cable Connection (OMNIA / Scanner)

Solution: In order to fix this problem you need to make sure that your cable is mating properly with both ends of the system and is in good working order.

Unplug your GPIB cable from each end of the test system and make sure that there are no broken or bent pins.
Reconnect the cable to the PC and the OMNIA/Scanner and make sure that it is making a good connection at each end.
Make sure that the OMNIA/Scanner power switch is set to the ON position.
If this doesn’t fix the problem you may need to replace your cable.

Error - 1073807343

Incorrect Communications Protocol Selected

Background: Automating your testing procedure requires that you interface a computer with your OMNIA and Scanner. In order to do this you can use the Autoware software to communicate with the OMNIA and Scanner in one of two ways: via an RS232 interface or via a GPIB interface. If you are using a GPIB interface and you have configured Autoware to use an RS-232 interface you will receive an error message.

Solution (OMNIA): In order to fix this problem you need to make sure that you have selected the GPIB communication option. This selection allows Autoware to talk successfully to the OMNIA.

From the startup screen select Setup System Parameters located in the Window Menu.
Under the Primary Unit tab, the first field asks you to select the communications protocol to use. Make sure that this parameter is set to “GPIB”
The next field asks you to select which number port to use. Make sure that you select the number that corresponds to the port you have the GPIB cable plugged into.
Select Save and Close located in the File Menu to return to the startup screen.

Solution (Scanner): In order to fix this problem you need to make sure that you have selected the GPIB communication option. This selection allows Autoware to talk successfully to the Scanner.

From the startup screen select Setup System Parameters located in the Window Menu.
Click the Remote Scanners tab at the top of the screen.
For each Remote Scanner being used, make sure that the Communication Type heading is set to “GPIB.”
Select Save and Close located in the File Menu to return to the startup screen.

Error #1 - Error with command "ADD..." - Event Register = 0

Incorrect Local Scanner Configuration

Background: The OMNIA is capable of interfacing with several different local Scanner configurations (none, 1 x 8 internal, 1 x 8 external, and 2 x 8 internal with 2 x 8 external). All of these Scanner channels are controlled locally by the OMNIA tester. When incorporating a Scanner into your testing procedure, it is important to define the correct configuration so that the Autoware software knows how many channels are present in the system. If you have selected fewer Scanner channels than are actually present Autoware will still function properly without error. However, if you have selected a Scanner configuration with more channels than actually exist, or if there is no Scanner at all, Autoware will display an error message similar to the one above (depending on the Scanner configuration).

Solution: In order to solve this problem you will need to reconfigure your Scanner settings.

From the startup screen select Setup System Parameters located in the Window Menu.
From here you will need to select the appropriate Scanner configuration. Under the Primary Unit tab the bottom-most field edits the Scanner parameters.
Using the mouse, click on the up and down arrows to scroll through the different Scanner configurations until you have set the parameter to the correct number of channels (none, 1 x 8, 2 x 8).
Select Save and Close located in the File Menu to return to the startup screen.

Remote Scanner Set Up as Local Scanner

Solution: In order to solve this problem you will need to reconfigure your Scanner settings.

From the startup screen select Setup System Parameters located in the Window Menu.
The first thing to do is disable the internal Scanner configuration. Under the Primary Unit tab, the bottom-most field edits the Scanner parameters.
Using the mouse, click on the up and down arrows to scroll through the different Scanner configurations until you have set the parameter to “None.”
Next you must configure the remote Scanner parameter to match your current configuration.
Click the Remote Scanners tab at the top of the screen.
Using the mouse, scroll through the arrows next to the heading “Number of Remote Scanners.” Depending on your configuration, you can set up a total of 12 remote Scanners. Once you have selected the correct number of remote Scanners you must then edit each Scanner’s operating parameters.
Make sure that the “Scanner Type” matches the Scanner (SC6540 or HS-16).
Set your communication type to either Serial (RS-232) or GPIB.
Next configure the proper port/address for the current Scanner (for more information on this read the Background section under Error – 1073807343).
Finally, set the correct number of HV (high voltage) and GND (ground bond) channels you have opted for with your Scanner.
Once all of the parameters for each Scanner have been set correctly select Save and Close located in the File Menu to return to the startup screen.

Local Scanner Set Up as Remote Scanner

Background: The OMNIA is capable of interfacing with both an internal and external Scanner controlled locally by the OMNIA tester, or with a remote Scanner which is controlled by the Autoware software through a direct connection to the PC. When incorporating a Scanner into your testing procedure, it is important to define whether Autoware should treat the Scanner as a local Scanner or a remote Scanner. If you have selected that your Scanner is to be controlled remotely and the Scanner is actually an internal or external Scanner that is controlled locally by the OMNIA you will receive an error message.

Solution: In order to solve this problem you will need to reconfigure your Scanner settings.

From the startup screen select Setup System Parameters located in the Window Menu.
The first thing to do is disable the remote Scanner configuration. Click the Remote Scanners tab at the top of the screen.
Using the mouse, scroll through the arrows next to the heading “Number of Remote Scanners” until the number is 0. You have now disabled the remote scanner configuration.
Next you must enable the proper local Scanner configuration. Click the Primary Unit tab at the top of the screen. The bottom-most field edits the Scanner parameters.
Using the mouse, click on the up and down arrows to scroll through the different Scanner configurations until you find the one that corresponds to your Scanner configuration (none, 1 x 8 channel, 2 x 8 channel).
Select Save and Close located in the File Menu to return to the startup screen.

Error #1 - Error with command "FL1" - Event Register = 0

Incorrect DUT HV setup

Solution: In order to solve this problem you will need to make sure that the DUT-HV parameter is consistent in both OMNIA’s hardware and Autoware’s software.

From the startup screen select Setup System Parameters located in the Window Menu.
Under the Primary Unit tab, make sure that the box next to DUT-HV Setting is checked.
Select Save and Close located in the File Menu to return to the startup screen.
Exit the Autoware program by selecting Exit Autoware from the File Menu.
From the Main Menu on the OMNIA’s LCD screen, press the softkey corresponding to Setup System.
From the Setup System Menu press the softkey corresponding to Hardware.
Toggle the DUT-HV Setup parameter until it is set to ON.
Press the Exit key twice to return to the Main Menu.
Now that both the hardware and software DUT-HV Setting parameters are configured properly you may run the Autoware software normally.

Error #1 - Error with command "SP" - Event Register = 16

Auto-Offset Error (GC/GB)

Error – 1073807202

Error - 1073807302

Old NI-VISA Error

Go to your PC’s control panel and locate the old NI-VISA runtime engine (the old version is 2.6.1).
Uninstall the old NI-VISA runtime engine.
Once the uninstall is completed, go to the Autoware Updates on the Associated Research website:
https://www.arisafety.com//products/software-solutions/software-updates/
The Autoware Updates have a new NI-VISA runtime engine built in. Run the update and the new NI-VISA will be installed.NOTE: If you are unable to update the version of Autoware, you will need to get the NI-VISA update directly from the National Instruments website. Select the version that matches with your PC’s operating system: http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/catnav:du/q/NI-VISA/