Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Feels like option D (see above) is doable according to conversation between Georgi and Danny Morton
    • they meets with Axilon next week to verify (manufacturer of mono assembly))
  • Use this as our current default solution, but can still change (final decision in weeks)
  • Matt W. and Ryan H. think the camlink converter box could be used for readout
    • quadrature encoder "frame format" is understood and relatively simple (absolute encoders are more difficult)
    • quadrature encoder readout can be triggered
    • might need either a new camlink converter board with new connectors or some "connector transition"
  • currently no use case for high rate absolute encoders

120Hz Encoder Plans

- plc is in the fee alcove and the encoder itself is in the fee

- (decision) we put a dedicated daq evr in the controls plc node or controls evr node or drp/ctl node?
- evr gets driven by xpm fiber so trigger stops on endrun
- ttl cable to plc (but could be encoder)
- drp executable joins udp packet to timestamp from kcu (reuses TDetSim firmware).  It is new UDPDetector, which we think inherits from XpmDetector (Detector Class Diagram)
- (decision) question: do we have udp direct connection or go through the router?  router is easier, but could drop the first packet and be off-by-one (can’t detect off by one with dropped shots). direct? cpo feels we should avoid the router.
- “direct” may mean a switch where we control the traffic?  (ATCA (8 sfp, 8 rj45) or top-of-rack with a new vlan?) could use it for xtcav as well.
- ready "early february”
- clearreadout means:  kcu clears its fifos, drp clears out UDP packets on configure/endrun
- ric idea: IF we could send out 1 trigger on beginrun then we could use that as the starting for future frame counters to detect a missing first packet.  not clear how to send that 1 trigger.

Mail message from Alex:

SXR servers are in R06. There’s likely space in there.
https://docs.google.com/spreadsheets/d/1woH6NHS4IrOvr2zDVZD4R8x73moTXAps1PBqADUauC4/edit#gid=1690903792
 
Our, or at least my understanding was that we can use an trigger output from any nearby host with an EVR. To be specific:
-          PLC: B940-009-R07
-          EVR: B940-009-R06 (whatever host we have running the exit slit camera)
 
I assumed the point/beauty of the EVRs is to distribute these trigger sources so it doesn’t have to originate from any specific node. We were going to include a counter in the payload so we could address any off-by-one issues. I guess it’s more complicated!
 
Sorry, Chris, I didn’t realize this thread had taken up residence elsewhere otherwise I would have responded sooner. I try to keep an eye on the pcds-it list but it’s kind of a blindspot for me.
 
The question I have at this point is, where does the Ethernet/<whatever medium we end up choosing> have to go to deliver the UDP packet?