Tags give the ability to mark specific points in history as being important
-
04.12.00
2d069db9 · ·New MINOR release 04.12.00 Changes since 04.11.01: - feat: handshake for PZT4 load relays - fix: chrome bars
-
04.11.01
580edb73 · ·New PATCH release 04.11.01 Changes since 04.11.00: - fix: don't link test against the selected adapter
-
04.11.00
73ad7866 · ·New MINOR release 04.11.00 Changes since 04.10.00: Adapt to ApplicationCore 4 BREAKING CHANGE: Config file name changed, as it is now auto-generated from the application instance name. - chore!: don't instantiate config reader - fix: remove outdated header - fix: required CMake version must come first - fix: code formatting in CMakeLists.txt -
04.10.00
7161e231 · ·New MINOR release 04.10.00 Changes since 04.09.00: - feat: time base multiplier
-
04.09.00
ec264a8c · ·New MINOR release 04.09.00 Changes since 04.08.01: - feat: Overall operational status
-
-
04.08.00
2185816f · ·New MINOR release 04.08.00 Changes since 04.07.00: - fix: write double buffering - fix: compiler warnings - chore: adapt to API changes in DeviceAccess 03.14 - chore: Port project to cmake imported targets.
-
04.07.00
3eb53014 · ·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
f0fc4223 · ·New MINOR release 04.06.00 Changes since 04.05.00: - feat: state machine seed device error - feat: internal trigger
-
04.05.00
4c35f246 · ·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
9d7998f5 · ·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
cc4e6a06 · ·New PATCH release 04.03.01 Changes since 04.03.00: - increase patch level to allow re-packaging
-
04.03.00
4c287180 · ·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
e5404912 · ·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
10528792 · ·Initial tag 04.01.00 First ApplicationCore based test release. - Feature-even with the 03.09. version of the server