Asycube - Asyril SA
Programming Guide
©
Copyright Asyril S.A.
000.101.572
Version : A1
63/83
6.3.2. Status Holding Registers (Read-only zone, offset=64)
The Status Holding Registers presented in Table 6-2
are used to get information on the Asycube. Examples: remaining vibration time, error state, …
Address
(decimal)
Holding Register name
Read/
Write
Data Range
Comments
64+0
HR_MODBUS_STATUS
R
0 to 15
The 4 first bits represents the errors status: Asycube Modbus errors status,
Internal Modbus communication error status, Asycube warnings status and
Asycube alarms status. More information in Section 6.4.
64+1
HR_MODBUS_ERROR_CODE
R
0 to 65535
The first byte (mask 0x0F) of this Holding Register contains Asycube Modbus
error code, while the second byte (mask 0xF0) contains the Internal Modbus
communication error code. More information in Section 6.4.2.
64+2
HR_WARNINGS
R
0 to 255
This Holding Register contains the Asycube warning code. More information in
Section 6.4.3 and Section 5.4.14.
64+3
HR_ALARMS
R
0 to 255
This Holding Register contains the Asycube alarm code. More information in
Section 6.4.3 and Section 5.4.15.
64+4
HR_MODBUS_PLATFORM_STATUS
R
0: DONE
1: BUSY
2: ERROR
This Holding Register gives the status of either the platform vibration trigged with
HR_PLATFORM_VIBRATION_TRIG or the platform centering trigged with
HR_PLATFORM_CENTERING_TRIG.
The transition DONE->BUSY occurs on the trigger rising edge if the data is
correct.
The transition DONE->ERROR occurs on the trigger rising edge if the data is
incorrect (e.g. index is out of range).
The transition BUSY->DONE occurs as soon as the vibration ends.
The transition BUSY->ERROR occurs if an Internal Modbus communication
error (See Section 6.4.2) before the vibration starts.