Nutzung der Digitizer Testumgebung auf der dal004

• Die dal004 hängt am "USER-Timing" Netz (Falls kein Timing --> Timing Simulieren )
• Eine funktionierende Konfiguration ist abgelegt auf dal004:/opt/fesa/local/DigitizerDU2-4.3.0

• Wenn die Timing-Simulation 2x läuft, kommt es zu Problemen
• Wenn zwei FESA Klassen auf das selbe Picoscope zugreifen kommt es zu Problemen
• 2x login auf dal004 und cd nach /opt/fesa/local/DigitizerDU-d.pinned
• 1x ./Inject_simulation.sh (Falls kein Timing auf dem USER NEtz läuft)
• 1x ./startManually_DigitizerDU_M.sh
• Momentan sind 4 scopes angeschlossen: 2x ps4000, 1x ps3000, 1x ps5000
• Die Pexaria kann zum Testen ein Rechtecksignal generieren. Mehr Info hier: https://www-acc.gsi.de/wiki/FESA/FESA-Class-Digitizer#WR_Timing
• IO2 der Pexaria ist mit ein Eingang "A" aller angeschlossenen scopes verbunden (Rechtecksignal)
• IO3 der Pexaria ist mit "Kanal H" der beiden ps4000 und des ps5000 scopes und mit DigIn0 des ps3000 verbunden. (Timing-Trigger)

Usage of a Digitizer Instance via Fesa Explorer

• Use a "get" on Property ChannelConfigDAQ to see all available channels and the flowgraph (*.grc file) which currently is loaded
  • The Naming convention is NOMEN:Signal:optModifier@SampleRate
  • optModifier is optional. E.g. can be "Triggered" for Triggered Sinks
• Subscribe to Property "SnoopTriggerEvents" in order to see which triggers currently are played by the Timing (Only triggers which are relevant for our class are shown)
• Use the property "AcquisitionDAQ" in STREAMING mode. Write a specific channel into the filter-item and press subscribe
• Modes
  • STREAMING
    • Like described above ... will sent values in a defined max. frequency to the client.
    • You can use the Setting-Property "StreamingClientUpdateConfig" in order to control the max client update rate.
    • Filters TriggerNameFilter is not taken into account
  • TRIGGER ()
    • Wait for a specified events and do 1 measurement if event passes by
    • Make sure that the event selected by "TriggerNameFilter" actually is played .. or leave it empty to trigger on all events
    • Triggered measurement only will work for triggered Sinks .. make sure the "channelNameFilter" you picked has "Trigered" in its name.
    • Property "Setting". The property is filled with valid default data !
      • Set Setting/trigger_evt_Number to the event# on which you want to measure
      • Set Setting/trigger_evt_Count to the number of expected events of event# (only in case of bursts ... set to 1 will do for the first)
    • Filter clientUpdateFrequency is not taken into account
  • SNAPSHOT (not supported so far)
    • Wait for a BEAM_ON event and do 1 to n measurements after event passes by
    • Property "Setting". The property is filled with valid default data !
      • Set Setting/snapshotTimes to e.g. (300,400,500) --> will make measurement 300(µs?), 400 and 500 after BEAM_ON event (not smaller than 100! )
  • SEQUENCE
    • Displays samples of a whole sequence, from SEQ_START till the next SEQ_START event.
    • Filters TriggerNameFilter and clientUpdateFrequency are not taken into account
• refTriggerName / refTriggerStamp
  • If there is WR-Timing, all samples are provided with relative timestamps in seconds (channelTimeSinceRefTrigger)
  • The "RefTrigger" is the stamp to which is referred .. the trigger may have been occured within time the samples were measured, but as well could have been occured before. (channelTimeSinceRefTrigger as well can be negative)
  • If available, the "Inject" event will be used as refTriggerEvent (can be changed via the expert Prop ConfigureRefTriggerEvents. Attention! First talk to me or R.Steinhagen before Setting it!)
• channelUserDelay /channelActualDelay --> Not used yet
• Other stuff -> Not used yet

Concrete Example dal007 (SIS18 Dipol)

• Open FEX --> Load Model from Webserver
• Filter for dal007, use prod server
• Use empty cycle selector (0,0,0,0) ( So far no support for specific cycles )
• Prop "ChannelConfigDAQ" will show all available channels. E.g:

GSI11MU2:U_1@1Hz
GSI11MU2:U_1@10Hz
GSI11MU2:U_1@25Hz
GSI11MU2:U_1@100Hz
GSI11MU2:U_1@1kHz
GSI11MU2:U_1@10kHz
GSI11MU2:U_1:Triggered@10kHz
.... same suffixes available for:
GSI11MU2:DeltaI_Circuit
GSI11MU2:I_Circuit
GSI11MU2:U_Set
GSI11MU2:I_Set
GSI11MU2:U_3
GSI11MU2:I_1
GSI11MU2:TIMING_1@1Hz (Timing Triggers generated on IO3 of Pexaria)
...

• ( Currently only one scope is active. Later additional channels will be shown )
• Open Prop "AcquisitionDAQ", put e.g: GSI11MU2:U_1@1kHz into channelNameFilter, select STREAMING for "acquisitionModeFIlter", press subscribe
• Open a Basic 2D Chart on "Channel Value".
• There is a Java GUI named "FixedDisplay", developed by R.Steinhagen. It publishes screenshots here: Web-Gui provided by R.Steinhagen.
• Expert Digitizer Application from Peter Benjamin (Link only works in acc Net)

Reset Server

• ssh auf den Rechner und "reboot" eingeben .. wie auf der SCU auch
• Oder via Management Port i64.acc.gsi.de (Useer/PW bei Alexander Schwinn oder Christoph Handel erfragen )
• Oder via Timing Netz (Siehe Rufbereitschafts Wiki)

Reset Scope

• Die Property "Init" macht ein Reset der Fesa Klasse
• USB3 Kabel rausziehen und wieder rein stecken ... falls das nicht hilft: Reset Server