- Aug 03, 2020
-
-
Martin Killenberg authored
- tests still failing - modifications incomplete - cleanup needed
-
- Jul 31, 2020
-
-
Martin Killenberg authored
- Initial values are sometimetimes only propagated in the first run of the main loops, not in prepare. If other modules are waiting for it they cannot enter their main loop. That's why all threads have to be started first, and only the it is waited for all of them to enter testable mode.
-
- Jul 28, 2020
-
-
Martin Killenberg authored
testProcessVariableRecovery: waiting for device to be opened avoids race conditin with runtime error
-
- Jul 21, 2020
-
-
Jens Georg authored
Only the blocking read in wfnd TEs will update the module's version
-
Jens Georg authored
This reverts commit bc329233.
-
Jens Georg authored
We propagate the version to the module on any read, if it is on an accessor with wait_for_new_data and there is new data (for readNonBlocking/readLatest)
-
- Jul 14, 2020
-
-
Martin Killenberg authored
- recoveryLock now protects the whole critical section - activateAsyncRead() is called on the device
-
- Jul 13, 2020
-
-
Martin Killenberg authored
-
Martin Killenberg authored
-
- Jul 09, 2020
-
-
Martin Killenberg authored
-
Christoph Kampmeyer authored
For receiving variables, the validity should be faulty after construction, see data validity propagation spec 2.6.1.
-
Martin Killenberg authored
restored write functionality of MetaDataPropagatingRegisterDecorator in case of locally set faulty status (DataValiditySpec 2.1.5)
-
Christoph Kampmeyer authored
Removed obsolete localValidity.
-
Christoph Kampmeyer authored
-
- Jul 08, 2020
-
-
Christoph Kampmeyer authored
Removed obsolete localValidity.
-
Christoph Kampmeyer authored
-
Martin Killenberg authored
- Removed extra exception handling from TriggerFanOut. It is all done by the ExceptionHandlingDecorator - ExceptionHandlingDecorator does not drop out of testable mode until the device is initialised.
-
- Jul 07, 2020
-
-
Martin Killenberg authored
- Removed extra exception handling from TriggerFanOut. It is all done by the ExceptionHandlingDecorator - ExceptionHandlingDecorator does not drop out of testable mode until the device is initialised.
-
- Jul 06, 2020
-
-
Martin Killenberg authored
-
Martin Killenberg authored
-
Martin Killenberg authored
wip: changed constructor of ExceptionHandlingDecorator to have a VariableNetworkNode as argument instead of a bunch of details
-
- Jul 03, 2020
-
-
Christoph Kampmeyer authored
It is now inferred from the TransferType in doPostRead of the MetaDataPropagatingRegisterAccessor, if the owning module's version number gets updated.
-
- Jul 02, 2020
-
-
Martin Killenberg authored
-
Martin Killenberg authored
-
Martin Killenberg authored
-
Martin Killenberg authored
-
Christoph Kampmeyer authored
Rearranged processing of fanouts and their consuming nodes. A list of consuming nodes and implementations is passed to the fanout constructors, so the nodes don't have to added later. This resolves conflicts in the order in which accessors are decorated and added to the fanouts. FanOut constructors could still use refactoring.
-
Martin Killenberg authored
-
Martin Killenberg authored
-
Martin Killenberg authored
- removed ExceptionHandlingDecorator::setOwnerValidity()
-
- Jul 01, 2020
-
-
Christoph Kampmeyer authored
-
Martin Killenberg authored
-
Martin Killenberg authored
- removed DeviceModule::waitForRecovery() - ExceptionHandlingDecorator is throwing to skip transfers
-
Christoph Kampmeyer authored
Ongoing refactoring. Consuming fanout works again.
-
Martin Killenberg authored
This reverts commit d025bb5a.
-
Martin Killenberg authored
-
Christoph Kampmeyer authored
-
Martin Killenberg authored
-
- Jun 30, 2020
-
-
Christoph Kampmeyer authored
-
- Jun 29, 2020
-
-
Martin Killenberg authored
-