DCCT: Transfer Recycler Devices from MIBEAM to ANUB
Devices and device names for the RR DCCT exist but are currently supported by the MIBEAM front end. We are transferring support of these devices as well as MDAT support from MIBEAM to ANUB.
#1 Updated by Roger Tokarek about 4 years ago
A series of dabbel files have been created and saved in git based on Wiki entry: ANUBTestDevices.
|dabbelRRDevicesFromMibeamToAnub.lis||Transfer R: BEAM Devices from MIBEAM to ANUB||Pending|
|dabbelRemoveRDCCTDevicesFromANUB.lis||Remove unwanted R: DCCT devices from ANUB||Pending|
|dabbelOldAnubAll.lis||All ANUB pre-transfer devices||In case of rollback|
|dabbelOldAnubR.lis||Only ANUB R: pre-transfer devices, a subset of above||In case of rollback|
|dabbelOldMibeamAll.lis||All MIBEAM pre-transfer devices||In case of rollback|
|dabbelOldMibeamR.lis||Only MIBEAM R: pre-transfer devices, a subset of above||In case of rollback|
#3 Updated by John Diamond about 4 years ago
Booster study time for today was cancelled so we await the next scheduled downtime to do our switch-over.
Enabled anub's MDAT transmitter and configured MDAT frame $70. Updated anubstartup but did not deploy to the boot area yet. Verified that the frame data is being computed and stored in the correct register on the transmitter. However, the scaling factor that stuffs the intensity reading into the MDAT frame was implemented as an unsigned int. This may work OK for the Toroids but it needs to be a float for the DCCT. Changing this requires that the command line parameter be passed as a string, so it break compatibility with Toroid front ends. For this reason, I've merged master into mirrdcct_master and applied my changes to that branch.
Aisha has pulled a cable (but not attached) from anub to the MDAT local box. Will consult with Vogel on when we can proceed with timing in the frame.
Also, a final concern is that the MDAT frame data won't include the base line correction as implemented. I will be opening a separate ticket for addressing this.
#4 Updated by John Diamond about 4 years ago
Deployed a test-level build for anub.
Updated the anubstartup script to load test build and deployed.
Beam will be off at 3am. We should reboot anub in the morning and verify that the frame data register is being updated (0xf0f06010) before meeting Vogel at MI-62 to time-in.
#5 Updated by John Diamond about 4 years ago
- Status changed from New to Assigned
Z:TC70D - MDAT frame $70 device for anub
R:TC70D - MDAT frame $70 device for mibeam
These should be reversed tomorrow after anub has been timed-in for MDAT $70
DABBEL listing for the MIBEAM R:TC70D -
! MOD R:TC70D ( "MDAT TC70 Frame Delay ", MIBEAM, , 01FFDBDE, 0, , "Main Injector", "JDIAMOND" ) MACHINE ( "none") AAMASK ("MCR+MCRCrewChief") SSDNHX PRREAD (0C0B/001F/0006/0E02) PRO PRREAD ( 4, 4, 60) PDB PRREAD ( "uSec", "uSec", 24, 0, 4, 0, 1, 0, , , , , , , -1.701398752450E+38, -1.698075682461E+38) SSDNHX PRSET (0C0B/001F/0006/0E02) PRO PRSET ( 4, 4, 60, 00, 00, 89, 00) PDB PRSET ( "uSec", "uSec", 28, 0, 4, 0, 1, 0, , , , , , , -2.147483648000E+09, 2147483647) !
#6 Updated by John Diamond about 4 years ago
Ready for tomorrow's switch -
clx50$ dabbel dabbelRRDevicesFromMibeamToAnub.dbl DABBEL: defaulting to syntax-checking mode DABBEL: Checking file in Syntax-Checking-Only mode DABBEL: Checking file in Syntax-Checking-Only mode ! DABBEL V7.23 running on file dabbelRRDevicesFromMibeamToAnub.dbl ! ! ! No syntax errors found