Difference between revisions of "DAQ Testing/20180730"
From PREX Wiki
Jump to navigationJump to searchLine 27: | Line 27: | ||
*** Signal shows up in channels 2 and 3, channel 3 is 0.25 times the signal in channel 2 | *** Signal shows up in channels 2 and 3, channel 3 is 0.25 times the signal in channel 2 | ||
*** The first 4 channels are doubled, top 5 channels are dead | *** The first 4 channels are doubled, top 5 channels are dead | ||
− | * Take all wires out and test the board (vqwk3) with no extra signals in it - to see if the cross-talk/multiplied channel problem is hardware or software | + | * After Lunch: Take all wires out and test the board (vqwk3) with no extra signals in it - to see if the cross-talk/multiplied channel problem is hardware or software |
− | ** | + | ** Run 4109 has all extra signal wires unplugged, replaced the EXT Gate trigger wire, plugged |
+ | *** Run 4109 - 0-1200 events - Ramp in channel 0 (expect signal in 0 and 1 if error persists) | ||
+ | *** Run 4109 - 1200-2600 events - Ramp in channel 1 (expect signal in 2 and 3 if error persists) | ||
+ | *** '''Problem persists - channels are coupled strangely still''' | ||
+ | * Replace QWeak ADC in 4th sloth (index 0, vqwk3) with a replacement board to see if it was a hardware or software problem | ||
+ | ** The old vqwk3 board has a strange device attached to it (see [[media:QWeakADCdifference-20180730.JPG|image]] - left is old, right is replacement) | ||
+ | ** Run 4110 has new board | ||
+ | *** Run 4110 - 1200 events - Ramp in channel 0 (expect signal in 0 and 1 if error persists in VME crate or software) | ||
+ | **** '''Error persists, channel 0 input still affects 0 and 1''' | ||
+ | *** Run 4110 - 1200 events - Ramp in channel 0 (expect signal in 0 and 1 if error persists in VME crate or software) | ||
+ | *** Run 4112 - Ramp in channel 1 (expect signal in 2 and 3 if error persists in VME crate or software) | ||
+ | **** | ||
== Result == | == Result == |
Revision as of 12:48, 30 July 2018
Back to Main Page >> DAQ Documentation Portal >> DAQ Testing >> DAQ Commissioning Notes
Previous Day of Testing << >> Next Day of Testing
July 30th, 2018 Testers: Cameron and Chandan
Goals
Figure out why the last few ADCs in the Counting House crate are giving strange signals
- Was it user error, plugging channels in the wrong places? - some was, still crosstalks on same board
- Are the neighboring channels experiencing cross talk? - yes, investigate more after lunch
- Are the neighboring channels hard wired in a strange way? - maybe, may be software instead
- Is the neighboring board (4) connected via VME backplane (to 3)? - no, probably just user error - note this in prior day run logs
- Is this intentional? - Caryn had set the vqwk# initialization in the boot script instead of the .crl file... - no, why would you sabotage your ADCs like this?
Test a backup QWeak ADC to see if the crosstalk/mislabeled ADC channels are hardware or software
- Replace vqwk3 with replacement and do dedicated runs for each channel and compare all signals
Testing ADCs
- Testing Qweak ADCs to understand strange channel mapping and crosstalk
- vqwk3 (board 4) - channel 0 - run 4107 -
- Signal shows up in channels 0 and 1, channel 0 is 0.25 times the signal in channel 1
- Neighboring vqwk4 doesn't see any crosstalk from vqwk3 - so that was some user error
- vqwk3 (board 4) - channel 1 - run 4108 -
- Signal shows up in channels 2 and 3, channel 3 is 0.25 times the signal in channel 2
- The first 4 channels are doubled, top 5 channels are dead
- vqwk3 (board 4) - channel 0 - run 4107 -
- After Lunch: Take all wires out and test the board (vqwk3) with no extra signals in it - to see if the cross-talk/multiplied channel problem is hardware or software
- Run 4109 has all extra signal wires unplugged, replaced the EXT Gate trigger wire, plugged
- Run 4109 - 0-1200 events - Ramp in channel 0 (expect signal in 0 and 1 if error persists)
- Run 4109 - 1200-2600 events - Ramp in channel 1 (expect signal in 2 and 3 if error persists)
- Problem persists - channels are coupled strangely still
- Run 4109 has all extra signal wires unplugged, replaced the EXT Gate trigger wire, plugged
- Replace QWeak ADC in 4th sloth (index 0, vqwk3) with a replacement board to see if it was a hardware or software problem
- The old vqwk3 board has a strange device attached to it (see image - left is old, right is replacement)
- Run 4110 has new board
- Run 4110 - 1200 events - Ramp in channel 0 (expect signal in 0 and 1 if error persists in VME crate or software)
- Error persists, channel 0 input still affects 0 and 1
- Run 4110 - 1200 events - Ramp in channel 0 (expect signal in 0 and 1 if error persists in VME crate or software)
- Run 4112 - Ramp in channel 1 (expect signal in 2 and 3 if error persists in VME crate or software)
- Run 4110 - 1200 events - Ramp in channel 0 (expect signal in 0 and 1 if error persists in VME crate or software)