Difference between revisions of "DAQ Testing/20180730"
From PREX Wiki
Jump to navigationJump to searchLine 6: | Line 6: | ||
== Goals == | == 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?''' | ||
== Testing ADCs == | == 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 | ||
+ | * 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: | ||
== Result == | == Result == |
Revision as of 11:24, 30 July 2018
Back to Main Page >> DAQ Documentation Portal >> DAQ Testing >> DAQ Commissioning Notes
Previous Day of Testing << >> Next Day of Testing
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?
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 -
- 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: