- Jan 16, 2025
-
-
Martin Christoph Hierholzer authored
The SharedDummy backend was crashing with a boost::interprocess::lock_exception when a previous instance was interrupted in the wrogn place. This is now fixed by catching the exception and removing the shared memory segment (which is then broken anyway).
-
- Jan 06, 2025
-
-
Jens Georg authored
-
- Dec 20, 2024
-
-
-
* existing problem: even after board was removed/shut down, reading normal (not dma) pci registers does not throw an error from QtHardMon. To fix it, check state of device node after read and write of mmaped pci bar * existing problem: when triggered by user interrupts, device error is never noticed, in particular when device does not send events anymore To fix it, add timer events for periodic devide node check * existing problem: exceptions from event handler thread never caught To fix it, add try/catch around boost::asio processing loop
-
- Dec 18, 2024
-
-
Martin Christoph Hierholzer authored
The XDMA backend called internally close() when a recovery of an exception was attempted. In particular if the recovery was still unsuccessful, the device was then left in the closed state leading to logic_error exceptions in subsequent read/write operations. This caused ApplicationCore applications to terminate immediately after an exception of an XDMA device was seen. This is now fixed by using a dedicated flag for the backend opened status which is independent of the underlying interface status.
-
- Dec 09, 2024
-
-
Martin Christoph Hierholzer authored
-
- Dec 06, 2024
-
-
Martin Christoph Hierholzer authored
This is required to terminate ApplicationCore applications properly when a poll-type input (connected internally) is waiting for initial values (which uses a blocking call to future_queue::pop_wait()).
-
Martin Christoph Hierholzer authored
-
- Dec 03, 2024
-
-
Martin Christoph Hierholzer authored
-
- Nov 27, 2024
-
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-
- Nov 26, 2024
-
-
Martin Christoph Hierholzer authored
-
- Nov 20, 2024
-
-
Martin Killenberg authored
-
- Nov 14, 2024
-
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-
- Nov 11, 2024
-
-
Martin Killenberg authored
fix(project-template): (re-)enable DOT support in Doxygen
-
Martin Killenberg authored
-
- Nov 08, 2024
-
-
Martin Christoph Hierholzer authored
These are usually not really used, since we do not have backends with a string raw data type (yet), but it is very convenient to have the interfaces of the accessors identical, since otherwise generic code does not instantiate when using getAsCooked/setAsCooked.
-
Martin Christoph Hierholzer authored
This is a convenient way to get to the NDRegisterAccessor shared pointer (with the right UserType), without the need for dynamic casting the TransferElement obtained via TransferElementAbstractor::getHighLevelImplElement()
-
- Oct 28, 2024
-
-
Martin Killenberg authored
-
- Oct 24, 2024
-
-
fiveisgreen authored
-
- Oct 21, 2024
-
-
this can simplify user's code
-
- Oct 18, 2024
-
-
Martin Christoph Hierholzer authored
-
- Oct 14, 2024
-
-
Martin Killenberg authored
-
Martin Killenberg authored
fix(project-template): find pattern in coding style check
-
Martin Killenberg authored
-
Martin Killenberg authored
-
- Oct 08, 2024
-
-
Martin Christoph Hierholzer authored
-
- Oct 04, 2024
-
-
Martin Christoph Hierholzer authored
-
- Sep 27, 2024
-
-
Dietrich Rothe authored
* improvement: acc.read throws if in ReadAnyGroup if the accessor is already in a ReadAnyGroup, that must be used for reading
-
- Sep 19, 2024
-
-
Martin Christoph Hierholzer authored
-
- Sep 18, 2024
-
-
Christian Willner authored
-
- Aug 30, 2024
-
-
Martin Christoph Hierholzer authored
-
- Aug 28, 2024
-
-
Martin Christoph Hierholzer authored
update project template
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-
- Aug 19, 2024
-
-
Martin Christoph Hierholzer authored
-
- Aug 08, 2024
-
-
Martin Christoph Hierholzer authored
The version of EPICS (3 or 7) is now defined by which EPICS version is used by the found adapter. There are no distinct names any more, also EPCIS3 is effectively phasing out.
-