Project

General

Profile

Feature #9391

Milestone #9388: 2015 Shutdown

Implement MDAT Receiver

Added by Roger Tokarek about 5 years ago. Updated about 5 years ago.

Status:
Assigned
Priority:
Normal
Assignee:
John Diamond
Category:
-
Start date:
07/07/2015
Due date:
% Done:

90%

Estimated time:
16.00 h
Spent time:
10.00 h
Duration:

Description

Read MI momentum from MDAT and use to correct the DCCT Intensity reading.

image.jpg (1.23 MB) image.jpg Momentum correction description John Diamond, 07/07/2015 04:04 PM

History

#1 Updated by John Diamond about 5 years ago

Attached is the original note from Tom Meyer's logbook concerning the momentum correction for beam intensity readings from the MI DCCT.

#3 Updated by Roger Tokarek about 5 years ago

  • Estimated time set to 16.00 h

#4 Updated by John Diamond about 5 years ago

  • Status changed from New to Assigned
  • Assignee changed from Roger Tokarek to John Diamond
  • % Done changed from 0 to 30

Implemented the PMCUCDMDATDrv class - a driver for the PMC-UCD MDAT Receiver.

#5 Updated by John Diamond about 5 years ago

Verified that we can load the new MDAT stuff on the target (mi14tor).
Created MDAT::rxEnable() and MDAT::txEnable to load the MDAT receiver and transmitter drivers dynamically since not all VMEINT nodes will have one or both of these devices.

#6 Updated by John Diamond about 5 years ago

Implemented the vmeintMDATChannel(..) shell command.

#7 Updated by John Diamond about 5 years ago

  • % Done changed from 30 to 50

Implemented filters, which gives us a flexible way to filter the raw intensity signal before returning it to the user. One such use case is the MI True Intensity Filter (MITrueIntensityFilter class) which applies the formula referenced above to the intensity signal using the MI p read from MDAT.

#8 Updated by John Diamond about 5 years ago

Commands for configuring filter chains:

  • vmeintFilterChainCreate chainID, deviceID - creates a filter chain identified by 'chainID' and filtering intensity device identified by 'deviceID'
  • vmeintFilterMITrueIntensityCreate chainID - Adds a MI True Intensity filter to filter chain idenfitified by 'chainID'
  • vmeintFilterRunAvgCreate chainID - Adds a running average filter to filter chain identified by 'chainID'

#9 Updated by John Diamond about 5 years ago

  • % Done changed from 50 to 80

Implemented FilterChainAccessor, which provides ACNET with access to the output from any filter in a filter chain.
Also, implemented the vmeintFilterChainACNETCreate( deviceID, chainID ) command. This maps an ACNET device (SSDN device ID) to a filter chain. The SSDN channel field can be used to select which filter in the chain returns data to ACNET.

#10 Updated by John Diamond about 5 years ago

Got anub to boot from anubstartup (target MVME5500-anub_64).

#11 Updated by John Diamond about 5 years ago

  • % Done changed from 80 to 90

Created a filter chain for the MI DCCT:

vmeintFilterChainCreate 0, 0
vmeintFilterMITrueIntensityCreate 0
vmeintFilterRunAvgCreate 0, 10

Made a test device called Z:DCCT with SSDN device ID 0x80:
vmeintFilterChainACNETCreate 0x80, 0

Was able to FTP without any problems, but with no signal. Will need beam and an MI ramp to fully test the true intensity filter...

Also available in: Atom PDF