-
01.09.00
New MINOR release 01.09.00 Changes since 01.08.01: - fix!: property names have dots - fix: project name BREAKING CHANGE: Variable names and/or hierarchies have changed.
-
01.08.01
New PATCH release 01.08.01 Changes since 01.08.00: - fix: required cmake version - chore: change application core and control system adapter to imported targets clean up unused dependency on xml parser and explicit doocs
-
01.08.00
New MINOR release 01.08.00 Changes since 01.07.01: fix: add MESSAGE to fred module The standard property MESSAGE has been removed from DOOCS locations and it's introduuced in the server for backward compatibility. Requires DOOCS 23.06 feat: add jenkinsfile chore: adapt to ApplicationCore 3
-
01.07.01
New PATCH release 01.07.01 Changes since 01.07.00: - Properties are invalidated on each disconnect (voluntary or through fault) (solves #7476) - Send an empty error message at server start to get rid of old and stale error messages (solves #7539) - Server not crashing on std::exceptions any more (solves #7475) - Set and clear invalidity flag for all data which is read from the server (solves #7540)
-
01.07.00
New MINOR release 01.07.00 Changes since 01.06.01: * Added property AUTOPWRALARM
-
01.06.01
New PATCH release 01.06.01 Changes since 01.06.00: - Fixed data validity for fw and cpld version - Fixed lastFredReset -- data validity is correct -- value is updated when the fred connects to the server - Data validity for XP watchdog properties is set correctly
-
01.06.00
Release: 01.06.00 Changelog since 01.05.00 - New config file scheme: - ServerConfiguration.xml Specifies number of fred locations for the server and details on their network hostnames. - FredApp-DoocsVariableConfig.xml Maps the fred nework hostnames to doocs locations. - Server now clears the xport watchdog statistics on making its first connection to a FRED - Channel voltages, Fan details and boxstate info are invalidated when server is not connected to a FRED.
-
01.05.00
New MINOR release 01.05.00 Changes since 01.04.00: * commit 0b042f1bd10e0d88d848140e58812dead09ec027 | | increase minor version for release. | * commit d515f5338b3cff50657d237cdbd7eebe022ba95a | | added: NAME property for channel. |
-
01.04.00
New MINOR release 01.04.00 Changes since 01.03.00: - Support for Uptime (time since last fred reboot) -- Property TIMESTAMP.LAST.FRED.RESET - Support for XPortWatchdog -- Proporties XPORT.POWERCYCLES and TIMESTAMP.LAST.XPORT.POWERCYCLE - Depends on FRED library version 2.1 - Implements redmine #4881
-
01.03.00
New MINOR release 01.03.00 Changes since 01.02.00: - fred: Add OperationMode for channels - added test server config for localhost and mskfreddevboard1
-
01.02.00
New MINOR release 01.02.00 Changes since 01.01.01: - Made compile with the latest ApplicationCore version (backward compatible, uses ControlSystemModule without argument) - Remove printing connection errors to log file, instead add a property which shows the error message. - Adapted to changed project name of the fred library
-
-
01.01.00
New MINOR release 01.01.00 Changes since 01.00.02: - Added error handling in case on/off/clearAlarms/powerIndependentOnly are called when the fred is offline. - Only print error messages once when they appear, and when the error state goes away. - Fans are now read out. - Fixed logic that connection status is checked in each update. Now the server properly re-connects when the device becomes available again and on server start - Renamed POWER.INDEPENDENT.ONLY to SWITCH.INDEPENDENT_ONLY for consistency with SWITCH.ON/OFF (causes minor version increase) - Exceptions are caught only in the mainLoop, which prevents server crashes when a device goes offline.
-
-
-
01.00.00
tagged to release.
-
-
00.03.01
tagged to release patch.
-
00.03.00
tagged to release supporting DAQ.
-
00.02.00
changed: Each location now runs in a separate thread. This should solve the problem that server becomes non responsive if one location is blocked.