lnls-dig / halcs

Hardware Abstraction Layer for Control Systems
GNU General Public License v3.0
1 stars 4 forks source link

[smio:trigger] Physical Trigger counter is showing wrong value #147

Closed lerwys closed 7 years ago

lerwys commented 7 years ago

Problem: Physical trigger halcs_get_trigger_count_rcv () shows weird results on startup, like the following:

[root@localhost .halcs-gradle]# ./examples/build/exe/trigger/production/afcv3_1/trigger --brokerendp tcp://10.0.18.38:8978 --boardslot 6 --halcsnumber 1 --channumber [0:23]
I: 17-02-20 17:14:56 My address is 'caca8016-359e-9b59-9c8b-3d68b547acef'
[client:trigger]: Trigger channel 0, counter recv = 0
[client:trigger]: Trigger channel 1, counter recv = 3
[client:trigger]: Trigger channel 2, counter recv = 3
[client:trigger]: Trigger channel 3, counter recv = 0
[client:trigger]: Trigger channel 4, counter recv = 0
[client:trigger]: Trigger channel 5, counter recv = 3
[client:trigger]: Trigger channel 6, counter recv = 3
[client:trigger]: Trigger channel 7, counter recv = 0
[client:trigger]: Trigger channel 8, counter recv = 0
[client:trigger]: Trigger channel 9, counter recv = 3
[client:trigger]: Trigger channel 10, counter recv = 3
[client:trigger]: Trigger channel 11, counter recv = 0
[client:trigger]: Trigger channel 12, counter recv = 0
[client:trigger]: Trigger channel 13, counter recv = 3
[client:trigger]: Trigger channel 14, counter recv = 3
[client:trigger]: Trigger channel 15, counter recv = 0
[client:trigger]: Trigger channel 16, counter recv = 0
[client:trigger]: Trigger channel 17, counter recv = 3
[client:trigger]: Trigger channel 18, counter recv = 3
[client:trigger]: Trigger channel 19, counter recv = 0
[client:trigger]: Trigger channel 20, counter recv = 0
[client:trigger]: Trigger channel 21, counter recv = 3
[client:trigger]: Trigger channel 22, counter recv = 3
[client:trigger]: Trigger channel 23, counter recv = 0

Even though we don have anything connected to trigger lines 8-23. Also, some trigger lines are stuck at counter 3.