Asycube - Asyril SA
Programming Guide
78/83
The data cannot be written because it is forbidden or the
index is out of range. An example would be selecting a
sequence (HR_SELECT_SEQUENCE) with a value out range
such as 27.
Table 6-7: Asycube Modbus error codes.
The second byte (mask 0xFF00) gives the internal Modbus communication error code (See
the value Error Bit in Table 5-2). The internal Modbus communication error
typically occurs when a vibration is trigged with incorrect parameters values. An example
would be trigging a platform centering (HR_PLATFORM_CENTERING_TRIG) while the value
of the X position (HR_PLATFORM_CENTERING_X) is out of range, such as 120%.
6.4.3. Asycube warnings and alarms
The Asycube has its own warnings and alarms. They can be read respectively in the Holding
Registers HR_WARNINGS (Address 66) and HR_ALARMS (Address 67). Their values are
explained in the Table 5-20 and Table 5-21.
6.5. Example of use
This section presents some examples showing how to control the Asycube through Modbus
TCP in production mode. We highly recommend using the Asycube HMI to configure the
vibrations parameters as described in the Asycube User Manual.
6.5.1. Set up the Modbus master (e.g. PLC)
Configure the Modbus master (=client) to communicate with the Asycube based on the
Asycube communication parameters (Section 6.1). Don’t forget to change your
master network settings (IP address, …).
Define a memory map of 16bits registers for data to be written in the Asycube. We
recommend creating as many registers as contained in the Control Holding Registers
(Section 0).
Define a memory map of 16bits registers for data to be read from the Asycube. We
recommend creating as many registers as contained in the Status Holding Registers
(Section 0).
Configure the Modbus master to alternatively write the Control Holding Registers and
read the Status Holding Registers, with a cycle time of 10 ms.