Document toolboxDocument toolbox

SA380 RailDAQ master to SA380 RailDAQ slave

Owned by Janos Vaczi (Unlicensed)
Last updated: Feb 07, 2017
3 min read

Since 4.9.5 the protocol between SA380 master and SA380 slave units has been changed. The new protocol needs some extra configuration.

Step-by-step guide

Setting up SA380 master unit:

  1. Set local IP address. (The slave units will be needed to be configured to connect to this IP address.)


    Press Menu:

    Press Configuration and enter passcode:

    Press Set local IP:

    Enter appropriate master IP address, subnet mask and default gateway. The default – and most usual – settings are:
    IP address: 10.0.1.1
    Subnet mask: 255.255.252.0
    Default gateway: 10.0.0.138
    Press Enter when finished.

  • Enter each slave unit's serial number to tell the master unit what slave data to anticipate.
    Go to configuration menu:

    Press RailDAQ master button:

    Enter the SA380 slave units' serial numbers, which are written onto the slave unit box or can be read on the touchscreen in the About box:

    When upgrading previous version of master/slave configuration, Slave 1 SA380 unit's IP address looks like: 10.0.2.1, Slave 2 is 10.0.2.2 etc.
    Slave IP addresses:

- Slave 1: 10.0.2.1

- Slave 2: 10.0.2.2

- Slave 3: 10.0.2.3

- Slave 4: 10.0.2.4

- Slave 5: 10.0.2.5

- Slave 6: 10.0.2.6

- Slave 7: 10.0.2.7

Once finished entering all belonging slave units, press Done. The logger will restart.

Setting up SA380 slave unit:

  1. Set local IP address. The slave must be able to connect to the master unit. There is no special restriction on the slave unit's IP address.
    The method is the same as for the master unit.

  2. Enter the master SA380 logger's IP address to make the slave unit to connect to the master.

    Press Menu:

    Press Configuration and enter passcode:

    Press RailDAQ slave:

    Press Local master:

    Enter the SA380 master's IP address.

    Press Done. Logger will restart.

Once the master and slave units are both configured, the communication can be verified:

Slave unit should display where it tries to connect to and Status is something other than an error message:

Master unit normally show slave unit activation: