Go to the U of M home page
School of Physics & Astronomy
Assay and Acquisition of Radiopure Materials

User Tools

Trace: • 121003 • aug9-12 • may24-12 • nmm • nov5_14 • may10-12 • feb7-13 • meeting8 • betai • feedback
vetoshield:daq

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
vetoshield:daq [2013/02/21 00:15] – [Software] wgilbertvetoshield:daq [2013/05/20 15:44] (current) – [DAQ Overview] wgilbert
Line 1: Line 1:
 ====== Data Acquisition System ====== ====== Data Acquisition System ======
 ===== DAQ Overview===== ===== DAQ Overview=====
-Signals from the proportional tubes making up the Veto Shield are conditioned by preamp cards on the ends of the tubes. Conditioned pulses from 32 preamps are sent via Low Voltage Differential Signaling (LVDS) to a Pulse Stretcher card in a crate in a corner rack. Each crate has a backplane mux that reads up to 8 stretcher cards, or 256 preamp channels. An IRIG time code is distributed to a Symmetricomm timing card in each DAQ computer, which generates clock signals synchronizing timing registers on the mux backplanes connected in its rack. Each time a tube triggers, a timestamped data packet is formed in the mux and transmitted via ribbon cable to an NI PCI-6534 digital I/O card in the DAQ computer. The data is written immediately to disk. The disk files from the four computers are later read and the data collected in a database for post-processing.   +Signals from the proportional tubes making up the Veto Shield are conditioned by preamp cards on the ends of the tubes. Conditioned pulses from 16 preamp cards (32 channels) are sent via a Low Voltage Differential Signaling (LVDS) ribbon to a Pulse Stretcher card in a crate in a corner rack. Each crate has a backplane mux that reads up to 8 stretcher cards, or 256 preamp channels. An IRIG time code is distributed to a Symmetricomm timing card in each DAQ computer which generates clock signals, synchronizing timing registers on the mux backplanes connected in its rack. Each time a tube triggers, a timestamped data packet is formed in the mux and transmitted via a multiconductor cable to a National Instruments PCI-6534 digital I/O card in the DAQ computer. Each computer monitors up to three mux crates. The data is written immediately to disk. The disk files from the four computers are later read and the data collected in a database for post-processing.   
  
  
 ===== Software ===== ===== Software =====
 +
 +===Current Version===
  
 **VetoDAQv5x** is the most recent version of the top-level Labview data acquisition application to be deployed. **VetoDAQv5x** is the most recent version of the top-level Labview data acquisition application to be deployed.
Line 14: Line 16:
   *Optional trigger rate high limit with automatic write inhibit.   *Optional trigger rate high limit with automatic write inhibit.
   *Counter background color indicates limit status, blue for 0, red for hi limit   *Counter background color indicates limit status, blue for 0, red for hi limit
 +  *automatic detection/correction of data framing errors 
  
-==Quick Start== +[[Vetoshield:daq:VetoDAQ Quick Start|Quick Start Instructions]]
-When the VetoDAQ app is first opened, the __Modify Veto DAQ Config__ window will pop up over the main app. When bias voltage, comments, etc. are entered, the operator clicks the <Accept> button to exit saving changes, or <Cancel> to exit without saving.+
  
-  - After the Config vi closes, the main __VetoDAQv5x__ front panel will be visible +[[Vetoshield:daq:datafiles|Data Files]] 
-  - Before starting any DAQ loops, the mux backplane cards connected to the computer should be toggled to an OFF state, with none of the green backplane LEDs blinking + 
-  - When ready to begin collecting data, the <Toggle Mux OFF/ON> button is clicked again, programming the strobe pulse to be issued after a short delay (~5 sec). This starts the muxes + \\
-  - Click the <DAQ Start> buttons in the control clusters during the delay after the Toggle Mux button is clicked, but before the strobe occurs. This reduces the possibility of data framing errors (receiving split trigger packets from the muxes). +
  
 ===Front Panel Descriptions=== ===Front Panel Descriptions===
Line 30: Line 31:
  
  
 + \\
  
 ===Labview Diagrams & Descriptions=== ===Labview Diagrams & Descriptions===
Line 35: Line 37:
 The workings of the DAQ vi's will be explained in general terms, but to get beyond that, one really has to open the source code in the development system and navigate through the diagrams.  With the context sensitive help window open, one can identify terminals in subvi connector icons just by mousing over them, without necessarily opening them. The workings of the DAQ vi's will be explained in general terms, but to get beyond that, one really has to open the source code in the development system and navigate through the diagrams.  With the context sensitive help window open, one can identify terminals in subvi connector icons just by mousing over them, without necessarily opening them.
  
 +[[Vetoshield:daq:VetoDAQv5x diag|main VetoDAQ v5x diagram]]
  
 +[[Vetoshield:daq:VetoDAQReadData diag| subvi VetoDAQReadData diagram]]
  
-[[Vetoshield:daq:VetoDAQv5x diag|main VetoDAQ v5x diagram]]+[[Vetoshield:daq:Rate&Limit|Veto Bit Rates, Limit,+Write Inhibit.vi]]
  
 +[[vetoshield:daq:Data Counter|Data Counter.vi]]
  
 + \\
 + ==Symmetricom Labview Drivers==
  
-[[Vetoshield:daq:VetoDAQReadData diag| subvi VetoDAQReadData diagram]]+The Labview driver vi's used in the apps above were sent to us by Jim Kline at Symmetricom on 4/3/2012. Symmetricom **does not support** any of these at this time, and were provided free of charge for us to use as best we can. They used in testing at Symmetricom, are better than the ones available for download on the website (in our opinion), and they utilize the Labview error cluster. 
  
 +{{vetodaq:bc637pci_LV.zip|bc637pci_LV.zip}}
 +
 +They were written in Labview 2008 and the file, when unzipped should create a directory of vi's with the same name. This should be copied into ...\LAbview20xx\instr.lib, then mass compiled (Tools|Advanced|Mass Compile) for use under the current version. When Labview is restarted, vi's in the instr.lib and user.lib subdirectories of Labview 20xx will show up in the function palettes. 
 +
 +The following demo vi is useful for experimenting with the card when the IRIG time signal is not available. It will unzip to a Labview LLB compressed library file which contains all called subvis, so it can be run without installing the driver library above.
 +
 +{{vetodaq:sync_card_to_labview_time_01.zip|Sync Card  to Labview Time 01.zip}}
 +
 + \\
 ===== Hardware ===== ===== Hardware =====
  
 ==== Overview ==== ==== Overview ====
  
 + \\
 +
 +====Timing Distribution====
 +
 +{{:vetoshield:datasheet_bc635pcie.pdf|Symmetricomm bc635 datasheet}}
 +
 +{{:vetoshield:bc635_637pci_v2_users_guide.pdf|Symmetricomm bc635 user guide}}
 +
 +{{:vetodaq:symcomm_breakout_sch.pdf|UMN breakout cable schematic}}
 +
 +{{:vetodaq:bom_sycomm_breakout_cable.pdf|UMN breakout cable parts list}}
 +
 +[[http://www.symmetricom.com/products/bus-level-timing/sdks-drivers-downloads/|drivers for Symmetricom card (.dll and timing program)]]
 +
 +
 + \\
 ==== Pulse Stretchers ==== ==== Pulse Stretchers ====
  
vetoshield/daq.1361427311.txt.gz · Last modified: 2013/02/21 00:15 by wgilbert

Page Tools