-
04.07.00
New MINOR release 04.07.00 Changes since 04.06.00: fix: only turn on FF and FB when DC voltage reached for the first time API BREAING CHANGE: New state ENABLING * The state maching does not directly go from DISABLED to ENABLED, but DISABLED->ENABLING->ENABLED * The transition to EBABLED is happening when the DC voltage ramp is ready * FF and FB are only active in ENABLED
-
04.06.00
New MINOR release 04.06.00 Changes since 04.05.00: - feat: state machine seed device error - feat: internal trigger
-
04.05.00
New MINOR release 04.05.00 Changes since 04.04.00: - fix: deprecation warnings - fix: custom table switch not taken into account The switch wheter to use a custom feed forward table was not immediately taken into account because it was a poll parameter. It was only processed parasitically if on of the other parameters changed. - fix: make dacVoltage float Since the dacVoltage now is converted to volts it's not integer any more. Also the dacVoltageOffThreshold has to be float because it's less than 1 Volt now.
-
04.04.00
New MINOR release 04.04.00 Changes since 04.03.01: - Improve cmake to add headers files to the library. - Adapt to changes in ApplicationCore 3.0. - Rejection message contains info why still disabling - Separate trigger into separate device
-
04.03.01
New PATCH release 04.03.01 Changes since 04.03.00: - increase patch level to allow re-packaging
-
04.03.00
New MINOR release 04.03.00 Changes since 04.02.00: -hwProtectionReset is written by the channel state machines -- The first channel state machine which is reset clears the flag on the device -- During disabling, a configurable amount of hw protection monitor errors is ignored because the HW takes several triggers until the flag is cleared - add RebootWatchdog
-
04.02.00
New MINOR release 04.02.00 Changes since 04.01.00: - improve test consistency The logical name mapping used for testing is now much closer to the real confi- Use ctk::Boolean -- All variables which are conceptually bool now use ctk::Boolean -- Part of the changes were necessary because ApplicationCore now treats 1-bit variables as ctk::Boolean, and the types in the server have to be consistent -- Causes history incompatibilities (at least to for previous piezoctrl4)
-
04.01.00
Initial tag 04.01.00 First ApplicationCore based test release. - Feature-even with the 03.09. version of the server