Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: added clarifications & first version of the table

...

silke says: "usb4" relative encoder reader can go up to 15MHz5MHz, but maybe not enough space in the vacuum environment. alex found another renishaw that goes up to 15MHz.

...

ankush encoder document: https://docs.google.com/document/d/1Ho1IpT4903wkUoJMV06z5hou9to5CfAgtJBDPdBl6I4/edit?ts=600b806d

      → (Silke) this lists the USB version of the encoder we originally used the PCI version for. We now have a box as Ankush laid out, except that it 'splits' the signal, so has in&out for each encoder channel. This device its listed towards the end of Supported Control & DAQ Devices

Matt says we may have an existing board that could do the readout/timestamping

...

  • 10kHz with interpolation?
  • multiple encoders?
    • combine absolute/relative (may be complexity issues)
    • 2 staggered slower encoders
  • need fpga timestamping
  • 100 microev resolution requirement


  • Optionmax ratework to be donedrawbacks/other consideration
    Aabsolute encoder used for relevant stage 10-20(?) kHz

    controls: rework PLC to send data (current solution likely ~1kHz)

    DAQ: likely FPGA timestamping


    B

    absolute encoder used for relevant stage, 

    interleave with second absolute encoder

    20-40 kHzas above

    need to ensure both encoders read back equivalent data,

    intersperse jitter from both?, same latency

    Cadd a relative quadrature encoder on shaft5 or more MHzDAQ: need board to read signal & timestamp

    complicated and possible not very reproducible mapping of measured &

    relevant motion

    Dadd a relative quadrature encoder in vacuum5 or more MHz

    DAQ: need board to read signal & timestamp

    engineering: figure out how to add relative encoder



To do

  • fill out the table options and costs (alex and silke)
  • talk to mechanical engineers (Georgi)
  • meet in two weeks

...