APPNOTE: Testing the communication path to a Logger.

APPNOTE: Testing the communication path between a computer and a Logger.

Last reviewed: January 14, 2011
Article ID: 110112sab

The information in this article applies to:

The Termview text terminal utility shipped with Pronto for Windows Revision 5.37 and later.

Target Audience.

This article is aimed at:

Technical Support Staff, Distributors and Advanced users of the Ranger Power Master Products; PM7000, PM6000, PM3000, PM2000, PM1000 and AP310.

Summary.

Random failures while communicating with a Ranger data logger are often caused by an unreliable or noisy commuincation path. Although the communication protocol used does have error detection and correction there is a limit beyond which it is unable to compensate and errors will occur.

Shipped with Pronto for Windows is a utility called TermView.exe that provides various communication path testing routines, this application note provides instructions on the use of the Modbus Loop Back function.

Running the Loop back test.

Follow these steps:
1) Connect to the Logger using TermView (see APPNOTE: Get started using TermView.exe, the Ranger text terminal utility )
Once the logger prompt is displayed:
termview open showing the prompt from the logger

termview open showing the prompt from the logger

2) From the TESTS menu select the item MODBUS LOOP BACK, the following dialog will appear.

loopback settings dialog with default settings

3) This shows the default settings, accept these and start the test by clicking OK.

4) Let the test run for a few seconds then from the TESTS menu select the item STOP TEST or click on the button

5) After the test has completed look in the output for the highlighted text:

:01080000000102030405060708090A0B0C0D0E0F101112131415161718191A1B1C1D1E1F07 :01080000000102030405060708090A0B0C0D0E0F101112131415161718191A1B1C1D1E1F07 :01080000000102030405060708090A0B0C0D0E0F101112131415161718191A1B1C1D1E1F07 :01080000000102030405060708090A0B0C0D0E0F101112131415161718191A1B1C1D1E1F07 :01080000000102030405060708090A0B0C0D0E0F101112131415161718191A1B1C1D1E1F07 :01080000000102030405060708090A0B0C0D0E0F101112131415161718191A1B1C1D1E1F07 :01080000000102030405060708090A0B0C0D0E0F101112131415161718191A1B1C1D1E1F07 Elapsed 3.7 one way bytes 2387(raw), 992(net) byte rate 641(raw), 266(net) errors 0 BER 26257 Response time (millisecs), max 22 min 18 avg 19.5

At the end of this line is the number of errors that were detected, this should be zero or a small number.

6) Finally if you wish to further stress the communication channel, select TESTS - MODBUS LOOP BACK again and
    a) Change Select size of data to 249,
    b) Set the checkbox Put packet number in first byte.
    c) Reduce the inter-packet delay to zero.
And click on OK.

Notes:

On high latency communication paths, for example those using a cellular modem or over a long distance (such as transatlantic) it may be necessary to increase the Packet Timeout to 2000 milliseconds or so.

References

APPNOTE: Utilities Installed with Pronto for Windows.

Back to Knowledge Base index

THE INFORMATION PROVIDED IN THE PRONTO FOR WINDOWS KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. OUTRAM RESEARCH LTD DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL OUTRAM RESEARCH LTD OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF OUTRAM RESEARCH LTD OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.