Release 1.4.1

This is a bugfix release that addresses the following issues:

• Add prescalers 3–7 to output option in CSS panels for the MTCA-EVR-300. (c2bccbe)
  This only affected the panels, not the IOC.
• Avoid invalid values for Qp-1 in sy87739l-convert.py. (70517e8)
• Avoid compile-time errors when using recent versions of GCC by making sure that <stdexcept> is included correctly. (2760ed1)
  In particular, this fixes issues that were discovered when compiling on Ubuntu 24.04.

None of these issues affects the IOC, so there is no immediate need to upgrade if version 1.4.0 is working for you.

Release 1.4.0

This is a feature release that brings the following changes:

• Avoid failure of record initialization when device is not connected (41d73ce).
  Before, when an output record’s value could not be initialized during IOC startup due to the device being offline, the whole record initialization would fail, thus resulting in the record not working correctly even when the device came back online at a later point in time. Now, the record’s value will simply remain undefined (and thus have an INVALID alarm severity), but the record initialization routine will complete, thus later processing of the record is possible when the device is back online.
• Replace current panel instead of opening a new tab in CSS GUI (1716127).
  When using the CSS / BOY panels, the various sub-panels (e.g. outputs, etc.) will replace the current panel instead of opening in the new tab. This way, the CSS workspace is not cluttered when navigating through the various panels of a single device.
• Support for the VME-EVR-230 (0b3a8f5).
  Now, the VME-EVR-230 is fully supported (in addition to the VME-EVR-230RF, which has been supported for a long time).
• Updated MRF kernel module (d2c9934, f9223e3, 4e756a2, 5049bc3).
  The MRF kernel module has been updated with changes from upstream. In addition to that, changes have been made to make the module compile with recent Linux kernels (up to 6.2.0).
• Bugfix for the Firmware:Version record (cf272f5).
  Before, the lower 16 bits of the FPGA firmware register were used, now only the lower 8 bits are used.
• Provide additional information about firmware (4ce693e).
  For the EVR, there are new records Firmware:FirmwareID, Firmware:RevisionID, and Firmware:SubreleaseID. Firmware:RevisionID replaces Firmware:Version. The old record is still supported at the moment, but is going to be removed in version 2.x of the device support.
• Major improvements for the MTCA-EVR-300:
  • The mapped memory segment is now larger, so that the memory for SFP diagnostics is included (87d389d).
    This means that SFP diagnostics data is now available for this device as well.
  • Delay compensation can now be configured (62933fd).
  • Backplane outputs can now be configured and a second mapping source can be chosen for all outputs (2225503).
• Some minor improvements to CSS panels and the documentation.

Release 1.3.1

This is a bugfix release that fixes one bug:

Bugfixes:

• Fix initialization of SFP module alarm limits (31cbd23). This bug only had the effect that the alarm limits on the analog records were not initialized correctly. As the actual alarming is done by checking alarm flags, this did not affect the alarm state, but was just an inconvenience when displaying alarm limits on the client.

Release 1.3.0

This release brings one new features and some minor improvements and bugfixes.

New features:

• Add records for storing used-defined descriptions (5a4d215). Please note that you have to make a choice about the record type used for descriptions when compiling the device support. Please refer to the installation instructions for details. Typically, this feature is only useful when also using Autosave, because the descriptions are not stored in hardware registers and thus will not survive an IOC restart unless they are preserved by Autosave.

Improvements:

• Show delays and pulse widths for pulse generators in microseconds in the CSS panel (93412e4).
• Delete an unused CSS panel (173d0b8).

Bugfixes:

• Fix compilation with older releases of EPICS Base (292569e). Version 1.2.0 introduced a bug that caused an error when compiling against a version of EPICS Base that did not define the aodset data structure yet. This problem is now fixed.
• Fix more “Write access denied” Javascript errors in the CSS panels (9b2d376, ab06439).
• Write EVG interrupt configuration as part of “Write all” action (40a61d0).
• Make SFP part number widget in CSS panel refer to the correct PV (f37dda8).

Release 1.2.0

This release brings two new features and several minor improvements.

New features:

• Preheat cache during initialization for UDP/IP devices (93e9ee7). This significantly shortens the IOC startup time for IOCs controlling more than one device.
• Diagnostic information for SFP modules (a26bc40). Please refer to the updated documentation for a list of PVs.

Improvements:

• Simplify mass configuration of univ. inputs and outputs (0687ff9).
• Add usage information to IOC shell functions when compiling against a recent release of EPICS Base (caa6824).
• Support IOC shell error signaling through iocshSetError when compiling against a recent release of EPICS Base (7fc1ab0).

Bugfixes:

• Avoid Javascript error in CSS / BOY panels when PVs are not writable (4019cf8).
• Fix compiler warning about non-virtual destructor (35e48e8).
• Set status to READ_ALARM instead of WRITE_ALARM when processing of a waveform record that acts as an input fails (4a154f3).

Release 1.1.0

This is a feature release that brings two improvements:

• The configuration macros for specifying which universal output modules are installed and whether they support setting a fine delay are now optional. This means that they only have to be specified when the corresponding module is installed because they will default to not installed.
• It is now possible to specify custom values for the enum (mbbo) record that configures the SY87739L fractional divider chip that is used by the internal clock generator of the EVGs and EVRs. Please refer to the “Clock generator configuration” section in docs/using.md for details.

Release 1.0.1

This is a maintenance release that provides two minor bugfixes:

• When a record is processed, but its device support has not been properly initialized, the record is now flagged with an INVALID alarm. Before, the processing would fail (and an error message would be written to the IOC's output), but the record's alarm severity would remain at NO_ALARM.
• When enabling software events on the EVG by writing to $(P)$(R)Event:Soft:Enabled, an event would be send if an event code had earlier been written to $(P)$(R)Event:Soft:EventCode. This could even happen across IOC restarts.
  For example, writing an event code, restarting the IOC and then enabling software events would cause the last set event code to be sent. This was particularly problematic because writing to $(P)$(R)WriteAll causes $(P)$(R)Event:Soft:Enabled to be processed, so the last event code would be sent again if software events were enabled and $(P)$(R)WriteAll was triggered.
  This bug is fixed now. Only writing to $(P)$(R)Event:Soft:EventCode will cause an event code to be sent, writing to $(P)$(R)Event:Soft:Enabled will only change the enabled flag without ever sending an event code.

Release 1.0.0

This is the first public release of the MRF device support for EPICS.

Don't be fooled by the low version number. This device support has been in use at KIT for years, this simply is the first version that is released publicly.