background image

3. Starting the work with the device

OPBOX-2.1 is powered from USB interface and is conform with USB2.0 standard. According
to   its  requirements   there   are   some  limits,   concerning   power   supply   (max.   start   current,
max.   continuous   power).   To   fulfill   this   standard   requirements   OPBOX   2.1   has   three
independent   power   supply   branches   (analogue   part,   12V   part   and   ADC/DAC   converters
part). Each branch has independent signals, switching it and showing error conditions.
After connecting the device to the USB port, all three branches are switched off and only
digital   part,   responsible   for   communication   is   working.   Before   starting   to   work   with   the
device (triggering acquisition) the user application must switch on the power supply of all
remaining branches.
Switching on sequence:

1. Setting bit [0] „Power Enable” in POWER_CTRL register;
2. Checking bit [4] „Power OK” in reg. POWER_CTRL until the value '1' will occur.

If the flag „Power OK” is set, the device is ready to work.
1. In each moment the user can check status flags of all power supply branches: „ANALOG
PWR Status”, „DC12V Status” and „VREG Status” in POWER_CTRL register. 
Switching  off analogue  branch   of  the  device  causes  loss  of  DAC   converter  settings,  thus
after each switching on sequence it is necessary to actualize some device settings:
1.

PULSE_AMPLITUDE (commend: (0xD6));

2.

Amplifier setting – register CONST_GAIN (Address: 0x28).

If the device cannot switch on the power in a correct way (the flag „power ON“ is not set
during few seconds) it is necessary to control the following:
1.

USB cable – if it is not damaged, of poor quality or too long;

2.

The cable should be replaced, the condition of the device controlled again;

3.

DB15   connector   should   be   disconnected,   if  used   and   the   device  condition   should   be

controlled again;
4.

The device should be connected to another computer and checked again.

During data acquisition the device automatically block the measurement command, if any of
status   flags   signals   a   failure.   In   the   case   if   the   voltage   of   USB   power   supply   falls
significantly during  100ms,  the  device automatically restarts  the  power supply sequence,
switching off all power supply branches and than switching them on again. During this time
all data acquisitions are blocked.
In the header of each acquisition status byte TriggerOverrunSource is written (byte 8) – it
contains the information  about  the source of  lost  triggers since last completed   till  actual
acquisition. If during this time one or more triggers couldn't be executed due to the failure
or overload of power supply, the flag „TrgOvrScr“ will be set to „1“.

4. Introduction to data acquisition settings.

The data  acquisition  system   in  OPBOX  2.1  (firmware rev. 2.1.60) was designed  with  the

goal to reach a real time acquisition speed (PRF) of up to 10000 measurements per second.
The device stores the data in internal  memory and allows the software to read the data in
packets. This allows to reach high medium speed of measurement data for different sizes of
measurement windows and limits the necessity to communicate with the device on the level of
control   functions   (inquires,   confirmations,   readings   of   results   from   measurement   gates,
encoder positions, etc.)

4.1. Basic features of acquisition in FIFO mode:

Allows to make the acquisition in real time, until the buffer is full, without the need to
read the data. This allows to reach high speed of measurements repetition (PRF).

Large   hardware   FIFO   buffer   (256kB)   ensures   stable   PRF   and   allows   to   reach   the
independence from the fluctuation of data speed on the USB interface;

System   controller   ensures   the   priority   of   acquisition   trigger,   interrupting   the   reading
during the acquisition time and starting it again, after the measurement is made.

Each measurement cycles creates in memory a data frame, where first 54 bytes are a

Summary of Contents for OPBOX-2.1

Page 1: ...48 071 329 68 54 fax 48 071 329 68 52 e mail optel optel pl http www optel pl Wroc aw OPBOX ver 2 1 Miniature ultrasonic data acquisition system with integrated pulser receiver Description and manual...

Page 2: ...Packet 7 5 7 Acquisition in real time 7 6 Header of Acquisition Frame 9 7 Configuration and maintenance of acquisition in real time 10 8 Comments to the acquisition settings 12 8 1 Calculating maxima...

Page 3: ...A D converter Resolution 10 bit 8 bits are stored Maximum input voltage 0 5V Sampling frequency switchable MHz 100 50 33 3 25 20 16 7 14 3 12 5 11 1 10 9 1 8 3 7 7 7 14 i 6 67 Data buffer 1 262090 25...

Page 4: ...igital input GPI5 or IDX input for encoder module ENC2 9 GPO 1 TTL 5V Digital output GPO1 10 GPO 3 TTL 5V Digital output GPO3 11 GPI 0 TTL LVTTL Digital input GPI0 or trigger input EXT_X or CHA input...

Page 5: ...POS_L 0x50 10 TRG_OVERRUN 0x12 42 PDB_MAX_POS_H 0x52 11 XY_DIVIDER 0x14 43 PDC_START_L 0x54 12 TIMER 0x16 44 PDC_START_H 0x56 13 TIMER_CAPT 0x18 45 PDC_STOP_L 0x58 14 ANALOG_CTRL 0x1A 46 PDC_STOP_H 0x...

Page 6: ...o another computer and checked again During data acquisition the device automatically block the measurement command if any of status flags signals a failure In the case if the voltage of USB power sup...

Page 7: ...Disabled switched on with bit 9 storeDisable in register MEASURE causes that data from ADC converter are not stored to the memory of the device Only acquisition header is stored This mode can be used...

Page 8: ...ion Data Header Acquisition Data HEADER_SIZE 54 bytes DEPTH 1 262090 bytes Frame FRAME_SIZE HEADER_SIZE DEPTH Packet PACKET_LENGTH 3 Frames Figure 5 2 Data organization in Header and Packets in StoreD...

Page 9: ...crossing position 21 15 8 useful bits 17 0 22 0x38 23 16 23 0x00 reserved 24 PDA MaxVal 0x3A 7 0 PDA gate maximum value of signal in the gate 25 0x00 reserved 26 PDA MaxPos 0x3C 7 0 PDA gate position...

Page 10: ...ACKET_LENGTH trying to read data before will cause failure reading error timeout the time needed to fulfill all acquisitions depends mostly on a chosen trigger source and the size of Measurement Windo...

Page 11: ...ning in the buffer of the device N should be written to the register PACKET_LEN Only in this situation the change of PACKET_LEN register to the smaller one do not reset the frame buffer in the device...

Page 12: ...large throughput of measurement data from the device to the PC one should try to increase the length of the packet that allows to diminish the amount of calls of data check function PACKET_READY and...

Page 13: ...s the setting of PACKET_LEN to PACKET_LEN_MAX maximal possible with new DEPTH setting 8 3 2 Changing of the length of acquisition packet PACKET_LEN Changing the length of acquisition packet similar as...

Page 14: ...eader the amount of lost triggers since the start of previous acquisition and the reason for this event CAPT_REG register Each of flag TrgOvrScr_A TrgOvrScr_H TrgOvrScr_F and TrgOvrScr_P in CAPT_REG r...

Page 15: ...one During transmission of the TGC curves table to the device it is necessary to block the triggering of acquisitions It is recommended to use for this purpose the zeroing of bit 4 Trigger Enable in...

Page 16: ...and writing the position of this sample in the register PDx_REF_POS_L and _H 2 Mode Rising detects rising slope first event occurs when one sample is lower than PDx_REF_VAL and the next sample is high...

Page 17: ...4 Connect the encoder power supply external 5 Set the configuration bits of the module work mode negation input filter in the ENCx_CTRL register of chosen encoder module 6 Set bit 0 Encoder X Enable...

Reviews: