Older News

  • 19-Dec-2019: big engineering run ends
  • 17-Dec-2019: Enigma release 5.0.4
    • 'promiscuous fix'
    • minor updates
  • 18-Nov-2019: beam in SIS18!
  • 13-Nov-2019: found an interesting bug; fixed by a workaround
  • 08-Nov-2019: big engineering run starts
  • 07-Nov-2019: readiness for big engineering run 2019
  • 06-Nov-2019: update Data Master
  • 04-Nov-2019: update DM-UNIPZ gateway
  • 29-Oct-2019: maintenance timing system starts (morning) and ends (evening)
  • 22-Oct-2019: dry-run starts (SIS18, ESR, CRYRING(?), HEST)
  • 21-Oct-2019: Enigma release 5.0.3
    • 'rescan fix'
    • minor updates
  • 14-Oct-2019:
    • machine commissioning continues (ESR ...)
    • run ends (CRYRING)
  • 27-Sep-2019: run starts (CRYRING)
  • 26-Sep-2019: dry-run ends (SIS18, ESR, CRYRING, HEST)
  • 24-Sep-2019: dry-run starts (SIS18, ESR, CRYRING, HEST)
  • 23-Sep-2019:
    • (conditional) readiness for dry-run and CRYRING run
    • fixed a few issues with WR -> MIL gateways (SIS18, ESR)
  • 19-Sep-2019: 160 White Rabbit Switches delivered
  • 18-Sep-2019: informative: LSA & BSS up again -> timing up & running
  • 17-Sep-2019: maintenance timing system ends (informative: LSA & BSS updates ongoing probably till the evening -> no timing)
  • 16-Sep-2019: maintenance timing system starts
  • 11-Sep-2019: Enigma release 5.0.2
    • minor update
    • no further release(s) planned until the start of the beam time
    • the timing team recommends migration of frontends to this release
  • 09-Sep-2019: power-cut in parts of the facility
    • clock master, data master, management master and WR network survived thx to UPS
    • some services like the timing test facility remained down and needed to be restarted manually
  • 09-Sep-2019: ion source operation @ CRYRING starts
  • 27-Aug-2019: maintenance timing system ends; finally PROduction is up again
  • 23-Aug-2019: need to extend maintenance window; we apologize for the inconvenience
  • 20-Aug-2019: maintenance timing system starts
  • 19-Aug-2019: Enigma released!
  • 08-Jul-2019: job opportunity in our team
  • 28-Jun-2019: maintenance timing system ends
  • 24-Jun-2019: maintenance timing system starts
  • 16-Apr-2019: beam operation ends
  • 01-Apr-2019: contract signed for the delivery of White Rabbit Switches for FAIR
  • 19-Mar-2019: technical stop: DM update (hardened against 'self-flushing of queues')
  • 08-Mar-2019: technical stop: DM update (stricter testing of schedules/cmds)
  • 12-Feb-2019: technical stop: DM update (added software reset)
  • 05-Feb-2019: beam operation starts
  • 01-Feb-2019: ready for beam operation (see here)
  • 25-Jan-2019: job opportunity in our team
  • 17-Dec-2018: SIS18, HEST, ESR: beam operation stops
  • 04-Dec-2018: technical stop in the morning; DM update followed by MASP and BSS testing
  • 26-Nov-2018: SIS18, HEST, ESR: beam operation starts (dry run stops)
  • 19-Nov-2018: technical stop in the morning; DM update followed by MASP and BSS testing
  • 12-Nov-2018: SIS18, HEST: dry-run starts
  • 11-Nov-2018: CRYRING: beam operation ends
  • 29-Oct-2018: CRYRING: beam operation starts
  • 23-Oct-2018: maintenance production system ends (switch-over GPSDO tested, update Data Master + UNIPZ ...)
  • 22-Oct-2018: maintenance production system starts
  • 04-Sep-2018: CRYRING: beam operation ends
  • 22-Aug-2018: CRYRING: beam operation starts
  • 20-Aug-2018: Broken Backup GPSDO repaired and reinstalled. Switch-over not tested due to missing maintenance window.
  • 15-Aug-2018: Data Master update during a technical stop (gateware, firmware)
  • 07-Aug-2018: Data Master update during a technical stop (gateware, firmware, software, FESA)
  • 06-Aug-2018: SIS18 commissioning without beam start
  • 03-Aug-2018: Dry Run end
  • 30-Jul-2018: Dry Run start
  • 20-Jul-2018: End maintenance timing system (update Data Master, UNIPZ Gateway ...)
  • 19-Jul-2018: Begin maintenance timing system (update Data Master, UNIPZ Gateway ...)
  • 13-Jul-2018: 1st beam time block ends
  • 11-Jul-2018: Rolling back Data Master update from Monday -> Transfer works again
  • 10-Jul-2018: Transfer from UNILAC to SIS does not work anymore
  • 09-Jul-2018: Data Master update during a 15 minute technical stop (firmware, software, FESA)
  • 12-Jun-2018: Start of 1st block of 2018 beam time
  • 12-Jun-2018: Run Readiness for 1st block (12 June til 13 July)
  • 06-Jun-2018: Data Master in operation for commissioning of UNILAC
  • 06-Jun-2018: Data Master maintenance postponed
  • 05-Jun-2018: Data Master not available
  • 18-May-2018: Dry Run #8 finished
  • 25-Apr-2018: Backup GPSDO broken. Clock Master operates without redundant reference clock input.
  • 20-Apr-2018: Dry Run #7 finished
  • 19-Apr-2018: Its Doomsday!
  • 19-Apr-2018: Data Master - UNILAC gateway: First operation including the full control system stack (successul!).
  • 13-Apr-2018: (Conditional) Run Readiness for Dry Run #7. Interface between Data Master and LSA/BSS not yet tested.
    • Data Master: upgraded with bug fixes
    • Gateway "Data Master UNIPZ": version 0.1 rolled out to production system
    • BOOTP/DHCP server migrated to ACO infrastructure (INN)
  • 25-Mar-2018: CRYRING run finished
  • 16-Mar-2018: Interruption at user network: Clock Master out of synch. Clock Master and Data Master restarted.
  • 15-Mar-2018: Dry Run #6 finished. The parallel run at CRYRING continues.
  • 14-Mar-2018: 58 new PCIe TR produced and commissioned
  • 09-Mar-2018: New version of Data Master and Generator rolled out for DR #6
  • 28-Feb-2018: Cesar is leaving the team. All the best for your future!
  • 16-Feb-2018: Dry Run #5 finished
  • 15-Feb-2018: Four First-of-Series PEXARIA5b boards were delivered from Experiment Electronics (EEL) and tested by Hardware and Electronics (HEL). Update (16 Feb): The boards seem to work fine. Green light for the Rest-of-Series.
  • 13-Feb-2018: Run Readiness for Dry Run #5.
  • 09-Feb-2018: Maintenance
    • Data Master gateware, firmware and software upgraded.
    • FESA class of Generator upgraded
    • All WRS upgraded and rebooted
    • WR->MIL gateway for ESR operational
  • 05-Feb-2018: Following the security patches applied by INN, software for release "cherry-v4" has been rebuild and is provided as "cherry-v4-meltdown".
  • 23-Jan-2018: Dry Run #4 finished.
  • 19-Jan-2018: Run Readiness for Dry Run #4.
  • 15-Jan-2018: Data Master patched. We are still hunting a bug. Update (18-Jan-2018): looks ok now, bug might be fixed.
  • 04-Jan-2018: Gateway Data Master UNILAC PZ survived 490000 injections. Total error rate is about 2E-4. Not yet supported by LSA.* 20-Dec-2017: Production system operational again. Playing schedule of previous Dry Run #3 (SIS18, HEST)
  • 19/20-Dec-2017: Maintenance clock master. Synchronization with BuTiS re-established. Switch-over to backup GPSDO tested.
  • 13-Dec-2017: Dry Run #3 finished including positive results.
  • 12-Dec-2017: Fix provided for testing. Seems to work. Very agile. Hm....
  • 11-Dec-2017: A recent update of OS on our development cluster during maintenance prevents proper usage of freshly compiled FESA classes in the facility. OS, saftlib and FESA are no longer compatible. We are working on a fix.
  • 08-Dec-2017: Run Readiness for Dry Run #3
  • 08-Dec-2017: Deployment of new version of Data Master fixing an issue reported during the CRYRING beam time.
  • 01-Dec-2017: CRYRING beam time finished successfully (although a hackish solution for the DM<->LSA interface was applied until 20 Nov 2017)
  • 24-Nov-2017: Production System: Clock Master broken. Switched over to Backup Clock Master. A restart of the Data Master was required as well.
  • 20-Nov-2017: New version of Data Master deployed successfully to production system (during technical stop). From now on, the Data Master is only supplied via LSA.
  • 15-Nov-2017: Dry Run #2 finished successfully
  • 13-Nov-2017: CRYRING beam time starts.
  • 10-Nov-2017: Run Readiness for Dry Run #2 (using old version of Data Master). CRYRING switches to new format of timing messages too.
  • 10-Nov-2017: Deployment of new version of Data Master re-scheduled to 20. November
  • 26-Oct-2017: Production Network: Dry Run #1 finished successfully
  • 23-Oct-2017: Production Network: Data Master plays "final" schedule for Dry Run #1
  • 16-Oct-2017: Production Network: Clock Master and Data Master restarted
  • 16-Oct-2017: User Network: Clock Master restarted
  • 13-Oct-2017: Production Network: Data Master plays schedule for SIS18 and HEST (preliminary schedule Dry Run #1)
  • 12-Oct-2017: New format for timing messages in Production Network (CRYRING will stay with old format for Dry Run #1)
  • 12-Oct-2017: New format for timing messages in User Network.
  • 11-Oct-2917: Timing Groups and Event Numbers updated.
  • 09-Oct-2017: Decision: New Format for Timing Messages for all Dry Runs and operation in 2018.
  • 06-Oct-2017: Timing network for Dry Run #1-3 operational
  • 12-Sep-2017: MIL-based "Pulszentrale" SIS18+ESR replaced by new FAIR style General Machine Timing System based on White Rabbit. Backwards compatibility with equipment still requiring MIL timing is accomplished by a Whiter Rabbit -> MIL Gateway.
  • 10-Aug-2017: cherry released. This release will be rolled out to CRYRING by the end of this week.
  • 09-Aug-2017: maintenance at all networks finished
  • 05-May-2017: it was decided not to roll out this snapshot
  • 25-Apr-2017: preparatory work a snapshot started
  • 30-Jan-2017: maintenance at the so-called user-network finished by successfully updating to release balloon
  • 20-Dec-2016: balloon released. This a major release including gateware, firmware, driver and software for the General Machine Timing as well as gateware of SCU specific hardware
  • 22-Nov-2016: all requested 10 VETAR2A VME boards for the retrofitting projects haven been delivered to the beam instrumentation department
  • 22-Sep-2016: management server upgraded to EL7
  • 15-Sep-2016: user network: the issue reported on 14-Sep-2016 has been resolved. However, most TRs (SCUs, PEXARIA, ...) are now blocked due to overflow of events scheduled for execution in about 300 years. In such a case, please power cycle your SCU. Rebooting is not enough. Please make sure your TR (SCU...) is flashed with the "old" Asterisk compatible gateware from January 2016. We are sorry for the inconvenience.
  • 14-Sep-2016: user and timing (TTF) networks: presently no link to the Data Masters. We are working on this issue. Remark: The production network at CRYRING is working fine.
  • 14-Sep-2016: schematics for form factor AMC approved
  • 25-Aug-2016: candidate for release Balloon available.
  • 26-Jul-2016: schematics for form factor AMC delivered by Cosylab
  • 04-Mar-2016: @15:30: "production", "timing" and "user" networks up again
  • 04-Mar-2016: @14:00: "production", "timing" and "user" networks down for short maintenance
  • 29-Feb-2016: "user" and "timing" networks up again. Both network are now phase locked to BuTiS.
  • 23-Feb-2016: four EXPLODER5A modules successfully commissioned and delivered to users
  • 22-Feb-2016: work on "User" and "Timing" networks completed
  • 29-Jan-2016: Snapshot rolled out to production network (CRYRING)
  • 28-Jan-2016: schematics for form factor AMC approved
  • 22-Jan-2016: snapshot released
  • 18-Jan-2016: creating a snapshot "release" of the General Machine Timing system. The snapshot includes gateware, drivers, libraries, saftlib. The main purpose of the snapshot is to provide major bug fixes.
  • 15-Jan-2016: four prototypes of form factor PMC delivered by Cosylab
  • 22-Dec-2015: monitoring tool for production network available again
  • 21-Dec-2015: monitoring tool for production network unavailable
  • 17-Dec-2015: schematics for form factor AMC delivered by Cosylab
  • 14-Dec-2015: @15:04: data master down - short interruption at CRYRING - @16:00: problem solved
  • 08-Dec-2015: Maintenance week: All White Rabbit Switches of the production system have been flashed to "version: v4.2 (Grzegorz Daniluk); compiled at Aug 28 2015 15:05:21"
  • 07-Dec-2015: After disabling active checks for monitoring, the production system behaved stable for about two weeks. There are occasional "late actions" but we believe this is due to too tight settings of the network latency at the data master.
  • 20-Nov-2015: The production system now monitors all TRs via "passive checks" in Nagios. Within the WR network, we took care of eliminating all traffic except timing message from the Data Master and WR PTP. The system did run for three days without failures. Hm...
  • 17-Nov-2015: Frequently, the production system shows an issue with "late actions". In case this happens, we immediately have to interrupt operation and restart the system. Typically, this should take half an hour. Sorry for the inconvenience.
  • 09 to 13-Nov-2015: production system not available
  • 06-Nov-2015: @1035 production system "up" with crossed fingers as their remain a few issues.
  • 06-Nov-2015: @0900 production system going down for short maintenance
  • 23-Oct-2015: Due to a broken switch and other issues, there was some trouble in bringing the system up again after the power-cut. Now we are back in business.
  • 15-Oct-2015: @1500 production system has been shut down due to an upcoming power-cut. Restart not before 19 October. No timing @ CRYRING. "Programmentwicklungsraum" and "Test Facility" might be affected.
  • 24-Sep-2015: @1821 production system up again. Sorry!
  • 24-Sep-2015: @1806 production system going down for urgent unscheduled maintenance...
  • 11-Aug-2015: AMC: Updated technical concept approved.
  • 06-Aug-2015: Received 25 Rest-of-Series of new White Rabbit switches.
  • 27-Jul-2015: Our colleagues from the beam instrumentation group have developed a small Java event viewer.
  • 23-Jul-2015: PMC: PCB layout and overall design approved
  • 17-Jul-2015: Production system delivers timing for the groups, YRS1, YRLE and YRME.
  • 15-Jul-2015: We start to receive Rest-Of-Series carrier module for the standalone receiver EXPLODER5a and also for the add-on board EXPLODER5a_db2. We discovered a bug with the power supply, but it seem to be easy to fix.
  • 08-Jul-2015: At 1053: The production system is up again.
  • 08-Jul-2015: Starting from 10 a.m., the timing system (production) will be down due to maintenance work. Scheduled downtime is one hour.
  • 23-Jun-2015: SaftLib available on SCUs. Installation requires a symlink and reboot.
  • 17-Jun-2015: 11 a.m. The production system is up again.
  • 17-Jun-2015: Starting from 10 a.m., the timing system (production) will be down due to maintenance work. Scheduled downtime is one hour. CRYRING will be affected.
  • 09-Jun-2015: First beam in CRYRING injector YRLE using the White Rabbit based timing system, see here.
  • 03-Jun-2015: Received on First-Of-Series carrier module for the standalone receiver EXPLODER5a. It works nicely!!!
  • 22-May-2015: GMT "ready for integration" of first equipment in CRYRING cave
  • 21-May-2015: Data Master of the production network is ready for equipment integration @ CRYRING
  • 23-Apr-2015: Received 22 Rest-of-Series of new White Rabbit switches.
  • 17-Apr-2015: After a few weeks of interruption, a very basic on-line schedule monitor is up again.
  • 16-Apr-2015: Due to commissioning of CRYRING, setting up of the production system will start soon. This implies setting up a distinct installation of White Rabbit. The distribution of timing messages for development in the existing facility will be discontinued.
  • 16-Mar-2015: Schematics of form factor PMC approved.
  • 16-Mar-2015: Engineering Specifications for form factors PMC, AMC and VME approved.
  • 06-Mar-2015: Design and First Proof-of-Principle for a Simple API For Timing (saftlib)
  • 27-Feb-2015: maintenance release asterisk for timing receiver gateware and firmware
  • 23-Dec-2014: received 6 First-of-Series of new White Rabbit switches.
  • 15-Dec-2014: two prototypes of EXPLODER5 standalone receiver delivered by EE. And even got the I/O board too! Except minor issues, it seems to work.
  • 25-Nov-2014: 30 VETAR2 VME modules commissioned and tested. 27 modules work, 3 modules have issues which might be possible to fix.
  • 21-Nov-2014: prototype of Data Master back in operation. Distributes messages for a fictive schedule.
  • 31-Oct-2014: FESA class of Data Master linked to application layer for miniCS (test mock-up in virtual machine).
  • 29-Sep-2014: 28 Rest-Of-Series VETAR2 VME modules received from external production.
  • 25-Sep-2014: Both ends of the timing system, data master and timing receiver nodes, can now be accessed by FESA.
  • 13-Aug-2014: two PEXARIA5 modules delivered to Cosylab as reference design.
  • 00-Aug-2014: two First-Of-Series VETAR2 VME modules received from external production. They work. One minor issues detected which will be fixed for the remaining modules.
  • 31-Jul-2014: 33 PEXARIA5 modules successfully tested and commissioned. Two remaining modules have issues we might be able to fix.
  • 09-Jul-2014: early prototype of data master starts sending timing messages via the timing network
  • 08-Jul-2014: achieved integration of timing receivers VETAR2 into prototype DAQ system for FAIR.
  • 03-Jul-2014: release asterisk for timing receiver gateware and firmware
  • 01-Jul-2014: 33 Rest-Of-Series PEXARIA5 PCIe modules received from external production.
  • 19-May-2014: two First-Of-Series PEXARIA5 PCIe modules received from external production. They work. Two minor issues detected which will be fixed for the remaining modules.
  • 30-Apr-2014: 120 WREX1 add-on boards (used to White Rabbitanize non-timing hardware) produced and delivered by EE
  • 22-Apr-2014: 48 add-on boards for I/O mezzanine cards for PCIe DAQ board produced and delivered by EE - modified by CSCOHW.
  • 01-Apr-2014: Technical Concept FAIR Timing Receiver Nodes v1.0 approved.
  • 18-Mar-2014: Detailed Specs FAIR Timing Receiver Nodes v3.2 approved.
  • 17-Feb-2014: Four prototypes I/O mezzanine cards for PCIe DAQ board produced and delivered by EE.
  • 11-Oct-2013: Achieved 50 kHz accepted trigger rate using the Timestamp Latch Unit for timestamping in a DAQ demonstrator. Two PEXARIA5 carrier boards have been used, each in combination with a Black Cat (!) mezzanine board for I/O.
  • 20-Sep-2013: Mini timing system for proton linac source: Migrated to FESA3 and SL6
  • 10-Sep-2013: Ten PEXARIA5 PCIe DAQ boards produced and delivered by EE. Used for prototyping of DAQ systems as well as the FAIR Data Master.
  • 09-Aug-2013: Ten VETAR2 VME boards produced and delivered by EE. They can be White-Rabbit enabled using the WREX1 add-on boards.
  • 24-Jun-2013: Twelve standalone receivers of type EXPLODER2C produced and delivered by EE - this is our swiss pocket knife.
  • 24-Jun-2013: 120 WREX1 add-on boards (used to White Rabbitanize non-timing hardware) produced and delivered by EE - all of them work
  • 23-May-2013: Mini timing system for proton linac source: Déménagement pour l'environnement français
  • 22-May-2013: Mini timing system for proton linac source: Linked to application layer
  • 03-May-2013: Mini timing system for proton linac source: Operational in a test environment
  • 08-Apr-2013: Received sample of radiation hard fibre
  • 27-Mar-2013: Received 15 V3.3 switches
  • 26-Mar-2013: Improvements of stability and precision of WR-PTP
  • 20-Feb-2013: It seems that the problem with the internal flash of switches is solved
  • 21-Jan-2013: Management server installed by IN group. Management network for White Rabbit switches. BOOTP server for White Rabbit nodes.
  • 23-Nov-2012: firsts interrupts via PCIe interface
  • 15-Nov-2012: clockmaster V3 switch broken, due to problem with internal flash
  • 16-Oct-2012: specification of PCIe White-Rabbit Timing Receiver PEXARIA2B - compatible to the SCU
  • 09-Oct-2012: grandmaster V3 switch locked to GPSDO
  • 28-Sep-2012: planning of personnel for the timing system at FAIR
  • 25-Sep-2012: Timing Starter Kit based on SPEC boards
  • 15-Sep-2012: V3 switch in lab locked to V3 grandmaster switch at ELR (clockmaster)
  • 13-Sep-2012: revision of Detailed Specification of the FAIR Accelerator Control System Component „Timing Receivers"
  • 29-Aug-2012: revision of Detailed Specification of the FAIR Accelerator Control System Component „General Machine Timing System“
  • 21-Aug-2012: in-house production of SIXIO2 FMC finished
  • 14-Aug-2012: delivery of prototype V3 switches
  • 14-Aug-2012: installation of GPS antenna and GPSDO at the FAIR timing master
  • 07-Aug-2012: specification of VME White-Rabbit Timing Receiver VETAR1 - compatible to the SCU
  • 27-Jun-2012: new racks for timing master in ELR/BG
  • 20-Jun-2012: installation of WR network cables and splice boxes between ELR/BG, LSB6, PER and EE lab
  • 19-Jun-2012: standalone White Rabbit Timing Receiver EXPLODER2C produced in-house
  • 06-Jun-2012: added a bit of hardware documentation
  • 05-Jun-2012: self-describing Wishbone bus
  • 08-May-2012: PCIe driver for PCIe (SCU, SPEC, PEXARIA2A)
  • 04-May-2012: V1.0 of Detailed Specification of the FAIR Accelerator Control System Component „General Machine Timing System “
  • 22-Mar-2012: 6th White Rabbit workshop @ GSI
  • 15-Feb-2012: WR-PTP link on SCU - thanks Tom!
  • 01-Feb-2012: Etherbone protocol in HDL and software
  • 13-Dec-2011: delivery of SPEC boards
  • 06-Dec-2011: General Machine Timing system workshop at GSI
  • 31-Oct-2011: V2.0 of Detailed Specification of the FAIR Accelerator Control System Component „Timing Receivers"
  • 19-Sep-2011: 5th White Rabbit workshop @ CERN
  • 28-May-2011: White Rabbit Node Functional Specifications
  • 14-Apr-2011: 4th White Rabbit workshop @ GSI
  • 25-Mar-2011: draft of new Timing page made public
  • 08-Mar-2011: draft TimingSystemContext available
  • 01-Mar-2011: "new" page created
  • 10-Dec-2010: first developer meeting @ CERN
  • 08-Dec-2010: White Rabbit Node Technical Specifications
  • 01-Dec-2009: FAIR Baseline Technical Report for the General Machine Timing System
  • 20-Jul-2009: White Rabbit workshop 3 @ CERN
  • 27-Oct-2008: White Rabbit workshop 2 @ CERN
  • 15-Feb-2008: White Rabbit workshop 1 @ CERN

-- DietrichBeck - 21 Jan 2013
Topic revision: r17 - 05 Feb 2020, DietrichBeck
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback