Warning

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

Asycube Firmware 6

Asycube Firmware 6.2.2

Released on 2021-08-12

Tip

This release note only concerns the Asycube 240,380 and 530.

This release adds two new features and fixes some bugs.

This firmware version is compatible with all Asycube.

New features

Add purge feature

The Asycube can handle the purge mechanism, by controlling the motor (with a P1 command to open the flap, P0 to close it) and reading the sensor state (P? command). Please refer to the documentation for more information.

Resolved issues

Deactivate the inputs to trigger a sequence

By default, the two digital inputs are deactivated and don’t trigger a sequence anymore. Please refer to the documentation to activate or deactivate the inputs.

Bug fix ‘Modbus HR_FLASH_OPERATIONS’

You can trigger the flash memory saving operations via Modbus without error. The bug was related to the bits 0b0001 (Flass All in memory) and 0b1000 (Flash Vibration Set) on Modbus HR_FLASH_OPERATIONS (address 32).

Bug fix ‘Sequence triggered by inputs’

You can trigger a sequence with an input even if the sequence contains a purge action.

Support impact

An upgrade from the previous firmware version will deactivate the inputs to trigger a sequence. You can reactivate them if needed.

Asycube Firmware 6.2.1

Released on 2020-11-03

Tip

This release note only concerns the Asycube 380 and 530.

This release fixes one bug.

This firmware version is compatible with all Asycube.

Resolved issues

Bug fix ‘The purge motor doesn’t move to its zero position’

The purge motor zero position has been slightly shortened to allow optimal closure of the purge flap.

Asycube Firmware 6.2.0

Released on 2020-09-11

Tip

This release note only concerns the Asycube 380 and 530.

This release adds one new feature.

This firmware version is compatible with all Asycube.

New features

Add purge feature

The Asycube can handle the purge mechanism, by controlling the motor and reading the sensor.

Asycube Firmware 6.1.0

Released on 2020-04-17

Tip

This release note only concerns the Asycube 380 and 530.

This release adds two new features and fixes one bug.

This firmware version is compatible with all Asycube.

Improvements

Remove the 100ms activation delay

The 100ms activation delay has been removed thanks to a transient phase at the beginning of the vibration. The 100ms activation delay is only needed for the first vibration after power-up or an alarm to limit the peak current consumption.

Improve the zero-position repeatability

The zero-position of the platform after a vibration has a better repeatability thanks to a transient phase at the end of the vibration.

Resolved issues

Bug fix ‘Actuator overheating without 24VA s-power’

The overheating monitoring was incorrect when the 24VA s-power was not connected/active.

Asycube Firmware 6.0.0

Released on 2019-12-06

Tip

This release note concerns the Asycube 50, 80, 240, 380 and 530.

This release is the first official release of the Asycube530V2.

Resolved issues

Bug fix ‘Er0016 blocking’

This fix prevents blocking the communication in special conditions (continuous hardware digital input trigger with an unconfigured sequence).

Incompatibility

This firmware version is compatible with all Asycube 50,80,240 and 380. Concerning the Asycube 530, this firmware is designed for the Asycube530V2 and is not compatible with the the Asycube530V1 because the electronics is different.

For information, the main differences between this Asycube530V2 v6.0.0 firmware version and the Asycube530V1 v4.1.0 firmware version are the following:

Major adaptation to the Asycube530V2 electronics (actuator driver, over-temperature management, power supply management, etc.)
Addition of a 100ms start-up delay before the vibrations to reduce the peak current consumption
Better IP address management with a different default IP address for each OEM customer
Bug fix ‘non configured vibration set’ makes the UV command more robust
Bug fix ‘Er0016 blocking’ prevents blocking the communication in special conditions