Tags

2.2.3

- minor cleanup, same as 2.2.2
- added systec detailed versioning readout for windows

2.2.2

tag 2.2.2 ready for production
-------------------------------
- some trailing fixes and cleanups since 2.2.1
- remains stable also with 1e6 frames per port sent, with all 16ports of an anagateFZ connected on the same bus
- conveniently tested to high confidence
- wrap up of validation reports stability, performance and versions still in progress
- alma9.3 for sock, otherwise (almost) any linux and alma9 for anagate, windows2022, windows2019

2.2.1intermediate

frame rate delays and diagnostics

2.2intermediate

builds for cc7, alma9, w2019 and w2022
api versioning corrected in CI/CD and VMs
new functionality implemented in CanModule
new test NOT YET implemented in canx
no windows-docker yet

2.1.0prerelease

this is tag 2.1.0prerelease
from merge devel-2.0.25
marks the many changes. This is still backwards compatible though, but it is more than just bugfixes, new functionality has been added.
validation "all signals" testing for w2022 done
w2019, cc7 a,d cal9 in progress for a second round
report for signals in progress
lots of changes

2.0.24intermediate

validation report https://edms.cern.ch/document/2827478/1
sticks with CanModule::2.0.24intermediate

build01

- builds against old vendor libs 2016 for cc7, cs9, w2016 , w2019 (jenkins)
- new canmodulevendorlibs structure

intermediate2.0.20

- qa fixes

2.0.19

- gettimeofday/C++ chrono cleanup to modernize code
- fixing OPCUA-2691: mini release to fix getPortStatus() for "sock", provide a more direct approach
  Now it just goes out directly and does a can_get_state() each time it is invoked, and wraps the result into the unified port as before status.
  port status is NOT part of the statistics any more, suppressed all code related.
  port status is updated each call, not each 10th call or after 10 seconds
  frankly, this makes more sense as well, must have had a bad day when coding the previous implementation ;-)
  not really tested, issue stays open until the OPCUA can open server confirms it. Pretty simple though, should work as-is.

2.0.17

2.0.17 stable - ready for production (except peak@windows)

    build chain cleanup
    out-of-source builds
    generated file VERSION.h into ./build/generated, only generated if not yet exists (should speed up your builds)
    differences linux/windows OK, builds everywhere
    no functional changes in code (no new tests needed)
    peak@windows reconnection behavior to be reviewed

2.0.13

2.0.8

- tests w2016 ok, scripted, remote control through pi
- wrapper (filimonov) added again

2.0.3

CanModule master 2.0.3

v2.0-buffer0

qa and doc for CanModule works with mirror repo in gitlab
OPCUA-1913
OPCUA-1518
OPCUA-1735
ENS-26903 
are fixed already.
NOTHING is tested yet.

1.1.9.4

- syncf flag gone
- hi speed to true

1.1.9.3

* using statistics on a per-connection basis
* tested with CanModule 1.1.9.3
* nothing functional changed, just a minor cleanup

1.1.9.2

same tag as CanModule