Skip to content

Troubleshooting

  1. Problem: the numbers coming from the powermeter read 0, or an "E" for Error appears in the bottom right of the screen.

Resolution: the data transfer between the powermeter and the computer is failing. It may be any of the following; check each and correct it.

  1. The line voltage breaker on the powermeter is OFF (CB 5A).

  2. A data cable connector has come loose. Check the back of the computer and the back of the powermeter.

  3. The data cable is plugged into the wrong port. A computer may have several communication ports, so the connector must be on the port configured under File → Communication Setup and File → Device Setup.

  4. The settings under File → Communication Setup do not match the powermeter, for example:

  5. Port number

  6. Baud rate

  7. DataBit/Parity

  8. Stop bit

  9. Check that the communication parameters in the powermeter match those on the computer. (See the manual for the particular powermeter model.)

2. Problem: after running for a long time — about 20 days — historical graphs are very slow to appear.

Resolution: there are several possible causes.

  1. The machine's hard disk is low on free space. Delete unnecessary files.

  2. Defragment the disk with a tool such as Perfect Disk, or the defragmenter supplied with Windows, to tidy up the files on it.

3. Problem: can the computer be made faster still, to speed things up?

Resolution: add memory (RAM), or upgrade to a faster CPU.

4. Problem: entering the program displays "License File Not Found".

Resolution: contact your dealer to resolve this.

5. Problem: after upgrading to a new version, the tool bars are untidy and take up too much of the display.

Resolution: rearrange them with the mouse. The program saves the arrangement when you leave it and uses it next time.

6. Problem: after upgrading, the menu and tool bars are not visible.

Resolution: press Alt + F to bring the menu up, then right-click on an empty part of the menu to switch the tool bars you want on or off.

7. Problem: a Modbus device has been configured for reading, but the device does not appear in the data table.

Resolution: the device has not been opened for reading any values. Go back to File → Device Setup and enable P1, or whichever P entries you need.

8. Problem: entering the program raises the error "The ordinal nn could not be located in the dynamic link library xxxx.dll".

Resolution: the DLL named in the message is mismatched, or is not the latest version. Reinstall the program, or replace that DLL with the latest version.

9. Problem: the program does not run when started, with no error message at all.

Resolution: one of the DLLs is not the latest version, or is inconsistent with the others — CrashRpt.dll, for example. Overwrite it with the correct version, or reinstall the program. If you are running a trial version, it may instead mean the trial period has expired, so the program can no longer run.