Warning

You are reading an old version of this documentation. If you want up-to-date information, please have a look at 2024.6 .

Example of use

This section presents some examples showing how to control the Asycube through Modbus TCP in production mode. Use Asycube Studio interface to configure the vibrations parameters.

Set up the Modbus master (e.g. PLC)

  • Configure the Modbus master (=client) to communicate with the Asycube based on the Asycube communication parameters (See Configuration). 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.

  • 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.

  • Configure the Modbus master to alternatively write the Control Holding Registers and read the Status Holding Registers, with a cycle time of 10 ms.

Handle the Status and Control Holding Registers

Vibration, sequence, backlight, read/write parameter

Start a platform vibration

Monitor a platform vibration

  • Read the HR_MODBUS_PLATFORM_STATUS. If the value is ERROR, refer to the HR_MODBUS_STATUS for more information. A BUSY value means that the command has been understood and that the vibration has started.

  • Monitor the HR_MODBUS_PLATFORM_STATUS and wait for its value to get back to DONE, which means that the vibration is completed.

  • Or monitor the HR_PLATFORM_REMAINING_TIME to see the remaining vibration time. The value decreases to 0 when the vibration is completed.

Start and monitor a sequence

Stop a sequence currently running

  • Stop the sequence by changing the value of the trigger HR_SEQUENCE_HALT from 0 to 1.

Switch the backlight ON