29
ATIM_ACW-D_UG_EN_V1.5
Functional description:
Imagine that you want to send three registers of PLC 1 and 3 registers of PLC 2 every 30 min:
The idea would be to store / write 3 registers of the PLC 2 via radio to the ACW-S in these registers
60000
to
60002
, for example every 15 min. Then the PLC 1 would write these registers to the ACW-S via RS232 / 485
in registers
60003
to
60005
by writing a 1 in register
60006
to trigger the sending of data on the Sigfox
network.
The ACW-B will be used here to provide local information from PLC 1 and 2. The ACW-B could be connected
to another PLC or to a simple control terminal. It would be enough for PLCs 1 and 2 to write to the ACW-S
registers
60009
/
60012
to
60062
to send ACW-B serial link information.
Configuration description:
The ACW-S will be configured in Modbus 'Slave' with the Modbus ID of your choice. Its radio parameters
must be the same as those of the ACW-A which is configured in bridge mode. Apart from your serial
configuration and radio settings (Bautrate, Channel identical to ACW-S), the default configuration is required
for the ACW-A.
The ACW-B meanwhile is configured in bridge mode but requires a radio configuration different from the
ACW-S (and thus also the ACW-B). Again, the default configuration is necessary except the radio (Baudrate,
Channel). To communicate with the ACW-B, the ACW-S radio settings (registers
60009
and
60010
) must be
identical to the ACW-B. This configuration can be sent once to the system startup or to each Modbus
communication.
Note:
When writing to registers
60012
to
60062
, the ACW-S will automatically change these radio
parameters (
60009
and
60010
) to transmit the local frame and will switch back to the radio parameters
configured with the ACW configurator to continue Modbus communication.
Note:
By default, the radio settings of the ACW-S registers are identical to the parameters configured with
the ACW configurator. So, if the ACW-A does not exist in the system, you can configure the ACW-B radio
parameters to the same values as the ACW-S and omit the radio configuration phase via Modbus. But in our
case, the Radio Modbus communication of the ACW-A can not work properly. The radio data (the payload
in the Modbus frame) is analyzed as a Modbus acknowledgment frame by the PLC 2.
