Bug #10049
TB getting garbage attenuation values on most cycles (but not all!)
Description
We expect the following:
0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 7, atten = 0, data = 0700 0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 6, atten = 0, data = 0600 0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 5, atten = 0, data = 0500 0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 4, atten = 0, data = 0400 0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 3, atten = 0, data = 0300 0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 2, atten = 0, data = 0200 0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 1, atten = 172, data = 01ac 0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 0, atten = 172, data = 00ac (24) press q to quit, any other key to continue... 0 uS 0 (null): TBPool.cpp:_handleCLStart() mcu id: 2, tb channel a set to 0, b set to 0 0 uS 0 (null): TBPool.cpp:_handleCLStart() mcu id: 2, tb channel a set to 0, b set to 0 0 uS 0 (null): TBPool.cpp:_handleCLStart() mcu id: 2, tb channel a set to 0, b set to 0 0 uS 0 (null): TBPool.cpp:_handleCLStart() mcu id: 1, tb channel a set to 0, b set to 0 0 uS 0 (null): TBPool.cpp:_handleCLStart() mcu id: 1, tb channel a set to 0, b set to 0 0 uS 0 (null): TBPool.cpp:_handleCLStart() mcu id: 0, tb channel a set to 0, b set to 0 0 uS 0 (null): TBPool.cpp:_handleCLStart() mcu id: 0, tb channel a set to 172, b set to 172 0 uS 0 (null): TBPool.cpp:_handleCLStart() mcu id: 1, tb channel a set to 0, b set to 0 0 uS 0 (null): TBPool.cpp:_handleCLStart() mcu id: 1, tb channel a set to 0, b set to 0 0 uS 0 (null): TBPool.cpp:_handleCLStart() mcu id: 0, tb channel a set to 0, b set to 0 0 uS 0 (null): TBPool.cpp:_handleCLStart() mcu id: 0, tb channel a set to 0, b set to 0 0 uS 0 (null): TBPool.cpp:_handleCLStart() Using intensity profile #0 0 uS 0 (null): TBPool.cpp:_handleCLStart() i:beam = 0 E12 0 uS 0 (null): TBPool.cpp:_handleCLStart() Received TYPE_SET_ATTENUATORS message. 0 uS 0 (null): DAQPool.cpp:arm() DAQ pool armed. 0 uS 0 (null): Controller.cpp:_handleCycleReset() Handling Cycle Reset Command
But we're seeing this for most spills (like 4/5):
0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 7, atten = 0, data = 0700 0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 6, atten = 0, data = 0600 0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 5, atten = 0, data = 0500 0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 4, atten = 0, data = 0400 0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 3, atten = 0, data = 0300 0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 2, atten = 0, data = 0200 0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 1, atten = 0, data = 0100 0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 0, atten = 0, data = 0000 0 uS 0 (null): DAQPool.cpp:disarm() DAQ pool disarmed. 0 uS 0 (null): Controller.cpp:_handleEndOfBeam() Handling End of Beam Command 0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 7, atten = 76, data = 074c 0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 6, atten = 217, data = 06d9 0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 5, atten = 29, data = 051d 0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 4, atten = 0, data = 0400 0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 3, atten = 160, data = 03a0 0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 2, atten = 238, data = 02ee 0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 1, atten = 20, data = 0114 0 uS 0 (null): TransitionBoard.cpp:setAtten() mcu id: 0, chan = 0, atten = 13, data = 000d 0 uS 0 (null): TBPool.cpp:_handleCLStart() i:beam = 0 E12 0 uS 0 (null): TBPool.cpp:_handleCLStart() Received TYPE_SET_ATTENUATORS message. 0 uS 0 (null): DAQPool.cpp:arm() DAQ pool armed. 0 uS 0 (null): Controller.cpp:_handleCycleReset() Handling Cycle Reset Command
History
#1 Updated by John Diamond over 5 years ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
When we're running no beam in the MI the DCCT may report a negative intensity which would mean that the intensity is below the threshold for the first row in the attenuation table. To fix, after I:BEAM is read we clamp negative readings to 0.
#2 Updated by John Diamond over 5 years ago
- Status changed from Resolved to Closed