Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Overview

This guide describes how to connect a master slave network of loggers.

  • An SA380TX is the master logger.
  • loggers are connected together using RS485.
  • Up to 7 devices can be slaved from a single SA380TX.
  • The TX can scan the bus on demand to auto-detect slaves.
  • Each slave device is identified by a unique identifier.

Connection Arrangement

Configuring an SA380TX-L as a slave logger

    1. Un-check the "Standalone" button in web config.

    2. For older loggers which don't have web config installed, using dPanel Desktop this can be achieved as below:


The VTI21 does not require any configuration.

SA380TX configuration

The SA380TX is configured using the following sequence of dialogues

  1. Enter the configuration screen
  2. Set the RS485 port for use with protobuf slaves:
  3. Ask the logger to auto-detect connected slave units. This will take approximately 10 seconds.
  4. review the connected slave units. Each unit is dispayed on its own button which will contain the slave type when known, and the units serial number. In the example below, the first unit is of unknown type, and the second is a slave SA380TX-L. The MPEC slave system automatically allocates channels and input types, so it is not necessary for complete slave type identification.
  5. Verify that the logger is connected to them. Each logger will be shown connected with the "+UnitActive: X" moniker where the X represents the logger number. Logger "0" is the SA380TX master.


Confirmation using the About Box

The about box can be used to display the status of slave loggers. This can be reached as follows:

 

This will bring up the about window which can give useful and immediate diagnostic information.

Loggers Connected Normally

The highlighted section shows master slave information, the number of slaves attached, their types and serial numbers. The communication state is also displayed against the slave number. This will iterate through a number of connection states. The following images show some typical failure states

All loggers disconnected

One logger is disconnected

  • No labels