VdAstrid versions
This document contains version information for the VdAstrid device.
Version 1.27.200.306 (9/9-2008 JSN):
CVdAstElOp:
- VVS62 closed automatic when accelerating
- CRE31TUN set to injection value when entering Inactive and not 10s after Dump
- Septum is always turned off if at a value larger than 450 A during dump.
- Tries a second reset of the septum if it does not turn on the first time
Version 1.26.124.268 (2007-01-10 JSN):
CBeamCurrent:
- Increased noiselevel. Single Mark is now 1.0 mA, BeamLoss detect is 2.0 mA
Version 1.25.122.264 (2006-11-28 JSN):
CVdAstElOp:
- Septum Ramp in operation from CVdAstElOp
- (Of course turn on/off septum when injecting
- If InjSeqVPast.SeptumStore>0, then Automatic ramping to Store value 10 min after Store is hit
- If InjSeqVPast.SeptumStore is changed during store, septum is ramped to the new value (and turned on/off as needed).
- Ramping FFG (to store value 10 s after Store is hit, Set Inject value back when align is pressed)
Version 1.25.122.262 (2006-11-21 JSN):
CVdAstElOp:
- RF ramped to -15 kHz starting with the start of DAF ramp (takes 8 s)
- Still working on Septum Ramp
Version 1.25.121.260 (2006-11-17 JSN):
Compiler directive: Changed from default to value /EHsc to /EHa: Should be /EHa. Otherwise, normal exceptions are not handled by try catch => program chrash/terminates when exception.
Working on including Septum Ramp in CAstElOp.
Version 1.25.121.258 (2006-11-08 JSN):
CVdAstElOp:
- Changed plunger control to subtract from a start value (set when starting accum)
Version 1.25.120.257 (2006-11-06 JSN):
CVdAstElOp:
- Added Auto Resto Save when entering accum, and 5 min after entering store
- Added parameter for kicker value for accum start.
- Automatic entry to elog with accelerated current when entering Store.
Version 1.25.111.241 (2006-05-30 TW):
CVdBeamCurrent, CVdFaraday: Added client monitor.
Version 1.25.107.237 (06-02-2006 TW):
Corrected Bugs:CVdBeamCurrent: Loading of Integrated current - Data not set to m_stDev before NewData called => Data may be reset to zeo if the client creatíon fails (sources unavaileble). Corrected.
Store of Integrateted current only if integrated current is >0.
Version 1.24.102.218 (16/8-2005 TW):
CVdBeamCurrent:
- Renamed m_st to m_stCal and m_stDev
- Implemented individual check for all client parameter arrivals and delayed beam calculation until until all data has arrived - solved "FEC01 consys restart => BeamCurrent shortly to 0"
- Implemented histories on:
- inj current, acc. current, acc Loss, Max. Inj. current: Added to history when accelerated
- Beam Loos: Added to history when beam is lost
- In30 and Step size now only updated when not accelerated.
- New calculation of BeamcurrentLoss - to Correct:
The calculation of beamloss is sometimes reacts on noise (at high currents?) – false beamloss marks and resetting of the lifetime calculations.
Beamloss calculation should be improved to better detect the full beam loss step (as it is now, often only is the last part of a beam loss, f.ex. show beamloss of 2 mA when the real beamloss is much higher
Version 1.24.102.214 (5/7-2005 TW):
Changed implementation of
Version 1.24.102.212 (5/7-2005 TW):
New device implemented: CVdDMxMultiKnobDevice
Version 1.24.102.208 (8/3-2005 TW):
BeamUsage Device: Changed dump wait time to 20 min, added SMS/MAIL notification message to mail lot 14.
Version 1.24.99.199 (6/1-2005 TW):
New device implemented: CUV1Device
Corrected bugs in BeamUsageDevice:
1. Hvis man slukker for enableDump, kan man ikke tænde
igen (dump-status forbliver i disable). Der bliver "automatisk" tændt igen efter
næste injektion (hvis man har efterladt enableDump on)
2. AutoKeep bliver ikke deAktiveret (via timedInactive
funktioen) hvis der ikke er (har været?) aktiveret en normal active bit.
Version 1.24.102.210 (28/6-2005 TW):
CUV1Device: Corrected bugs, main bug:
When scanning from SVH program, motors sometimes waits aprox. 5 seconds before moving is started. On Console, motor positions is not updated to new positions – but when pressing ‘GO’ on the motor, the motor moves imedeatly and the console position is updated. The error could be in the UV1 device or the motor device.
Version
1.23.96.186 (31/8-2004 JSN):
CVdAstElOp: Now ramp CRE31TUN.dac during
acceleration from Accum value to Store Value
CVdAstElOp: Added SafeAccum option (with AutoSafeWeekend),
and Plunger SafeAdd
Version 1.24.95.181 (26/7-2004 TW):
Corrected bug:VdBeamUsage: Wish counters not cleared when auto clearing wishes Monday morning
Version 1.23.92.166 (5/3-2004 JSN):
CVdAstElOp: Added Fast Mic. trigger during Accumulation option
Version 1.23.92.165 (5/3-2004 TW):
Added CVdBeamUsage device
Version 1.23.92.160 (20/2-2004 TW/JSN):
CVdBeamCurrent: Added beamLoss parameter
CVdAstElOp: Added QuickNote and most of its automation
Version 1.23.92.159 (13/2-2004 TW):
Implemented history on .data parameter. Partly tested (run with no data input).
Version 1.23.92.157 (4/2-2004 TW):
Corrected bug and improved value marking.
Version 1.22.90.151 (25/11-2003 TW):
REIMPLEMENTED!
- Implemented/Corrected
- It would be a very large advantage for the users to know the beam current with less noise. One option is to average for longer time, but a better option is to use the fitting data (say from the 1 min lifetime) to give the present current (say with a 1 second update rate). Parameter SurName Ifit.
- The lifetime should not be allowed to go negative (would be an increase in current). The lifetime should be limited to say 0-200h (negative lifetime should be be set to 200 h).
- It would be a neat feature to be able to detect drops in the current and report it somehow. A simple way is just to detect a drop (0.5mA) and then reset the lifetime calculation (effective immediate). While the lifetime is invalid (and zero), Ifit is just the average of the collected data. Lifetime equal to zero can then be used to signal a poor current determination (ie. experiments should discard (and pause) datataking).
- There is a problem around the change of month (at midnight), where the lifetime goes to zero for some time.
Version 1.22.89.146 (30/9-2003 JSN):
- CVdAstElOp:
- Corrected bug in CycleStat..AfterStore Checks.
Version 1.22.89.143 (10/9-2003 JSN):
- CVdAstElOp:
- Added CRE31TUN tuning phase inj/store control.
- AlignAlign was added a few versions ago..
Version 1.20.80.131 (23/5-2003 JSN):
- CVdAstIonOp:
- Added calculation of NSACurCalc.
Version 1.20.79.130 (1/5-2003 JSN):
- CVdAstElOp:
- Moved phaseMod on to 10s after stored.
- RF Plunger Integrator control improved (possibility of integrator on during align/accum.
- AutoAlign implemented (10s after going into Inactive)
Version 1.19.79.129 (22/4-2003 JSN):
* CVdAstElOp: Added RF plunger integrator control.
Version 1.19.79.128 (10/4-2003 JSN):
* CVdAstElOp: Added MicClock, Kicker, RFfreq, and (partly) RFpower handling. The beam is kicked out if the CycleStat is changed from Accum back to Align, and RFpower, Kicker, MicClock is set to Align values. The RFphaseModulation is turned off when going to Inactive and back on again when going in Store. The RFfrequency during align and accum is saved when going to store mode, and reloaded when going to align from inactive. The RFfrequency is been ramped to the store value just after going into store mode.
Version 1.17.72.118 (9/1-2003 JSN):
* New device CVdAstIonOp(CCalcDevice): Copy the beam rev. freq and energy at storage flattop to two new parameters. The copy happens at the first flattop after the CRI31AMC.s_DAFmode has been in stop.
Version 1.17.72.114 (9/10-2002 JSN):
* CVdButtonPickupDevice: Finished
implemention.
* CBoolean::WaitUntilTrue: Corrected use of this class.
Version 1.17.72.113 (1/10-2002 JSN):
* CVdAstElOp: Added DMHx3 accum/store handling.
Version 1.16.??.111 (13/9-2002 JSN):
* New CVdAstElOp: Plunger control implemented.
Version 1.16.69.109 (15/08-2002 JSN):
*Corrected CConSysClient initialization in all devices, so that CConSysClient:Initialize(..) now is called as the last step in the constructor.
Version 1.16.65.93 (12/04-2002 TW):
CVdBeamCurrent: Implemented new parameters: Injected current, Acc Current, Lost current
CVdBeamCurrent: Implemented integrated current parameters.
Corrected minor bugs.
Version 1.16.65.99 (15/05-2002 JSN):
CVdCalcAst: Now uses BeamCurrentAst.slow to normalize Beamloss. Dependency list changed so no signaling of BeamLoss.normalize when BeamCurrent changes.
Version 1.16.60.93 (12/04-2002 TW):
CVdBeamCurrent: Marking of beamcurrent (all versions and history) added, when the beam is accelerated and when beam looses > 1 mA is detected.
Version 1.16.60.92 (10/04-2002 TW):
CVdBeamCurrent: Monitor to protect variable in PreStopDevice. Already removed in previous version.
Corrected: CVdBeamCurrent: Does not calculate lifetime correctly around
CVdBeamCurrent: Lifetime calculations stopped if the beam current is less than 10 mA. This is done to prevent noise data generated when the beam is lost.
Version 1.16.60.91 (3/04-2002 jsn):
VdCalcAst: Implemented Beamloss calculation (including normalised) (first version actually implemented some weeks ago).
Version 1.12.43.62 (30/01-2001 TW):
CVdBeamCurrent:Write and []: Implemented type check on data and address before usage.
Version 1.11.40.58 (21/11-00 JSN):
CVdMultiplexer: MuxScan .start did on Write reset .scan.
Version 1.8.25.37 (8/2-00 TW):
CVdBeamCurrent: History implenmented for normal beamcurrent. A macro definetion has been defined to obtain the history from the list. The macro can read from a given start time. The fast beam current history has been changed so it also use this macro.
The fast beam current now also has to send a request for history in order to receive the history.
Version 1.8.25.36 (8/2-00 TW):
CVdBeamCurrent: New data types added:
slow, parameter 8: Update data value every second, current the mean value
of received values.
Packet, paremeter 9: Return a packet of values rec. since last update, (50
ms between points). The first return value is the total history
I*Tau, parameter 10: return I*tau10
CVdBeamCurrent: History implemented on fast beam current, packet
beamcurrent.
The current is stored in tree decreasing resolutions.
Corrected memory leak error, due to use of SAFE_DATA_READ.
Version 1.6.17.26 (20/10-99 TW):
CVdViewer: Updated to new beamline configuration.
Version 1.1.12.19 (17/3-99 TW):
CVdBeamCurrent: Does not return beam current data before valid client data exist.
CVdBeamCurrent: Error detected, code changed so crash should not be possible, not tested.
CVdBeamCurrent: Reset - now also reset calibration maximum to the default value.
Version 1.1.12.16 (9/3-99 TW):
CVdBeamCurrent: Problems - sometimes locks. Maybe problem with monitors.
CVdBeamCurrent: Reset implemented. Creates a new client connection and reset lifetime calculation.
Version 1.1.12.16 (25/2-99 TW):
Device destruction corrected for all devices.
CVdBeamCurrent: Removed all #IFDEF _ASTRID sections
CVdBeamCurrent: Added missing monitor around most operations.
CVdFaraday: Added missing monitor around most operations.
CVdMultiplexer: Added missing monitor around most operations, Added database monitor.
CVdViewer: Added missing monitor around most operations, Added database monitor.
Version 1.1.12.15 (23/2-99 TW):
Initialisation in CKernelDevice, CConSysKernel changed - now loads all devices and call create before starting the client construction and database initialisation. All database load and client creation in the devices must be done in separate threads in the devices and must wait for the new sync. object, m_devicesLoaded in the CConSysKernel, to be TRUE before database initilisation/client creation.
All devices updated for this change - remark not tested !!!
Version 1.1.7.9 (13/11-98 TW):
Operator []: Changed return value fron CDataValue* to CConSysData*:
Operators []: Changed return values in case of address error:
Before, returned NULL, now returns CInvalidAddress with a description of the addressing fault.
Version 1.1.2.8 (22/9-98 TW):
Memory leak in lifetime calc corrected.
Compiler option corrected (Was set to generate code to AstridSerialDevice)
Client changed: Corrected error in data order in NewData.
Version 1.1.2.6 (16/7-98 TW):
Removed VdMass from VdAstrid
Version 1.1.2.3 (3/7-98 TW):
New clean version of RCM
A new clean version of rcm has been created. The revision numbers now follow the RCM version numbers.
Automatic insertion of RCM version numbers in resource version
The version informations in the resource script generate the version information from the common ConSys version header file and the version file generated by the new TCL scripts.
Version 1.0.33.38 (21/6-98):
MemCheck added
The headers for MemCheck is added to all .cpp and .c files. To enable MemCheck define MEMCHECK in the settings of the component. MemCheck MUST be installed on the computer.
CVdBeamCurrent tested for memory leaks - none found.
Last Modified 06 May 2020