Welcome | spec | C-PLOT | Support | Users | Contact
 



Motors
Counters
MCA
Interfaces

    Hardware reference : Timers/Counters : Ortec 974/994/995/997 NIM Timers and Counters

Ortec 974/994/995/997 NIM Timers and Counters



Interface:
  • GPIB, Serial

Manufacturer:


config file

RS_OR9XT = device_name baud_rate number_of_counters 
GP_OR9XT = gpib_address number_of_counters 
RS_OR9XC = device_name baud_rate number_of_counters 
GP_OR9XC = gpib_address number_of_counters 
RS_OR9XB = device_name baud_rate number_of_counters 
GP_OR9XB = gpib_address number_of_counters 

edconf:   DEVICES screen
SCALERS       DEVICE   ADDR  <>MODE  NUM                                 <>TYPE
    YES    /dev/tty1           9600    4   Ortec 974/994 Counter/Timer (Serial)
    YES                   3            4     Ortec 974/994 Counter/Timer (GPIB)
    YES    /dev/tty2           9600    2 Ortec 974/994/995/997 Counter (Serial)
    YES                   3            2   Ortec 974/994/995/997 Counter (GPIB)
    YES    /dev/tty3           9600    3 Ortec 994 Blind Timer/Counter (Serial)
    YES                   3            3   Ortec 994 Blind Timer/Counter (GPIB) 
      

edconf:   SCALERS screen
NUMBER        NAME  MNEMONIC  <>DEVICE  UNIT  CHAN   <>USE AS  SCALE FACTOR
     0     Seconds       sec     OR9XX     0     0   timebase          1000
     1     Monitor       mon     OR9XX     0     1    monitor             1
     2    Detector       det     OR9XX     0     2    counter             1
      
spec supports the Ortec 974, 994, 995 and 997 counter and counter-timer NIM modules over both GPIB and RS-232 interfaces. When running the configuration editor, select from the above descriptions on the device configuration screen to specify which Ortec modules you are using and how you are using them.

Only one module can be selected as a counter/timer. The 974 module can be assigned a maximum of four channels. The 994 should be assigned two channels normally and three channels when used as a blind timer. The 995 has two channels and the 997 has one.

On the scaler configuration screen, choose OR9XX as the controller for all channels associated with an Ortec module. The unit numbers selected for each channel correspond to the order the Ortec modules appear on the device configuration screen. When using the 994 as a blind timer, you must select channel number 2 for the timebase.



Using the 974
The 974 is a four-channel counter/timer having a minimum 0.1 second time base. You should connect the monitor counts through a tee to the EXT IN connector on the back of module and to the COUNTER INPUT 2 connector on the front of the module. Use the COUNTER INPUT 3 and 4 connectors for one or two detector input channels. Also, make sure that the internal dip switch S-1 has position 6 set to one-cycle.



Using the 994 as a Normal Timer
The 994 is a two-channel counter/timer with a minimum 0.01 second time base. In order to obtain accurate elapsed time readings, one counter channel is used to count time and the other is used to count monitor counts. An additional counter, such as the 995 or 997 is normally used to accumulate detector counts and is gated by the 994. The monitor count source should be connected to both the IN A and IN B front panel connectors of the 994 using a tee. The internal jumpers W3 and W4 must both be set to the TIME position. Jumper W1 must be set to the NORMAL position. Also, make sure the internal dip switch S-1 has position 6 set to one-cycle and position 7 set to COUNTER/TIMER. Finally, make sure the front panel DWELL switch is turned all the way off.



Using the 994 as a Blind Timer
In the blind timer mode, the 994 has the monitor counts connected to IN A and detector counts connected to IN B. The internal jumpers W3 and W4 must both be set to the COUNTS position. Jumper W1 must be set to the NORMAL position. Also, make sure the internal dip switch S-1 has position 6 set to one-cycle and position 7 set to COUNTER/TIMER. Finally, make sure the front panel DWELL switch is turned all the way off.

When operated as a blind timer, spec cannot read back the elapsed time from the module. Instead, when counting to monitor counts, when counting in powder mode, when reading the counters during updated counting and when counting is aborted with a ^C , the elapsed count time is estimated from the software clock.



Gating
An external enable signal from certain motor controllers may be be fed into the rear-panel gate BNC input on the 974 or the front panel enable BNC input on the 994 for precise counter gating in powder-mode scans.

If using a second Ortec module as a counter, you must connect the INTERVAL BNC connector (rear panel on 974, front panel on 994) to the master GATE on the 974 rear panel or to the ENABLE or individual GATE inputs on the 994, 995 or 997 modules.



Setting Operational Parameters
The counter_par() function can be used to set various parameters associated with the Ortec module code in spec. The first argument to counter_par() is a channel number, although all the commands affect all channels of the associated module, or all of the Ortec modules, if appropriate.

 

Function Reference:

counter_par(counter,"alarm",mode)
If mode is zero, turns off the more efficient ALARM mode of operation of the timer, and turns on a slower polled mode. If mode is one, ALARM mode is turned on. The default operation is for ALARM mode to be turned on, and there is generally no reason to turn it off.
counter_par(counter,"alarm")
Returns one if ALARM mode is on. Otherwise returns zero.
counter_par(counter,"display",channel)
Sets the counter channel that will be displayed on the associated module. For the 974 modules, valid values for channel are 1 to 4. For the the 994 and 995 modules, valid values for channel are 0 and 1.
counter_par(counter,"display")
Returns the channel number currently being displayed.
counter_par(counter,"local",mode)
If mode is nonzero, will force the associated module to go into local mode to allow front panel operation. In addition, the module will be placed in local mode after each count interval. If mode is zero, the module will be set to remote mode at the start of the next count interval, and will not be set back to local mode after counting. When spec starts up, not switching to local mode is the default behavior to minimize overhead.
counter_par(counter,"local")
Returns zero if the associated module is to be kept in remote mode. Otherwise, returns one.

Top