Project

General

Profile

Task #11022

Milestone #10477: ANUB Startup

Milestone #11019: Cycle devices for anub

Support for :BEAMnX devices

Added by John Diamond almost 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Start date:
11/29/2015
Due date:
% Done:

100%

Estimated time:
4.00 h
Spent time:
Duration:

Description

Where n = first hit of machine cycle events (e.g. 2 for MI and E for RR).
This is a cycle device that returns sample data from the last machine cycle. For example, if the last MI machine cycle was a $2A then this cycle returns the same data as I:BEAM2A.

History

#1 Updated by John Diamond almost 5 years ago

  • % Done changed from 0 to 70

Implemented internal support for :BEAMnX devices via the CycleDeviceMachine class.
Implemented CycleDeviceMgr::show() to help test this.
Configured MI and RR cycle device machine groups on anub and tested.
Need to implement ACNET interface for :BEAMnX devices and test that.

#2 Updated by John Diamond almost 5 years ago

  • % Done changed from 70 to 90
Implemented CycleDeviceAccessor::machineRead() to provide ACNET with access to a machine's active cycle device.
Created the following devices:
  • I:DCCT20
  • I:DCCT21
  • I:DCCT23
  • I:DCCT2A
  • I:DCCT2X
  • R:DCCTE3
  • R:DCCTEX

Tested what I could without a beam signal...

#3 Updated by John Diamond almost 5 years ago

  • Status changed from Assigned to Closed
  • % Done changed from 90 to 100

Was using CycleDeviceMgr::getSample instead of ::getMachineSample()... Corrected that and also noticed that the scaling factor was wrong on most of the above devices. After fixing that I was able to verify that the machine array devices are working as expected.



Also available in: Atom PDF