Home

DAQ-800

1. Input values from channels LEERY status DaqSingleDigitalInputScan logical device channel_array array_length input_array if status 0 printf Error reading digital input Status code d n status ZKK Close the FS KRAI status DaqCloseDevice logical device if status 0 printf Error closing device Status code d n status return status 13 89 13 31 DaqSingleDigitalOutput The DaqSingleDigitalOutput procedure provides a simplified interface for outputting a single point to a single digital output channel The format of the command is shown below The value specified by output value is output to the digital output channel specified by channel number on the adapter specified by logical device This procedure executes the DAQDRIVE procedures DaqDigitalOutput DagArmRequest DaqTriggerRequest and DaqReleaseRequest before returning to the calling application unsigned short DaqSingleDigitalOutput unsigned short logical_device unsigned short channel number void far output value logical_device This unsigned short integer value is used to define the target hardware device This is the value returned to the application by the DaqOpenDevice command channel_number This unsigned short integer value is used to specify which digital output channel on logical_device is to receive the output data output_value This void pointer specifies the address of the dat
2. Figure 12 Analog output request structure IMPORTANT 1 Once the request is armed using DagArmRequest the only field the application can modify is request status All other fields in the request structure must remain constant until the operation is completed or otherwise terminated 2 If the request structure is dynamically allocated by the application it MUST NOT be de allocated until the request has been released by the DaqReleaseRequest procedure In addition applications using the Windows DLL version of DAQDRIVE should use DaqAllocateMemory if dynamically allocated request structures are required 13 11 channel_array_ptr This pointer defines the address of an unsigned short integer array specifying the logical analog output channel s to be operated on by this request reserved1 4 This unsigned short integer array is reserved for the future expansion of DAQDRIVE For maximum compatibility the application should initialize all reserved variables to 0 array_length This unsigned short integer value defines the number of channels contained in the array pointed to by channel_array_ptr DAC_buffer This pointer defines the address of the first data buffer structure Data buffer structures are discussed in chapter 9 reserved2 4 This unsigned short integer array is reserved for the future expansion of DAQDRIVE For maximum compatibility the application should initialize all reserved va
3. Step 1 Initialize Hardware logical_device 0 status DaqOpenDevice DAQ1200 amp logical_device device_type config_file if status 0 printf Error opening device Status code d n status exit status Step 2 Output the value to channel 2 KERJ output_value 1 status DaqSingleDigitalOutput logical_device 2 amp output_value if status 0 printf n nDigital I O output error Status code d n n status else printf n nComplete No errors Step 3 Close Hardware Device status DagCloseDevice logical_device if status 0 printf Error closing device Status code d n status return status DaqSingleDigitalOutput is a very basic interface without any allowance for multiple channels multiple output values trigger sources etc It acts as a DAQDRIVE macro defining the necessary data structures executing the digital output configuration procedure DaqDigitalOutput arming the requested configuration DaqgArmRequest and triggering the operation DaqTriggerRequest For users interested in learning more about DAQDRIVE s digital output interface the following example program creates the equivalent of the DaqSingleDigitalOutput procedure DAQDRIVE User s Manual 3 21 unsigned short MySingleDigitalOutput unsigned short logical_device unsigned short channel_number void far output_value struct digio_reques
4. Step 1 Initialize Hardware logical_device 0 status DaqOpenDevice DA8P 12 if status 0 printf Error opening device exit status amp logical_device device_type config_file Status code d n status Step 2 Output the digital I O values Mad status DaqSingleDigitalOutputScan logical device channel_array B output_array if status 0 printf n nDigital I O output error Status code d n n status else printf n nComplete No errors Step 3 Close Hardware Device status DagCloseDevice logical_device if status 0 printf Error closing device Status code d n status return status DaqSingleDigitalOutputScan is a very basic interface without any allowance for timing information trigger sources etc It acts as a DAQDRIVE macro defining the necessary data structures executing the digital output configuration procedure DaqDigitalOutput arming the requested configuration DaqArmRequest and triggering the operation DaqTriggerRequest For users interested in learning more about DAQDRIVE s digital output interface the following example program creates the equivalent of the DaqSingleDigitalOutputScan procedure 3 24 unsigned short MySingleDigitalOutputScan unsigned short logical_device unsigned short far channel array unsigned short array length void far output array struct digio_re
5. Step 4 Arm the Request status DagArmRequest request_handle if status 0 printf Arm request error Status code d n status DaqReleaseRequest request_handle DaqCloseDevice logical device exit status Step 5 Trigger the Request status DaqTriggerRequest request handle if status 0 printf Trigger request error Status code d n status DaqReleaseRequest request_handle DaqCloseDevice logical_device exit status Step 6 Wait for completion or error SE event mask COMPLETE_EVENT RUNTIME ERROR EVENT while user_request request_status amp event mask 0 wait for event if user_request request_status amp COMPLETE EVENT 0 printf n n D A Output Request complete n else printf Run time error Operation aborted n DaqReleaseRequest request_handle DaqCloseDevice logical_device exit status Step 7 Release the Request status DaqReleaseRequest request_handle if status 0 printf Could not release configuration Status code sd n status exit status Step 8 Close Hardware Device status DagCloseDevice logical_device if status 0 printf Error closing device Status code d n status return status DAQDRIVE User s Manual 12 16 12 2 4 Example 4 This example outputs 600 cycles of a sinewave 300 cycles of a ramp and 18
6. automatically initialized to all 0 main Initialize Hardware 0 printf Error opening device exit status the digital output request structure channel_array_ptr array_length digio_buffer trigger_source trigger_mode IO_mode clock_source sample_rate number_of_scans scan_event_level timeout_interval my_data user_request Output a pattern to digital output channel 0 unsigned short logical device unsigned short request handle unsigned short channel unsigned short status unsigned char pattern 20 0 1 1 0 1 Lu Ah Te 0 L D Leo He D ip ie oprit unsigned long event_mask char far device_type DA8P 12B char far config_file da8p 12b dat adi amp logical_device Status code Step 2 Output data channel 0 Prepare Buffer Structure my_data data_buffer pattern Z my_data buffer_length 20 j my data buffer cycles 500 my_data next_structure NULL my_data buffer_status BUFFER_FULL I amp channel 1 my data INTERNAL TRIGGER CONTINUOUS_TRIGGER BACKGROUND_IRQ INTERNAL_CLOCK 200 20 500 0 0 structures are KKKJ adi Mad device_type config_file sd n status set pointer to output data number of points in buffer 500 cycles through buffer indicate no more buffers indicate buffer full ready aK arr
7. Figure 17 continued Digital output request structure definition DAQDRIVE User s Manual 13 32 include daqdrive bi include userdata h JEKKAKKKAKKKKKKKKKKKKK e hh IIIA ARR e hh I RR RR AKI I I k k k k k k k k k d Output three 50 point patterns to three digital output channels XL JEKKAKKKAKKKKKKKKKKKKK e hh kk IA ARR KKK KKK k k A k k k k k k k k k k k unsigned short main unsigned short logical_device unsigned short request_handle unsigned short channel_num 3 0 1 5 unsigned short status unsigned char data_array 150 struct digio_request user_request struct DAQDRIVE buffer data structure k Open the device see DaqOpenDevice ERKEK k Prepare data structure for digital output EER EK BRR RK KK e He e II k A e hh hh hh IR A e e hh hh A A e e A A k e hh k k kk k kk k k kk k k d data is in data_array data_array is 150 points long SE output buffer 10 times next_structure NULL no more structures SZ JEKKAKKKAKKKKKKKKKKKKKKKAKKKKKKKKKKKAKAKAKKKKKKKKKKKAKAKAKKKKKKKKKKKKKKKKKKJ data structure data buffer data array data structure buffer length 150 data_structure buffer_cycles 10 data_structure next_structure NULL Jenni Prepare the digital output request structure KREKKJ JEKKAKKKAKKKKKKKKKKKKK KKK KKKKKKKKKKKAKAKAKKKKKKKKKKKAKAKKKKKKKKKKKKKKKKKKKKJ channel list is in channel num channel num is 3 channels long XL data is in da
8. Step 2 Input data channel 0 gain 2 Prepare Buffer Structures my_data 0 data_buffer amp buffer 0 0 set pointer to data array ay my_data 0 buffer_length 1000 number of points in buffer ay my_data 0 next_structure amp my_data 1 point to next buffer ay my_data 0 buffer_status BUFFER_EMPTY buffer empty ready XI my_data 1 data_buffer amp buffer 1 0 set pointer to data array XI my_data 1 buffer_length 1000 number of points in buffer vy my_data 1 next_structure amp my_data 2 point to next buffer SR my_data 1 buffer_status BUFFER_EMPTY buffer empty ready y my_data 2 data_buffer amp buffer 2 0 set pointer to data array XZ my_data 2 buffer_length 1000 number of points in buffer SR my_data 2 next_structure amp my_data 3 point to next buffer See my_data 2 buffer_status BUFFER_EMPTY buffer empty ready 12 9 if status 0 printf A D request error Status code DaqCloseDevice logical_device exit status Step 3 Arm the Request status if status printf Arm request error Status code DaqReleaseRequest request_handle DaqCloseDevice logical_device exit status Daq rmRequest request_handle be 0 Step 4 Open a data file Mad output file fopen ADC_DATA ASC w KKKJ Step 5 Trigger the Re
9. Another simple case of digital output is to output one value each to multiple digital I O channels under CPU control This allows multiple digital outputs to be updated simultaneously or nearly simultaneously depending on the data acquisition hardware A simplified interface for this operation is provided through the DagSingleDigitalOutputScan procedure The format of this command is shown below unsigned short DaqSingleDigitaloutputScan unsigned short logical_device unsigned short far channel array unsigned short array length void far output_array DaqSingleDigitalOutputScan outputs the values in the array specified by output_array to the digital I O channels in the array specified by channel array on the adapter specified by logical device A digital I O channel may appear in channel_array only once and a one to one correspondence is required between the number of digital output channels and the number of output values Therefore array_length specifies the length of both channel_array and output_array The following example shows the usage of DagSingleDigitalOutputScan DAQDRIVE User s Manual 3 23 Output a single sample to digital I O channels 1 2 3 unsigned short main unsigned short logical_device unsigned short status unsigned short channel_array 5 1 2 3 4 5 unsigned char output arrayl5 e QO E E char far device type DA8P 12B char far config file da8p 12b dat
10. DAQDRIVE User s Manual 6 7 6 3 2 Example 2 Simple Waveform Generation Purpose Output 300 cycles of a 60 Hz sinewave defined with 180 points per cycle struct struct KKK KK KKK KK KKK KK my_request channel_array_ptr my_request array_length my request DAC buffer my request trigger source my request trigger slope my request 10 mode my request clock source my data buffer status unsigned short channel number unsigned short sinewave 180 DAC_request my_request DAQDRIVE buffer my data Assume data values have been calculated HRA ERT and stored in sinewave AA EE Construct the request structure KKK kchannel number 1 my data TTL_TRIGGER RISING_EDGE FOREGROUND_DMA INTERNAL_CLOCK my_request sample_rate 60 180 my_request number_of_scans 300 180 my_request scan_event_level 0 my_request calibration NO_CALIBRATION my_request timeout_interval 0 my_request request_status NO_EVENTS Construct the data buffer structure ERARE my_data data_buffer sinewave my_data buffer_length 180 my_data buffer_cycles 300 my_data next_buffer NULL BUFFER_FULL Variations on example 2 To change the number of points from 180 to 360 re define sinewave J and then set my request sample rate 60 360 my request number of scans 300 360 my data buffer length 360 To change the number of cycles from 300 to 15 000 set my request numb
11. To guarantee structures are byte aligned within the Borland C C environment select Options Compiler Code Generation then confirm the Word alignment box is not checked For byte aligned structures from the Borland C C command line use the a option 2 3 2 3 Program optimization When selecting the optimization options for the Borland C C compiler problems may arise if the Invariant code motion option is selected and DAQDRIVE is operated in one of the background modes IRQ or DMA To disable the Invariant code motion optimization within the Borland C C environment select Options Compiler Optimizations then confirm the Invariant code motion box is not checked From the Borland C C command line make sure the Om and O2 options are not used IMPORTANT It is strongly recommended that the Invariant code motion optimization option be disabled when using the Borland C C compiler 2 6 2 4 Creating DOS Applications Using The TSR Drivers DAQDRIVE provides a TSR Terminate and Stay Resident driver for creating DOS applications in any language that supports software interrupt int calls In addition libraries are provided to interface the following high level languages to the DAQDRIVE TSR Visual Basic for DOS Quick Basic version 4 5 Turbo Pascal version 7 0 and newer and most C compilers Although the interface to each of these languages is similar the methods for generating applicati
12. channel_number gain_settings 4 my data TTL_TRIGGER RISING_EDGE FOREGROUND_CPU INTERNAL_CLOCK my_request channel_array_ptr my_request gain_array_ptr my_request array_length my request ADC buffer my request trigger source my request trigger slope my request 10 mode my request clock source my request sample rate 500 my_request number_of_scans 1000 my_request scan_event_level 0 my_request calibration NO_CALIBRATION my_request timeout_interval 0 my_request request_status NO_EVENTS Construct the data buffer structure Ae 4 my_data data_buffer input_values my_data buffer_length 4 1000 my_data next_buffer NULL my_data buffer_status BUFFER_EMPTY Variations on example 2 1 To change the number of points from 1000 per channel to 5000 per channel re define input valuesi and then set my_request number_of_scans 5000 my_data buffer_length 4 5000 2 To notify the application every time 100 scans are complete set my_request scan_event_level 100 3 To enable a time out if no data is available for a period of 3 seconds set my_request timeout_interval 3 5 8 6 D A Converter Requests In chapter 3 some special purpose procedures were presented to help the user get familiar with DAQDRIVE s D A converter interface The key to understanding and utilizing DAQDRIVE however is to understand its request structures This chapter will present the analog
13. my ADC data 500 The final step is to set the BUFFER_EMPTY status in the buffer_status field Once BUFFER_EMPTY is set and the request is armed the application must not modify my_ADC_data or input_data until BUFFER_FULL is set or until the operation is terminated my_ADC_data buffer_status BUFFER_EMPTY 9 8 9 2 3 Example 3 Using Multiple Data Buffers The purpose of this example is to use multiple data buffers to input 25 000 samples from a single analog input channel The application could allocate a single 25 000 sample buffer but for this example will allocate one 10 000 sample buffer and one 15 000 sample buffer Assuming a 12 bit A D converter operating in unipolar mode the samples are each size unsigned short unsigned short input_data0 10000 unsigned short input_datal1 15000 The next step is to allocate and configure two DAQDRIVE _buffer structures The data_buffer fields are set to point to the arrays defined above and the buffer_length fields are set accordingly The first structure has its next_structure field set to point to the second structure The second structure has its next_structure field set to NULL struct DAQDRIVE _buffer my_ADC_data 2 my_ADC_data 0 data_buffer my_ADC_data 0 buffer_length my_ADC_data 0 next_structure input_data0 10000 my_ADC_data 1 my_ADC_data 1 data_buffer my_ADC_data 1 buffer_length my_ADC_data 1 next_structure input_datal 15000 NU
14. DAQDRIVE User s Manual 13 42 resolution This unsigned short integer value specifies the resolution of the D A converter in bits signal_type This unsigned short integer value specifies the D A output signal type Value Description Ox0001 When set to 1 this bit indicates the D A output is bipolar Ox0002 When set to 1 this bit indicates the D A output is unipolar data_coding This unsigned short integer value specifies the D A data coding format Value Description 0 Indicates data is in two s complement format 1 Indicates data is in binary format min_digital This long integer value defines the minimum digital value accepted by the D A max_digital This long integer value defines the maximum digital value accepted by the D A zero_offset This long integer value defines the offset or zero value of the D A min_analog This floating point value defines the minimum analog output from the D A max_analog This floating point value defines the maximum analog output from the D A min_sample_rate This floating point value specifies the minimum sampling rate supported by the D A max_sample_rate This floating point value specifies the maximum single channel sampling rate supported by the D A max_scan_rate This floating point value specifies the maximum multi channel scanning sampling rate supported by the D A reference_source This u
15. _fmalloc exp_info gain_array_length sizeof float k Get the available gain settings EKRE status DaqGetExpGainInfo logical_device ADC_device exp_device gain_array if status 0 printf Error getting expansion board gain settings n printf Status code d n status exit status Display the available gain settings E fp printf Expansion board d supports the following gains n exp device for i 0 i lt exp_info gain_array_length i printf gain d f n i gain_arrayl i 13 57 13 18 DaqGetRuntimeError DaqGetRuntimeError returns the last run time error encountered by the request specified by request_handle unsigned short DaqGetRuntimeError unsigned short request_handle unsigned short far terror code request handle This unsigned short integer variable is used to define which request s error status to retrieve This is the value returned to the application by the configuration procedures DaqAnaloginput DaqAnalogOutput DaqDigitalInput or DaqDigitalOutput error_code This pointer defines an unsigned short integer where the error code from the last run time error will be stored Chapter 14 provides an explanation of these error codes DAQDRIVE resets the request s error_code to 0 each time the request is armed DAQDRIVE User s Manual 13 58 include daqdrive bi include userdata h BRR RK KK KK II e hh I A ARR e hh A e
16. amp output_value Step 3 Output value to channel Greg Step 4 Close Hardware Device LER status DaqCloseDevice logical device if status 0 printf Error closing device Status code d n status return status logical device 0 status DaqOpenDevice DAQ1200 glogical device device type config file if status 0 printf Error opening device Status code d n status printf n nEnter a digital output channel number or 99 to quit status DaqSingleDigitalOutput logical device channel sgoutput value if status 0 printf n n Digital output error Status code d n n status printf Press lt ESC gt to continue n while getch Oxlb while channel 99 DAQDRIVE User s Manual 12 24 12 4 2 Example 2 This example outputs a 20 point pattern to digital output channel 0 Step 1 status if status Prepare struct DAQDRIVE buffer struct digio request unsigned short logical device DagOpenDevice DA8P 12 0 user_request user_request user_request user_request user_request user_request user_request user_request user_request user_request user_request include lt stdlib h gt include lt stdio h gt include lt math h gt include userdata h include daqdrive h tinclude daqopenc h include da8p 12 h When defined global or static
17. dev_info ADC_devices printf Sd D A converter s n dev_info DAC_devices printf Sd digital I O device s n dev_info digio_devices printf and d counter timer channel s n dev_info timer_devices 13 49 13 15 DaqGetDigioCfgInfo DaqGetDigioCfgInfo returns the configuration of the digital I O channel specified by digio_device on the adapter specified by logical_device unsigned short DaqGetDigioCfgInfo unsigned short logical_device unsigned short digio_device struct digio_configuration far digio_info logical_device digio_device digio_info This unsigned short integer value is used to define the target hardware device This is the value returned to the application by the DaqOpenDevice command This unsigned short integer value is used to select one of the digital I O channels on the target hardware device This structure pointer defines the address of a digital I O configuration structure where the configuration of the specified digital I O channel will be stored struct digio_configuration unsigned short data_size unsigned short io_mode T data size This unsigned short integer value specifies the size of the digital I O channel in bits io_mode This unsigned short integer value specifies the operating mode of the digital I O channel Value Description 0x0001 When set to 1 this bit indicates the digital I O channel is configured for i
18. k Request A D input See DagAnalogInput KKK Arm the request HERES status DagArmRequest request_handle if status 0 printf Arm request error Status code d n status DaqReleaseRequest request_handle DaqCloseDevice logical device exit status x Trigger the request HERE status DaqTriggerRequest request_handle if status 0 printf Trigger request error Status code d n status DaqStopRequest request_handle DaqReleaseRequest request_handle DaqCloseDevice logical_device exit status Abort the request PERE status DaqStopRequest request_handle if status 0 printf Request failed to stop Status code d n status k x Release the request KEREKES status DaqReleaseRequest request_handle if status 0 printf Could not release configuration Status code d n status k Close the DAQP 16 status DagCloseDevice logical_device if status 0 printf Error closing device Status code d n status return status 13 95 13 34 DaqTriggerRequest When an operation has been configured for an internal trigger DaqTriggerRequest is executed after the DagArmRequest function to start the operation An error is returned to the application if DaqTriggerRequest is executed for an operation not configured for internal trigger This error is non fatal and program execution
19. no scan events user_request calibration NO_CALIBRATION no calibration user_request timeout_interval 0 disable time out user_request request_status 0 initialize status request_handle 0 new request status DaqgAnalogInput logical device amp user_request amp request_handle SO Ann status sd n status seconds Please wait n sd n status Mad RUNTIME_ERROR_EVENT BUFFER_FULL fprintf output file 6d n buffer current_buffer i BUFFER EMPTY buffer empty XL SI N St TY SI St E Wi DAQDRIVE User s Manual 12 10 if current_buffer 3 current_buffer 0 else current_buffer t while user_request request_status amp event_mask 0 wait for event Ze Exit if error KEKA if user_request request_status amp RUNTIME_ERROR_EVENT 0 DaqGetRuntimeError request_handle amp status printf n n nRun time error Error code td Operation aborted n status DaqReleaseRequest request_handle DaqCloseDevice logical_device fclose output file exit status Write any remaining buffers and close file RAK do if my_data current_buffer buffer_status BUFFER_FULL for i 0 i lt 1000 i fprintf output_file 6d n buffer current_buffer i my_data current_buffer buffer status BUFFER_EMPTY buffer empty if current_buf
20. Arm the Request status DagArmRequest request_handle if status 0 printf Arm request error Status code d n status DaqReleaseRequest request_handle DaqCloseDevice logical_device exit status Step 4 Trigger the Request status DaqTriggerRequest request_handle if status 0 printf Trigger request error Status code d n status DaqReleaseRequest request_handle DaqCloseDevice logical_device exit status Step 5 Wait for completion or error EREN event_mask COMPLETE_EVENT RUNTIME_ERROR_EVENT printf TaT printf n Press lt ESC gt to continue while getch Oxlb else printf Run time error Operation aborted n DaqReleaseRequest request_handle DaqCloseDevice logical_device exit status T xxx Step 6 Release the Request status DaqReleaseRequest request_handle if status 0 printf Could not release configuration Status code sd n exit status Step 7 Close Hardware Device KEES status DaqCloseDevice logical_device if status 0 printf Error closing device Status code d n status return status status DaqgAnalogInput logical device amp user_request amp request_handle printf Acquiring data This will take 2 seconds Please wait n while user_request request_status amp event mask 0 wait for event if user_request requ
21. Status code d n status exit status Display the available gain settings KKKKKJ printf The DAQ 1201 supports the following A D gain settings n for i 0 i lt ADC_info gain_array_length i printf gain d f n i gain_arrayl i 13 41 13 12 DaqGetDACfgInfo DaqGetDACfegInfo returns the configuration of the D A converter specified by DAC_device on the adapter specified by logical_device unsigned short DaqGetDACfgInfo unsigned short logical_device unsigned short DAC_device struct DAC_configuration far DAC_info logical_device This unsigned short integer value is used to define the target hardware device This is the value returned to the application by the DaqOpenDevice command DAC device This unsigned short integer value is used to select one of the D A converters on the target hardware device DAC_info This structure pointer defines the address of a D A configuration structure where the configuration of the specified D A converter will be stored a DAC_configuration unsigned short resolution unsigned short signal_type unsigned short data_coding long min_digital long max digital long zero offset float min analog float max analog float min sample rate float max sample rate float max scan rate unsigned short reference source float reference voltage unsigned short gain array length unsigned short calibration modes Ir
22. This is an unsigned long integer value defining the number of data points to be converted word_array must be at least array_length short integers in length while byte_array must be at least array_length 2 short integers array_length bytes in length DAQDRIVE User s Manual 13 102 include daqdrive h include userdata h JEKKAKKKAKKKKKKKKKKKKKKKAKKKKKKKKKKKKKAKAKKKKKKKKKKKAKAKAKKKKKKKKKKKKKKKKKKJ Output 16 points to a digital output channel tj JEKKAKKKAKKKKKKKKKKKKKKAKAKKKKKKKKKKKAKAKAKKKKKKKKKKKAKAKAKKKKKKKKKKKKKKKKKKJ unsigned short main unsigned short logical_device unsigned short request_handle unsigned short channel num unsigned short status unsigned short data_array 16 unsigned short array_index struct digio_request user_request struct DAQDRIVE buffer data_structure Open the device see DaqOpenDevice RES 224 k Prepare output data ERE RES for array_index 0 array index lt 16 array_index data arraylarray indexl array_index Pack data for output KERER DaqWordsToBytes data_array data_array 16 Prepare data structure for digital output PERKY JEKKAKKKAKKKKKKKKKKKKKKKAKKKKKKKKKKKAKAKAKKKKKKKKKKKAKAKAKKKKKKKKKKKKKKKKKKJ data is in data array data array is 16 points long X output buffer 1 time next_structure NULL no more structures ay JEKKAKKKAKKKKKKKKKKKKKKKAKAKKKKKKKKKKKKAKAKKKKKKKKKKKAKAKAKKKKKKKKKKKKKKKKKKJ
23. This pointer defines the starting address of a character array string which defines the name of the DAQDRIVE configuration file to be used This character string must contain the drive path filename and extension of the desired configuration file DAQDRIVE User s Manual 13 68 include daqdrive h include daqopenw h include userdata h unsigned short main unsigned short logical_device unsigned short status char far device type DAQP 208 char far config_file c daqp 208 daqp 208 dat char far DLL_name c daqp 208 daqpwin dll n k Open the DAQP 208 logical_device 0 status DaqOpenDevice DLL_name KSlogical device device type config_file if status 0 printf Error opening configuration file Status code d n status exit status Perform any DAQP 208 operations here EE k Close the DAQP 208 status DagCloseDevice logical_device if status 0 printf Error closing device Status code d n status return status include daqdrive bi include daqopenw h include userdata h unsigned short main unsigned short logical device unsigned short status char far device type IOP 241 char far config_file c iop 241 iop 241 dat n char far DLL_name iop 241 dll1 k Open the IOP 241 logical_device 0 status DaqOpenDevice DLL_name KSlog
24. W Most Windows languages supporting Dynamic Link Libraries DLLs including Visual C C Borland C C Turbo Pascal for Windows and Borland Delphi DAQDRIVE uses a data defined rather than a function defined interface What this means is that each data acquisition operation is defined by a series of configuration parameters and requires very few function calls to implement Because of this approach DAQDRIVE may seem a little unusual even intimidating at times However after writing a few example programs we feel the user will discover the power behind this type of interface DAQDRIVE supports high speed data I O by providing support for foreground CPU software polled and background DMA and interrupt driven operation For increased flexibility DAQDRIVE also supports software internal and hardware external clock and trigger sources DAQDRIVE supports multiple data acquisition adapters in a single system In fact the number of adapters is limited only by the amount of available system memory DAQDRIVE also supports multiple tasks from one or more applications operating on one or more hardware devices This multi tasking support is accomplished by tracking all system and data acquisition resources and rejecting any request for which all of the necessary resources are not available DAQDRIVE User s Manual 1 1 In order to minimize the code size of the application programs DAQDRIVE is distributed as a two part driver
25. languages which support the Windows DLL Dynamic Link Library interface When the Windows application programs are executed they must be able to dynamically link to DAQDRIVE DLL and one or more hardware dependent DLLs Windows searches for any necessary DLLs in the following locations 1 the current directory 2 the Windows directory directory containing WIN COM 3 the Windows System directory directory containing GDI EXE 4 the directory of the application program 5 all directories specified by the PATH environment variable 6 all directories mapped to network drives The DAQDRIVE installation program installs the DAQDRIVE DLL and the DLLs for any selected hardware device into the Windows System directory In addition the installation program installs the DAQDRIVE import library DAQDRIVE LIB into the DAQDRIVE WINDLL directory This import library can be used by many Windows compilers to simplify the linking of application programs to the APIs available within the DAQDRIVE DLL DAQDRIVE has been tested with application programs written in Microsoft Visual C C Borland C C Turbo Pascal for Windows and Borland Delphi The following sections provide additional information about producing Windows applications in the languages above DAQDRIVE User s Manual 2 21 2 5 1 Microsoft Visual C C To generate application programs using the DAQDRIVE DLL with Microsoft Visual C C the application must be linked with
26. request is armed 2 Once the request is armed using DaqgArmRequest the only field the application can modify is request_status All other fields in the request structure must remain constant until the operation is completed or otherwise terminated 3 If the request structure is dynamically allocated by the application it MUST NOT be de allocated until the request has been released by the DaqReleaseRequest procedure In addition applications using the Windows DLL version of DAQDRIVE should use DaqAllocateMemory if dynamically allocated request structures are required 62 1 Reserved Fields The fields reserved through reserved5 are provided for expansion of the analog output request structure in future releases of DAQDRIVE To maintain maximum compatibility the application program should initialize all reserved fields to 0 6 2 2 Channel Selections The analog output request structure begins with a list of one or more analog output channels to be operated on by this request The application provides the memory address of the first channel in the list using the channel_array_ptr field and must specify the length of the list in the array_length field 6 2 3 Data Buffers DAC_buffer defines the request s data buffer structure s containing the data to be output to the specified channel s The application program must define these buffers within the guidelines provided in chapter 9 6 2 4 Trigger Selections The trigger sele
27. xxx Step 7 Release the Request status DaqReleaseRequest request_handle if status 0 printf Could not release configuration Status code sd n status exit status Step 8 Close Hardware Device status DaqCloseDevice logical device if status 0 printf Error closing device Status code d n status return status l E wait for event i DAQDRIVE User s Manual 12 26 13 Command Reference Analog Input DaqAnalogInput DaqSingleAnaloginput DaqSingleAnaloginputScan Digital Input DaqDigitalInput DaqSingleDigitalinput DaqSingleDigitalinputScan Process Control DagArmRequest DaqCloseDevice DaqOpenDevice DaqReleaseRequest DagResetDevice DagStopRequest DaqTriggerRequest System Configuration DaqGetA DCfgInfo DaqGetA DGaininfo DaqGetDACfgInfo DaqGetDAGaininfo DaqGetDeviceCfgInfo DaqGetDigioCfgInfo DaqGetExpCfegInfo DaqGetExpGainInfo Analog Output DaqAnalogOutput DaqSingleAnalogOutput DaqSingleAnalogOutputScan Digital Output DaqDigitalOutput DaqSingleDigitalOutput DaqSingleDigitalOutputScan System Monitoring DaqGetRuntimeError DaqNotifyEvent DaqPostMessageEvent DaqUserBreak Miscellaneous DaqAllocateMemory DaqBytesToVVords DaqFreeMemory DaqVersionNumber DaqWordsToBytes 13 1 DaqAllocateMemory DaqAllocateMemory is a DAQDRIVE utility function used to dynamically allocate memory for use by the application program All
28. 13 12 trigger_voltage This double precision value defines the trigger voltage level for the analog trigger trigger_voltage is ignored for all other trigger sources Trigger selections are discussed in chapter 10 trigger_value This unsigned long value defines the value required on the digital input for a digital trigger to be generated trigger_value is ignored for all other trigger sources Trigger selections are discussed in chapter 10 reserved3 4 This unsigned short integer array is reserved for the future expansion of DAQDRIVE For maximum compatibility the application should initialize all reserved variables to 0 IO_mode This unsigned short integer value specifies the method of data transfer clock_source DAQDRIVE Constant Value Description FOREGROUND_CPU 0 DAQDRIVE takes control of the CPU until the request is complete BACKGROUND_IRQ 1 hardware interrupts are used to gain control of the CPU and input the data FOREGROUND_DMA 2 DMA is used to input the data the CPU monitors controls the DMA operation BACKGROUND_DMA 3 DMA is used to input the data interrupts are used to monitor control the DMA operation This unsigned short value selects the clock source to provide the timing for multiple point output operations DAQDRIVE Constant Value Description INTERNAL_CLOCK 0 the sampling rate is generated by the on board clock circuitry EXTERNAL_CLOCK 1 the sampling rate is generated from an exte
29. 2 0 Loe short output_array 2 1024 2316 unsigned short array_length 2 char far device type DAQP 208 char far config_file c daqp 208 daqp 208 dat Open the DAQP 208 logical_device 0 status DaqOpenDevice DAQP amp logical_device device type config file if status 0 printf Error opening configuration file Status code d n status exit status Output values to D A channels EREKE status DaqSingleAnalogOutputScan logical device channel_array array_length output_array if status 0 printf Error writing to D A Status code d n status fe ee Close the DAQP 208 status DaqCloseDevice logical device if status 0 printf Error closing device Status code d n status return status 13 85 13 29 DaqSingleDigitalInput The DaqSingleDigitalinput procedure provides a simplified interface for inputting a single point from a single digital input channel The format of the command is shown below The digital input specified by channel_number on the adapter defined by logical_device is returned to the address specified by input_value This procedure executes the DAQDRIVE procedures DaqDigitalinput DagArmRequest DaqTriggerRequest and DaqReleaseRequest before returning to the calling application unsigned short DaqSingleDigitalInput unsigned short logical_device unsigned short channel_number
30. 5 3 Foreground DMA mode This mode uses the DMA controller to output the data to the hardware device while using the CPU to monitor and control the DMA operation From the moment the request is triggered DAQDRIVE uses all of the CPU time and will not return control to the application program until the request is completed or otherwise terminated 6 2 5 4 Background DMA mode This mode uses the DMA controller to output the data to the hardware device while using interrupts generated by the hardware device to gain control of the CPU to monitor and control the DMA operation DAQDRIVE does not require all of the CPU time in this mode and returns control of the CPU to the application after the request is triggered 6 2 6 Clock Sources The clock_source field is used to define the source of the timing signal for requests containing multiple data values 6 2 6 1 Internal Clock When the clock source field is set for an internal clock the timing for the request is provided by the adapter s on board timer circuitry The clock_rate field is unused with the internal clock source and any value provided in the clock_rate field is ignored 6 2 6 2 External Clock Setting the clock_source field to external indicates the timing for the request is provided by a signal input to the adapter as defined by the hardware device The clock_rate field must be used to define the frequency of the external clock signal in Hertz 6 4 6 2 7 Sampling Rate
31. DAQDRIVE s analog output interface the following example program creates the equivalent of the DaqSingleAnalogOutputScan procedure 3 12 unsigned short MySingleAnalogOutputScan unsigned short logical_device request_handle 0 status DaqAnalogOutput logical_device my_request amp request_handle if status 0 return status Zinnen If no errors arm the request KAKKKJ status DagArmRequest request handle if status 0 DaqReleaseRequest request_handle return status Jenni If no errors software trigger the request KKK status DaqTriggerRequest request handle if status 0 DaqStopRequest request_handle DaqReleaseRequest request_handle return status JAKAKAK If no errors release the request and return KAKKKJ status DaqReleaseRequest request handle return status unsigned short far channel array unsigned short array length void far output array struct DAC_request my_request struct DAQDRIVE buffer my data unsigned short request handle unsigned short status Construct the request structure KE my_request channel_array_ptr channel array my request array length array length my request DAC buffer bm data my request trigger source INTERNAL TRIGGER my request 10 mode FOREGROUND CPU my request number of scans 1 my_request scan_event_level 0 my_request calibration NO_CALIBRAT
32. DagSingleAnalogInputScan DAQDRIVE User s Manual 3 5 Input a single sample from A D channels 0 1 3 and 7 ad unsigned short main unsigned short logical_device unsigned short channel_array 4 0 1 3 7 unsigned short gain_array 4 St Le Dy ps Q E unsigned short status short input_array 4 char far device type DAQP 208 char far config_file daqp 208 dat Step 1 Initialize Hardware logical_device 0 status DaqOpenDevice DAQP amp logical_device device type config file if status 0 printf Error opening device Status code d n status exit status Step 2 Input one sample from each channel HERS status DaqSingleAnalogInputScan logical device channel_array gain_array 4 input_array if status 0 printf n nA D input error Status code d n n status else printf Channel 0 Sd n n input_array 0 printf Channel 1 Sd n n input_array 1 printf Channel 2 Sd n n input_array 2 printf Channel 3 Sd n n input_array 3 Step 3 Close Hardware Device status DagCloseDevice logical_device if status 0 printf Error closing device Status code d n status return status DagSingleAnalogInputScan is a very basic interface without any allowance for timing information trigger sources etc It acts as a DAQDRIVE macro defining the necessary data structures executing
33. DaqOpenDevice REA ERY k Get the expansion board configuration KERER ADC_device 0 exp_device 0 status DaqGetExpCfgInfo logical_device ADC_device exp device sexp info if status 0 printf Error getting exp board configuration Status code d n status exit status Display the expansion board configuration RARER printf Expansion board number d on A D number d n exp device ADC device if exp_info signal_type 1 printf is configured for unipolar and else printf is configured for bipolar and if exp_info input_mode 1 printf single ended operation n else printf differential operation n printf has d analog inputs n exp_info num_mux_channels printf and supports d gain settings n exp_info gain_array_length DAQDRIVE User s Manual 13 54 This page intentionally left blank 13 55 13 17 DaqGetExpGainInfo DaqGetExpGainInfo returns an array of the gain settings supported by the expansion board specified by exp_device connected to the A D converter specified by ADC_device on the adapter specified by logical_device The length of the array is determined by the gain_array_length variable returned by the DaqGetExpCfgInfo command unsigned short DaqGetExpGainInfo unsigned short logical_device unsigned short ADC_device unsigned short exp_device float far gain_array logical_device This unsigned short
34. DaqgAnalogInput logical device fuser request amp request_handle if status 0 printf A D request error Status code Sd n status DaqCloseDevice logical_device exit status Step 3 Arm the Request status DagArmRequest request_handle if status 0 printf Arm request error Status code d n status DaqReleaseRequest request_handle DaqCloseDevice logical device exit status Step 4 Trigger the Request printf Acquiring data This will take 10 seconds Please wait n status DaqTriggerRequest request_handle if status 0 printf Trigger request error Status code d n status DaqReleaseRequest request_handle DaqCloseDevice logical device exit status Step 5 Wait for completion or error AREY event_mask COMPLETE_EVENT RUNTIME_ERROR_EVENT while user_request request_status amp event mask 0 wait for event if user_request request_status amp COMPLETE EVENT 0 if successful display data for i 0 i lt 50 i _clearscreen _GCLEARSCREEN for j 0 j lt 20 j printf sample 4d value 6d n 1120 tj input datal 1120 tj1 5 printf n Press SESC to continue while getch Oxlb else printf Run time error Operation aborted n DaqReleaseRequest request_handle DaqCloseDevice logical_device exit status xxx Step 6 Rele
35. If no errors software trigger the request PERKY status DaqTriggerRequest request_handle if status 0 DaqStopRequest request_handle DaqReleaseRequest request_handle return status RRKKK If no errors release the request and return KAKKKJ status DaqReleaseRequest request handle return status H 3 10 3 2 2 DaqSingleAnalogOutputScan Another simple case of analog output is to output one value each to multiple D A converters under CPU control This allows multiple analog outputs to be updated simultaneously or nearly simultaneously depending on the data acquisition hardware A simplified interface for this operation is provided through the DagSingleAnalogOutputScan procedure The format of this command is shown below unsigned short DaqSingleAnalogoutputScan unsigned short logical device unsigned short far channel array unsigned short array length void far output_array DaqSingleAnalogOutputScan outputs the values in the array specified by output_array to the D A converter channels in the array specified by channel_array on the adapter specified by logical_device A D A channel may appear in channel_array only once and a one to one correspondence is required between the number of D A converter channels and the number of output values Therefore array_length specifies the length of both channel_array and output_array The following example shows the usage of DaqSingl
36. In each of these examples one data acquisition adapter was selected for the purpose of illustration All of these examples are written in C using the DOS C library version of DAQDRIVE Additional example programs are also provided on the distribution diskette s supplied with the data acquisition hardware 12 1 Analog Input A D Examples 12 1 1 Example 1 This example inputs a single value to a single A D channel Input a single point from a single A D channel ART include lt conio h gt include lt graph h gt include lt stdio h gt include lt stdlib h gt include userdata h include daqdrive h include daqopenc h include dagp h unsigned short main unsigned short logical_device unsigned short status unsigned short channel short input_value float gain char far device type DAQP 16 char far config_file daqp 16 dat Step 1 Initialize Hardware logical_device 0 status DaqOpenDevice DAQP glogical device device type config file if status 0 printf Error opening device Status code d n status exit status Step 2 Get A D channel and gain _clearscreen _GCLEARSCREEN printf n nEnter a channel number between 0 and 7 or 99 to quit scanf d amp channel if channel 99 printf n nEnter a gain of 1 2 4 or 8 scanf f amp gain Step 3 Input value from c
37. KA KA KKK KKKA KA KKK Perform all DAQDRIVE functions NKAKKAKAKAKA KA KKK KKK KA KA KA KA KA KKK KA KA KA KA KA KKK KA KA KA KKK AK KKK KA KA KA KA KKK KKKA KA KKK DaqOpenDevice DaqCloseDevice V KKK KKK KK KK KA KKK KKK AKA KA KA KA KKK KA KA KA KA KA KKK KA KA KA KKK AK KKK KA KA KA KA KKK KK KK KK KKK Optionally restore heap NAKKAKAKAKA KA KKK KKK AKA KA KA KA KKK KA KA KA KA KA KKK KA KA KA KA KKK KKK AKA KA KA KKK KKK AKA KKK HeapSize SETMEM 1410000 DAQDRIVE User s Manual 2 13 2 4 5 4 The DaqOpenDevice Command DAQDRIVE s DaqOpenDevice command requires two null terminated string variables DeviceType and ConfigFile Because Quick Basic does not support null terminated strings the user must create these strings by appending a null character CHRS 0 to the end of each string before passing it to DAQDRIVE For example A FILENAME DAT normal Quick Basic string B FILENAME DAT CHR 0 null terminated string Furthermore Quick Basic is unable to pass the address of a string variable as a far pointer To overcome this problem the DaqOpenDevice procedure is declared differently for the Quick Basic version of DAQDRIVE DaqOpenDevice BYVAL TSRNumber AS Integer SEG LogicalDevice AS Integer BYVAL DeviceTypeSegment AS Integer BYVAL DeviceTypeOffset AS Integer BYVAL ConfigFileSegment AS Integer BYVAL ConfigFileOffset AS Integer The string variables normally found in the DaqOpenDevice
38. The first part contains the application program interface API and is also responsible for memory management file I O and other hardware independent functions Regardless of the number of hardware devices installed only one copy of the hardware independent driver is required The second part of the driver is hardware dependent and is responsible for implementing the requested operations on the target hardware device These drivers are supplied with the data acquisition adapter and generally support only one family of hardware devices Only one hardware dependent driver is required for each family of hardware installed in the system Application Program 1 Hardyvare independent driver t Hardware dependent driver Figure 1 DAQDRIVE interface between an application program and one hardware device 1 2 Application Program Hardware independent driver Hardware dependent driver Figure 2 DAQDRIVE interface between an application program and multiple devices of the same family Application Program Hardware independent driver Hardware dependent driver Hardware dependent driver Figure 3 DAQDRIVE interface between an application program and multiple devices of different families DAQDRIVE User s Manual 1 3 This Page Intentionally Left Blank 1 4 2 Befor
39. The sampling rate specifies the number of samples second Hz to be output to the hardware device The application specifies a desired sampling rate in the sample_rate field of the request structure On most hardware devices only a finite number of sampling rates are achievable When DagAnalogOutput configures a request the closest available sampling rate is selected and the sample_rate field is updated with the actual rate at which the data will be output 6 2 8 Number Of Scans The number_of_scans field determines the number of times the channel s specified in the channel list are processed For example to output 100 samples to a single D A channel number_of_scans must be set to 100 To output 50 samples each to two D A channels 100 points total number_of_scans is set to 50 6 2 9 Scan Events DAQDRIVE generates a scan event each time the number of scans specified by scan_event_level are completed For example if scan_event_level is set to 50 a scan event is generated every time the channel array is processed 50 times DAQDRIVE events are discussed in detail in chapter 11 6 2 10 Calibration Selections The calibration field allows the application to specify the type of calibration to be performed if any by the hardware device s during the requested operation In general enabling calibration results in lower throughput rates while providing greater accuracy 6 2 10 1 Auto calibration Enabling auto calibration instructs
40. WER J status DaqCloseDevice logical_device if status 0 printf Error closing device Status code d n status return status request_handle 0 new request status DaqDigitalInput logical device amp user_request amp request_handle printf Digital input request error Status code sd n status while user_request request_status amp event mask 0 wait for event int input_data i 20 3 status DAQDRIVE User s Manual 12 22 This page intentionally left blank 12 23 12 4 Digital Output Examples 12 4 1 Example 1 This example outputs a single value to a single digital output channel Output a single point to a single D A channel EEK include lt conio h gt include lt graph h gt include lt stdio h gt include lt stdlib h gt include userdata h include daqdrive h include daqopenc h include daql200 h unsigned short main unsigned short logical_device unsigned short status unsigned short channel unsigned char output value char far device type DAQ 1201 char far config file daq 1201 dat Step 1 Initialize Hardware exit status Step 2 Get digital output channel and output value ERT _clearscreen _GCLEARSCREEN scanf d amp channel if channel 99 printf n nEnter the output value between 0 and 255 scanf Sd
41. a 6 3 6 2 3 Data BTR EE 6 3 6 24 Trigger Selections dy got ml R ee Wy wes oat NTR E WEES 6 3 6 2 5 Data Transfer Modes 6 3 6 2 6 Clock SOURCES n r Card ko Coe oh hd Lore t d 6 4 6 2 7 Sampling Rate neasi has ku o tae ee e ie sh ti oe 6 5 6 2 8 Number Of EEN 6 5 629 Scan EVES ites Saletan EN Set os Getta 6 5 6 2 10 Calibration Selections uua 6 5 62 HNS TS ee s a a Pa Eh aka E E E E to 6 6 6 2 12 Request Status d si Dei rep d da tt dh e ae 6 6 6 3 Analog Output Examples dat ga qara nte da pr na vs 6 7 6 3 1 Example 1 DC Voltage Level Output 6 7 6 3 2 Example 2 Simple Waveform Generation 7 8 7 Digital Input Requests 0 c eee ee 7 1 74 DagDigitallnp t EE 7 1 7 2 The Digital Input Request Structure 005 7 2 7 2 1 Reserved Fields njat J S ole aa Seth RE 7 3 7 2 2 Channel Selections eege Piao Pew Eee oh hee hare anys 7 3 7 2 3 Data Buffers EEN 7 3 7 2 4 Trigger Selections rn unnn nunna 7 3 7 2 5 Data Transfer Modes geegent e tehe e o dre EE 7 3 7 2 6 Clock SOURCES air i REEE ore Bab EE 7 4 72 7 SAM INS ALCS hes oo viti n dt DE hat ita as Silent aR ech a 7 5 EE per COL EE 7 5 72 9 ao E Aa a a a E A OAS 7 5 7 2 10 Time out ee eee tenes 7 5 7 2 11 Request Status isha e AN 7 5 7 3 Digital Input Examples nigra Cara sa De eh A COREG ORES 7 6 7 3 1 Example 1 Single Value Input aku WA I deh Seal tek ees 7 6 iv 7 3 2 Example 2 Multiple Val
42. a simple input operation is to acquire 100 samples from a single A D channel To perform this operation the application must first allocate enough memory to hold 100 samples Assuming a 12 bit A D converter operating in bipolar mode the samples are each size short Therefore the memory allocation may be done as simply as short input_data 100 The next step is to allocate and configure a DAQDRIVE _buffer structure data_buffer is set to point to the array defined above Its length is 100 points and there are no other structures so next_structure is set to NULL struct DAQDRIVE buffer my_ADC_data my_ADC_data data_buffer input_data my_ADC_data buffer_length 100 my_ADC_data next_structure NULL The next step is to allocate and configure an ADC_request structure The ADC_request structure is beyond the scope of this chapter and will not be discussed here except for the ADC_buffer and number_of_scans fields which directly relate to the data structure configuration For this example ADC_buffer is set to point to our DAQDRIVE _buffer structure and the number_of_scans is set to 100 scans 1 channel scan struct ADC request my_ADC_request my ADC request ADC buffer my_ADC_request number of scans my ADC data 100 The final step is to set the BUFFER_EMPTY status in the buffer status field Once BUFFER_EMPTY is set and the request is armed the application must not modify my_ADC_data or input_data until BUFFER_FU
43. ak More eae d 13 46 13 14 DaqGetDeviceCfgInfo EE 13 48 vi 13 15 DaqGetDigioCfgI nfo u ja dd K or r eo 13 50 13 16 Dag Gelixp ea Orinda dan i dd Da d Pe ae 13 52 13 17 DaqGetExpGain nfo gjor sea vate ae a Gate nn ent ae 13 56 13 18 DaqGetRuntimeError tege tata KAN Da es 13 58 13 19 DagGet limerCiaIniloss seria weeks dado ea AS 13 60 13 20 DaqNotifyEvent ag Sd R ciero EE 13 62 13 20 1 The user defined event procedure 13 63 E U DaqoOpe niDev C ga ves vs We wie one VSR eae a as 13 65 13 21 1 DaqOpenDevice C Library Version 13 66 13 21 2 DaqOpenDevice VVindovys DLL Version 13 68 13 21 3 DaqOpenDevice TSR Version 0 13 70 13 22 DaqPostM ssageE V N saccades oacd want de da nd EN 13 72 18 221 The Event Message ssc nu ae Po GE AS 13 73 13 23 D qRele seRequest EE 13 74 13 24 DaqResetDevice e Ze erg ech D Aen E See r 13 76 13 25 DaqSingleAnaloginiput ee ERENNERT 13 78 13 26 DagsingleAnalog in pultcani ngi dek dak Dade cake esas 13 80 13 27 DaqSingleAnalogOutput sates ndre Bas par da we Poss 13 82 13 28 DaqSingleAnalogOutputScan 13 84 13 29 DaqSingleDigitalinput ia aa aa cee eee 13 86 13 30 DaqSingleDigitalinputScan aa aa aa 13 88 13 31 DaqSingleDigitalOutput di ka j Seas 13 90 13 32 DaqSingleDigitalOutputScan ia aaa aaa 13 92 13 33 DaqStopRequest see si ndaq ks e ses Woh ens KNN 13 94 13 34 DaqTriggerRequest qv d Ae RUE e da ka ua eo ae
44. and should be executed before the request is armed The format of the command is shown below unsigned short DaqNotifyEvent unsigned short request_handle void far pascal event_procedure unsigned short unsigned short unsigned short unsigned long event_mask request_handle event_procedure event_mask This unsigned short integer variable is used to define which request is to use the event procedure defined by event_procedure This is the value returned to the application by the configuration procedures DaqAnaloginput DagAnalogOutput DaqDigitalInput or DaqDigitalOutput This pointer defines the starting address of the procedure to be executed when an event occurs event_procedure is defined in the following section This unsigned long integer value is used to specify which events the application wishes to be notified of event_mask is defined as a bit mask setting a specific bit to logic 1 enables notification of the corresponding event The bit definitions of event mask are given below DAQDRIVE constant Value Description NO_EVENTS 0x00000000 Disable all event notification TRIGGER_EVENT 0x00000001 Enable notification of trigger events COMPLETE_EVENT 0x00000002 Enable notification of complete events BUFFER_EMPTY_EVENT 0x00000004 Enable notification of buffer empty events BUFFER FULL EVENT 0x00000008 Enable notification of buffer full events SCAN_EVENT 0x
45. appear as follows byte byte byte byte packed array 14 2E 6 F7 un packed array 14 0 2E 0 6 0 F7 0 integer integer integer integer void DaqBytesToWords unsigned short far byte_array unsigned short far word_array unsigned long array length byte_array This is a pointer to an unsigned short integer array containing the packed values to be converted byte_array must be at least array_length 2 short integers array_length bytes in length and may specify the same array as word_array word_array This is a pointer to an unsigned short integer array where the un packed values will be stored word_array must be at least array_length short integers in length and may specify the same array as byte_array array_length This is an unsigned long integer value defining the number of data points to be converted byte_array must be at least array length 2 short integers array_length bytes in length while word_array must be at least array_length short integers in length DAQDRIVE User s Manual 13 18 include daqdrive bi include userdata h JEKKAKKKAKKKKKKKKKKKKKKKAKAKKKKKKKKKKKKK e hh I ARR ARI IA AAA k k k k k d Input 100 points each from 4 digital input channels E JEKKAKKKAKKKKKKKKKKKKKKAKAKKKKKKKKKKKKAKAKKKKKKKKKKKAKAKKKKKKKKKKKKKKKKKKKKJ unsigned short main unsigned short logical_device unsigned short request_handle unsigned shor
46. case 1 printf supports auto calibration n break case 2 printf supports auto zero n break case 3 printf supports auto calibration and auto zero n break printf has a max scan length of d channels n ADC_info max_scan_length printf supports d gain settings n ADC_info gain_array_length printf and has d expansion boards attached ADC_info num_exp_boards printf for a total of d analog inputs n ADC_info total_inputs prince ep Bt printf The A D returns values in the range ld ADC_info min_digital printf to ld n ADC_info max_digitla printf which corresponds to an input range of S ADC info min analog printf to f volts n ADC info max analog BIH TCA gt printf A single input may be sampled up to f Hz ADC_info max_sample_rate printf and multiple inputs up to Hz n ADC_info max_scan_rate printf The minimum sampling rate is f Hz n ADC info min sample rate 13 39 13 11 DaqGetADGainInfo DaqGetADGainInfo returns an array of the gain settings supported by the A D converter specified by ADC_device on the adapter specified by logical_device The length of the array is determined by the gain_array_length variable returned by the DaqGetADCfgInfo command unsigned short DaqGetADGainInfo unsigned short logical device unsigned short ADC_device float far gain_array logical_device This unsigned short in
47. command have been replaced by integer values which contain the segment and offset address of the string The application program can obtain these addresses using the VARSEG and SADD functions as shown in the following example NAKKAKAKAKA KA KKK KKK KA KA KA KA KA KKK KA KA KA KA KA KKK KA KA KA KKK AK KKK KA KA KA KA KKK KK KK KA KKK Step 1 Open the device NAKKAKAKAKA KA KKK KKK KA KA KA KA KA KKK KA KA KA KA KA KKK KA KA KA KA KKK KKK AKA KA KA KKK KA KA KA KKK LogicalDeviceS 0 DeviceTypeS DA8P 12B CHRS 0 ConfigFileS da8p 12b dat CHRS 0 Status DaqOpenDevice amp HF006 LogicalDevices VARSEG DeviceType SADD DeviceTypes VARSEG ConfigFile SADD Configriles 2 14 2 4 5 5 Storing a variable s address in a data structure Another short coming of Quick Basic is its inability to easily operate on a variable s address Because of this limitation all of the variables declared as far pointers in the DAQDRIVE data structures have been divided into two integer values a segment address and an offset address An example of this is the channel array variable in the ADCRequest structure unsigned short far channel_array_ptr which becomes ChannelArrayPtrOffset AS Integer ChannelArrayPtrSegment AS Integer For an array named Channel the application fills in the array s address using the VARSEG and VARPTR procedures as follows DIM Channel 10 AS Integer ADCRequest ChannelArrayPtrO
48. data channel 0 gain 2 Prepare Buffer Structure my_data data_buffer amp current_sample set pointer to data storage zy my_data buffer_length 1 number of points in buffer XI my_data next_structure NULL indicate no more buffers XL my_data buffer_status BUFFER_EMPTY indicate buffer empty ready x Prepare the A D request structure KE user request channel array ptr amp channel array of channels S user_request gain_array_ptr amp gain array of gains XI user_request array_length 1 number of channels user request ADC_buffer Em data pointer to data XI user request trigger source INTERNAL TRIGGER internal trigger ag user_request trigger_mode CONTINUOUS_TRIGGER input all points XI user request 10 mode BACKGROUND_IRQ background mode S user_request clock_source INTERNAL CLOCK use on board clock user_request sample_rate 1 1 Hz input rate KI user request number of scans 20 20 scans user_request scan_event_level 0 no scan events nann nannan malihanan t ian ten ORT TONO T TAN oe nA nn A Lk nn ian Ak user_request timeout_interval 0 disable time out kj user request request status 0 initialize status Set request_handle 0 new request SZ status DaqgAnalogInput logical device amp user_request amp request_handle if status 0 printf A D request error S
49. data structure data buffer data array data structure buffer length 16 data_structure buffer_cycles 1 data_structure next_structure NULL Jenni Prepare the digital output request structure KRAKKJ Request digital output ERREF request_handle 0 status DaqDigitalOutput logical_device amp user_request amp request_handle if status 0 printf Digital output request error Status code d n status DaqCloseDevice logical_device exit status 13 103 This page intentionally left blank DAQDRIVE User s Manual 13 104 14 Error Messages 00 10 11 12 13 14 15 30 No Errors The procedure completed without error Error opening configuration file The DaqOpenDevice procedure could not open the configuration file specified by config_file Verify the drive path and file name are correct File is not a valid DAQDRIVE configuration file The file specified as the hardware configuration file is not a valid DAQDRIVE configuration file Select a different configuration file Configuration file invalid for specified adapter type The adapter specified by the device_type variable does not match the type of hardware defined by the configuration file Select a different configuration file Error reading configuration file An error occurred while reading the adapter configuration file If there are no problems with the disk drive generate a ne
50. defined on odd address One or more data buffers allocated for the DMA mode operation are aligned on an odd address When using 16 bit DMA transfers all data buffers must reside on even addresses word aligned Internal DMA error This is an internal DAQDRIVE error If this error is received contact Omega s technical support department If possible have the hardware device type and software version numbers available when calling Invalid trigger source The trigger source specified is not one of DAQDRIVE s trigger source selections Trigger source not supported The trigger source specified is not supported by the adapter for the requested operation Consult the hardware specific appendices for supported trigger sources Invalid trigger slope The trigger slope specified is not one of DAQDRIVE s trigger slope selections Trigger slope not supported The trigger slope specified is not supported by the adapter for the requested operation Consult the hardware specific appendices for supported trigger slopes 14 7
51. defines a floating point variable vyhere software version firmvvare version the version of DAQDRIVE will be stored This pointer defines a floating point variable vyhere the version of the hardware specific software driver will be stored This pointer defines a floating point variable where the version of the adapter s firmware will be stored Adapters which have no firmware will set this value to 0 DAQDRIVE User s Manual 13 100 include daqdrive bi include daqopenc h include userdata h include daql200 h unsigned short main unsigned short logical device unsigned short status float DAQDRIVE _version float software_version float firmware_version char far device type DAQ 1201 char far config_file c daq 1201 daq 1201 dat k Open the DAQ 1201 logical_device 0 status DaqOpenDevice DAQ1200 amp logical_device device type config_file if status 0 printf Error opening configuration file Status code d n status exit status T Get version numbers KER ERY status DaqVersionNumber device_number amp DAQDRIVE version ssoftvare version sfirmuvare version if status 0 printf Error reading version numbers Status code d n status Display version information EE printf DAQDRIVE version 5 2f n DAQDRIVE _version printf DAQ 1201 driver version 5 2f n software_version printf DAQ 1201
52. double sample rate unsigned short reserved4 4 unsigned long number_of_scans unsigned long scan event level unsigned short reserved5 8 unsigned short timeout_interval unsigned long request status Ya IMPORTANT 1 Ifthe application program modifies the contents of the request structure after executing DaqDigitalinput the updated structure must be re verified by DaqDigitalInput before the request is armed 2 Once the request is armed using DaqgArmRequest the only field the application can modify is request_status All other fields in the request structure must remain constant until the operation is completed or otherwise terminated 3 If the request structure is dynamically allocated by the application it MUST NOT be de allocated until the request has been released by the DaqReleaseRequest procedure In addition applications using the Windows DLL version of DAQDRIVE should use DaqAllocateMemory if dynamically allocated request structures are required 7 2 7 2 1 Reserved Fields The fields reserved through reserved5 are provided for expansion of the digital input request structure in future releases of DAQDRIVE To maintain maximum compatibility the application program should initialize all reserved fields to 0 7 2 2 Channel Selections The digital input request structure begins with a list of one or more digital input channels to be operated on by this request The application p
53. eS 13 96 13 35 DaqWserBredk ag side 9 tad d niad da Fe de 13 98 13 36 DaqVersionNumber agrar e isha aes Ye t Vase t th 13 100 13 37 DaqWordsToBytes sy geni dow Barit dh whe de e 8 ee 13 102 14 Error Messages nde k ar KA de R RA 14 1 ISA PPONGIC S da de s e ore eae wae ae ees 15 1 DAQDRIVE User s Manual vii List of Figures Figure 1 DAQDRIVE interface between an application program and one hardware device i aa ia aaa 1 2 Figure 2 DAQDRIVE interface between an application program and multiple devices of the same family 1 3 Figure 3 DAQDRIVE interface between an application program and multiple devices of different families 1 3 Figure 4 buffer_status definition for input operations A D and digital input EE 9 3 Figure 5 buffer_status definition for output operations D A and digital output aag RZ R d eae e e EE E Te 9 4 Figure 6 Summary of DAQDRIVE trigger sources and parameters Ze e wer EE kri se ole aod ais 10 1 Figure 7 request status bit definitions aa aaa 11 3 Figure 8 event ype definition dar vi Bars pg da nyr he ba 11 6 Figure 9 event mask bit definitions aa aaa ruusun 11 7 Figure 10 Analog input request structure aaa aaa 13 5 Figure 11 Analog input request structure definition 13 6 Figure 12 Analog output request structure 13 11 Figure 13 Analog output request structure definition 13 12 Figure 14 Digital input request
54. error event Figure 8 event type definition DAQDRIVE User s Manual 11 6 The application may enable or disable the notification of specific events using the bits of the event_mask variable as defined in figure 9 To enable notification of an event the application need only set the corresponding bit in the event_mask to 1 To disable the notification the event_mask bit is cleared to 0 Because event_mask is a bit mask multiple events may be enabled by ORing specific event notification bits IMPORTANT event_mask only controls the notification of events The request_status field in the request structure is updated regardless of the event_mask settings DAQDRIVE constant Value Description NO_EVENTS 0x00000000 Disable all event notification TRIGGER EVENT 0x00000001 Enable notification of trigger events COMPLETE EVENT 0x00000002 Enable notification of complete events BUFFER_EMPTY_EVENT 0x00000004 Enable notification of buffer empty events BUFFER_FULL_EVENT 0x00000008 Enable notification of buffer full events SCAN_EVENT 0x00000010 Enable notification of scan events USER BREAK EVENT 0x20000000 Enable notification of user break events TIMEOUT_EVENT 0x40000000 Enable notification of time out events RUNTIME ERROR EVENT 0x80000000 Enable notification of run time error events Figure 9 event_mask bit definitions 11 7 include daqdri
55. ever clear any of the event bits to 0 Therefore the application should initialize request_status during the configuration process and may modify its contents at any time DAQDRIVE Constant Value Description NO_EVENTS 0x00000000 This constant does not represent an event status It is provided to the application for convenience TRIGGER_EVENT 0x00000001 When set to 1 this bit indicates the specified trigger has been received COMPLETE_EVENT 0x00000002 When set to 1 this bit indicates the request has completed successfully BUFFER_EMPTY_EVENT 0x00000004 When set to 1 this bit indicates at least one of the specified output data buffers has been emptied BUFFER_FULL_EVENT 0x00000008 When set to 1 this bit indicates at least one of the specified input data buffers has been filled SCAN_EVENT 0x00000010 When set to 1 this bit indicates the number of scans specified by scan_event_level have been completed at least once USER BREAK EVENT 0x20000000 When set to 1 this bit indicates the request has terminated due to a user break TIMEOUT EVENT 0x40000000 When set to 1 this bit indicates the request has terminated because the specified time out interval was exceeded RUNTIME_ERROR_EVENT 0x80000000 When set to 1 this bit indicates the request has terminated because of an error during processing The application can determine the source of the error using the DaqGetRuntimeError procedure
56. far device type DA8P 12B char far config_file da8p 12b dat Step 1 Initialize Hardware logical_device 0 status DaqOpenDevice DA8P 12 amp logical_device device_type config_file if status 0 printf Error opening device Status code d n status exit status Step 2 Get D A channel and output value ERE _clearscreen _GCLEARSCREEN printf n nEnter a channel number between 0 and 7 or 99 to quit scanf d amp channel if channel 99 printf n nEnter the output value between 2048 and 2047 mi scanf Sd amp output_value Step 3 Output data Prepare Buffer Structure my_data data_buffer koutput value point to output data Xy my_data buffer_length 1 number of points ay my_data buffer_cycles 1 cycle buffer once a my_data next_structure NULL no more buffers my_data buffer_status BUFFER_FULL buffer full ready XI Prepare the D A request structure SEET user_request channel_array_ptr amp channel array of channels X EE E ard K 7 dette Satine EA 4 12 13 user request DAC buffer amp my_data pointer to data wea user request trigger source TTL_TRIGGER select TTL trigger user_request trigger_slope RISING_EDGE rising edge trigger user request 10 mode BACKGROUND_IRQ background mode aed user_request number_of_scans 1 scan chan
57. firmware version 5 2f n firmware_version 13 101 13 37 DaqWordsToBytes DaqWordsToBytes performs the reverse of the DaqBytesToWords function converting an unsigned short integer array of 16 bit un packed values into an unsigned short integer array of 8 bit packed values These functions are provided especially for languages that do not support 8 bit variable types DaqWordsToBytes reads the un packed unsigned short integer values in array word_array converts these values to their packed 8 bit values and stores the results in array byte_array For an array of four values the packed and un packed arrays appear as follows integer integer integer integer un packed array 14 0 2E 0 6 0 F7 0 packed array 14 2E 6 F7 byte byte byte byte void DaqWordsToBytes unsigned short far word array unsigned short far byte_array unsigned long array length Word array byte_array array_length This is a pointer to an unsigned short integer array where the un packed values will be stored word_array must be at least array_length short integers in length and may specify the same array as byte_array This is a pointer to an unsigned short integer array containing the packed values to be converted byte_array must be at least array_length 2 short integers array_length bytes in length and may specify the same array as word_array
58. integer array is reserved for the future expansion of DAQDRIVE For maximum compatibility the application should initialize all reserved variables to 0 Figure15 continued Digital input request structure definition 13 25 timeout_interval This unsigned short integer value defines a time out interval in seconds for foreground mode processes The operation will abort if the digital input can not be read every timeout_interval seconds Setting timeout_interval 0 disables the time out function and causes the routine to wait indefinitely request_status This unsigned long integer value provides the application with the current status of the request DAQDRIVE does not rely on the information contained in this field nor does it ever clear any of the event bits to 0 Therefore the application should initialize request_status during the configuration process and may modify its contents at any time DAQDRIVE Constant Value Description NO_EVENTS 0x00000000 This constant does not represent an event status It is provided to the application for convenience TRIGGER_EVENT 0x00000001 When set to 1 this bit indicates the specified trigger has been received COMPLETE_EVENT 0x00000002 When set to 1 this bit indicates the request has completed successfully BUFFER_EMPTY_EVENT 0x00000004 When set to 1 this bit indicates at least one of the specified output data buffers has been emptied BUFFER_FULL_EVENT
59. integer value is used to define the target hardware device This is the value returned to the application by the DaqOpenDevice command ADC device This unsigned short integer value is used to select one of the A D converters on the target hardware device exp_device This unsigned short integer value is used to select one of the expansion boards connected to the A D converter on the target hardware device gain_array This pointer defines the first element of an array of floating point values where the available expansion board gain settings will be stored The application must allocate the array used to store these gain settings The length of the array is determined by the gain_array_length variable returned by the DaqGetExpCfgInfo command DAQDRIVE User s Manual 13 56 include daqdrive bi include userdata h include daql200 h unsigned short main unsigned short logical device unsigned short ADC device unsigned short exp device unsigned short status unsigned short i struct exp_configuration exp_info float far gain_array char far device type DAQ 1201 char far config_file c daq 1201 daq 1201 dat Open the DAQ 1201 see DaqOpenDevice KERR k Get the expansion board configuration Zen ADC_device 0 exp_device 1 status DaqGetExpCfgInfo logical_device ADC_device exp device sexp info Create an array to hold the gain settings KERR J gain_array
60. is used to monitor control the current state of the data buffer buffer_status is defined on the following pages for input operations see figure 4 and for output operations see figure 5 This void huge pointer specifies the address of the actual input output data buffer data_buffer is declared as a void to allow it to point to data of any type It is the application program s responsibility to ensure the data pointed to by data_buffer is correct for the request type and the target hardware as listed in the tables below Request type Resolution Configuration data type A Dor D A 1 to 8 bits unipolar unsigned char bipolar signed char 9 to 16 bits unipolar unsigned short bipolar signed short 17 to 32 bits unipolar unsigned long bipolar signed long Request type Channel size in bits data type digital input or 1 to 8 bits unsigned char digital output 9 to 16 bits unsigned short 17 to 32 bits unsigned long DAQDRIVE User s Manual buffer length buffer cycles next structure This unsigned long integer value defines the length of data buffer in units of number of points Each data buffer must be large enough to hold at least 1 point for every channel in the channel list Therefore buffer length must be greater than 0 This unsigned long integer value is used during output operations D A digital output only to define the number of times the data in this stru
61. memory is allocated from the global far heap and should be de allocated using the DaqFreeMemory procedure before the application terminates The application programmer may wish to use this procedure instead of the mechanisms provided within the application language because it eliminates language and operating systems dependencies Special note to Window s DLL users In the DLL version of DAQDRIVE DaqAllocateMemory performs a GlobalLock and a GlobalPageLock on the allocated memory This allows the memory to be used within DAQDRIVE s interrupt service routines unsigned short DaqAllocateMemory unsigned long memory size unsigned short far memory handle void far far memory pointer memory_size This unsigned long integer value is used to specify the amount of memory required by the application memory_handle This unsigned short integer pointer defines the address of a variable where the handle associated with this allocation will be stored The application must preserve this handle for later use by the DaqFreeMemory procedure memory pointer This void pointer defines the address of a pointer variable where the starting address of the newly allocated memory block will be stored The memory is allocated in a manner that makes memory_pointer compatible with all data types including huge DAQDRIVE User s Manual 13 2 include daqdrive bi include userdata h JEKKAKKKAKKKKKKKKKKKKK e hh KKKKKKKKKK
62. my_DAC_data 2 buffer_cycles 75 my_DAC_data 2 next_structure NULL The next step is to allocate and configure a DAC_request structure The DAC_request structure is beyond the scope of this chapter and will not be discussed here except for the DAC_buffer and number_of_scans fields which directly relate to the data structure configuration For this example DAC buffer is set to point to our first DAQDRIVE buffer structure and the number_of_scans is defined as follows number_of_samples samples_per_scan 50 cycles 360 samples cycle sine 45 cycles 2 samples cycle square 75 cycles 30 samples cycle triangle 20 340 samples 1 sample scan 20 340 scans number_of_scans DAQDRIVE User s Manual 9 19 struct DAC request my_DAC_request my_DAC_request DAC_buffer my_DAC_request number of scans my DAC data 20340 The final step is to set the BUFFER_EMPTY status in the buffer_status fields Once BUFFER_EMPTY is set and the request is armed the application must not modify the DAQDRIVE _buffer structures or the associated input data buffers until BUFFER_FULL is set or until the operation is terminated my_DAC_data 0 buffer_status BUFFER_EMPTY my_DAC_data 1 buffer_status BUFFER_EMPTY my_DAC_data 2 buffer_status BUFFER_EMPTY Variations on example 5 To execute only the sinewave portion of the buffers simply change number_of_scans to 50 360 my_DAC_reques
63. of the CPU time In contrast background mode operations generally provide lower data transfer rates while allowing the CPU to perform other tasks 8 2 5 1 Foreground CPU mode This mode uses the CPU to output the data to the hardware device From the moment the request is triggered DAQDRIVE uses all of the CPU time and will not return control to the application program until the request is completed or otherwise terminated DAQDRIVE User s Manual 8 3 8 2 5 2 Background IRQ mode This mode uses interrupts generated by the hardware device to gain control of the CPU to output the data to the hardware device DAQDRIVE does not require all of the CPU time in this mode and returns control of the CPU to the application after the request is triggered 8 2 5 3 Foreground DMA mode This mode uses the DMA controller to output the data to the hardware device while using the CPU to monitor and control the DMA operation From the moment the request is triggered DAQDRIVE uses all of the CPU time and will not return control to the application program until the request is completed or otherwise terminated 8 2 5 4 Background DMA mode This mode uses the DMA controller to output the data to the hardware device while using interrupts generated by the hardware device to gain control of the CPU to monitor and control the DMA operation DAQDRIVE does not require all of the CPU time in this mode and returns control of the CPU to the application afte
64. operations Figure 4 buffer_status definition for input operations A D and digital input DAQDRIVE User s Manual 9 3 buffer_status OUTPUT OPERATIONS Bit Value DAQDRIVE constant Description 0 0x0001 BUFFER_FULL BUFFER_FULL indicates the data buffer associated with this structure is full The application must set BUFFER_FULL to 1 to inform DAQDRIVE that the data buffer is ready for output After the application sets BUFFER_FULL and arms the request it MUST NOT modify the contents of the DAQDRIVE _buffer structure or the associated data buffer until DAQDRIVE sets BUFFER_EMPTY to 1 or until the operation is halted this includes modifying BUFFER_FULL DAQDRIVE clears BUFFER_FULL to 0 when the first data value is removed from the buffer and will report a buffer under run error if a data buffer is encountered that does not have BUFFER_FULL bit set DAQDRIVE will never set BUFFER_FULL during output operations 1 0x0002 BUFFER_EMPTY BUFFER_EMPTY indicates the data buffer associated with this structure is empty DAQDRIVE sets BUFFER_EMPTY to 1 after the last value is removed from the data buffer Once BUFFER_EMPTY is set DAQDRIVE will not operate on this buffer again unless BUFFER_FULL is re set to 1 by the application program DAQDRIVE will never clear BUFFER_EMPTY during output operations The application program may use BUFFER_EMPTY to determine when a data buffer may be safely accessed After the
65. output request structure and provide examples to illustrate how this structure is configured for some common applications 61 DaqAnalogOutput DaqAnalogOutput is DAQDRIVE s D A converter interface Any analog output operation is possible with the proper configuration of the request structure The format of the command is shown below unsigned short DaqAnalogOutput unsigned short logical device struct DAC_request far user_request unsigned short far request handle DaqAnalogOutput performs the configuration portion of an analog output request For a new configuration the application program sets request_handle to 0 before calling DaqAnalogOutput DaqAnalogOutput then analyzes the data structure specified by user_request to determine if all of the parameters are valid and if the requested operation can be performed by the device specified by logical_device If the requested operation is valid DagAnalogOutput assigns request_handle a unique non zero value This request handle is used to identify this request in all future operations If the application program modifies the contents of user_request after executing DaqAnalogOutput the structure must be verified again To request re verification of a previously approved request the application executes DaqAnalogOutput with request_handle set to the value returned by DaqAnalogOutput when the request was first approved All parameters except the channel list may be modified after
66. procedure 3 18 unsigned short MySingleDigitalInputScan unsigned short logical device unsigned short far channel_array unsigned short array_length void far input array struct digio_request my_request struct DAQDRIVE buffer my data unsigned short request handle unsigned short status Construct the request structure REKER my_request channel_array_ptr channel_array my_request array_length array_length my_request ADC_buffer amp my_data my request trigger source INTERNAL TRIGGER my request 10 mode FOREGROUND CPU my request number of scans 1 my_request scan_event_level 0 my_request timeout_interval 0 my_request request_status NO_EVENTS Construct the data buffer structure Rok ke d my_data data_buffer void huge input_array my_data buffer_length array_length my_data next_buffer NULL my_data buffer_status BUFFER_EMPTY Execute the request ERE KT request_handle 0 status DaqDigitalInput logical device my request amp request_handle if status 0 return status Jenni If no errors arm the request KAKKKJ status DagArmRequest request handle if status 0 DaqReleaseRequest request_handle return status Jenni If no errors software trigger the request KKK status DaqTriggerRequest request handle if status 0 DaqStopRequest request_handle DaqReleaseRequest request_hand
67. request_handle unsigned long event_mask unsigned short window handle When an event occurs DAQDRIVE uses the Windows PostMessage procedure to send an event message to the window specified by window_handle The message number uMsg is the sum of the event value specified in figure 8 and the Windows message constant WM USER The two message specific arguments LPARAM and VVPARAM are used to specify the request s request handle and an event error_code respectively The error code is set to 0 for all events except the run time error event where it is used to specify the type of error encountered as defined in chapter 14 The application may enable or disable the notification of certain events using the bits of the event_mask variable as defined in figure 9 To enable notification of an event the application need only set the corresponding bit in the event_mask to 1 To disable the notification the event_mask bit is cleared to 0 Because event_mask is a bit mask multiple events may be enabled by ORing specific event notification bits IMPORTANT event_mask only controls the notification of events The request_status field in the request structure is updated regardless of the event_mask settings 11 9 This page intentionally left blank DAQDRIVE User s Manual 11 10 12 Common Application Examples This chapter is dedicated to providing working example programs for some common data acquisition applications
68. request_handle is provided to the event procedure a single event procedure may service events from multiple requests void far pascal event_procedure unsigned short request_handle unsigned short event_type unsigned short error_code The following restrictions apply to the event procedure 1 only one event procedure may be installed per request 2 the event procedure can not call any DAQDRIVE procedures 3 Because the event procedure may be called from within an interrupt service routine ISR the event procedure should avoid using BIOS DOS or Windows system calls 11 5 DAQDRIVE constant Value Description EVENT_TYPE_TRIGGER 0 This call to the notification procedure is the result of a trigger event EVENT_TYPE_COMPLETE 1 This call to the notification procedure is the result of a complete event EVENT_TYPE_BUFFER_EMPTY 2 This call to the notification procedure is the result of a buffer empty event EVENT_TYPE_BUFFER_FULL 3 This call to the notification procedure is the result of a buffer full event EVENT TYPE SCAN 4 This call to the notification procedure is the result of a scan event EVENT TYPE USER BREAK 29 This call to the notification procedure is the result of a user break event EVENT TYPE TIMEOUT 30 This call to the notification procedure is the result of a time out event EVENT TYPE RUNTIME ERROR 31 This call to the notification procedure is the result of a run time
69. s manual and the appendices in the DAQDRIVE User s Manual 5 5 back of this document for details about how auto zero operates on the device in use 5 2 11 Time out The timeout_interval field is used primarily during foreground mode operations to instruct DAQDRIVE when to abandon the processing of a request When DAQDRIVE has control of the CPU and is waiting for an event to occur i e waiting for a trigger or waiting for the A D to complete a conversion DAQDRIVE will wait timeout_interval seconds and if the event has not occurred the request will be aborted 5 2 12 Request Status The request_status field provides a mechanism for the application to monitor the state of a request The request status is an integral part of DAQDRIVE s event mechanisms and is discussed in detail in chapter 11 5 6 5 3 5 3 1 Analog Input Examples Example 1 Single Channel Input Purpose Input 1000 samples from a single analog input channel at a 10KHz sampling rate unsign struct struct RRR KK my_req my_req my_req my_req my_req my_req my_req my_req my_req my_req my_req my_req my_req KKK KK my_dat my_dat my_dat my_dat unsigned short channel_list float gain list ed short ADC request DAQDRIVE buffer Construct the request structure uest channel_array_ptr uest gain_arraytptr uest array_length uest ADC buffer uest trigger source uest 10 mode uest clock source uest sample rat
70. sample from digital I O channel 3 KA unsigned short main unsigned short logical_device unsigned short status unsigned char input_value char far device type DAQP 16 char far config_file daqp 16 dat Step 1 Initialize Hardware logical_device 0 status DaqOpenDevice DAQP glogical device device type config file if status 0 printf Error opening device Status code d n status exit status Step 2 Input one value from channel 3 KERJ status DaqSingleDigitalInput logical_device 3 amp input_value if status 0 printf n nDigital input error Status code d n n status else printf Channel 3 Sd n n int input_value Step 3 Close Hardware Device status DagCloseDevice logical_device if status 0 printf Error closing device Status code d n status return status DaqSingleDigitalinput is a very basic interface without any allowance for multiple channels multiple input values trigger sources etc Itactsasa DAQDRIVE macro defining the necessary data structures executing the digital input configuration procedure DaqDigitalInput arming the requested configuration DaqArmRequest and triggering the operation DaqTriggerRequest For users interested in learning more about DAQDRIVE s digital input interface the following example program creates the equivalent of the DaqSingleDigitalin
71. structure aa aa aaa 13 23 Figure 15 Digital input request structure definition 13 24 Figure 16 Digital output request structure 13 29 Figure 17 Digital output request structure definition 13 30 Figure 18 A D converter configuration structure definition 13 37 Figure 19 D A converter configuration structure definition 13 43 Figure 20 Device configuration structure definition 13 48 Figure 21 Digital I O configuration structure definition 13 50 Figure 22 Analog input expansion board configuration struc DU ece ION ey iru Sand en kati at ie R d oe She Ree 13 53 Figure 23 Counter timer configuration structure definition 13 60 Figure 24 input_array data types as a function of analog input channel type visit ose eae eae eee ess 13 81 Figure 25 output_array data types as a function of analog o tputchannel type cyan ay pace N RAR re tiss ee 13 85 viii 1 Introduction DAQDRIVE is Omega s universal data acquisition interface for the DAQ series of ISA bus and PCMCIA data acquisition adapters DAQDRIVE goes beyond the drivers normally distributed with data acquisition adapters by isolating the application programmer from the hardware DAQDRIVE provides support for application programs written in the following languages vv Microsoft C C W Borland C C W Visual Basic for DOS W Quick Basic version 4 5 W Turbo Pascal for DOS version 7 0 and newer
72. the DAQDRIVE import library DAQDRIVE LIB installed in the DAQDRIVE WINDLL directory by the DAQDRIVE installation program This library is model independent and should work with most C compilers for Windows Three additional files are installed into the DAQDRIVE WINDLL C directory for the programmer s convenience These files contain the prototypes of the DAQDRIVE procedures the DAQDRIVE data structure definitions and the DAQDRIVE constants mentioned throughout this document These files must be included in all application programs DAQDRIVE H procedure prototypes DAQOPENW H DaqOpenDevice definition for Windows USERDATA H data structures and pre defined constants 2 5 1 1 Creating byte aligned data structures Because DAQDRIVE supports multiple languages the DAQDRIVE data structures are byte aligned packed The application program must also set structure packing to byte aligned for proper operation IMPORTANT For proper operation all application programs must be compiled using byte aligned data structures To select byte aligned structures within the Microsoft Visual C C environment first select Options Project Compiler then set the structure member alignment field to 1 byte For byte aligned structures from the Visual C C command line use the Zp1 option 2 22 2 5 2 Borland C C To generate application programs using the DAQDRIVE DLL with Borland C C the application must be lin
73. the DaqDigitalOutput procedure If the application modifies a previously configured request the application must call DaqDigitalOutput using the previously assigned request_handle All parameters except the channel list may be modified using a reconfiguration request To modify the channel list the present request must be released DaqReleaseRequest and a new configuration requested DAQDRIVE User s Manual 13 28 oe digio_request unsigned short far channel_array ptr unsigned short reserved1 4 unsigned short array_length struct DAQDRIVE buffer far digio_buffer unsigned short reserved2 4 unsigned short trigger source unsigned short trigger mode unsigned short trigger_slope unsigned short trigger_channel double trigger_voltage unsigned long trigger_value unsigned short reserved3 4 unsigned short TO mode unsigned short clock source double clock rate double sample rate unsigned short reserved4 4 unsigned long number_of_scans unsigned long scan_event_level unsigned short reserved5 8 unsigned short timeout_interval unsigned long request status le Figure 16 Digital output request structure IMPORTANT 1 Once the request is armed using DagArmRequest the only field the application can modify is request_status All other fields in the request structure must remain constant until the operation is completed or otherwise terminated 2 If th
74. the configuration of the expansion board specified by exp_device which is connected to the A D converter specified by ADC_device on the adapter specified by logical_device unsigned short DaqGetExpCfgInfo unsigned short logical_device unsigned short ADC_device unsigned short exp_device struct exp_configuration far exp_info logical_device This unsigned short integer value is used to define the target hardware device This is the value returned to the application by the DaqOpenDevice command ADC device This unsigned short integer value is used to select one of the A D converters on the target hardware device ep device This unsigned short integer value is used to select one of the expansion boards connected to the A D converter on the target hardware device exp_info This structure pointer defines the address of an expansion board configuration structure where the configuration of the specified expansion board will be stored struct exp_configuration unsigned short signal_type unsigned short input mode unsigned short num_mux_channels float max sample rate float max scan rate unsigned short gain array length Ir DAQDRIVE User s Manual 13 52 signal_type This unsigned short integer value specifies the expansion board input signal type Value Description Ox0001 When set to 1 this bit indicates the expansion board input is bipolar Ox0002 When set to 1 this bi
75. the hardware device to perform one or more calibration cycles on the D A converter s specified by this request The results of auto calibration vary with different hardware devices Consult the hardware user s manual and the appendices in the back of this document for details about how auto calibration operates on the device in use 6 2 10 2 Auto zero Enabling auto zero instructs the hardware device to perform one or more zero offset adjustment cycles on the D A converter s specified by this request The results of auto zeroing vary with different hardware devices Consult the hardware user s manual and the appendices in the DAQDRIVE User s Manual 6 5 back of this document for details about how auto zero operates on the device in use 6 2 11 Time out The timeout_interval field is used primarily during foreground mode operations to instruct DAQDRIVE when to abandon the processing of a request When DAQDRIVE has control of the CPU and is waiting for an event to occur i e waiting for a trigger or waiting for the D A to become ready DAQDRIVE will wait timeout_interval seconds and if the event has not occurred the request will be aborted 6 2 12 Request Status The request_status field provides a mechanism for the application to monitor the state of a request The request status is an integral part of DAQDRIVE s event mechanisms and is discussed in detail in chapter 11 6 6 6 3 6 3 1 Analog Output Examples Exam
76. time and will not return control to the application program until the request is completed or otherwise terminated DAQDRIVE User s Manual 7 3 7 2 5 2 Background IRQ mode This mode uses interrupts generated by the hardware device to gain control of the CPU to input the data to the hardware device DAQDRIVE does not require all of the CPU time in this mode and returns control of the CPU to the application after the request is triggered 7 2 5 3 Foreground DMA mode This mode uses the DMA controller to input the data from the hardware device while using the CPU to monitor and control the DMA operation From the moment the request is triggered DAQDRIVE uses all of the CPU time and will not return control to the application program until the request is completed or otherwise terminated 7 2 5 4 Background DMA mode This mode uses the DMA controller to input the data from the hardware device while using interrupts generated by the hardware device to gain control of the CPU to monitor and control the DMA operation DAQDRIVE does not require all of the CPU time in this mode and returns control of the CPU to the application after the request is triggered 7 2 6 Clock Sources The clock_source field is used to define the source of the timing signal for requests acquiring multiple samples 7 2 6 1 Internal Clock When the clock source field is set for an internal clock the timing for the request is provided by the adapter s on board ti
77. unsigned short main unsigned short logical_device unsigned short request_handle unsigned short status short data_array 500 struct ADC_request user_request struct DAQDRIVE buffer data structure k Open the device see DaqOpenDevice X T x Prepare data structure for analog output KERRE Jenni Prepare the A D request structure KKK Request A D input KERER request_handle 0 status DaqAnalogInput logical_device amp user_request amp request_handle if status 0 printf A D request error Status code d n status DaqCloseDevice logical_device exit status x Arm the request KEKA status DagArmRequest request handle if status 0 printf Arm request error Status code d n status DaqReleaseRequest request_handle DaqCloseDevice logical_device exit status 13 17 13 5 DaqBytesToWords DaqBytesToVVords reverses the function of DaqVVordsToBytes converting an unsigned short integer array of 8 bit packed values into an unsigned short integer array of 16 bit un packed values These function are provided especially for languages that do not support 8 bit variable types DaqBytesToVVords reads the packed 8 bit values in array byte_array converts these values to their un packed 16 bit unsigned short integer format and stores the results in array word_array For an array of four values the packed and un packed arrays
78. value of 1 indicates no DMA channel is defined ADC_devices This unsigned short integer value specifies the number of A D converters on the device DAC_devices This unsigned short integer value specifies the number of D A converters on the device digio_devices This unsigned short integer value specifies the number of digital I O channels on the device timer_devices This unsigned short integer value specifies the number of counter timer channels on the device Figure 20 Device configuration structure definition DAQDRIVE User s Manual 13 48 include daqdrive bi include userdata h include dagp h unsigned short main unsigned short logical_device unsigned short status struct device_configuration dev_info char far device type DAQP 208 char far config_file c daqp 208 daqp 208 dat Open the DAQP 208 see DaqOpenDevice R k Get the DAQP 208 configuration PEEK 4 status DaqGetDeviceCfginfo logical device amp dev_info if status 0 printf Error getting device configuration Status code sd n status exit status k Display the DAQP 208 configuration RARER printf The DAQP 208 is located at address 4XH n dev_info base_address printf with interrupt level d n dev_info IRQ printf and DMA channels Sd and d n n dev_info DMA1 dev_info DMA2 printf The DAQP 208 contains d A D converter s n
79. void far input value logical device This unsigned short integer value is used to define the target hardware device This is the value returned to the application by the DaqOpenDevice command channel_number This unsigned short integer value is used to specify which digital input channel on logical_device is to be read input_value This void pointer specifies the address where the value read from the digital input channel is to be stored input_value is declared as a void to allow it to point to data of any type It is the application program s responsibility to ensure the data pointed to by input_value is the correct type for the target hardware as listed in the table below Channel size in bits data type 1 to 8 bits unsigned char 9 to 16 bits unsigned short 17 to 32 bits unsigned long DAQDRIVE User s Manual 13 86 include daqdrive h include daqopenc h include userdata h include dagp h unsigned short main unsigned short logical_device unsigned short status unsigned short digio_channel short input_value char far device type DAQP 16 char far config_file c daqp 16 daqgp 16 dat festke Open th DAQP 16 device_number 0 status DaqOpenDevice DAQP amp logical_device device type config file if status 0 printf Error opening configuration file Status code d n status exit status Input on
80. will be stored ae ADC_configuration unsigned short resolution unsigned short signal_type unsigned short input mode unsigned short data coding long min digital long max digital long zero offset float min analog float max analog float min sample rate float max sample rate float max scan rate unsigned short num exp boards unsigned short total channels unsigned short max scan length unsigned short gain array length unsigned short calibration modes Ir DAQDRIVE User s Manual 13 36 resolution This unsigned short integer value specifies the resolution of the A D converter in bits signal_type This unsigned short integer value specifies the A D input signal type Value Description 0x0001 When set to 1 this bit indicates the A D input is bipolar Ox0002 When set to 1 this bit indicates the A D input is unipolar input_mode This unsigned short integer value specifies the A D input mode Value Description Ox0001 When set to 1 this bit indicates the A D input is differential Ox0002 When set to 1 this bit indicates the A D input is single ended data_coding This unsigned short integer value specifies the A D data coding format Value Description 0 Indicates data is in two s complement format 1 Indicates data is in binary format min_digital This long integer value defines the minimum digital value returned by the
81. 0 amp logical_device device type if status 0 exit status Step 2 Input data channel 0 gain 1 Prepare Buffer Structure Prepare the A D request structure ZE printf Error opening device Status code d n status config file my data data buffer input data set pointer to data array my_data buffer_length 1000 number of points in buffer my_data next_structure NULL indicate no more buffers my_data buffer_status BUFFER_EMPTY indicate buffer empty ready user_request channel_array_ptr amp channel array of channels user_request gain_array_ptr amp gain array of gains user_request array_length 1 number of channels user_request ADC_buffer amp my_data pointer to data user_request trigger_source INTERNAL_TRIGGER internal trigger user_request trigger_mode CONTINUOUS_TRIGGER input all points user request 10 mode BACKGROUND_IRQ background mode user_request clock_source INTERNAL_CLOCK use on board clock user_request sample_rate 100 100 Hz input rate user_request number_of_scans 1000 1000 scans user_request scan_event_level 0 no scan events user_request calibration NO_CALIBRATION no calibration user_request timeout_interval 0 disable time out ti XL S ti XL 12 3 request_handle 0 new request i status
82. 0 next_structure amp my_data 1l point to next buffer my_data 0 buffer_status BUFFER_FULL indicate buffer full ready my_data 1 data_buffer ramp set pointer to output data my_data 1 buffer_length 120 number of points in buffer When defined global or static structures are initialized to all 0 KEK S S ST ah Ay St s 12 17 DaqCloseDevice logical_device exit status Step 4 Arm the Request status DagArmRequest request_handle if status 0 printf Arm request error Status code d n status DaqReleaseRequest request_handle DaqCloseDevice logical_device exit status Step 5 Trigger the Request status DaqTriggerRequest request_handle if status 0 printf Trigger request error Status code d n status DaqReleaseRequest request_handle DaqCloseDevice logical_device exit status Step 6 Wait for completion or error AJ event mask COMPLETE EVENT RUNTIME ERROR EVENT vhile user request request status event mask 0 wait here for event if user_request request_status amp COMPLETE EVENT 0 printf n n D A Output Request complete n else printf Run time error Operation aborted n DaqReleaseRequest request_handle DaqCloseDevice logical device exit status my datalll next structure smy datal217 point to next bu
83. 0 samples using only 40K of memory The first step is to allocate two buffers with 10 000 points each unsigned short input_data0 10000 unsigned short input_datal1 10000 The next step is to allocate and configure two DAQDRIVE _buffer structures The data_buffer fields are set to point to the arrays defined above and the buffer_length fields are set accordingly The first structure has its next_structure field set to point to the second structure The second structure has its next_structure field set to point to the first structure forming a circular buffer struct DAQDRIVE buffer my_ADC_data 2 my_ADC_data 0 data_buffer my_ADC_data 0 buffer_length my_ADC_data 0 next_structure input_data0 10000 my_ADC_data 1 my_ADC_data 1 data_buffer my_ADC_data 1 buffer_length my_ADC_data 1 next_structure input_datal 10000 my_ADC_data 0 The next step is to allocate and configure an ADC_request structure The ADC_request structure is beyond the scope of this chapter and will not be discussed here except for the ADC_buffer and number_of_scans fields which directly relate to the data structure configuration For this example ADC_buffer is set to point to our first DAQDRIVE _buffer structure and the number_of_scans is set to 100 000 scans 5 channel scan struct ADC request my_ADC_request my ADC request ADC buffer my_ADC_request number of scans my ADC data 100000 The key to acquiring 500 000 sample
84. 000 cycles of a square wave to D A channel 0 Output sine ramp and square waves to D A channel 0 BERS include lt stdlib h gt include lt stdio h gt include lt math h gt include userdata h include daqdrive bi tinclude daqopenc h include da8p 12 h struct DAQDRIVE buffer my_data 3 struct DAC_request user_request unsigned short main unsigned short logical_device unsigned short request_handle unsigned short channel unsigned short status unsigned short i short sinewave 60 short ramp 120 short square 2 unsigned long event mask char far device type DA8P 12B char far config file da8p 12b dat Step 1 Initialize Hardware logical_device 0 status DaqOpenDevice DA8P 12 amp logical_device device type config_file if status 0 printf Error opening device Status code d n status exit status Step 2 Define the output channel and data values EER channel 0 for i 0 i lt 60 i sinewave i short 2047 sin 2 3 1416 i 60 for i 0 i lt 120 i ramp i short 2047 0 i 119 square 0 2048 squarelll 2047 Step 3 Output data Prepare Buffer Structures my_data 0 data_buffer sinewave set pointer to output data my_data 0 buffer_length 60 number of points in buffer my_data 0 buffer_cycles 600 600 cycles through buffer my_data
85. 00000010 Enable notification of scan events USER BREAK EVENT 0x20000000 Enable notification of user break events TIMEOUT_EVENT 0x40000000 Enable notification of time out events RUNTIME_ERROR_EVENT 0x80000000 Enable notification of run time error events DAQDRIVE User s Manual 13 62 13 20 1 The user defined event procedure The application programmer must create the procedure to be executed for event notification This procedure must be a far pascal compatible procedure of type void does not return a value and it must accept three unsigned short integer parameters request_handle event_type and error_code A sample C declaration of this procedure is shown below void far pascal event_procedure unsigned short request_handle unsigned short event_type unsigned short error_code When executed DAQDRIVE provides the event procedure with the request s request_handle the type of event which has occurred see the table below and an event error code This error code is set to 0 for all events except the run time error event where it is used to specify the type of error encountered as defined in chapter 14 Since the request handle is provided to the event procedure a single event procedure may be used to service events from multiple requests DAQDRIVE constant Value Description EVENT_TYPE_TRIGGER 0 This call to the notification procedure is the result of a trig
86. 0x00000008 When set to 1 this bit indicates at least one of the specified input data buffers has been filled SCAN_EVENT 0x00000010 When set to 1 this bit indicates the number of scans specified by scan_event_level have been completed at least once USER BREAK EVENT 0x20000000 When set to 1 this bit indicates the request has terminated due to a user break TIMEOUT EVENT 0x40000000 When set to 1 this bit indicates the request has terminated because the specified time out interval was exceeded RUNTIME_ERROR_EVENT 0x80000000 When set to 1 this bit indicates the request has terminated because of an error during processing The application can determine the source of the error using the DaqGetRuntimeError procedure Figure 15 continued Digital input request structure definition DAQDRIVE User s Manual 13 26 include daqdrive bi include userdata h JEKKAKKKAKKKKKKKKKKKKKKKAKAKKKKKKKKKKKKK e hh I ARR ARI IA AAA k k k k k d Input 100 points each from 4 digital input channels JEKKAKKKAKKKKKKKKKKKKKKAKAKKKKKKKKKKKKAKAKKKKKKKKKKKAKAKKKKKKKKKKKKKKKKKKKKJ unsigned short main unsigned short logical_device unsigned short request_handle unsigned short channel_num 4 0 1 6 3 unsigned short status unsigned char data array 400 struct digio_request user_request struct DAQDRIVE buffer data structure k k Open the device see DaqOpenDevice T k Prepare data struct
87. 1 Introduction eme EE NEE NEEN 1 1 2 Before Beginning 32255 cei ccssateors Er 2 1 2 1 Software Installation pu Daja oe at AE PLS Gy eae SA 2 1 2 2 Creating DAQDRIVE Configuration Files 2 2 2 3 Creating DOS Applications Using The C Libraries 2 3 2 3 1 Microsoft Visual CC 2 3 23 2 Borland C C HR na dy Dan dridh e ee las a apes Soe n ko Dood kara We re na 2 5 2 4 Creating DOS Applications Using The TSR Drivers 2 7 2 4 1 Loading The TSRs Into Memory i aak incue 2 7 2 4 2 Removing The TSRs From Memory 2 8 2 4 3 Microsoft C C oo ccc ec eee eee eee 2 9 2 4 4 Borland C C and Turbo C in 2 10 E E E PO 2 12 2 4 6 Visual Basic for DOS Au So eee Die are e Deag P t aes 2 16 247 Turbo Pascal ett vd taht ats Ak ak teak 2 19 2 5 Creating Windows Applications 0134 ese ha gee urea 2 21 2 5 1 Microsoft Visual C C 0 eee eee 2 22 2 5 2 Borland C CPE act Barit Duda di dk a n De he bad 2 23 2 5 3 Visual Basic for Windows isa sedi 2 546044 048 2 25 2 5 4 Turbo Pascal for Windows Borland Delphi 3 26 3 Quick Start Procedures aa 3 1 ST Analog Input sK D ti Dm R AGS SSR NTR 3 2 3 1 1 DagsingleAnaloginput A ie Ki Se ee beanies Sade heads 3 2 3 1 2 DagSingleAnaloginputScan e 7 cco cee s 3 5 3 2 Analog OUL PUG EE 3 8 3 2 1 DagSingleAnalogOutput aa aa 3 8 3 2 2 DaqSingleAnalogOutputScan ia aaa aaa 3 11 3 3 Digital INDUE EE 3 1
88. 4 This unsigned short integer array is reserved for the future expansion of DAQDRIVE For maximum compatibility the application should initialize all reserved variables to 0 trigger_source This unsigned short integer value specifies the trigger source for this request Trigger selections are discussed in chapter 10 trigger_mode DAQDRIVE Constant Value Description INTERNAL_TRIGGER 0 internal software trigger TTL_TRIGGER 1 TTL trigger ANALOG_TRIGGER 2 analog trigger DIGITAL_TRIGGER 3 digital value trigger This unsigned short integer value defines the trigger mode Trigger selections are discussed in chapter 10 DAQDRIVE Constant Value Description CONTINUOUS_TRIGGER 0 only one trigger is required to start the output operation ONE_SHOT_TRIGGER 1 a trigger is required for each input scan trigger_slope This unsigned short integer value defines the slope for TTL and analog triggers trigger_slope is ignored for all other trigger sources Trigger selections are discussed in chapter 10 DAQDRIVE Constant Value Description RISING_EDGE 0 for TTL and analog triggers only specifies a low to high transition is required FALLING_EDGE 1 for TTL and analog triggers only specifies a high to low transition is required trigger_channel This unsigned short value specifies the channel to be used as the input for the analog or digital trigger sources trigger_channel is undefined for all o
89. 4 3 3 1 DaqSingleDigitallnput ada geet See da ory 3 14 3 3 2 DaqSingleDigitalinputScan aa aa aa 3 17 E E 3 20 3 4 1 DaqSingleDigitalOutput aaa aa 3 20 3 4 2 DaqSingleDigitalOutputScan aa aaa aaa 3 23 4 Performing An Acquisition 4 1 5 A D Converter Requests aaa eee eee 5 1 9 1 eelere vargut ei a eee ee ere ena ee 5 1 5 2 The Analog Input Request Structure 5 2 5 2 1 Reserved Fields ug seg s da che Ae ek v r os 5 3 5 2 2 Channel Selections Gain Settings 0 5 3 5 2 R E H Buffers EE 5 3 5 24 Trigger Selections oe gosi rarer was ti SE ula hig 5 3 5 25 Data Transfer Mod s saj dra vate ko dha Dara nda N b 3 DAQDRIVE User s Manual iii 5 2 6 Clock Sources en on EEE A E aE a 5 4 5 2 7 Sampling Rate gS oe tne ad tie put ea a DR derek Sears es 5 5 5 2 8 Number OF Seans xs ae Soe ts aoa ee we ae ae Ge te SM 5 5 529 Scan Events egene eana a eh ioe eae Dian Bohan SNE 5 5 5 2 10 Calibration Selections 5 5 5 2 11 Time out e EERE eee eens 5 6 5 212 E Status Gantien e edd aeia ae ia i o EE 5 6 5 3 Analog Input Examples gras runn Bales ys 5 7 5 3 1 Example 1 Single Channel Input 5 7 5 3 2 Example 2 Multiple Channel Input 6 8 6 D A Converter Requests 6 1 6 1 DaqAnalogOutput EEN 6 1 6 2 The Analog Output Request Structure 0 6 2 6 2 Reserved Field Lut nja vet nata ase ee ee ERS 6 3 6 2 2 Channel Select onde dii e boi oan Ok ite Dr ee Ga
90. A D max_digital This long integer value defines the maximum digital value returned by the A D zero_offset This long integer value defines the offset or zero value reading returned by the A D min_analog This floating point value defines the minimum analog input to the A D max_analog This floating point value defines the maximum analog input to the A D min_sample_rate This floating point value specifies the minimum sampling rate supported by the A D max_sample_rate This floating point value specifies the maximum single channel sampling rate supported by the A D max_scan_rate This floating point value specifies the maximum multi channel scanning sampling rate supported by the A D Figure 18 A D converter configuration structure definition 13 37 num_exp_boards This unsigned short integer value defines the number of analog input expansion boards connected to the A D total_channels This unsigned short integer value specifies the total number of analog inputs available on the A D max_scan_length This unsigned short integer value defines the maximum scan length of the A D This is the maximum length of the channel list for A D requests gain_array_length This unsigned short integer value specifies the number of available A D gain settings The application must allocate an array of length gain_array_length before executing DaqGetA DGaininfo cali
91. AQDRIVE R removes the DAQDRIVE TSR 2 8 2 4 3 Microsoft C C To generate application programs using the DAQDRIVE TSR with Microsoft C C the application must be linked with the DAQDRIVE library DAQTSRC LIB installed in the DAQDRIVE TSR C directory by the DAQDRIVE installation program This library is model independent and should work with most C compilers for DOS Three additional files are installed in the DAQDRIVE TSR C directory for the programmer s convenience These files contain the prototypes of all the DAQDRIVE procedures the DAQDRIVE data structure definitions and the DAQDRIVE constants mentioned throughout this document These files must be included in all application programs DAQDRIVE H procedure prototypes DAQOPENT H DaqOpenDevice prototype USERDATA H data structures and pre defined constants 2 4 3 1 Creating byte aligned data structures Because DAQDRIVE supports multiple languages the DAQDRIVE data structures are byte aligned packed The application program must also set structure packing to byte aligned for proper operation IMPORTANT For proper operation all application programs must be compiled using byte aligned data structures To define byte aligned structures with Microsoft C use the Zp1 command line option Within the Microsoft Visual C C environment select Options Project Compiler and set the structure member alignment field to 1 byte DAQDRIVE User s M
92. AnalogInput logical_device ADC_channel gain setting sinput value if status 0 printf Error reading from A D Status code d n status fe ee Close the DAQ 1201 status DagCloseDevice logical_device if status 0 printf Error closing device Status code d n status return status l 13 79 13 26 DaqSingleAnalogInputScan The DagSingleAnalogInputScan procedure provides a simplified interface for inputting a single point from multiple A D converter channels The format of the command is shown below The analog input channels specified by channel_array on the adapter defined by logical_device are configured for the gain settings specified by gain_array The analog inputs are then converted to digital values which are returned to the array specified by input_array There is a one to one correspondence between the number of analog input channels the number of gain settings and the number of samples Therefore array_length specifies the length of channel_array gain_array and input_array This procedure executes the DAQDRIVE procedures DaqAnalogInput DagArmRequest DaqTriggerRequest and DaqReleaseRequest before returning to the calling application unsigned short DaqSingleAnalogInputScan unsigned short logical_device unsigned short far channel_array float far gain_array unsigned short array length void far input_array logical_device This unsigned short integer valu
93. BS C library support for DOS applications DAQDRIVE TSR TSR driver support for DOS applications DAQDRIVE WINDLL Support for Windows applications DAQDRIVE User s Manual 2 1 2 2 Creating DAQDRIVE Configuration Files Before an application program can operate on a hardware device the device must be initialized using the DaqOpenDevice procedure One of the parameters provided to this procedure is a data file which specifies the configuration of the target hardware Some of the information contained in the configuration file includes General Information v hardware type e g DAQP 16 DAQ 1201 DAQP 208 v I O address V interrupt level DMA channels Analog Input A D Information V number of channels V resolution gain settings V input modes bipolar unipolar single ended differential Analog Input Expansion Information V number of channels V input modes bipolar unipolar single ended differential V gain settings signal conditioning Analog Output D A Information V number of channels V resolution Digital I O Information V number of channels v channel size I O mode input output bi directional Counter Timer Information V number of channels V channel size number of bits V input frequency DAQDRIVE configuration files are created by the DAQDRIVE Configuration Utility program installed by the DAQDRIVE installation program for Windows Under no circumstances should the user attempt to c
94. CALIBRATION user request timeout interval 0 user_request request_status NO_EVENTS Indicate data buffer ready for output HEE HAF data_structure buffer_status BUFFER_FULL Request D A output RARER request_handle 0 status DaqAnalogOutput logical device user_request amp request_handle if status 0 printf D A request error Status code d n status DaqCloseDevice logical_device exit status 13 15 13 4 DaqArmRequest DagArmRequest is executed after the DaqAnalogInput DaqAnalogOutput DaqDigitalinput or DaqDigitalOutput functions to prepare the specified configuration for execution During the arming process any resources required for the request e g IRQS DMA channels timers are allocated for use by this request and all hardware is prepared for the impending trigger unsigned short DaqArmRequest unsigned short request handle request_handle This unsigned short integer variable is used to define which request is to be armed This is the value returned to the application by the configuration procedures DaqAnalogInput DaqAnalogOutput DaqDigitalInput or DaqDigitalOutput DAQDRIVE User s Manual 13 16 include daqdrive bi include userdata h JEKKKKKAKKKKKKKKKKKKKKKAKAKKKKKKKKKKKAKAKKKKKKKKKKKKKAKAKKKKKKKKKKKKKKKKKKKJ Input 500 points from an A D channel 7 JEKKKKKAKAKKKKKKKKKKKKKAKKKKKKKKKKKKAKAKAKKKKKKKKKKKKKAKAKKKKKKKKKKKKKKKKKKKJ
95. C_request user_request struct DAQDRIVE buffer data structure Open the DASP 12B see DaqOpenDevice RARER Jenni define D A output channel and calculate output data REE RET Prepare data structure for analog output KE k Prepare the D A request structure KERRE k Request D A output See DaqAnalogOutput XT k Arm the request See Daq rmkRequest ise x x Trigger the request AER ERT status DaqTriggerRequest request_handle if status 0 printf Trigger request error Status code Sd Yn status DaqStopRequest request_handle DaqReleaseRequest request_handle DaqCloseDevice logical_device exit status Wait for completion or error RARER event_mask COMPLETE_EVENT RUNTIME_ERROR_EVENT while user_request request_status amp event_mask 0 if user_request request_status amp COMPLETE EVENT 0 printf Request complete n else status GetRuntimeError request handle amp error printf Run time error d Waveform aborted n error x x Release the request FEE status DaqReleaseRequest request_handle if status 0 printf Could not release configuration Status code d n status k Close the DA8P 12B status DaqCloseDevice logical_device if status 0 printf Error closing device Status code d n status return status H 13 75 13 24 Dad Rese
96. DAC_data 1 buffer_status BUFFER_EMPTY BUFFER_EMPTY 9 18 9 3 5 Example 5 Creating Complex Output Patterns Combining the ideas of example 2 and example 4 the application of example 5 wants to output 50 cycles of a sinewave containing 360 samples 45 cycles of a square wave containing 2 samples and 75 cycles of a triangle wave containing 30 samples Assuming a 12 bit D A converter operating in bipolar mode the following arrays are defined short sine 360 short square 2 short triangle 30 The next step is to allocate and configure three DAQDRIVE _buffer structures The data_buffer fields are set to point to the arrays defined above and the buffer_length fields are set accordingly The first structure has its next_structure field set to point to the second structure The second structure has its next_structure field set to point to the third structure and the third structure has its next_structure field set to NULL since it is the last structure in the chain struct DAQDRIVE buffer my_DAC_data 3 my_DAC_data 0 data_buffer sine my _DAC_data 0 buffer_length 360 my_DAC_data 0 buffer_cycles 50 my_DAC_data 0 next_structure amp my_DAC_data 1 my_DAC_data 1 data_buffer square my_DAC_data 1 buffer_length 2 my_DAC_data 1 buffer_cycles 45 my_DAC_data 1 next_structure amp my_DAC_data 2 my_DAC_data 2 data_buffer triangle my DAC datal21 buffer length 30
97. DAQDRIVE buffer my_DAC_data 2 my DAC datal0 data buffer output data my DAC datal0 l buffer length 25000 my_DAC_data 0 buffer_cycles F my DAC datal0 l next structure amp my_DAC_data 1 my_DAC_data 1 data_buffer output_datal my DAC datalll buffer length 25000 my_DAC_data 1 buffer_cycles 1 my_DAC_data 1 next_structure amp my_DAC_data 0 The next step is to allocate and configure a DAC_request structure The DAC_request structure is beyond the scope of this chapter and will not be discussed here except for the DAC_buffer and number_of_scans fields which directly relate to the data structure configuration For this example DAC_buffer is set to point to our first DAQDRIVE _buffer structure and number_of_scans is set to 500 000 scans 1 channel scan struct DAC request my_DAC_request my_DAC_request DAC_buffer my_DAC_request number of scans my DAC data 500000 The key to processing 500 000 samples with only enough buffer space to hold 50 000 samples is in the use of the BUFFER_FULL and BUFFER_EMPTY bits Before arming the request the BUFFER_FULL bits in the buffer_status fields are set CA my_DAC_data 0 buffer_status my_DAC_data 1 buffer_status BUFFER_FUL BUFFER_FU CA DAQDRIVE User s Manual 9 21 The application may not modify the DAQDRIVE _buffer structures or the data buffers until the operation is halted or until DAQDRIVE sets the BU
98. E library DAQDRV BC LIB compact model DAQDRIVE library DAQDRV BL LIB large model DAQDRIVE library Three additional files are installed in the DAQDRIVE C_LIBS directory for the programmer s convenience These files contain the prototypes of all the DAQDRIVE procedures the DAQDRIVE data structure definitions and the DAQDRIVE constants mentioned throughout this document These files must be included in all application programs DAQDRIVE H procedure prototypes DAQOPENC H DaqOpenbDevice definition for C USERDATA H data structures and pre defined constants 2 3 2 1 The hardware dependent include file The C library version of the DaqOpenDevice procedure is implemented as a macro using the token pasting operator to create a unique open command for each hardware device Application programs must include the file DAQOPENC H and the hardware dependent include file defined in the target hardware s appendix of the DAQDRIVE User s Manual Supplement The DAQDRIVE installation program installs these files into the DAQDRIVE C_LIBS directory DAQDRIVE User s Manual 2 5 2 3 2 2 Creating byte aligned data structures Because DAQDRIVE supports multiple languages the DAQDRIVE data structures are byte aligned packed The application program must also set structure packing to byte aligned for proper operation IMPORTANT For proper operation all application programs must be compiled using byte aligned data structures
99. FFER_EMPTY bit If this is a background operation the application may sit in a loop waiting for BUFFER_EMPTY and re filling each buffer as it becomes available wait in dead loop until buffer 0 is empty while my DAC datalo0 buffer status amp BUFFER_EMPTY 0 buffer 0 is empty re fill buffer from input file clear BUFFER_EMPTY and re set BUFFER_FULL when complete my DAC datal0 buffer status BUFFER_FULL wait in dead loop until buffer 1 is empty while my DAC datalll buffer status amp BUFFER EMPTY 0 buffer 1 is empty re fill buffer from input file clear BUFFER_EMPTY and re set BUFFER_FULL when complete my DAC datalll buffer status BUFFER_FULL repeat until 500 000 samples are processed Another option for background mode operations is to monitor the BUFFER_EMPTY_EVENT bit in the DAC_request structure s request_status field The application may assume the BUFFER_EMPTY bit is set before the BUFFER_EMPTY_EVENT is generated and that the application may safely access the data buffer wait in dead loop for BUFFER_EMPTY_EVENT while my DAC request request status BUFFER_EMPTY_EVENT 0 a buffer is empty determine which buffer re fill the buffer clear BUFFER_EMPTY and re set BUFFER_FULL if my_DAC_data 0 buffer_status amp BUFFER EMPTY 0 re fill buffer 0 my DAC datal0 buffer status else vre fill buffer 1 BUFFER_FULL my
100. ION my_request timeout_interval 0 my_request request_status NO_EVENTS Construct the data buffer structure PR EST my_data data_buffer void huge output_array my_data buffer_length array_length my_data buffer_cycles 1 my_data next_buffer NULL my_data buffer_status BUFFER FULL Execute the request BER EK DAQDRIVE User s Manual 3 13 3 3 Digital Input DAQDRIVE provides two special purpose procedures for digital input DagSingleDigitallnput and DaqSingleDigitalinputScan The intent of this section is to provide an overview of these procedures For details on the implementation of the procedures consult the alphabetical listing of commands in chapter 13 3 3 1 DaqSingleDigitalInput One of the simplest cases of digital input is to input a single sample from a single digital I O channel under CPU control DAQDRIVE provides a simplified interface for this operation through the DaqSingleDigitalinput procedure The format of this command is shown below unsigned short DaqSingleDigitalInput unsigned short logical_device unsigned short channel_number void far input_value DaqSingleDigitalinput inputs a single sample from the digital I O specified by channel_number on the adapter specified by logical_device The sample is stored in the memory location specified by input_value The following example shows the usage of DaqSingleDigitalinput 3 14 Input a single
101. K KKKA KA KKK 1 Increase the size of the Visual Basic stack by 2K V KKK KKK KKK KKK KKK KKK KKK KA KA KA KKK KA KA KA KK KKK KKK KKK KA KKK KKK K KA KA KA KA KKK KKKA KA KKK CLEAR 2048 NAKKAKAKAKA KA KKK KKK AKA KA KA KA KKK KA KA KA KA KA KKK KA KA KA KA KKK KKK AKA KA KA KKK KKKA KA KKK Decrease the size of the heap so DAQDRIVE can allocate required memory NKAKAKAKAKAKAKAKK KKK KA KA KA KA KA KKK KA KA KA KA KA KKK KA KA KA KA KKK KKK AKA KA KA KKK KKKA KA KKK HeapSize SETMEM 10000 NAKKAKAKAKA KA KKK KA KA KA KA KA KA KKK KA KA KA KA KA KKK KA KA KA KA KKK KKK AKA KA KA KKK KKK AKA KKK Perform all DAQDRIVE functions NAKKAKAKAKAKAKK KKK KA KA KA KA KA KKK KA KA KA KA KA KKK KA KA KA KKK AK KKK KA KA KA KA KKK KKKA KA KKK DaqOpenDevice DaqCloseDevice V KKK KKK KK KK KKK KKK KKK KKK KKK KA KKK KA KA KA KA KA KKK KA KA KA KKK AK KKK KA KA KA KA KKK KK KK KA KKK Optionally restore heap NAKKAKAKAKA KA KKK KKK AKA KA KA KA KKK KA KA KA KA KA KKK KA KA KA KA KKK KKK AKA KA KA KKK KKK AKA KKK HeapSize SETMEM 410000 2 4 6 3 The DaqOpenDevice Command DAQDRIVE s DaqOpenDevice command requires two null terminated string variables DeviceType and ConfigFile Because Visual Basic does not support null terminated strings the user must create these strings by appending a null character CHRS 0 to the end of each string before passing it to DAQDRIVE For example A FILENAME DAT normal Visual Basic str
102. KKK KA KKKKKKKKKAKAKAKKKKKKKKKKKKKKKKKKJ Input 5000 points each from 2 analog input channels E JEKKKKKAKKKKKKKKKKKKKKAKAKKKKKKKKKKKK e hh k e A A e e A AE e e k hh IIIA k k k k k k k d unsigned short main unsigned short logical_device unsigned short request_handle unsigned short channel_num 2 float gain_settings 2 unsigned long memory_size unsigned short memory_handle void far memory_pointer unsigned short status n struct ADC_request user_request struct DAQDRIVE buffer data_structure Open the device see DaqOpenDevice REPRE L k Allocate memory for the input data LER ERS 5000 samples channel 2 channels 2 bytes sample KERKERS memory size 5000 2 sizeof short status DaqAllocateMemory memory_size amp memory_handle amp memory_pointer if status 0 printf Error allocating data buffer Status code d n status DaqCloseDevice logical_device exit status Prepare data structure for analog input AER ERY data_structure data_buffer memory_pointer data_structure buffer_length 10000 k x Prepare the A D request structure EA T Request A D input KAKKKJ request handle 0 status DaqAnalogInput logical device Kuser request srequest handle if status 0 printf A D request error Status code d n status DaqF reeMemory memory handle memory_pointer DaqCloseDevice logical device exit stat
103. LL The next step is to allocate and configure an ADC_request structure The ADC_request structure is beyond the scope of this chapter and will not be discussed here except for the ADC_buffer and number_of_scans fields which directly relate to the data structure configuration For this example ADC_buffer is set to point to our first DAQDRIVE _buffer structure and the number_of_scans is set to 25 000 scans 1 channel scan struct ADC request my_ADC_request my ADC request ADC buffer my ADC request number of scans my ADC data 25000 The final step is to set the BUFFER_EMPTY status in the buffer status fields Once BUFFER_EMPTY is set and the request is armed the application must not modify the DAQDRIVE _buffer structures or the associated input data buffers until BUFFER_FULL is set or until the operation is terminated my_ADC_data 0 buffer_status BUFFER_EMPTY my_ADC_data 1 buffer_status BUFFER EMPTY DAQDRIVE User s Manual 9 9 9 2 4 Example 4 Acquiring Large Amounts Of Data The purpose of example 4 is to illustrate one way to acquire large amounts of data using relatively small amounts of memory If for example an application wants to input 100 000 samples from each of 5 analog input channels using a 12 bit A D converter operating in unipolar mode the samples are each size unsigned short and 500 000 samples would require 1 Megabyte of memory This example will acquire the 500 00
104. LL is set or until the operation is terminated my_ADC_data buffer_status BUFFER EMPTY DAQDRIVE User s Manual 9 7 9 2 2 Example 2 Multi Channel Analog Input The purpose of this example is to input 500 samples each from three analog input channels To perform this operation the application must first allocate enough memory to hold 1500 3 500 samples Assuming a 16 bit A D converter operating in unipolar mode the samples are each size unsigned short Therefore the memory allocation may be done as simply as unsigned short input_data 1500 The next step is to allocate and configure a DAQDRIVE _buffer structure data_buffer is set to point to the array defined above Its length is 1500 points and there are no other structures so next_structure is set to NULL struct DAQDRIVE _buffer my_ADC_data my_ADC_data data_buffer input_data my_ADC_data buffer_length 1500 my_ADC_data next_structure NULL The next step is to allocate and configure an ADC_request structure The ADC_request structure is beyond the scope of this chapter and will not be discussed here except for the ADC_buffer and number_of_scans fields which directly relate to the data structure configuration For this example ADC_buffer is set to point to our DAQDRIVE _buffer structure and the number_of_scans is set to 500 scans 3 channels scan struct ADC request my_ADC_request my ADC request ADC buffer my ADC request number of scans
105. Q1200 amp logical_device device type config file if status 0 printf Error opening configuration file Status code d n status exit status Output one value to D A channel 0 See DAC channel 0 output_value 1024 status DaqSingleAnalogOutput logical_device DAC channel amp output_value if status 0 printf Error writing to D A Status code d n status k Close the DAQ 1201 status DagCloseDevice logical device if status 0 printf Error closing device Status code d n status return status 13 83 13 28 DaqSingleAnalogOutputScan The DaqSingleAnalogOutputScan procedure provides a simplified interface for outputting a single point to multiple D A converter The format of the command is shown below The values specified by output_array are output to the D A converters specified by channel_array on the adapter specified by logical_device A D A channel may appear in channel_array only once There is a one to one correspondence between the number of analog output channels and the number of output values Therefore array_length specifies the length of both channel_array and output_array This procedure executes the DAQDRIVE procedures DaqAnalogOutput DagArmRequest DaqTriggerRequest and DaqReleaseRequest before returning to the calling application unsigned short DaqSingleAnalogoutputScan unsigned short logical device unsigned shor
106. The DA8P 12B supports the following D A gain settings n for i 0 i lt DAC_info gain_array_length i printf gain d f n i gain_array i 13 47 13 14 DaqGetDeviceCfgInfo DaqGetDeviceCfgInfo returns the basic configuration of the adapter specified by logical_device unsigned short DaqGetDeviceCfgInfo unsigned short logical_device struct device_configuration far dev_info logical_device This unsigned short integer value is used to define the target hardware device This is the value returned to the application by the DaqOpenDevice command dev_info This structure pointer defines the address of a device configuration structure where the configuration of the specified logical device will be stored C struct device_configuration unsigned short base address short IRQ short DMA1 short DMA2 unsigned short ADC devices unsigned short DAC_devices unsigned short digio_devices unsigned short timer_devices Ir base address This unsigned short integer value specifies the base I O address of the device IRQ This unsigned short integer value specifies the IRQ level for the device A value of 1 indicates no IRQ level is defined DMA1 This unsigned short integer value specifies the primary DMA channel for the device A value of 1 indicates no DMA channel is defined DMA2 This unsigned short integer value specifies the secondary DMA channel for the device A
107. User s Manual 14 4 310 400 410 450 500 600 650 700 Memory release error An error occurred while DAQDRIVE was attempting to release memory previously allocated for internal use If this error occurs the system has become unstable Channel in use by another request One or more channels specified by this request are currently in use by other request s This request must wait until the other request s are complete and have made their channels available Timer in use by another request One or more timer channels required for the requested operation are currently in use by other request s This request must wait until the other request s are complete and have made their timer channels available Hardware dependent resource in use by another device A hardware specific resource required for the requested operation is currently in use by another request This request must wait until the other request is complete and relinquishes control of the resource Consult the target hardware s appendix in the DAQDRIVE User s Manual Supplement to determine the cause of this error Invalid procedure call for a request that is not configured The procedure cannot be executed because the request has not been configured Make sure the configuration procedure DaqAnalogInput DaqAnalogOutput DaqDigitalInput or DaqDigitalOutput executed successfully Invalid procedure call for a request that is not armed The procedure ca
108. _DAC_data 1 buffer_status BUFFER_FULL repeat until 500 000 samples are processed 9 22 DAQDRIVE User s Manual 9 23 Another option for background mode operations and the only option available for foreground mode operations is to use the event notification procedure DaqNotifyEvent The idea of event notification is that DAQDRIVE will execute a user supplied procedure each time an event occurs This mechanism can be used to re fill the data buffers on each occurrence of the BUFFER_EMPTY_EVENT The details of event notification are beyond the scope of this chapter but are discussed in chapter 11 The methods shown in example 5 will work only if the application can process the data and re set BUFFER_FULL before DAQDRIVE tries to access that buffer again If DAQDRIVE tries to access a buffer in which the BUFFER_FULL bit has not been set a buffer under run error will occur 9 24 This page intentionally left blank DAQDRIVE User s Manual 10 Trigger Selections Once a request has been configured and armed the trigger determines when the requested operation will begin A summary of available trigger sources and their required parameters is shown in figure 6 below Source Slope Channel Voltage Value internal TTL x analog x x x digital x x Figure 6 Summary of DAQDRIVE trigger sources and parameters 10 1 Trigger Sources When a request is configured the
109. _IRQ user_request clock_source INTERNAL_CLOCK user_request sample_rate 1000 user_request number_of_scans 500 user_request scan_event_level 0 user_request calibration NO_CALIBRATION user request timeout interval 0 user_request request_status NO_EVENTS k Indicate data buffer ready for input ERREK data_structure buffer_status BUFFER_EMPTY Request A D input KAKKKJ request handle 0 status DaqAnalogInput logical device Kuser request amp request_handle if status 0 printf A D request error Status code d n status DaqCloseDevice logical_device exit status 13 9 13 3 DaqAnalogOutput DaqAnalogOutput is DAQDRIVE s generic D A converter interface It does not configure any hardware but acts simply to confirm that all parameters are valid and that the type of operation requested is supported by the target hardware unsigned short DaqAnalogoutput unsigned short logical_device struct DAC_request far user_request unsigned short far request handle logical device This unsigned short integer value is used to define the target hardware device This is the value returned to the application by the DaqOpenDevice command user_request This structure pointer defines the address of a D A request structure containing the desired configuration information for this operation This structure is discussed in detail on the following pages request_
110. _TRIGGER my_request I0_mode FOREGROUND_CPU my_request number_of_scans 1 my_request scan_event_level 0 my_request calibration NO_CALIBRATION my_request timeout_interval 0 my_request request_status NO_EVENTS Construct the data buffer structure EK my data data buffer void huge input_array my_data buffer_length array_length my_data next_buffer NULL my_data buffer_status BUFFER_EMPTY Execute the request Ek request_handle 0 status DaqgAnalogInput logical device my_request amp request_handle KKKKKJ KKKKKJ DAQDRIVE User s Manual 3 2 Analog Output For analog output DAQDRIVE provides two special purpose procedures DaqSingleAnalogOutput and DagSingleAnalogOutputScan The intent of this section is to provide an overview of these procedures For details on the implementation of the procedures consult the alphabetical listing of commands in chapter 13 3 2 1 DaqSingleAnalogOutput One of the simplest cases of analog output is to output a single value to a single D A converter under CPU control DAQDRIVE provides a simplified interface for this function through the DaqSingleAnalogOutput procedure The format of this command is shown below unsigned short DaqSingleAnalogoutput unsigned short logical device unsigned short channel number void far output value DaqSingleAnalogOutput outputs the value specified by output value to the DJA conv
111. a to be written to the digital output channel output_value is declared as a void to allow it to point to data of any type It is the application program s responsibility to ensure the data pointed to by output_value is the correct type for the target hardware as listed in the table below Channel size in bits data type 1 to 8 bits unsigned char 9 to 16 bits unsigned short 17 to 32 bits unsigned long DAQDRIVE User s Manual 13 90 include daqdrive h include daqopenc h include userdata h include da8p 12 h unsigned short main unsigned short logical device unsigned short status unsigned short digio channel short output value char far device type DA8P 12B char far config file c da8p 12b da8p 12b dat Open the DASP 12B logical_device 0 status DaqOpenDevice DA8P 12 amp logical_device device type config_file if status 0 printf Error opening configuration file Status code d n status exit status Output one value to digital output channel 3 KRAKKJ digio channel 3 output_value 1 status DaqSingleDigitalOutput logical_device digio channel G amp output_value if status 0 printf Error writing to digital output Status code td Ann status jgskkk Close the DA8P 12B 7 status DagCloseDevice logical_device if status 0 printf Error closing device Status code d
112. above and the buffer_length fields are set accordingly The first structure has its next_structure field set to point to the second structure The second structure has its next_structure field set to NULL struct DAQDRIVE _buffer my_DAC_data 2 my_DAC_data 0 data_buffer output_data0 my DAC datal0 l buffer length 5000 my_DAC_data 0 buffer_cycles 1 my_DAC_data 0 next_structure amp my_DAC_data 1 my_DAC_data 1 data_buffer output_datal my DAC datalll buffer length 3000 my_DAC_data 1 buffer_cycles 1 my_DAC_data 1 next_structure NULL The next step is to allocate and configure a DAC_request structure The DAC_request structure is beyond the scope of this chapter and will not be discussed here except for the DAC_buffer and number_of_scans fields which directly relate to the data structure configuration For this example DAC butter is set to point to our first DAQDRIVE buffer structure and number_of_scans is set to 4 000 scans 2 channels scan struct DAC_request my_DAC_request my DAC request DAC_buffer my DA request number of scans my DAC data 4000 The final step is to set the BUFFER_EMPTY status in the buffer_status fields Once BUFFER_EMPTY is set and the request is armed the application must not modify the DAQDRIVE _buffer structures or the associated input data buffers until BUFFER_FULL is set or until the operation is terminated my_DAC_data 0 buffer_status my_
113. an event is reported before the buffer full event 11 1 11 1 5 Scan Event The scan event is generated each time the number of scans specified by the scan event level have been completed If a scan event occurs at the same time as the complete event the scan event is reported before the complete event If a scan event and a buffer full or buffer empty event occur simultaneously the scan event is reported before the buffer full or buffer empty event 11 1 6 User Break Event The user break event is generated when a request is aborted as a result of the user break procedure The user break procedure is discussed in section 13 35 A request will never report any events after the user break event 11 1 7 Time out Event The time out event is generated when a request is aborted because the specified time out interval was exceeded A request will never report any events after the time out event 11 1 8 Run time Error Event The run time error event is generated when an error occurs during the processing of the request The application can determine the source of the error using the DaqGetRuntimeError procedure A request will never report any events after the time out event 11 2 Monitoring Events Using The Request Status One method of monitoring DAQDRIVE events is through the request_status field in the request structure When an event occurs during the processing of a request DAQDRIVE sets the corresponding bit to 1 in the req
114. analog inputs with a rising edge TTL trigger in one shot mode then each low to high transition of the TTL trigger input will cause six samples to be input one sample from each of the six channels in the channel list 10 2 2 Continuous Trigger Mode When a request is configured for continuous trigger mode only one trigger occurrence is required to initiate the request the remainder of the operation is executed periodically at time intervals specified by the sample rate For example if a request is configured to output data to an analog output channel with a falling edge TTL trigger in continuous mode at a sample rate of 1KHz then a high to low transition of the TTL trigger will output the first sample with additional samples following at Ims intervals 1KHz If a request is configured to input data from ten digital inputs with a continuous mode internal trigger at a 50Hz sample rate then ten samples will be input when the DaqTriggerRequest procedure is executed and ten more samples will be input at each 20ms 50Hz interval thereafter 10 3 This page intentionally left blank DAQDRIVE User s Manual 10 4 11 DAQDRIVE Events DAQDRIVE uses events to keep the application program informed of the progress of a request The following sections provide descriptions of DAQDRIVE events and methods of monitoring these events from the application program 11 1 Event Descriptions 11 1 1 Trigger Event The trigger event is gener
115. anual 2 9 2 4 4 Borland C C and Turbo C To generate application programs using the DAQDRIVE TSR with Borland C C or Turbo C the application must be linked with the DAQDRIVE library DAQTSRC LIB installed in the DAQDRIVE TSR C directory by the DAQDRIVE installation program This library is model independent and should work with most C compilers for DOS Three additional files are installed in the DAQDRIVE TSR C directory for the programmer s convenience These files contain the prototypes of all the DAQDRIVE procedures the DAQDRIVE data structure definitions and the DAQDRIVE constants mentioned throughout this document These files must be included in all application programs DAQDRIVE H procedure prototypes DAQOPENT H DaqOpenDevice prototype USERDATA H data structures and pre defined constants 2 4 4 1 Creating byte aligned data structures Because DAQDRIVE supports multiple languages the DAQDRIVE data structures are byte aligned packed The application program must also set structure packing to byte aligned for proper operation IMPORTANT For proper operation all application programs must be compiled using byte aligned data structures To guarantee structures are byte aligned within the Borland C C environment select Options Compiler Code Generation then confirm the Word alignment box is not checked Within the Turbo C environment select Options Compiler Code Generation then set the Align
116. application program must specify a trigger source in the request structure Depending on which trigger is specified additional trigger related fields in the structure may also be required see figure 6 When these additional settings are not required any value provided in the field is ignored 10 1 1 Internal Trigger The simplest trigger source is an internal trigger also referred to as a software trigger To generate an internal trigger the application program must execute the DaqTriggerRequest procedure The internal trigger source does not require any additional configuration parameters and any values provided in these fields are ignored 10 1 2 TTL Trigger The TTL trigger is a specific TTL input to the hardware device that is designated by the adapter as a trigger input When the TTL trigger source is selected the trigger slope must also be defined as either rising edge requiring a low to high transition of the trigger signal or falling edge requiring a high to low transition of the trigger signal The trigger channel trigger voltage and trigger value settings are not required and any values provided in these fields is ignored 10 1 10 1 3 Analog Trigger The analog trigger source allows a request to be initiated by an analog input voltage level When the analog trigger is selected the application must specify the voltage required to generate the trigger and the analog input channel to be monitored for this trigger volta
117. application sets BUFFER_FULL and arms the request it MUST NOT modify the contents of the DAQDRIVE _buffer structure or the associated data buffer until DAQDRIVE sets BUFFER_EMPTY to 1 or until the operation is halted The application may clear BUFFER_EMPTY at any time Figure 5 buffer_status definition for output operations D A and digital output 9 1 Multiple Channel Operations When defining a data buffer for single channel operations the data buffer is simply an array of values and is stored in system memory in continuous increasing memory locations For example if an application requests 10 samples from a single analog input channel the application must declare an array to hold the ten values short array 10 This array appears in system memory as arraylol arraylll array 2 array 9 When DAQDRIVE is acquiring the data however it does not view this memory as an array but simply as a data buffer For this single channel example DAQDRIVE would place the following information in the data buffer samplel sample2 sample3 samplel0 which the application views as array 0 samplel array 1 sample2 array 2 sample3 array 9 samplel0 As mentioned above DAQDRIVE views the memory as a data buffer and not as an array If this same buffer was used to acquire 5 samples from each of two A D channels DAQDRIVE would place the following data in the buffer chanl chan2 chanl chan2 chan
118. ase the Request status DaqReleaseRequest request_handle if status 0 printf Could not release configuration Status code d n status exit status Step 7 Close Hardware Device KERJ status DaqCloseDevice logical device if status 0 printf Error closing device Status code d n status return status DAQDRIVE User s Manual 12 4 12 1 3 Example 3 This example inputs 200 samples each from five A D channels at 100Hz Tnput 200 samples each from A D channels 0 to 4 EREI include lt conio h gt include lt graph h gt include lt stdlib h gt include lt stdio h gt include userdata h include daqdrive h tinclude daqopenc h include dagp h When defined global or static structures are Ke automatically initialized to all 0 k struct DAQDRIVE buffer my_data struct ADC_request user_request unsigned short main unsigned short logical_device unsigned short request_handle unsigned short channel 5 0 Li 2 3 4 float gain 5 SI Lao 10 220 4 0 AE ks unsigned short status unsigned short i j k short input_data 200 5 unsigned long event_mask char far device type DAQP 208 char far config_file daqp 208 dat Step 1 Initialize Hardware logical_device 0 status DaqOpenDevice DAQP amp logical_device device type config file if status 0 printf Error ope
119. ated when a valid trigger is received If the request was configured for continuous trigger mode only one trigger event will occur when the operation is initiated If the request was configured for one shot trigger mode a trigger event is generated with each occurrence of the trigger 11 1 2 Complete Event The complete event is generated when a request has completed successfully If the complete event occurs at the same time as the buffer full event the buffer empty event and or the scan event the events are reported in the following sequence scan event buffer full or buffer empty event complete event A request will never report any events after the complete event 11 1 3 Buffer Empty Event The buffer empty event is generated during output operations each time one of the specified output data buffers has been completely emptied If a buffer empty event occurs at the same time as the complete event the buffer full event is reported before the complete event If a buffer empty event and a scan event occur simultaneously the scan event is reported before the buffer empty event 11 1 4 Buffer Full Event The buffer full event is generated during input operations each time one of the specified input data buffers has been completely filled If a buffer full event occurs at the same time as the complete event the buffer full event is reported before the complete event If a buffer full event and a scan event occur simultaneously the sc
120. ation may safely access the data buffer wait in dead loop until a buffer is full while my ADC request request status BUFFER_FULL_EVENT 0 a buffer is full determine which buffer process the data clear BUFFER FULL and re set BUFFER EMPTY 1f my ADC datal0 buffer status BUFFER FULL 0 process buffer 0 my ADC datal0 buffer status BUFFER EMPTY else process buffer 1 my_ADC_data 1 buffer_status BUFFER EMPTY repeat until 500 000 samples are processed 9 12 DAQDRIVE User s Manual 9 13 Another option for background mode operations and the only option available for foreground mode operations is to use the event notification procedure DaqNotifyEvent The idea of event notification is that DAQDRIVE will execute a user supplied procedure each time an event occurs This mechanism can be used to process a data buffer on each occurrence of the BUFFER FULL EVENT The details of event notification are beyond the scope of this chapter but are discussed in chapter 11 The methods shown in example 4 will work only if the application can process the data and re set BUFFER_EMPTY before DAQDRIVE tries to access that buffer again If DAQDRIVE tries to access a buffer in which the BUFFER_EMPTY bit has not been set a buffer over run error will occur 9 14 9 3 Output Operation Examples 9 3 1 Example 1 Single Channel Analog Output An example of a simple output
121. ator to create a unique open command for each hardware device Application programs must include the file DAQOPENC H and the hardware dependent include file defined in the target hardware s appendix of the DAQDRIVE User s Manual Supplement The DAQDRIVE installation program installs these files into the DAQDRIVE C_LIBS directory DAQDRIVE User s Manual 2 3 2 3 1 2 Creating byte aligned data structures Because DAQDRIVE supports multiple languages the DAQDRIVE data structures are byte aligned packed The application program must also set structure packing to byte aligned for proper operation IMPORTANT For proper operation all application programs must be compiled using byte aligned data structures To select byte aligned structures within the Visual C C environment first select Options Project Compiler then set the structure member alignment field to 1 byte For byte aligned structures from the Visual C C command line use the Zp1 option 2 4 2 3 2 Borland C C To generate application programs using Borland C C the applications must be linked to one of the following DAQDRIVE libraries AND one or more hardware dependent libraries These libraries MUST match the memory model selected for the application program The DAQDRIVE installation program installs the following files into the DAQDRIVE C_LIBS directory DAQDRV BS LIB small model DAQDRIVE library DAQDRV BM LIB medium model DAQDRIV
122. ay of channels number of channels pointer to data internal trigger output all points background mode use on board clock 10 patterns secon 10000 scans no scan events disable time out KI k E d Ef S 12 25 request_handle 0 new request status DaqDigitalOutput logical device amp user_request amp request_handle if status 0 printf Digital output request error Status code Sd n status DaqCloseDevice logical_device exit status Step 4 Arm the Request status DagArmRequest request_handle if status 0 printf Arm request error Status code d n status DaqReleaseRequest request_handle DaqCloseDevice logical device exit status Step 5 Trigger the Request status DaqTriggerRequest request handle if status 0 printf Trigger request error Status code d n status DaqReleaseRequest request_handle DaqCloseDevice logical_device exit status Step 6 Wait for completion or error SE event mask COMPLETE_EVENT RUNTIME ERROR EVENT while user_request request_status amp event_mask if user_request request_status amp COMPLETE EVENT 0 printf n n D A Output Request complete n else printf Run time error Operation aborted n DaqReleaseRequest request_handle DaqCloseDevice logical device exit status
123. bration_modes This unsigned short integer value specifies the supported calibration modes of the A D sub system Value Description Ox0001 When set to 1 this bit indicates the A D supports auto calibration Ox0002 When set to 1 this bit indicates the A D supports auto zero Figure 18 continued A D converter configuration structure definition DAQDRIVE User s Manual 13 38 include daqdrive bi include userdata h include daql200 h unsigned short main unsigned short logical device unsigned short ADC_devices unsigned short status struct ADC_configuration ADC_info char far device type DAQ 1201 char far config_file c daq 1201 daq 1201 dat Open the DAQ 1201 see DaqOpenDevice CERES k k Get the A D configuration ERR RES ADC_device 0 status DaqGetADCfgInfo logical_device ADC device SADC info if status 0 printf Error getting A D configuration Status code d n status exit status T Display the A D configuration RARER J printf A D number d ADC device printf has a resolution of d bits n ADC_info resolution if ADC_info signal_type 1 printf is configured for unipolar and else printf is configured for bipolar and if ADC_info input_mode 1 printf single ended operation n else printf differential operation n switch ADC_info calibration_modes
124. buffer associated with this structure is full DAQDRIVE sets BUFFER_FULL to 1 after the last value is transferred into the data buffer Once BUFFER_FULL is set DAQDRIVE will not operate on this buffer again unless BUFFER_EMPTY is re set to 1 by the application program DAQDRIVE will never clear BUFFER_FULL during input operations The application program may use BUFFER_FULL to determine when a data buffer may be safely accessed After the application sets BUFFER_EMPTY and arms the request it MUST NOT modify the contents of the DAQDRIVE _buffer structure or the associated data buffer until DAQDRIVE sets BUFFER_FULL to 1 or until the operation is halted The application may clear BUFFER_FULL at any time 0x0002 BUFFER_EMPTY BUFFER_EMPTY indicates the data buffer associated with this structure is empty The application must set BUFFER_EMPTY to 1 to inform DAQDRIVE that the data buffer is ready for input After the application sets BUFFER_EMPTY and arms the request it MUST NOT modify the contents of the DAQDRIVE _buffer structure or the associated data buffer until DAQDRIVE sets BUFFER_FULL to 1 or until the operation is halted this includes modifying BUFFER_EMPTY DAQDRIVE clears BUFFER_EMPTY to 0 when the first data value is transferred into the buffer and will report a buffer over run error if a data buffer is encountered that does not have the BUFFER_EMPTY bit set DAQDRIVE will never set BUFFER_EMPTY during input
125. calling Configuration file error This is an internal DAQDRIVE error If this error is received contact Omega s technical support department If possible have the hardware device type and software version numbers available when calling Configuration file error This is an internal DAQDRIVE error If this error is received contact Omega s technical support department If possible have the hardware device type and software version numbers available when calling Invalid logical device number An adapter could not be found with the specified logical device number Make sure the DaqOpenDevice procedure executed successfully and that the logical device number matches the value returned by the DaqOpenDevice procedure No logical devices defined There are no adapters currently opened Make sure the DaqOpenDevice procedure is executed without error before any other procedures are called Invalid request handle A request could not be found with the specified request handle Make sure the configuration procedure DaqAnalogInput DaqAnalogOutput DaqDigitalinput or DaqDigitalOutput executed successfully and that the request handle matches the value returned by the configuration procedure 14 3 200 201 205 250 251 255 300 No interrupt level defined for adapter The requested operation requires a hardware interrupt IRQ and no interrupt level was defined for the adapter in the hardware configuration fil
126. char far device_type DA8P 12B char far config_file c da8p 12b da8p 12b dat Open the DASP 12B logical_device 0 status DaqOpenDevice TSR_number amp logical_device device type config file if status 0 printf Error opening configuration file Status code d n status exit status Perform any DA8P 12B operations here RERE a Close the DA8P 12B KEREK status DagCloseDevice logical device if status 0 printf Error closing device Status code d n status return status 13 71 13 22 DaqPostMessageEvent DaqPostMessageEvent is available only in the DLL version of DAQDRIVE for use under Windows It installs a pre defined messaging procedure using DaqNotifyEvent to post event messages to the application s window and should be executed before the request is armed DaqNotifyEvent and DaqPostMessageEvent can not both be used on the same request unsigned short DaqPostMessageEvent unsigned short request_handle unsigned long event_mask unsigned short window handle request handle This unsigned short integer variable is used to define which request is to use the event procedure defined by event procedure Thisis the value returned to the application by the configuration procedures DaqAnaloginput DaqAnalogOutput DaqDigitalInput or DaqDigitalOutput event mask This unsigned long integer value is used to specify which events
127. cing the equivalent of a 25 000 point data buffer containing 250 cycles of the sinewave NOTE In this example setting buffer_cycles 250 effectively created a 25 000 point data buffer In the same way setting buffer_cycles 300 would have effectively created a 30 000 point data buffer Had a 30 000 point data buffer been used with number_of_scans set to 25 000 the result would have been the same except the BUFFER_EMPTY bit would not have been set since all 30 000 points were not output to the D A 9 16 9 3 3 Example 3 Multi Channel Analog Output The purpose of this example is to output 500 samples each to three analog output channels To perform this operation the application must first allocate enough system memory to hold 1500 3 500 samples Assuming a 12 bit D A converter operating in unipolar mode the samples are each size unsigned short Therefore the memory allocation may be done as simply as unsigned short output_data 1500 The next step is to allocate and configure a DAQDRIVE buffer structure data_buffer is set to point to the array defined above Its length is 1500 points the buffer will be processed only once buffer_cycles 1 and there are no other structures so next_structure is set to NULL struct DAQDRIVE _buffer my_DAC_data my_DAC_data data_buffer output_data my_DAC_data buffer_length 1500 my_DAC_data buffer_cycles 1 my_DAC_data next_structure NULL The next step
128. ck_source double clock_rate double sample_rate unsigned short reserved4 4 unsigned long number_of_scans unsigned long scan_event_level unsigned short reserved5 8 s s N unsigned short calibration unsigned short timeout_interval unsigned long request status T IMPORTANT 1 If the application program modifies the contents of the request structure after executing DaqAnalogInput the updated structure must be re verified by DaqAnalogInput before the request is armed 2 Once the request is armed using DaqgArmRequest the only field the application can modify is request_status All other fields in the request structure must remain constant until the operation is completed or otherwise terminated 3 If the request structure is dynamically allocated by the application it MUST NOT be de allocated until the request has been released by the DaqReleaseRequest procedure In addition applications using the Windows DLL version of DAQDRIVE should use DaqAllocateMemory if dynamically allocated request structures are required 52 1 Reserved Fields The fields reserved through reserved5 are provided for expansion of the analog input request structure in future releases of DAQDRIVE To maintain maximum compatibility the application program should initialize all reserved fields to 0 5 2 2 Channel Selections Gain Settings The analog input request structure begins with a list of on
129. clarations and constants throughout this document but has been removed from the Visual Basic for DOS version of DAQDRIVE 2 4 6 2 Adjusting the size of the Visual Basic s stack and heap DAQDRIVE uses the application program s stack for storing local variables and for passing variables between DAQDRIVE procedures By default Visual Basic for DOS only allocates 2K of memory for the application s stack which may be insufficient under come circumstances It is recommended that the user increase the size of the application s stack by at least 2K using the CLEAR command Note that the CLEAR command also clears all data memory and should therefore be used at the beginning of the application program In addition application programs written using Visual Basic for DOS allocate all available DOS memory for use as a local heap This causes DAQDRIVE to report an error 300 memory allocation error when the application attempts to open a device The application program must reduce the size of the heap using Visual Basic s SETMEM function before executing DaqOpenDevice As a guide the application should reduce the 2 16 heap by 10 000 bytes for each hardware device to be opened and once the DaqOpenDevice procedure has been executed the allocated heap space must not be returned to Visual Basic until the DaqCloseDevice procedure has been completed V KKK KKK KKK KKK KK KKK KA KA KA KA KA KKK KA KA KA KA KA KKK KA KA KA KKK AK KKK KA KA KA KA KK
130. ction determines how the requested operation will be initiated after being armed Six fields are required to define and configure the trigger for the request trigger_source trigger_mode trigger_slope trigger_channel trigger_voltage and trigger_value Because the trigger selection is an integral part of the operation and is common to all of DAQDRIVE s request structures trigger configurations are discussed separately in chapter 10 6 2 5 Data Transfer Modes The request structure field IO mode determines the mechanism that will be used to output the data to the hardware device In general the foreground modes provide the highest data transfer rates at the expense of requiring 100 of the CPU time In contrast background mode operations generally provide lower data transfer rates while allowing the CPU to perform other tasks 6 2 5 1 Foreground CPU mode This mode uses the CPU to output the data to the hardware device From the moment the request is triggered DAQDRIVE uses all of the CPU time and will not return control to the application program until the request is completed or otherwise terminated DAQDRIVE User s Manual 6 3 6 2 5 2 Background IRO mode This mode uses interrupts generated by the hardware device to gain control of the CPU to output the data to the hardware device DAQDRIVE does not require all of the CPU time in this mode and returns control of the CPU to the application after the request is triggered 6 2
131. cture for analog output EER ERY JEKKKKKAKKKKKKKKKKKKKKAKAKKKKKKKKKKKKAKAKKKKKKKKKKKAKAKKKKKKKKKKKKKKKKKKKKJ data is in data array data array is 20 points long SE output buffer 1 time next_structure NULL no more structures SZ JEKKAKKKAKKKKKKKKKKKKK e hh hh kk E EE e hh hh E EE E hh k k k k kk k kk k k k k k k d data structure data buffer data_array data_structure buffer_length 20 data_structure buffer_cycles 1 data_structure next_structure NULL k Prepare the D A request structure EA ER JEKKAKKKAKKKKKKKKKKKKKKKAKAKKKKKKKKKKKKKAKKKKKKKKKKKKKKAKAKKKKKKKKKKKKKKKKKKJ channel list is in channel num channel num is 1 channel long RE data is in data structure trigger source is internal XL trigger mode is continuous output using IRQs in background use internal clock output 1 point every 10ms 100Hz repeat all buffers once do not signal buffer scan events ay do not implement time out JEKKAKKKAKKKKKKKKKKKKKKAKAKKKKKKKKKKKKAKAKKKKKKKKKKKAKAKKKKKKKKKKKKKKKKKKKKJ user request channel array ptr channel num user request array length 1 user_request DAC_buffer data_structure user request trigger source INTERNAL TRIGGER user request trigger mode CONT INUOUS_TRIGGER user request 10 mode BACKGROUND_IRQ user_request clock_source INTERNAL_CLOCK user_request sample_rate 100 user_request number_of_scans 1 user_request scan_event_level 0 user_request calibration NO_
132. cture is processed before continuing on to the next structure Setting buffer cycles 0 causes the data in this buffer to be processed continuously next_structure will never be accessed buffer_cycles is undefined for input operations and any value in this field will be ignored This structure pointer is used to connect multiple data buffers for larger acquisition requests When the data buffer associated with this structure has been filled or emptied DAQDRIVE will switch to the structure pointed to by next_structure and continue the operation using the new structure s data buffer next_buffer is set to NULL if there are no more structures in the chain IMPORTANT 1 Once the request is armed using DagArmRequest the application program must obey the rules defined in figures 4 and 5 for accessing the buffer structures and data buffers at run time These rules apply until the operation is completed or otherwise terminated 2 If the buffer structures or the data buffers are dynamically allocated by the application they MUST NOT be de allocated until the request is completed or otherwise terminated In addition applications using the Windows DLL version of DAQDRIVE should use DaqAllocateMemory if dynamically allocated buffer structures or data buffers are required 9 2 buffer_status INPUT OPERATIONS Bit Value DAQDRIVE constant Description 0x0001 BUFFER_FULL BUFFER_FULL indicates the data
133. d short channel_array 3 0 Ly SR float gain_array 3 1 0 1 0 8 0 short input_array 3 unsigned short array_length char far device type DAQP 208 char far config_file c daqp 208 daqp 208 dat jJkkAkKKK Open the DAQP 208 logical_device 0 status DaqOpenDevice DAQP amp logical_device device type config file if status 0 printf Error opening configuration file Status code Sd n status exit status Input one value from A D channels 0 1 and 2 KAKKKJ status DaqSingleAnalogInputScan logical device channel array gain_array array length input_array if status 0 printf Error reading from A D Status code d n status juskak Close the DAQP 208 status DaqCloseDevice logical device if status 0 printf Error closing device Status code d n status return status 13 81 13 27 DaqSingleAnalogOutput The DaqSingleAnalogOutput procedure provides a simplified interface for outputting a single point to a single D A converter The format of the command is shown below The value specified by output_value is output to the D A converter specified by channel_number on the adapter specified by logical_device This procedure executes the DAQDRIVE procedures DaqAnalogOutput DaqArmRequest DaqTriggerRequest and DaqReleaseRequest before returning to the calling application unsigned short DaqSingleAnal
134. da8p 12 h unsigned short main unsigned short logical_device unsigned short status char far device_type DA8P 12B char far config_file c da8p 12b da8p 12b dat Open the DA8P 12B logical_device 0 status DaqOpenDevice DA8P 12 amp logical_device device_type config_file if status 0 printf Error opening configuration file Status code d n status exit status Perform any DA8P 12B operations here KERE k k Close the DASP 12B KKK status DagCloseDevice logical device if status 0 printf Error closing device Status code d n status return status include daqdrive h include daqopenc h include userdata h include dagp h unsigned short main unsigned short logical device unsigned short status char far device type DAQP 16 char far config_file c daqp 16 dagp 16 dat feexes Open the DAQP 16 logical_device 0 status DaqOpenDevice DAQP amp logical_device device type config file if status 0 printf Error opening configuration file Status code d n status exit status x Perform any DAQP 16 operations here Sek k Close the DAQP 16 status DaqCloseDevice logical device if status 0 printf Error closing device Status code d n status return status 13 67 13 21 2 DaqOpenDevice Win
135. dows DLL Version The Windows DLL version of DaqOpenDevice is intended for Windows applications that interface to the DAQDRIVE dynamic link libraries DLLs Consult the target hardware s appendix in the DAQDRIVE User s Manual Supplement for the required settings of the DLL_name and device_type variables unsigned short DaqOpenDevice char far DLL_name unsigned short far logical_device char far device_type char far config file DLL name This pointer defines the starting address of a character array string specifying the hardware dependent DLL required for the desired adapter The name of this DLL is contained in the target hardware s appendix in the DAQDRIVE User s Manual Supplement If DLL name does not specify a path Windows will search for the DLL in the follovving order the current directory the Windows directory the Windows system directory the application s directory the system s PATH and any mapped network drives logical_device This pointer specifies the address of an unsigned short integer where the logical device number assigned by DAQDRIVE will be stored The application should initialize the integer pointed to by logical_device to 0 device_type This pointer defines the starting address of a character array string which describes the hardware device to be opened The target hardware s appendix of the DAQDRIVE User s Manual Supplement contains the valid settings for device_type config file
136. e I SE xi 12 21 if status 0 DaqCloseDevice logical_device exit status Step 3 Arm the Request status DagArmRequest request_handle if status 0 printf Arm request error Status code d n status DaqReleaseRequest request_handle DaqCloseDevice logical device exit status Step 4 Trigger the Request status DaqTriggerRequest request_handle if status 0 printf Trigger request error Status code d n status DaqReleaseRequest request_handle DaqCloseDevice logical_device exit status Step 5 Wait for completion or error KR event mask COMPLETE EVENT RUNTIME ERROR EVENT if user request request status amp COMPLETE EVENT if successful display data 0 for i 0 i lt 50 itt _clearscreen _GCLEARSCREEN for j 0 j lt 20 j printf sample 4d value 2xH n i 20 j printf n Press lt ESC gt to continue while getch 0x1b else printf Run time error Operation aborted n DaqReleaseRequest request_handle DaqCloseDevice logical_device exit status xxx Step 6 Release the Request status DaqReleaseRequest request_handle if status 0 printf Could not release configuration Status code sd n exit status Step 7 Close Hardware Device
137. e Interrupt in use by another device The requested operation requires a hardware interrupt IRQ that is currently in use by another device This operation must be requested again after the other device has relinquished control of the interrupt Internal interrupt error This is an internal DAQDRIVE error If this error is received contact Omega s technical support department If possible have the hardware device type and software version numbers available when calling No DMA channel defined for adapter The requested operation requires one or more DMA channels and no DMA channels were defined for the adapter in the hardware configuration file DMA channel in use by another device The requested operation requires one or more DMA channels that are currently in use by other device s This operation must be requested again after the other device s have relinquished control of the DMA channels Internal DMA error This is an internal DAQDRIVE error If this error is received contact Omega s technical support department If possible have the hardware device type and software version numbers available when calling Memory allocation error An error occurred while DAQDRIVE was attempting to allocate memory for internal use Generally this error only occurs when there is no more memory available in the system Remove any unnecessary device drivers and memory resident programs and execute the application again DAQDRIVE
138. e uest number of scans uest scan event level uest calibration uest timeout interval 0 2 input_values 1000 my_request my_data KKKKKJ channel list ggain list 1 my_data INTERNAL_TRIGGER BACKGROUND_IRQ INTERNAL_CLOCK 10000 1000 0 NO_CALIBRATION 0 NO_EVENTS uest request_status Construct the data buffer structure KREE a data_buffer input_values 1000 NULL BUFFER_EMPTY a buffer_length a next_structure a buffer_status Variations on example 1 To change the operating mode from background mode with interrupts to foreground mode using DMA set my request IO mode FOREGROUND_DMA To change the trigger mode to an analog trigger set my request trigger source ANALOG_TRIGGER my request trigger channel 0 my request trigger voltage 3 0 my request trigger Slope RISING EDGE To enable calibration for the request set my request calibration AUTO CALIBRATE or my request calibration AUTO ZERO or my request calibration AUTO CALIBRATE AUTO ZERO DAQDRIVE User s Manual 5 7 5 3 2 Example 2 Multiple Channel Input Purpose Input 1000 sample from each of 4 analog input channels at a rate of 500Hz unsigned short channel_number 4 0 1 14 6 float gain_settings 4 ZIL ko TO TOOH unsigned short input_values 4 1000 struct ADC request my request struct DAQDRIVE buffer my data Construct the request structure REREAD
139. e variable and the name of the include file h which defines the open command for the target device unsigned short DaqOpenDevice PROCEDURE unsigned short far logical_device char far device_type char far config file PROCEDURE This is a constant used by the macro to define the open procedure of the driver to be accessed and must be entered exactly as it is defined in the target hardware s appendix of the DAQDRIVE User s Manual Supplement PROCEDURE is used with the token pasting operator to generate a unique open procedure for each type of hardware device logical_device This pointer specifies the address of an unsigned short integer where the logical device number assigned by DAQDRIVE will be stored The application should initialize the integer pointed to by logical_device to 0 device_type This pointer defines the starting address of a character array string which describes the hardware device to be opened The target hardware s appendix of the DAQDRIVE User s Manual Supplement contains the valid settings for device_type config file This pointer defines the starting address of a character array string which defines the name of the DAQDRIVE configuration file to be used This character string must contain the drive path filename and extension of the desired configuration file DAQDRIVE User s Manual 13 66 include daqdrive h include daqopenc h include userdata h include
140. e A Ae EE e hh KKK e k k k k d Output a 20 point waveform to a D A channel ti JEKKAKKKAKAKKKKKKKKKKKKKAKAKKKKKKKKKAKAKAKKKKKKKKKKKKKAKAKKKKKKKKKKKKKKKKKKKJ unsigned short main unsigned short logical_device unsigned short request_handle unsigned short channel unsigned short status unsigned short error_code unsigned short i short data_array 20 unsigned long event_mask struct DAC_request user_request struct DAQDRIVE buffer data structure Open the device see DaqOpenDevice BERK J x x define D A output channel and calculate output data REE RET Prepare data structure for analog output PEAKS Jenni Prepare the D A request structure BERS Request D A output See DagAnalogOutput RARER k Arm the request See Daq rmkRequest KERRY x Trigger the request KKK Wait for completion or error RARER SY event_mask COMPLETE_EVENT RUNTIME_ERROR_EVENT while user_request request_status amp event_mask 0 if user_request request_status amp COMPLETE_EVENT 0 printf Request complete n else status DaqGetRuntimeError request_handle error_code printf Run time error d Request aborted n error code Jenni Release the request KL status DaqReleaseRequest request_handle if status 0 printf Could not release configuration Status code d n status k Close the device status DagCloseDevice l
141. e Beginning 2 1 Software Installation The DAQDRIVE distribution disks include installation programs for both DOS and Windows The Windows installation program is recommended for all systems equipped with Windows or Windows 95 and allows a complete DAQDRIVE installation for DOS and or Windows including the installation of all DAQDRIVE utility programs The DOS installation program may be used to install the DAQDRIVE components which are used to create DOS applications ONLY The DOS installation program WILL NOT install the DAQDRIVE components required for Windows based applications nor will it install any of the DAQDRIVE utility programs including the DAQDRIVE Configuration Utility From Windows Windows 95 1 From the Windows program manager select File Run or from the Windows 95 desktop select Start Run 2 Assuming DAQDRIVE distribution disk 1 is in drive A enter A SETUP in the command line text box and click OK From DOS 1 Assuming DAQDRIVE distribution disk 1 is in drive A type A INSTALL and press lt Enter gt Follow the on screen instructions to select the DAQDRIVE components to be installed and insert the remaining diskettes as required When the installation program is complete one or more of the following subdirectories will have been created in the target directory DAQDRIVE CONFIG DAQDRIVE Configuration Utility DAQDRIVE TUTOR DAQDRIVE Request Structure Tutorial DAQDRIVE C_LI
142. e execution stop BERK KS exit_program COMPLETE_EVENT RUNTIME_ERROR_EVENT TIMEOUT_EVENT Wait for exit event KERRE while my_request request_status amp exit_program 0 hae Wait in dead loop for any event PER ERT while my_request request_status NO_EVENTS Process trigger event KKK if my request request status amp TRIGGER EVENT 0 DAQDRIVE User s Manual 11 4 11 3 Monitoring Events Using Event Notification Event notification allows the user to define a procedure that DAQDRIVE will execute each time an event occurs Event notification is especially useful during foreground mode operations when DAQDRIVE has control of the CPU The request s event notification procedure is installed using DaqNotifyEvent and should be installed before the request is armed unsigned short DaqNotifyEvent unsigned short request_handle void far pascal event_procedure unsigned short unsigned short unsigned short unsigned long event_mask The event procedure defined by the application program must be a Tar pascal compatible procedure of type void When executed DAQDRIVE provides the event procedure with the request s request_handle the type of event which has occurred as shown in figure 8 and an event error code This error code is set to 0 for all events except the run time error event where it is used to specify the type of error encountered as defined in chapter 14 Since the
143. e is used to define the target hardware device This is the value returned to the application by the DaqOpenDevice command channel array This pointer specifies the address of an unsigned short integer array containing the analog input channels on logical device to be sampled gain array This pointer specifies the address of a floating point array defining the gain setting for the channels specified by channel array array length This unsigned short integer value defines the length of channel array gain array and input array input array This void pointer specifies the address of an array where the values input from the A D converter are to be stored input array is declared as a void to allow it to point to data of any type It is the application program s responsibility to ensure the data pointed to by input_array is the correct type for the target hardware as listed in the table below DAQDRIVE User s Manual 13 80 Resolution Configuration data type 1 to 8 bits unipolar unsigned char bipolar signed char 9 to 16 bits unipolar unsigned short bipolar signed short 17 to 32 bits unipolar unsigned long bipolar signed long Figure 24 input_array data types as a function of analog input channel type include daqdrive h tinclude daqopenc h include userdata h tinclude dagp h unsigned short main unsigned short logical device unsigned short status unsigne
144. e or more analog input channels to be operated on by this request The application provides the memory address of the first channel in the list using the channel_array_ptr field In addition to the channel list the application must provide a gain setting for each channel in the channel list The application provides the memory address of the first gain setting in the gain list using the gain_array_ptr field For each channel in the channel list there must be one and only one setting in the gain list Therefore the lengths of both lists are specified by the array_length field 5 2 3 Data Buffers ADC_buffer defines the request s data buffer structure s to be used for storing the data input from the specified channel s The application program must define these buffers within the guidelines provided in chapter 9 5 2 4 Trigger Selections The trigger selection determines how the requested operation will be initiated after being armed Six fields are required to define and configure the trigger for the request trigger_source trigger_mode trigger_slope trigger_channel trigger_voltage and trigger_value Because the trigger selection is an integral part of the operation and is common to all of DAQDRIVE s request structures trigger configurations are discussed separately in chapter 10 5 2 5 Data Transfer Modes The request structure field IO_mode determines the mechanism that will be used to input the data from the hardware device In ge
145. e request structure is dynamically allocated by the application it MUST NOT be de allocated until the request has been released by the DaqReleaseRequest procedure In addition applications using the Windows DLL version of DAQDRIVE should use DaqAllocateMemory if dynamically allocated request structures are required 13 29 channel_array_ptr This pointer defines the address of an unsigned short integer array specifying the logical digital output channel s to be operated on by this request reserved1 4 This unsigned short integer array is reserved for the future expansion of DAQDRIVE For maximum compatibility the application should initialize all reserved variables to 0 array_length This unsigned short integer value defines the number of channels contained in the array pointed to by channel_array_ptr digio_buffer This pointer defines the address of the first data buffer structure Data buffer structures are discussed in chapter 9 reserved2 4 This unsigned short integer array is reserved for the future expansion of DAQDRIVE For maximum compatibility the application should initialize all reserved variables to 0 trigger_source This unsigned short integer value specifies the trigger source for this request Trigger selections are discussed in chapter 10 DAQDRIVE Constant Value Description INTERNAL_TRIGGER 0 internal software trigger TTL_TRIGGER 1 TTL trigger ANALOG_TRIGGER 2 a
146. e required PCMCIA Card and Socket Services or Plug and Play support software is not installed on the system The user must specify the hardware configuration in the configuration file or the required software drivers must be installed on the system Invalid device type An invalid device type was specified in the configuration file If there are no apparent problems reading the file generate a new configuration file using the DAQDRIVE configuration utility Configuration file error This is an internal DAQDRIVE error If this error is received contact Omega s technical support department If possible have the hardware device type and software version numbers available when calling Configuration file error This is an internal DAQDRIVE error If this error is received contact Omega s technical support department If possible have the hardware device type and software version numbers available when calling DAQDRIVE User s Manual 14 2 71 72 73 74 100 120 150 Configuration file error This is an internal DAQDRIVE error If this error is received contact Omega s technical support department If possible have the hardware device type and software version numbers available when calling Configuration file error This is an internal DAQDRIVE error If this error is received contact Omega s technical support department If possible have the hardware device type and software version numbers available when
147. e value from digital input channel 0 KRAKKJ digio channel 0 status DaqSingleDigitalInput logical device digio channel input_value if status 0 printf Error reading digital input Status code d n status k Close the DAQP 16 status DagCloseDevice logical device if status 0 printf Error closing device Status code d n status return status 13 87 13 30 DaqSingleDigitalinputScan The DagSingleDigitalInputScan procedure provides a simplified interface for inputting a single point from multiple digital input channels The format of the command is shown below The digital input channels specified by channel_array on the adapter defined by logical_device are returned to the array specified by input_array There is a one to one correspondence between the number of digital input channels and the number of input values Therefore array_length specifies the length of both channel_array and input_array This procedure executes the DAQDRIVE procedures DaqDigitalinput DaqgArmRequest DaqTriggerRequest and DaqReleaseRequest before returning to the calling application unsigned short DaqSingleDigitalInputScan unsigned short logical device unsigned short far channel array unsigned short array length void far input array logical device This unsigned short integer value is used to define the target hardware device This is the value returned to the applicatio
148. eAnalogOutputScan DAQDRIVE User s Manual 3 11 Output a single sample to D A channels 1 5 and 2 ERE unsigned short main unsigned short logical device unsigned short status unsigned short channel_array 3 1 oy S ki short output_array 3 413 3781 1468 char far device_type DA8P 12B char far config_file da8p 12b dat Step 1 Initialize Hardware logical_device 0 status DaqOpenDevice DA8P 12 amp logical_device device_type config_file if status 0 printf Error opening device Status code d n status exit status Step 2 Output the D A values status DaqSingleAnalogOutputScan logical device channel_array 3 output_array if status 0 printf n nD A output error Status code d n n status else printf n nComplete No errors Step 3 Close Hardware Device status DagCloseDevice logical_device if status 0 printf Error closing device Status code d n status return status DagSingleAnalogOutputScan is a very basic interface without any allowance for timing information trigger sources etc It acts as a DAQDRIVE macro defining the necessary data structures executing the analog output configuration procedure DaqAnalogOutput arming the requested configuration DaqArmRequest and triggering the operation DaqTriggerRequest For users interested in learning more about
149. ed char input_array 3 char far device type IOP 241 char far config_file iop 241 dat Step 1 Initialize Hardware logical_device 0 status DaqOpenDevice IOP241 amp logical_device device type config_file if status 0 printf Error opening device Status code d n status exit status Step 2 Input one sample from each channel EK Y status DaqSingleDigitalInputScan logical device channel_array 3 input_array if status 0 printf n nA D input error Status code d n n status else printf Channel 3 d n n int input_array 0 printf Channel 2 d n n int input_array 1 printf Channel 1 d n n int input_array 2 Step 3 Close Hardware Device status DaqCloseDevice logical_device if status 0 printf Error closing device Status code d n status return status DaqSingleDigitalinputScan is a very basic interface without any allowance for timing information trigger sources etc It acts as a DAQDRIVE macro defining the necessary data structures executing the digital input configuration procedure DaqDigitalinput arming the requested configuration DaqArmRequest and triggering the operation DaqTriggerRequest For users interested in learning more about DAQDRIVE s digital input interface the following example program creates the equivalent of the DaqSingleDigitalinputScan
150. ed4 4 This unsigned short integer array is reserved for the future expansion of DAQDRIVE For maximum compatibility the application should initialize all reserved variables to 0 number_of_scans This unsigned long integer value defines the number of times the channels specified in channel_array_ptr will be written Setting number_of_cycles 0 will cause the channels to be scanned continuously scan_event_level This unsigned long integer value defines the frequency at which scan events are reported to the application For example setting scan_event_level to 100 causes a scan event to be generated each time 100 scans are completed reserved5 8 This unsigned short integer array is reserved for the future expansion of DAQDRIVE For maximum compatibility the application should initialize all reserved variables to 0 Figure 17 continued Digital output request structure definition 13 31 timeout_interval This unsigned short integer value defines a time out interval in seconds for foreground mode processes The operation will abort if the digital output can not be updated every timeout_interval seconds Setting timeout_interval 0 disables the time out function and causes the routine to wait indefinitely request_status This unsigned long integer value provides the application with the current status of the request DAQDRIVE does not rely on the information contained in this field nor does it
151. endices for specifics on adapter calibration DAQDRIVE Constant Value Description NO_CALIBRATION 0x0000 No calibration requested AUTO_CALIBRATE 0x0001 Perform auto calibration on this request AUTO_ZERO 0x0002 Perform auto zero on this request timeout_interval This unsigned short integer value defines a time out interval in seconds for foreground mode processes The operation will abort if the analog output can not be updated every timeout_interval seconds Setting timeout_interval 0 disables the time out function and causes the routine to wait indefinitely request_status This unsigned long integer value provides the application with the current status of the request DAQDRIVE does not rely on the information contained in this field nor does it ever clear any of the event bits to 0 Therefore the application should initialize request_status during the configuration process and may modify its contents at any time DAQDRIVE Constant Value Description NO_EVENTS 0x00000000 This constant does not represent an event status It is provided to the application for convenience TRIGGER_EVENT 0x00000001 When set to 1 this bit indicates the specified trigger has been received COMPLETE_EVENT 0x00000002 When set to 1 this bit indicates the request has completed successfully BUFFER_EMPTY_EVENT 0x00000004 When set to 1 this bit indicates at least one of the specified output data bu
152. equest structure in future releases of DAQDRIVE To maintain maximum compatibility the application program should initialize all reserved fields to 0 8 2 2 Channel Selections The digital output request structure begins with a list of one or more digital output channels to be operated on by this request The application provides the memory address of the first channel in the list using the channel_array_ptr field and must specify the length of the list in the array_length field 8 2 3 Data Buffers digio buffer defines the request s data buffer structure s containing the data to be output to the specified channel s The application program must define these buffers within the guidelines provided in chapter 9 8 2 4 Trigger Selections The trigger selection determines how the requested operation will be initiated after being armed Six fields are required to define and configure the trigger for the request trigger_source trigger_mode trigger_slope trigger_channel trigger_voltage and trigger_value Because the trigger selection is an integral part of the operation and is common to all of DAQDRIVE s request structures trigger configurations are discussed separately in chapter 10 8 2 5 Data Transfer Modes The request structure field IO_mode determines the mechanism that will be used to output the data to the hardware device In general the foreground modes provide the highest data transfer rates at the expense of requiring 100
153. equired and any resources required by this device may be freed unsigned short DaqCloseDevice unsigned short logical_device logical_device This unsigned short integer value is used to define the target hardware device This is the value returned to the application by the DaqOpenDevice command DAQDRIVE User s Manual 13 20 include daqdrive h include daqopenc h include userdata h include dagp h unsigned short main unsigned short logical_device unsigned short status char far device type DAQP 16 char far config_file c daqp 16 daqgp 16 dat Open the DAQP 16 logical_device 0 status DaqOpenDevice DAQP amp logical_device device type config file if status 0 printf Error opening configuration file Status code d n status exit status k Perform any DAQP 16 operations here RES T jeti Close the DAQP lt 16 2 Sien status DagCloseDevice logical_device if status 0 printf Error closing device Status code d n status return status 13 21 13 7 DaqDigitalInput DaqDigitalinput is DAQDRIVE s generic digital input interface DaqDigitalinput does not configure any hardware but acts simply to confirm that all parameters are valid and that the type of operation requested is supported by the target hardware unsigned short DaqDigitalInput unsigned short logical_device struct digio_req
154. er of scans 15000 my_data buffer_cycles 15000 To enable a time out if the trigger does not occur within 15 seconds after the request is armed set my request timeout interval 15 6 8 7 Digital Input Requests In chapter 3 some special purpose procedures were presented to help the user get familiar with DAQDRIVE s digital input interface The key to understanding and utilizing DAQDRIVE however is to understand its request structures This chapter will present the digital input request structure and provide examples to illustrate how this structure is configured for some common applications 71 DagqDigitalInput DaqDigitalinput is DAQDRIVE s digital input interface Any digital input operation is possible with the proper configuration of the request structure The format of the command is shown below unsigned short DaqDigitalInput unsigned short logical_device struct digio_request far user_request unsigned short far request handle DaqDigitalinput performs the configuration portion of a digital input request For a new configuration the application program sets request_handle to 0 before calling DaqDigitalInput DaqDigitalinput then analyzes the data structure specified by user_request to determine if all of the parameters are valid and if the requested operation can be performed by the device specified by logical_device If the requested operation is valid DaqDigitalinput assigns request handle a uni
155. errors release the request and return KAKKKJ status DaqReleaseRequest request handle return status U 3 16 3 3 2 DaqSingleDigitalinputScan Another simple case of digital input is to input one value each from multiple digital I O channels under CPU control This allows multiple digital inputs to be sampled simultaneously or nearly simultaneously depending on the data acquisition hardware A simplified interface for this operation is provided through the DaqSingleDigitalinputScan procedure The format of this command is shown below unsigned short DaqSingleDigitalInputScan unsigned short logical_device unsigned short far channel array unsigned short array length void far input array DaqSingleDigitalinputScan inputs a single sample from each of the digital I O channels specified by channel array on the adapter specified by logical_device The samples are stored in the array specified by input_array A one to one correspondence is required between the number of digital input channels and the number of samples Therefore array_length specifies the length of channel_array and input_array The following example shows the usage of DaqSingleDigitalinputScan DAQDRIVE User s Manual 3 17 Input a single sample from digital I O channels 3 2 and 1 EE unsigned short main unsigned short logical_device unsigned short channel_array 3 3 2 1 unsigned short status unsign
156. erter specified by channel number on the adapter specified by logical device The following example shows the usage of DagSingleAnalogOutput 3 8 Output a single sample to D A channel 1 RRES unsigned short main unsigned short logical_device unsigned short status short output_value char far device_type char far config_file DAQ 1201 daq 1201 dat Step 1 Initialize Hardware logical_device 0 status DaqOpenDevice DAQ1200 amp logical_device device type config file if status 0 printf Error opening device Status code d n status exit status T Step 2 Output the value to channel 1 KERJ output_value 512 status DaqSingleAnalogOutput logical_device 1 amp output_value if status 0 printf n nD A output error Status code d n n status else printf n nComplete No errors Step 3 Close Hardware Device status DagCloseDevice logical_device if status 0 printf Error closing device Status code d n status return status DaqSingleAnalogOutput is a very basic interface without any allowance for multiple channels multiple output values trigger sources etc It acts as a DAQDRIVE macro defining the necessary data structures executing the analog output configuration procedure DaqAnalogOutput arming the requested configuration DaqgArmRequest and triggering the operation DaqTriggerReq
157. es have been calculated KKK and stored in pattern KERRE Ji Construct the request structure KR gchannel number 1 my data EXTERNAL TRIGGER RISING_EDGE BACKGROUND_IRQ INTERNAL_CLOCK my_request sample_rate 100 my_request number_of_scans 100 128 my_request scan_event_level 0 my_request timeout_interval 0 my_request request_status NO_EVENTS Construct the data buffer structure SE my data data buffer pattern my_data buffer_length 128 my_data buffer_cycles 100 my_data next_buffer NULL BUFFER_FULL Variations on example 2 1 To change the number of points from 128 to 64 re define patterni and then set my_request number_of_scans 100 64 my_data buffer_length 64 To change the number of cycles from 100 to 800 set my_request number_of_scans 800 128 my_data buffer_cycles 800 DAQDRIVE User s Manual 8 7 This page intentionally left blank 9 Defining Data Buffers DAQDRIVE s data buffers are defined as structures containing the buffer configuration and a pointer to the data storage area This allows multiple data buffers to be defined as each buffer is completely self contained buffer_status data_buffer struct DAQDRIVE buffer unsigned short buffer status void huge tdata buffer unsigned long buffer length unsigned long buffer cycles struct DAQDRIVE buffer far X nemt structure Ve This unsigned short integer value
158. est request_handle DaqCloseDevice logical_device exit status x x x Trigger the request KKK status DaqTriggerRequest request handle if status 0 printf Trigger error Status code d n status DaqReleaseRequest request_handle DaqCloseDevice logical device exit status L 13 97 13 35 DaqUserBreak DaqUserBreak allows the application program to install a procedure written by the application programmer that DAQDRIVE will execute periodically during foreground mode operations If the application wants to terminate the operation the user break procedure need only return a non zero value To continue the operation the user break procedure must return zero unsigned short DaqUserBreak unsigned short request handle request handle break procedure unsigned short far pascal break procedure This unsigned short integer variable is used to define which request is to use the user break procedure defined by break_procedure This is the value returned to the application by the configuration procedures DaqAnaloginput DaqAnalogOutput DaqDigitalInput or DaqDigitalOutput This pointer defines the starting address of the procedure to be executed during foreground mode operations break procedure must be a far pascal compatible procedure of type unsigned short that has no input parameters A sample C declaration of this procedure is shown below unsi
159. est_status amp COMPLETE EVENT 0 if successful display data for i O i lt 10 i _clearscreen _GCLEARSCREEN for j 0 j lt 20 j printf sample 4d i 20 4 for k 0 k lt 5 k printf 6d input_data i 20 j k status KE DAQDRIVE User s Manual 12 6 12 1 4 Example 4 This example simulates a volt meter operation reading 20 samples from A D channel 0 s at 1Hz using only one data memory location Input 20 samples from A D channel 0 RAK include lt conio h gt include lt graph h gt include lt stdlib h gt include lt stdio h gt include userdata h include daqdrive bi tinclude daqopenc h include dagqp h When defined global or static structures are RHR SY automatically initialized to all 0 Zeg struct DAQDRIVE buffer my_data struct ADC_request user_request unsigned short main unsigned short logical device unsigned short request handle unsigned short channel unsigned short status short current_sample float gain unsigned long event_mask char far device type DAQP 16 char far config_file daqp 16 dat Step 1 Initialize Hardware logical_device 0 status DaqOpenDevice DAQP amp logical_device device type config file if status 0 printf Error opening device Status code d n status exit status Step 2 Input
160. evice exit status Prepare data structure for analog input AER ERY data_structure data_buffer memory_pointer data_structure buffer_length 10000 Jenni Prepare the A D request structure EA RAY Request A D input See Daq naloginput SET Arm the request See DagqArmRequest KERRE Jenni Trigger the request See DaqTriggerRequest SEET x Wait for complete EER RE k Free allocated memory Ze status DaqFreeMemory memory_handle memory_pointer if status 0 printf Error de allocating memory Status code d n status DaqCloseDevice logical_device exit status k Close the device See DaqCloseDevice K E 13 35 13 10 DaqGetADCfgInfo DaqGetADCfgInfo returns the configuration of the A D converter specified by ADC_device on the adapter specified by logical_device unsigned short DaqGetADCfgInfo unsigned short logical_device unsigned short ADC_device struct ADC_configuration far ADC_info logical_device This unsigned short integer value is used to define the target hardware device This is the value returned to the application by the DaqOpenDevice command ADC device This unsigned short integer value is used to select one of the A D converters on the target hardware device ADC_info This structure pointer defines the address of an A D configuration structure where the configuration of the specified A D converter
161. f an error during processing The application can determine the source of the error using the DaqGetRuntimeError procedure Figure 7 request_status bit definitions 11 3 Quatech Inc include daqdrive bi include userdata h unsigned short exit_program printf Trigger received n my request request status amp TRIGGER_EVENT k k Process scan event KEK if my request request status 8 SCAN EVENT 0 printf Scan Event n my request request status sz SCAN_EVENT k Indicate time out error KREKKJ if my request request status amp TIMEOUT EVENT 0 printf Request aborted Time out error n Indicate run time error KKK if my request request status 8 RUNTIME ERROR EVENT 0 printf Request aborted Run time error n Jenni Indicate complete no errors KERER if my_request request_status amp COMPLETE_EVENT 0 printf Request completed nn Jenni Release the request See DaqReleaseRequest KKK Close the device See DaqCloseDevice ek RY Open the device see DaqOpenDevice FREER Prepare a background request ARIK my_request 1I0O_mode BACKGROUND_IRQ my_request request_status NO_EVENTS k Request the operation PEERY Arm the request See Daq rmRequest KKK x x Trigger the request See DaqTriggerRequest KKK k Define events which will mak
162. fer 3 current_buffer 0 else current buffertt while current buffer 0 fclose output file xxx Step 6 Release the Request status DaqReleaseRequest request_handle if status 0 printf Could not release configuration Status code d n status exit status Step 7 Close Hardware Device HERS status DagCloseDevice logical device if status 0 printf Error closing device Status code d n status return status H 12 11 12 2 Analog Output D A Examples 12 2 1 Example 1 This example outputs a single value to a single D A channel Output a single point to a single D A channel L include lt conio h gt include lt graph h gt include lt stdio h gt include lt stdlib h gt include userdata h include daqdrive h include daqopenc h include daql200 h unsigned short main unsigned short logical_device unsigned short status unsigned short channel short output_value char far device type DAQ 1201 char far config_file daq 1201 dat Step 1 Initialize Hardware logical_device 0 status DaqOpenDevice DAQ1200 amp logical_device device_type config_file if status 0 printf Error opening device Status code d n status exit status Step 2 Get D A channel and output value LEAS _clearscreen _GCLEARSCREEN printf n nEnter a cha
163. ffer my_data 1 buffer_status BUFFER_FULL indicate buffer full ready K my_data 2 data_buffer square set pointer to output data KI my datal2 1 buffer length 2 number of points in buffer kj my_data 2 buffer_cycles 18000 18000 cycles through buffer k my_data 2 next_structure NULL mo more buffers Kl my_data 2 buffer_status BUFFER_FULL indicate buffer full ready Kei Prepare the D A request structure KEK user request channel array p r channel array of channels Ej user_request array_length 1 number of channels SE user_request DAC_buffer amp my_data 0 pointer to data Ry user_request trigger_source INTERNAL_TRIGGER internal trigger ae user_request trigger_mode CONTINUOUS_TRIGGER output all points ay user_request IO_mode BACKGROUND_IRQ background mode X user_request clock_source INTERNAL CLOCK use on board clock KA user request sample rate 3600 3600 points second user request number of scans 601 6001 36000 scans of sine 1201 3001 36000 scans of ramp XL 2 x 180001 36000 scans of square user_request scan_event_level 0 no scan events user_request calibration NO_CALIBRATION no calibration ay user_request timeout_interval 0 disable time out user_request request_status 0 initialize status kE request_handle 0 new request status DaqAnalogOutput logical device amp user_request amp
164. ffers has been emptied BUFFER_FULL_EVENT 0x00000008 When set to 1 this bit indicates at least one of the specified input data buffers has been filled SCAN_EVENT 0x00000010 When set to 1 this bit indicates the number of scans specified by scan_event_level have been completed at least once USER_BREAK_EVENT 0x20000000 When set to 1 this bit indicates the request has terminated due to a user break TIMEOUT_EVENT 0x40000000 When set to 1 this bit indicates the request has terminated because the specified time out interval was exceeded RUNTIME_ERROR_EVENT 0x80000000 When set to 1 this bit indicates the request has terminated because of an error during processing The application can determine the source of the error using the DaqGetRuntimeError procedure Figure 13 continued Analog output request structure definition DAQDRIVE User s Manual 13 14 include daqdrive bi include userdata h JEKKAKKKAKKKKKKKKKKKKKKKAKKKKKKKKKKKAKAKAKKKKKKKKKKKAKAKKKKKKKKKKKKKKKKKKKKJ Output a 20 point waveform to a D A channel XI JEKKAKKKAKKKKKKKKKKKKKKKAKKKKKKKKKKKAKAKAKKKKKKKKKKKAKAKKKKKKKKKKKKKKKKKKKKJ unsigned short main unsigned short logical_device unsigned short request_handle unsigned short channel num 0 unsigned short status short data_array 20 struct DAC_request user_request struct DAQDRIVE buffer data structure k Open the device see DaqOpenDevice HERE Jenni Prepare data stru
165. ffset VARPTR Channellol ADCRequest ChannelArrayPtrSegment VARSEG Channellol 2 4 5 6 Dynamic memory allocation To prevent Quick Basic from dynamically relocating variables it is good practice to declare all variables before the first instruction of the application program DAQDRIVE User s Manual 2 15 2 4 6 Visual Basic for DOS To generate application programs using the DAQDRIVE TSR with Visual Basic for DOS the Quick Library DAQVBDOS QLB must be loaded from the Visual Basic command line using the L option DAQVBDOS QLB is installed into the DAQDRIVE TSR VBDOS directory by the DAQDRIVE installation program A standard object library DAQVBDOS LIB is also installed in this directory for creating executable programs EXE using Visual Basic for DOS Two additional files are installed into the DAQDRIVE TSR VBDOS directory for the programmer s convenience These files contain the prototypes of all the DAQDRIVE procedures the DAQDRIVE data structure definitions and the DAQDRIVE constants mentioned throughout this document These files must be included in all application programs DAQVBDOS INC procedure declarations USERDATA INC data structures and pre defined constants 2 4 6 1 Visual Basic for DOS and the under score character One difference between the Visual Basic for DOS version and other versions of DAQDRIVE is that Visual Basic reserves the underscore character _ The underscore character appears in data de
166. fining the numeric coprocessor switch N 2 26 3 Quick Start Procedures DAQDRIVE s data defined interface may be considerably different from normal data acquisition drivers and for simple operations may seem to result in more work for the application programmer For this reason DAQDRIVE provides a set of procedures to perform simple operations in the normal way These procedures act as DAQDRIVE macros configuring all of the necessary data structures and executing all of the routines required to complete the pre defined function To use any of these functions the application need only follow the steps listed below Step 1 Define The Hardware Configuration DAQDRIVE determines the configuration of a device from the data file specified when the device is opened These configuration files are created using the DAQDRIVE configuration utility as described in Appendix A of the DAQDRIVE User s Manual Supplement Step 2 Open The Hardware Device Before the application program can use an adapter it must first open the device using the DaqOpenDevice command The application must provide the open command with the adapter type and specify the name of a configuration file generated in step 1 vyhich describes the target hardware s configuration If the open command completes successfully DAQDRIVE assigns a logical device number to be used for all future references to the adapter Step 3 Execute The Quick Start Procedure s The
167. g the optimization options for the Borland C C compiler problems may arise if the Invariant code motion option is selected and DAQDRIVE is operated in one of the background modes IRQ or DMA To disable the Invariant code motion optimization within the Borland C C environment select Options Compiler Optimizations then confirm the Invariant code motion box is not checked From the Borland C C command line make sure the Om and O2 options are not used IMPORTANT It is strongly recommended that the Invariant code motion optimization option be disabled when using the Borland C C compiler 2 24 2 5 3 Visual Basic for Windows Visual Basic programming support is provided by the VisualDAQ and VisualDAQ Light software packages VisualDAQ is a set of Visual Basic custom controls for Omega s data acquistion hardware The VisualDAQ controls provide an easy interface to interact with Omega s data acquisition product line VisualDAQ Light which is included free with the purchase of any data aquisition product provides a simple interface to perform single point data aquisition I O On line documentation is included with VisualDAQ Light VisualDAQ provides Visual Basic programmers with custom controls to configure all parameters of the data aquisition board VisualDAQ is sold seperately and includes a complete programming reference manual DAQDRIVE User s Manual 2 25 2 5 4 Turbo Pascal for Wi
168. ge In addition the trigger slope must be specified as either rising edge the voltage must transition from below the trigger voltage to above the trigger voltage or falling edge the voltage must transition from above the trigger voltage to below the trigger voltage The trigger value setting is not required for an analog trigger and any value provided in this field is ignored 10 1 4 Digital Trigger The digital trigger allows a request to be initiated when a specific value is detected on a digital input channel When the digital trigger is selected the application must specify the digital input channel to be monitored and the value that must be received to generate the trigger The trigger slope and trigger voltage settings are not required for a digital trigger and any value provided in these fields is ignored DAQDRIVE User s Manual 10 2 10 2 Trigger Modes DAQDRIVE supports two trigger modes one shot and continuous When the application configures a request the trigger mode must be specified along with the trigger source 10 2 1 One shot Trigger Mode When a request is configured for one shot trigger mode a separate occurrence of the trigger is required for each scan of the channel list For example if a single digital output channel is configured for an internal trigger in one shot mode each call to DaqTriggerRequest will output one sample to the specified digital channel If a request is configured to input data from six
169. ger event EVENT_TYPE_COMPLETE 1 This call to the notification procedure is the result of a complete event EVENT_TYPE_BUFFER_EMPTY 2 This call to the notification procedure is the result of a buffer empty event EVENT_TYPE_BUFFER_FULL 3 This call to the notification procedure is the result of a buffer full event EVENT_TYPE_SCAN 4 This call to the notification procedure is the result of a scan event EVENT TYPE USER BREAK 29 This call to the notification procedure is the result of a user break event EVENT TYPE TIMEOUT 30 This call to the notification procedure is the result of a time out event EVENT TYPE RUNTIME ERROR 31 This call to the notification procedure is the result of a run time error event 13 63 include daqdrive bi include userdata h Define an event procedure ek REE void far pascal my_event_procedure unsigned short request_handle unsigned short event_type unsigned short error_code switch event_type case EVENT_TYPE_TRIGGER k process trigger events EKRAR break case EVENT_TYPE_COMPLETE k process complete events RE break case EVENT TYPE RUNTIME ERROR k process run time error events RAR RK break x Define the main procedure BERET void main unsigned short request_handle unsigned short status unsigned long event mask Open the device see DaqOpenDevice KERER Request an operation gets a reques
170. gerRequest request_handle if status 0 DaqStopRequest request_handle DaqReleaseRequest request_handle return status JAKKAKAK If no errors release the request and return KAKKKJ status DaqReleaseRequest request handle return status l 3 1 2 DaqSingleAnalogInputScan Another simple case of analog input is to input one value each from multiple A D channels under CPU control This allows multiple analog inputs to be sampled simultaneously or nearly simultaneously depending on the data acquisition hardware A simplified interface for this operation is provided through the DagSingleAnalogInputScan procedure The format of this command is shown below unsigned short DaqSingleAnalogInputScan unsigned short logical_device unsigned short far channel array float far gain array unsigned short array length void far input array DaqSingleAnaloginputScan inputs a single sample from each of the A D channels specified by channel array using the corresponding gain setting in the gain_array The A D channels are located on the adapter specified by logical device and the samples are stored in the array specified by input array A one to one correspondence is required between the number of analog input channels the gain settings and the number of samples Therefore array_length specifies the length of channel_array gain_array and input_array The following example shows the usage of
171. gical_device if status 0 printf Error resetting device Status code d n status return status Perform additional DASP 12 operations KERRE fe ee Close the DASP I2B status DagCloseDevice logical_device if status 0 printf Error closing device Status code d n status return status 13 77 13 25 DaqSingleAnalogInput The DagSingleAnalogInput procedure provides a simplified interface for inputting a single point from a single A D converter channel The format of the command is shown below The analog input specified by channel_number on the adapter defined by logical_device is configured for the gain specified by gain_setting The analog input is converted to a digital value which is returned to the address specified by input_value This procedure executes the DAQDRIVE procedures DaqAnalogInput DagArmRequest DaqTriggerRequest and DaqReleaseRequest before returning to the calling application unsigned short DaqSingleAnalogInput unsigned short logical_device unsigned short channel_number float gain_setting void far input value logical_device This unsigned short integer value is used to define the target hardware device This is the value returned to the application by the DaqOpenDevice command channel_number This unsigned short integer value is used to specify which A D converter channel on logical_device is to be converted gain_
172. gned short far pascal break_procedure DAQDRIVE User s Manual 13 98 include daqdrive bi include userdata h Define a global counter variable eka eS global_counter 0 Define a user break procedure RAKI unsigned short far pascal my break procedure global_counter if global_counter lt 10000 return 0 less than 10 000 gt keep going J else return 1 more than 10 000 gt abort operation Define the main procedure E RERE void main unsigned short request_handle unsigned short status Open the device see DaqOpenDevice AKSE Request an operation gets a request handle RARER Install user break procedure T status DaqUserBreak request_handle my_break_procedure if status 0 printf Error installing user break n k Arm the request See DagqArmRequest Ks k k Trigger the request See DaqTriggerRequest KKK 13 99 13 36 DaqVersionNumber DaqVersionNumber returns the version numbers of the software drivers unsigned short DaqVersionNumber unsigned short logical_device float far DAQDRIVE version float far softuare version float far firmvare version logical device This unsigned short integer value is used to define the target hardware device This is the value returned to the application by the DaqOpenDevice command DAQDRIVE version This pointer
173. handle This unsigned short integer pointer is used to identify this analog output request For a new configuration request_handle is set to 0 by the application before calling DaqAnalogOutput If the configuration is successful request_handle will be assigned a unique non zero value by the DaqAnalogOutput procedure If the application modifies a previously configured request the application must call DaqAnalogOutput using the previously assigned request handle All parameters except the channel list may be modified using a reconfiguration request To modify the channel list the present request must be released DaqReleaseRequest and a nevy configuration requested DAQDRIVE User s Manual 13 10 ame DAC_request unsigned short far channel_array ptr unsigned short reserved1 4 unsigned short array_length struct DAQDRIVE buffer far DAC buffer unsigned short reserved2 4 unsigned short trigger_source unsigned short trigger mode unsigned short trigger_slope unsigned short trigger channel double trigger_voltage unsigned long trigger value unsigned short reserved3 4 unsigned short TO mode unsigned short clock source double clock rate double sample rate unsigned short reserved4 4 unsigned long number_of_scans unsigned long scan_event_level unsigned short reserved5 8 s s unsigned short calibration unsigned short timeout_interval unsigned long request status Hi
174. hannel EER Step 4 Close Hardware Device EARS status DagCloseDevice logical_device if status 0 printf Error closing device Status code d n status return status Se status DaqSingleAnalogInput logical_device channel gain amp input_value if status 0 printf n nA D input error Status code d n n status else printf Channel gt d Sd n n channel input value printf Press lt ESC gt to continue n while getch 0x1b while channel 99 DAQDRIVE User s Manual 12 2 12 1 2 Example 2 This example inputs 1000 samples from A D channel 0 at 100Hz Input 1000 samples from A D channel 0 ERE include lt conio h gt include lt graph h gt include lt stdlib h gt include lt stdio h gt include userdata h include daqdrive h tinclude daqopenc h include daql200 h When defined global or static structures are kaj automatically initialized to all 0 K struct DAQDRIVE buffer my data struct ADC request user request unsigned short main unsigned short logical_device unsigned short request_handle unsigned short channel unsigned short status unsigned short i j short input_data 1000 float gain unsigned long event_mask char far device_type DAQ 1201 char far config_file daq 1201 dat Step 1 Initialize Hardware logical_device 0 status DaqopenDevice DAQ120
175. har far config_file daqp 16 dat Step 1 Initialize Hardware logical_device 0 status DaqOpenDevice DAQP amp logical_device device type config file if status 0 printf Error opening device Status code d n status exit status do Step 2 Get digital input channel ERY _clearscreen _GCLEARSCREEN printf n nEnter a digital input channel number or 99 to quit scanf d amp channel if channel 99 Step 3 Input value from channel ERS status DaqSingleDigitalInput logical_device channel amp input_value Status code xH n n channel continue n Mad sd n n status int input_value sd n status DAQDRIVE User s Manual 12 20 12 3 2 Example 2 This example inputs 1000 samples from digital I O channel 0 Input 1000 samples from digital input channel 0 SEET include lt conio h gt include lt graph h gt include lt stdlib h gt include lt stdio h gt include userdata h include daqdrive bi include daqopenc h include iop241 h When defined global or static structures are EKR automatically initialized to all 0 KERS struct DAQDRIVE buffer my data struct digio request user request unsigned short main unsigned short logical_device unsigned short request_handle unsigned short channel unsigned short status unsigned short i j unsigned char inpu
176. he internal clock source max_rate This double precision floating point value specifies the maximum output frequency of the counter timer when using the internal clock source Figure 23 Counter timer configuration structure definition DAQDRIVE User s Manual 13 60 include daqdrive bi include userdata h include iop241 h unsigned short main unsigned short logical_device unsigned short timer_device unsigned short status struct timer_configuration timer_info char far device type IOP 241 char far config_file c iop 241 iop 241 dat k Open the IOP 241 see DaqOpenDevice KKKKKJ Get a digital I O channel configuration Sei digio_device 0 status DaqGetTimerCfgInfo logical_device timer_device amp timer_info if status 0 printf Error getting digital configuration Status code d n status exit status Display the digital I O configuration XK f printf Counter timer channel gt d timer_device printf is d bits wide n timer_info data_size printf has an internal clock rate of S n timer_info internal_clock_rate printf Hz which can produce output rates between f timer_info min_rate printf and f Hz n timer_info max_rate 13 61 13 20 DaqNotifyEvent DaqNotifyEvent allows the application program to install a procedure that DAQDRIVE will execute each time an event occurs
177. high transition is required FALLING_EDGE 1 for TTL and analog triggers only specifies a high to low transition is required trigger_channel This unsigned short value specifies the channel to be used as the input for the analog or digital trigger sources trigger_channel is undefined for all other trigger sources Trigger selections are discussed in chapter 10 Figure 15 Digital input request structure definition DAQDRIVE User s Manual 13 24 trigger_voltage This double precision value defines the trigger voltage level for the analog trigger trigger_voltage is ignored for all other trigger sources Trigger selections are discussed in chapter 10 trigger_value This unsigned long value defines the value required on the digital input for a digital trigger to be generated trigger_value is ignored for all other trigger sources Trigger selections are discussed in chapter 10 reserved3 4 This unsigned short integer array is reserved for the future expansion of DAQDRIVE For maximum compatibility the application should initialize all reserved variables to 0 IO_mode This unsigned short integer value specifies the method of data transfer clock_source DAQDRIVE Constant Value Description FOREGROUND_CPU 0 DAQDRIVE takes control of the CPU until the request is complete BACKGROUND_IRQ 1 hardware interrupts are used to gain control of the CPU and input the data FOREGROUND_DMA 2 DMA
178. ical device device type config_file if status 0 printf Error opening configuration file Status code d n status exit status Perform any IOP 241 operations here KEK k Close the IOP 241 status DagCloseDevice logical device if status 0 printf Error closing device Status code d n status return status 13 69 13 21 3 DaqOpenDevice TSR Version The TSR version of DaqOpenDevice is intended for DOS applications that interface to the memory resident version of DAQDRIVE Consult the target hardware s appendix in the DAQDRIVE User s Manual Supplement for the required settings of the TSR_number and device_type variables unsigned short DaqOpenDevice unsigned short TSR_number unsigned short far logical_device char far device_type char far config file TSK number This unsigned short integer variable specifies the interrupt service number for the desired adapter TSR_number is defined in the target hardware s appendix of the DAQDRIVE User s Manual Supplement and should not be confused with the software interrupt number where DAQDRIVE is installed logical_device This pointer specifies the address of an unsigned short integer where the logical device number assigned by DAQDRIVE will be stored The application should initialize the integer pointed to by logical_device to 0 device_type This pointer defines the starting address of a cha
179. ication must not modify my DAC data or output data until BUFFER_EMPTY is set or until the operation is terminated my_DAC_data buffer_status BUFFER_FULL DAQDRIVE User s Manual 9 15 9 3 2 Example 2 Creating Repetitive Signals In example 1 100 samples were output to a single D A channel If these 100 points represent a sinewave and the desired output is 250 cycles of this sinewave the application could allocate 25 000 250 100 points calculate 250 cycles of the sinewave and output 25 000 points to the D A A simpler approach is to change the configuration as shown below the original values from example 1 are shown in the comments short output_data 100 struct DAQDRIVE _buffer my_DAC_data my_DAC_data data_buffer output_data my_DAC_data buffer_length 100 my_DAC_data buffer_cycles 250 was 1 my_DAC_data next_structure NULL struct DAC request my_DAC_request my_DAC_request DAC_buffer my_DAC_request number of scans my DAC data 25000 was 100 my_DAC_data buffer_status BUFFER_FULL By changing the number_of_scans to 25 000 the application is instructing DAQDRIVE to output 25 000 samples to the D A channel In order to generate these 25 000 points however the application is also instructing DAQDRIVE to process the data buffer 250 times buffer_cycles 250 The result is that the 100 points contained in the data buffer will be output to the D A converter 250 times produ
180. if status 0 printf Error closing device Status code d n status return status 13 93 13 33 DaqStopRequest The DaqStopRequest halts a request that is currently armed and or triggered see DaqArmRequest and DaqTriggerRequest When DaqStopRequest is complete the request is in the same state it was in after the configuration procedure DaqAnalogInput DaqAnalogOutput DaqDigitalInput or DaqDigitalOutput procedures unsigned short DaqStopRequest unsigned short request handle request_handle This unsigned short integer variable is used to define which request is to be halted This is the value returned to the application by the configuration procedures DaqAnaloginput DaqAnalogOutput DaqDigitalInput or DaqDigitalOutput DAQDRIVE User s Manual 13 94 include daqdrive h include userdata h RRR RK KK KK II I RRR KARRI A ARR e hh I IIR RR ARI k E kk k e k e k k d Input 1000 points from the A D in background mode using interrupts SEH JEKKKKKAKKKKKKKKKKKKKKKAKKKKKKKKKKKKKAKAKKKKKKKKKKKKKAKAKKKKKKKKKKKKKKKKKKKJ unsigned short main unsigned short logical_device unsigned short request_handle unsigned short status short data_array 1000 struct ADC_request user_request struct DAQDRIVE buffer data structure Open the DAQP 16 See DaqOpenDevice RARER k k Prepare data structure for analog input KARTER Jenni Prepare the A D request structure KAKKKJ
181. ing B FILENAME DAT CHRS 0 null terminated string Furthermore Visual Basic for DOS is unable to pass the address of a string variable as a far pointer To overcome this problem the DaqOpenDevice procedure is declared differently for the Visual Basic for DOS version of DAQDRIVE DaqOpenDevice BYVAL TSRNumber AS Integer SEG LogicalDevice AS Integer BYVAL DeviceTypePtr AS Long BYVAL ConfigFilePtr AS Long DAQDRIVE User s Manual 2 17 The string variables normally found in the DaqOpenDevice command have been replaced by long integer values which contain the string s address The application program can obtain the string address using the SSEGADD function as shown in the following example V KKK KKK KK KK KA KKK KKK AKA KA KA KA KKK KA KA KA KA KA KKK KA KA KA KA KKK KKK AKA KA KA KKK KKKA KA KKK Step 1 Open the device NAKKAKAKAKAKAKK KKK KA KA KA KA KA KKK KA KA KA KA KA KKK KA KA KA KA KKK KKK AKA KA KA KKK KKKA KA KKK LogicalDevicet 0 DeviceTypeS DA8P 12B CHRS 0 ConfigFileS da8p 12b dat CHRS 0 Status DaqOpenDevice amp HF006 LogicalDevices SSEGADD DeviceType SSEGADD ConfigFile 2 4 6 4 Storing a variable s address in a data structure Another short coming of Visual Basic for DOS is its inability to easily operate on a variable s address Because of this limitation all of the variables declared as Tar pointers in the DAQDRIVE data structures have been divided in
182. ing the arm process if any of the required resources are not available Step 6 Trigger The Request After the request is armed the next step is to trigger the request and start the operation If the request specified an internal software trigger the application must now issue the trigger using DaqTriggerRequest If the request specified any of the hardware trigger sources the application may wait for the trigger event to occur or it may continue to step 7 Step 7 Wait For Completion With the operation in progress the application must wait for the request to be completed before any further action can be taken on this request If necessary the application can terminate the request using the DaqStopRequest procedure When the operation is completed or otherwise terminated any system resources allocated by the request are freed for use by other requests However the channel s specified in the request structure s channel list remain allocated to the request until the request is released by the DaqReleaseRequest procedure Step 8 Release The Configuration After the operation is complete or otherwise terminated the request may be released using DaqReleaseRequest Releasing the request frees the channel s used by the request making them available for future requests Step 9 Close The Hardware Device The final step after all operations on the hardware are complete is to close the device using DaqCloseDevice to free any remaini
183. ingleAnaloginput 3 2 Input a single sample from A D channel 0 KA unsigned short main unsigned short logical_device unsigned short status short input_value char far device_type char far config_file DAQP 16 daqp 16 dat Step 1 Initialize Hardware logical_device 0 status DaqOpenDevice DAQP amp logical_device device type config file if status 0 printf Error opening device Status code d n status exit status Step 2 Input value from channel 0 gain of 1 ER status DaqSingleAnalogInput logical_device 0 1 amp input_value if status 0 printf n nA D input error Status code d n n status else printf Channel 0 Sd n n input value Step 3 Close Hardware Device status DaqCloseDevice logical_device if status 0 printf Error closing device Status code d n status return status DaqSingleAnaloginput is a very basic interface without any allowance for multiple channels multiple input values trigger sources etc It acts as a DAQDRIVE macro defining the necessary data structures executing the analog input configuration procedure DaqAnalogInput arming the requested configuration DaqArmRequest and triggering the operation DaqTriggerRequest For users interested in learning more about DAQDRIVE s analog input interface the following example program creates the equivale
184. input for a digital trigger to be generated trigger_value is ignored for all other trigger sources Trigger selections are discussed in chapter 10 reserved3 4 This unsigned short integer array is reserved for the future expansion of DAQDRIVE For maximum compatibility the application should initialize all reserved variables to 0 IO_mode This unsigned short integer value specifies the method of data transfer clock_source DAQDRIVE Constant Value Description FOREGROUND_CPU 0 DAQDRIVE takes control of the CPU until the request is complete BACKGROUND_IRQ 1 hardware interrupts are used to gain control of the CPU and input the data FOREGROUND_DMA 2 DMA is used to input the data the CPU monitors controls the DMA operation BACKGROUND DMA 3 DMA is used to input the data interrupts are used to monitor control the DMA operation This unsigned short value selects the clock source to provide the timing for multiple point output operations DAQDRIVE Constant Value Description INTERNAL CLOCK 0 the sampling rate is generated by the on board clock circuitry EXTERNAL CLOCK 1 the sampling rate is generated from an external input clock rate This double precision value defines the clock frequency of the external clock clock rate is ignored for internal clock sources sample rate This double precision value specifies the output data rate in samples second Hz for multiple point operations reserv
185. is to allocate and configure a DAC_request structure The DAC_request structure is beyond the scope of this chapter and will not be discussed here except for the DAC_buffer and number_of_scans fields which directly relate to the data structure configuration For this example DAC_buffer is set to point to our DAQDRIVE _buffer structure and the number_of_scans is set to 500 scans 3 channels scan struct DAC_request my_DAC_request my_DAC_request DAC buffer my_DAC_request number of scans The final step is to set the BUFFER_FULL status in the buffer status field Once BUFFER_FULL is set and the request is armed the application must not modify my DAC data or output data until BUFFER_EMPTY is set or until the operation is terminated my_DAC_data buffer_status BUFFER_FULL DAQDRIVE User s Manual 9 17 9 3 4 Example 4 Using Multiple Data Buffers The purpose of this example is to use multiple data buffers to output 4 000 points each to two analog output channels The application could allocate a single 8 000 2 4000 sample buffer but for this example will allocate one 5 000 sample buffer and one 3 000 sample buffer Assuming a 12 bit D A converter operating in unipolar mode the samples are each size unsigned short unsigned short output_data0 5000 unsigned short output_datal 3000 The next step is to allocate and configure two DAQDRIVE _buffer structures The data_buffer fields are set to point to the arrays defined
186. is used to input the data the CPU monitors controls the DMA operation BACKGROUND DMA 3 DMA is used to input the data interrupts are used to monitor control the DMA operation This unsigned short value selects the clock source to provide the timing for multiple point input operations DAQDRIVE Constant Value Description INTERNAL CLOCK 0 the sampling rate is generated by the on board clock circuitry EXTERNAL CLOCK 1 the sampling rate is generated from an external input clock rate This double precision value defines the clock frequency of the external clock clock rate is ignored for internal clock sources sample rate This double precision value specifies the input data rate in samples second Hz for multiple point operations reserved4 4 This unsigned short integer array is reserved for the future expansion of DAQDRIVE For maximum compatibility the application should initialize all reserved variables to 0 number_of_scans This unsigned long integer value defines the number of times the channels specified in channel_array_ptr will be input Setting number_of_cycles 0 will cause the channels to be scanned continuously scan_event_level This unsigned long integer value defines the frequency at which scan events are reported to the application For example setting scan_event_level to 100 causes a scan event to be generated each time 100 scans are completed reserved5 8 This unsigned short
187. ked with the DAQDRIVE import library DAQDRIVE LIB installed in the DAQDRIVE WINDLL directory by the DAQDRIVE installation program This library is model independent and should work with most C compilers for Windows Three additional files are installed into the DAQDRIVE WINDLL C directory for the programmer s convenience These files contain the prototypes of the DAQDRIVE procedures the DAQDRIVE data structure definitions and the DAQDRIVE constants mentioned throughout this document These files must be included in all application programs DAQDRIVE H procedure prototypes DAQOPENW H DaqOpenDevice definition for Windows USERDATA H data structures and pre defined constants 2 5 2 1 Creating byte aligned data structures Because DAQDRIVE supports multiple languages the DAQDRIVE data structures are byte aligned packed The application program must also set structure packing to byte aligned for proper operation IMPORTANT For proper operation all application programs must be compiled using byte aligned data structures Borland C C defines structures as byte aligned by default To guarantee structures are byte aligned within the Borland C C environment select Options Compiler Code Generation then confirm the Word alignment box is not checked For byte aligned structures from the Borland C C command line use the a option DAQDRIVE User s Manual 2 23 2 5 2 2 Program optimization When selectin
188. l chan2 which the application would view as array 0 chanl sample 1 arraylll chan2 sample 1 array 2 chanl sample 2 array 3 chan2 sample 2 array 8 chanl sample 5 array 9 chan2 sample 5 Obviously as the number of channels increases it becomes more difficult to determine the correlation between the channel number and the value DAQDRIVE User s Manual 9 5 One solution to this problem is to use two dimensional arrays Re defining the array of the previous example to short array 5 2 does not change the size of the data buffer The array now appears in memory as array 0 0 arraylollll array 4 0 array 4 1 and after DAQDRIVE loads the data into the buffer the application views the data as array 0 0 chanl sample 1 arraylollll chan2 sample 1 array 1 0 chanl sample 2 array 1 1 chan2 sample 2 array 4 0 chanl sample 5 array 4 1 chan2 sample 5 In general terms the array may be defined as arraylsample number channel_number Although the previous examples only illustrated the definition of data buffers for input operations it should be noted that all DAQDRIVE requests implement the same buffer structure and therefore all output data buffers must be defined accordingly 9 6 9 2 Input Operation Examples 9 2 1 Example 1 Single Channel Analog Input An example of
189. le return status RRKKK If no errors release the request and return KAKKKJ status DaqReleaseRequest request handle return status 1 DAQDRIVE User s Manual 3 19 3 4 Digital Output DAQDRIVE provides two special purpose procedures for digital output DaqSingleDigitalOutput and DaqSingleDigitalOutputScan The intent of this section is to provide an overview of these procedures For details on the implementation of the procedures consult the alphabetical listing of commands in chapter 13 3 4 1 DaqSingleDigitalOutput One of the simplest cases of digital output is to output a single value to a single digital I O channel under CPU control DAQDRIVE provides a simplified interface for this function through the DaqSingleDigitalOutput procedure The format of this command is shown below unsigned short DaqSingleDigitaloutput unsigned short logical_device unsigned short channel_number void far output_value DaqSingleDigitalOutput outputs the value specified by output value to the digital I O channel specified by channel number on the adapter specified by logical device The following example shows the usage of DaqSingleDigitalOutput Output a single sample to digital I O channel 2 d unsigned short main unsigned short logical device unsigned short status unsigned char output value char far device type DAQ 1201 char far config file daq 1201 dat
190. may continue unsigned short DaqTriggerRequest unsigned short request_handle request_handle This unsigned short integer variable is used to define which request is to be triggered This is the value returned to the application by the configuration procedures DaqAnaloginput DaqAnalogOutput DaqDigitalInput or DaqDigitalOutput DAQDRIVE User s Manual 13 96 include daqdrive bi include userdata h JEKKAKKKAKKKKKKKKKKKKKKKAKAKKKKKKKKKKKAKAKKKKKKKKKKKKKAKAKKKKKKKKKKKKKKKKKKKJ Output 5 points to 5 digital output channels X JEKKKKKAKKKKKKKKKKKKKKKAKKKKKKKKKKKKKAKAKKKKKKKKKKKKKAKAKKKKKKKKKKKKKKKKKKKJ unsigned short main unsigned short logical_device unsigned short request_handle unsigned short status short data_array 5 struct DIGOUT_request user_request struct DAQDRIVE buffer data structure Open the device see DaqOpenDevice KKK Jenni Prepare data structure for digital output BER T x k k Prepare the digital I O request structure PER ERS Request digital output KKK request handle 0 status DaqDigitalOutput logical device amp user_request amp request_handle if status 0 printf Digital I O request error Status code d n status DaqCloseDevice logical_device exit status x Arm the request REALE status DagArmRequest request_handle if status 0 printf Arm request error Status code d n status DaqReleaseRequ
191. ment option to byte For byte aligned structures from the Borland C C or Turbo C command lines use the a option 2 10 2 4 4 2 Program optimization When selecting the optimization options for the Borland C C compiler problems may arise if the Invariant code motion option is selected and DAQDRIVE is operated in one of the background modes IRQ or DMA To disable the Invariant code motion optimization within the Borland C C environment select Options Compiler Optimizations then confirm the Invariant code motion box is not checked From the Borland C C command line make sure the Om and O2 options are not used IMPORTANT It is strongly recommended that the Invariant code motion optimization option be disabled when using the Borland C C compiler DAQDRIVE User s Manual 2 11 2 4 5 Quick Basic To generate application programs using the DAQDRIVE TSR with Quick Basic 4 5 the Quick Library DAQQB45 QLB must be loaded from the Quick Basic command line using the L option DAQQB45 QLB is installed into the DAQDRIVE TSR QB45 directory by the DAQDRIVE installation program A standard library DAQQB45 LIB is also installed in this directory for creating executable programs EXE using Quick Basic Two additional files are installed into the DAQDRIVE TSR QB45 directory for the programmer s convenience These files contain the prototypes of all the DAQDRIVE procedures the DAQDRIVE data str
192. mer circuitry The clock_rate field is unused with the internal clock source and any value provided in the clock_rate field is ignored 7 2 6 2 External Clock Setting the clock_source field to external indicates the timing for the request is provided by a signal input to the adapter as defined by the hardware device The clock_rate field must be used to define the frequency of the external clock signal in Hertz 7 4 7 2 7 Sampling Rate The sampling rate specifies the number of samples second Hz to be input from the hardware device The application specifies a desired sampling rate in the sample_rate field of the request structure On most hardware devices only a finite number of sampling rates are achievable When DaqDigitalinput configures a request the closest available sampling rate is selected and the sample_rate field is updated with the actual rate at which the data will be output 7 2 8 Number Of Scans The number_of_scans field determines the number of times the channel s specified in the channel list are processed For example to input 100 samples from a single digital input channel number_of_scans must be set to 100 To input 50 samples each from four digital input channels 200 points total number_of_scans is set to 50 7 2 9 Scan Events DAQDRIVE generates a scan event each time the number of scans specified by scan_event_level are completed For example if scan_event_level is set to 50 a scan event is gene
193. n status return status 13 91 13 32 DaqSingleDigitalOutputScan The DaqSingleDigitalOutputScan procedure provides a simplified interface for outputting a single point to multiple digital output channels The format of the command is shown below The values specified by the array output_array are output to the digital output channels specified by channel_array on the adapter defined by logical_device There is a one to one correspondence between the number of digital output channels and the number of output values Therefore array_length specifies the length of both channel_array and output_array This procedure executes the DAQDRIVE procedures DaqDigitalinput DaqArmkRequest DaqTriggerRequest and DaqReleaseRequest before returning to the calling application unsigned short DaqSingleDigitaloutputScan unsigned short logical_device unsigned short far channel array unsigned short array length void far output_array logical_device This unsigned short integer value is used to define the target hardware device This is the value returned to the application by the DaqOpenDevice command channel array This pointer specifies the address of an unsigned short integer array containing the digital output channels on logical_device to be written array_length This unsigned short integer value defines the length of channel_array and output_array output_array This void pointer specifies the address of a
194. n array containing the values to be output to the channels specified by channel_array output_array is declared as a void to allow it to point to data of any type It is the application program s responsibility to ensure the data pointed to by output_array is the correct type for the target hardware as listed in the table below Channel size in bits data type 1 to 8 bits unsigned char 9 to 16 bits unsigned short 17 to 32 bits unsigned long DAQDRIVE User s Manual 13 92 include daqdrive h include daqopenc h include userdata h include iop241 h unsigned short main unsigned short logical_device unsigned short status unsigned short channel_array 4 doi Oy eo LSA Ts short output_array 4 S07 e Ap IOS unsigned short array_length 4 char far device type IOP 241 char far config file c iop 241 iop 241 dat k Open the IOP 241 device_number 0 status DaqOpenDevice IOP241 amp logical_device device type config_file if status 0 printf Error opening configuration file Status code d n status exit status Output one value to digital output channel 3 RARER status DaqSingleDigitalOutputScan logical device channel_array array_length output_array if status 0 printf Error writing to digital output Status code d n status ZKK Close the TOP 24 KAT status DagCloseDevice logical_device
195. n by the DaqOpenDevice command channel array This pointer specifies the address of an unsigned short integer array containing the digital input channels on logical device to be input array length This unsigned short integer value defines the length of channel array and input array input array This void pointer specifies the address of an array where the values read from the digital input channels are to be stored input_array is declared as a void to allow it to point to data of any type It is the application program s responsibility to ensure the data pointed to by input_array is the correct type for the target hardware as listed in the table below Channel size in bits data type 1 to 8 bits unsigned char 9 to 16 bits unsigned short 17 to 32 bits unsigned long DAQDRIVE User s Manual 13 88 include daqdrive h include daqopenc h include userdata h include iop241 h unsigned short main unsigned short logical device unsigned short status unsigned short channel arrayl3l 3 0 6 short input_array 3 unsigned short array length 3 char far device type IOP 241 char far config_file c iop 241 iop 241 dat k Open the IOP 241 device_number 0 status DaqOpenDevice IOP241 amp logical_device device type config_file if status 0 printf Error opening configuration file Status code d n status exit status
196. n detail in chapters 5 through 8 In addition to the request structure the application must define one or more data buffer structures where the request s data is stored These data buffer structures are discussed in chapter 9 Step 4 Request The Operation The next step is to request the operation The configuration procedures serves to validate the contents of the request structure and to determine if the target hardware can support the type of operation requested If the request is not valid an error is returned and the application must redefine the request If the request is valid and the operation is supported by the hardware a request handle is issued to identify this configuration Once the request handle is issued the channel s specified in the request structure s channel list are allocated for use by this request Any other hardware resources required to execute the request timers triggers etc remain available until the request is armed Chapters 5 through 8 contain detailed descriptions of each type of DAQDRIVE request 4 2 Step 5 Arm The Request With a valid configuration requested the application must now arm the request in order to prepare the hardware for the impending trigger It is during the arm procedure DaqArmRequest that the hardware is programmed and any system resources required for the request i e IRQ levels DMA channels timers etc are allocated and assigned to the request An error will occur dur
197. nalog trigger DIGITAL_TRIGGER 3 digital value trigger trigger_mode This unsigned short integer value defines the trigger mode Trigger selections are discussed in chapter 10 DAQDRIVE Constant Value Description CONTINUOUS_TRIGGER 0 only one trigger is required to start the output operation ONE_SHOT_TRIGGER 1 a trigger is required for each output scan trigger_slope This unsigned short integer value defines the slope for TTL and analog triggers trigger_slope is ignored for all other trigger sources Trigger selections are discussed in chapter 10 DAQDRIVE Constant Value Description RISING_EDGE 0 for TTL and analog triggers only specifies a low to high transition is required FALLING_EDGE 1 for TTL and analog triggers only specifies a high to low transition is required trigger_channel This unsigned short value specifies the channel to be used as the input for the analog or digital trigger sources trigger_channel is undefined for all other trigger sources Trigger selections are discussed in chapter 10 Figure 17 Digital output request structure definition DAQDRIVE User s Manual 13 30 trigger_voltage This double precision value defines the trigger voltage level for the analog trigger trigger_voltage is ignored for all other trigger sources Trigger selections are discussed in chapter 10 trigger_value This unsigned long value defines the value required on the digital
198. ndows Borland Delphi DAQDRIVE supports applications written with Turbo Pascal for Windows version 1 5 and newer through the unit files DAQDRV W TPU and DAQDATA TPU while Borland Delphi applications are supported with the unit files DAQDRV W DCU and DAQDATA DCU The unit DAQDRV W defines the interface to the DAQDRIVE DLL functions while DAQDATA defines the DAQDRIVE data structures Pascal records and constants mentioned throughout this document All of these files are installed into the DAQDRIVE WINDLL PASCAL directory by the DAQDRIVE installation program In order to access DAQDRIVE s functions data structures and constants all Turbo Pascal for Windows and Borland Delphi application programs must include the following statement USES DAQDRV W DAQDATA 2 5 4 1 Using other Turbo Pascal for Windows Delphi versions When using versions other than Turbo Pascal for Windows 1 5 or Borland Delphi 1 0 the user must create new unit files by re compiling the source files DAQDRV W PAS and DAQDATA PAS These files are also installed into the DAQDRIVE WINDLL PASCAL directory by the DAQDRIVE installation program 2 5 4 2 Turbo Pascal for Windows and floating point math The Turbo Pascal for Windows floating point emulation library only supports variables of type real To use the single and double precision variables required by DAQDRIVE the 8087 floating point math mode must be enabled by selecting Options Compiler 08x87 code or by de
199. ned short status short data_array 1000 struct ADC_request user_request struct DAQDRIVE buffer data structure Open the device see DaqOpenDevice KARI Prepare data structure for analog input HERR L JEKKKKKAKKKKKKKKKKKKKKKAKKKKKKKKKKKAKAKAKKKKKKKKKKKAKAKKKKKKKKKKKKKKKKKKKKJ put data in data array data array is 1000 points long XT next_structure NULL no more structures SE JEKKAKKKAKKKKKKKKKKKKKKAKAKKKKKKKKKKKKKAKKKKKKKKKKKKKKAKAKKKKKKKKKKKKKKKKKKJ data structure data buffer data array data structure buffer length 1000 data_structure next_structure NULL Jenni Prepare the A D request structure EA ERY BRR KK KK KK III I RRR RR RRA A ARR ARIA IIR E e II IA k kk k k e channel list is in channel num gain list is in gain settings SE channel amp gain array length is 2 use data_structure for data SE trigger source is internal trigger mode is continuous XI input using IRQs in background use internal clock ay sample at 1 KHz scan channel list 500 times ay do not signal buffer scan events do not implement time out XI JEKKAKKKAKKKKKKKKKKKKKKAKAKKKKKKKKKKKK e IRR E I I IA k k k k k kk k k d user_request channel_array_ptr channel num user_request gain_array_ptr gain_settings user_request array_length EK user_request ADC_buffer data_structure user_request trigger_source INTERNAL_TRIGGER user request trigger mode CONT INUOUS_TRIGGER user request 10 mode BACKGROUND
200. nela once user_request scan_event_level 0 no scan events user_request calibration NO_CALIBRATION no calibration E user request timeout interval 0 disable time out user_request request_status 0 initialize status S request_handle 0 new request ay status Daq Analogoutput logical_device amp user_request amp request_handle p if status 0 printf D A request error Status code d n status DaqCloseDevice logical_device exit status Step 4 Arm the Request status DaqArmRequest request_handle if status 0 printf Arm request error Status code sd n status DaqReleaseRequest request_handle DaqCloseDevice logical_device exit status Step 5 Wait for completion or error ERE printf n n n Waiting for trigger event_mask COMPLETE_EVENT RUNTIME_ERROR_EVENT while user_request request_status amp event mask 0 wait for event XI 1f user_request request_status amp COMPLETE_EVENT 0 printf n n D A Output Request complete n else printf Run time error Operation aborted n DaqReleaseRequest request_handle DaqCloseDevice logical_device exit status xxx Step 6 Release the Request status DaqReleaseRequest request_handle if status 0 printf Could not release configuration Status code sd n status exit status while cha
201. neral the foreground modes provide the highest data transfer rates at the expense of requiring 100 of the CPU time In contrast background mode operations generally provide lower data transfer rates while allowing the CPU to perform other tasks DAQDRIVE User s Manual 5 3 5 2 5 1 Foreground CPU mode This mode uses the CPU to input the data from the hardware device From the moment the request is triggered DAQDRIVE uses all of the CPU time and will not return control to the application program until the request is completed or otherwise terminated 5 2 5 2 Background IRQ mode This mode uses interrupts generated by the hardware device to gain control of the CPU to input the data to the hardware device DAQDRIVE does not require all of the CPU time in this mode and returns control of the CPU to the application after the request is triggered 5 2 5 3 Foreground DMA mode This mode uses the DMA controller to input the data from the hardware device while using the CPU to monitor and control the DMA operation From the moment the request is triggered DAQDRIVE uses all of the CPU time and will not return control to the application program until the request is completed or otherwise terminated 5 2 5 4 Background DMA mode This mode uses the DMA controller to input the data from the hardware device while using interrupts generated by the hardware device to gain control of the CPU to monitor and control the DMA operation DAQDRIVE d
202. ng resources used by that device System integrity can not be guaranteed if the application program exits without closing the hardware device DAQDRIVE User s Manual 4 3 This Page Intentionally Left Blank 4 4 5 A D Converter Requests In chapter 3 some special purpose procedures were presented to help the user get familiar with DAQDRIVE s A D converter interface The key to understanding and utilizing DAQDRIVE however is to understand its request structures This chapter will present the analog input request structure and provide examples to illustrate how this structure is configured for some common applications 51 DaqAnalogInput DaqAnaloginput is DAQDRIVE s A D converter interface Any analog input operation is possible with the proper configuration of the request structure The format of the command is shown below unsigned short DaqAnaloginput unsigned short logical device struct ADC_request far user_request unsigned short far request handle DaqAnalogInput performs the configuration portion of an analog input request For a new configuration the application program sets request_handle to 0 before calling DaqAnalogInput DaqAnalogInput then analyzes the data structure specified by user_request to determine if all of the parameters are valid and if the requested operation can be performed by the device specified by logical_device If the requested operation is valid DaqAnaloginput assigns reques
203. ning device Status code d n status exit status Step 2 Input data Prepare Buffer Structure my_data data_buffer input_data set pointer to data array kif my_data buffer_length 1000 number of points in buffer my_data next_structure NULL indicate no more buffers XI my_data buffer_status BUFFER_EMPTY indicate buffer empty ready Prepare the A D request structure KKR user_request channel_array_ptr channel array of channels K user_request gain_array_ptr gain array of gains i user request array length 5 number of channels user_request ADC_buffer smy data pointer to data SE user request trigger source INTERNAL TRIGGER internal trigger wh user request trigger mode CONTINUOUS_TRIGGER input all points ta user request 10 mode BACKGROUND_IRQ background mode SZ user_request clock_source INTERNAL CLOCK use on board clock user_request sample_rate 100 100 Hz input rate k user_request number_of_scans 200 200 scans user_request scan_event_level 0 no scan events user_request calibration NO_CALIBRATION no calibration i user request timeout interval 0 disable time out user_request request_status 0 initialize status E 12 5 if status 0 printf A D request error Status code d n status DaqCloseDevice logical_device exit status Step 3
204. nnel 99 Step 7 Close Hardware Device Re status DaqCloseDevice logical device if status 0 printf Error closing device Status code d n status return status DAQDRIVE User s Manual 12 14 12 2 3 Example 3 This example outputs 1000 cycles of a 60 Hz sinewave to D A channel 0 The sinewave contains 60 points per cycle Output a sinewave to D A channel 0 include lt stdlib h gt include lt stdio h gt include lt math h gt include userdata h include daqdrive h include daqopenc h include dagqp h When defined global or static structures are KEK automatically initialized to all 0 BERS struct DAQDRIVE buffer my_data struct DAC_request user_request unsigned short main unsigned short logical device unsigned short request handle unsigned short channel unsigned short status unsigned short i short sinewave 60 unsigned long event mask char far device type DAQP 208 char far config file daqp 208 dat Step 1 Initialize Hardware logical_device 0 status DaqOpenDevice DAQP amp logical_device device type config file if status 0 printf Error opening device Status code d n status exit status Step 2 Get D A channel and output values BERT channel 0 for i 0 i lt 60 i sinewave i short 2047 sin 2 3 1416 i 60 Step 3 Out
205. nnel number between 0 and 7 or 99 to quit scanf d amp channel if channel 99 printf n nEnter the output value between 2048 and 2047 mi scanf Sd amp output_value Step 3 Output value to channel Z Step 4 Close Hardware Device GE status DagCloseDevice logical_device if status 0 printf Error closing device Status code d n status return status l status DaqSingleAnalogOutput logical device channel amp output_value if status 0 printf Ann D A output error Status code sd n n status printf Press lt ESC gt to continue n while getch Oxlb while channel 99 DAQDRIVE User s Manual 12 12 12 2 2 Example 2 This example outputs a single value to a single D A channel using a TTL trigger Output a single point to a single D A channel on an external trigger ART include lt graph h gt include lt stdlib h gt include lt stdio h gt include userdata h include daqdrive h include daqopenc h include da8p 12 h When defined global or static structures are aT automatically initialized to all 0 REX struct DAQDRIVE buffer my_data struct DAC_request user_request unsigned short main unsigned short logical device unsigned short request handle unsigned short status unsigned short channel short output_value unsigned long event_mask char
206. nnot be executed because the request has not been armed Make sure the DagArmRequest procedure executed successfully Invalid procedure call for a request that is armed The procedure cannot be executed because the request has been armed The request may be removed from the arm state by executing the DaqStopRequest procedure Trigger command invalid with specified trigger source The DaqTriggerRequest procedure was executed on a request that was not configured for a software trigger This is not a critical error and the application program may continue 14 5 800 1000 1050 1100 1101 1150 1160 1280 Invalid re configuration request The re configuration request can not be processed because the channel list was modified All parameters except the channel list may be modified by a re configuration request To modify the channel list the request must be released DaqReleaseRequest and a new configuration must be requested Requested function not supported by target hardware The requested operation can not be performed on the target hardware Consult the target hardware s appendix in the DAQDRIVE User s Manual Supplement to determine which parameter s are not supported by the adapter Invalid operation in multi user mode The procedure could not be executed because more than one application is currently operating on the adapter This error is generally reported by procedures that effect the state of the hard
207. nput mode 0x0002 When set to 1 this bit indicates the digital I O channel is configured for output mode 0x0003 When both bits are set to 1 the digital I O channel can operate in input or output mode bi directional operation Figure 21 Digital I O configuration structure definition DAQDRIVE User s Manual 13 50 include daqdrive bi include userdata h include iop241 h unsigned short main unsigned short logical_device unsigned short digio_device unsigned short status struct digio_configuration digio_info char far device_type IOP 241 char far config_file c iop 241 iop 241 dat k Open the IOP 241 see DaqOpenDevice KKKKKJ Get a digital I O channel configuration Sei digio_device 0 status DaqGetDigioCfgInfo logical_device digio_device amp digio_info if status 0 printf Error getting digital configuration Status code d n status exit status Display the digital I O configuration KERR printf Digital I O channel Sd digio device printf is d bits wide n digio_info data_size switch digio_info io_mode case 1 printf and is configured for input mode n break case 2 printf and is configured for output mode n break case 3 printf and is configured for bi directional operation n break 13 51 13 16 DaqGetExpCfgInfo DaqGetExpCfginfo returns
208. nsigned short integer value defines the source of the D A s reference voltage reference_voltage This floating point value specifies the value of the D A s reference voltage gain_array_length This unsigned short integer value specifies the number of available D A gain settings The application must allocate an array of length gain_array_length before executing DaqGetDAGaininfo calibration_modes This unsigned short integer value specifies the supported calibration modes of the D A sub system Value Description Ox0001 When set to 1 this bit indicates the D A supports auto calibration Ox0002 When set to 1 this bit indicates the D A supports auto zero Figure 19 D A converter configuration structure definition 13 43 Quatech Inc DAQDRIVE User s Manual 13 44 This page intentionally left blank 13 45 13 13 DaqGetDAGainInfo DaqGetDAGainInfo returns an array of the gain settings supported by the D A converter specified by DAC_device on the adapter specified by logical_device The length of the array is determined by the gain_array_length variable returned by the DaqGetDACfgInfo command unsigned short DaqGetDAGainInfo unsigned short logical_device unsigned short DAC_device float far gain_array logical_device This unsigned short integer value is used to define the target hardware device This is the value returned to the application by the DaqOpenDe
209. nt Value Description INTERNAL CLOCK 0 the sampling rate is generated by the on board clock circuitry EXTERNAL CLOCK 1 the sampling rate is generated from an external input clock rate This double precision value defines the clock frequency of the external clock clock rate is ignored for internal clock sources sample rate This double precision value specifies the input data rate in samples second Hz for multiple point operations reserved4 4 This unsigned short integer array is reserved for the future expansion of DAQDRIVE For maximum compatibility the application should initialize all reserved variables to 0 number_of_scans This unsigned long integer value defines the number of times the channels specified in channel_array_ptr will be input Setting number_of_cycles 0 will cause the channels to be scanned continuously scan_event_level This unsigned long integer value defines the frequency at which scan events are reported to the application For example setting scan_event_level to 100 causes a scan event to be generated each time 100 scans are completed reserved5 8 This unsigned short integer array is reserved for the future expansion of DAQDRIVE For maximum compatibility the application should initialize all reserved variables to 0 Figure 11 continued Analog input request structure definition 13 7 calibration This unsigned short integer value specifies the t
210. nt of the DaqSingleAnaloginput procedure DAQDRIVE User s Manual 3 3 unsigned short MySingleAnalogInput unsigned short logical_device unsigned short channel_number float gain_setting void far input value struct ADC_request my_request struct DAQDRIVE buffer my data unsigned short request handle unsigned short status Construct the request structure FREAK my_request channel_array_ptr amp channel_number my_request gain_array_ptr amp gain_setting my_request array_length 1 my request ADC buffer Em data my request trigger source INTERNAL TRIGGER my request 10 mode FOREGROUND CPU my request number of scans 1 my_request scan_event_level 0 my_request calibration NO_CALIBRATION my_request timeout_interval 0 my_request request_status NO_EVENTS Construct the data buffer structure KKK my data data buffer void huge input value my data buffer length 1 my_data next_structure NULL my_data buffer_status BUFFER_EMPTY Execute the request LEERY request_handle 0 status DaqAnalogInput logical device my_request amp request_handle if status 0 return status x Tf no errors arm the request ARE AY status DagArmRequest request_handle if status 0 DaqReleaseRequest request_handle return status Jenni If no errors software trigger the request REP ERT status DaqTrig
211. o 0 array_length This unsigned short integer value defines the number of channels contained in the array pointed to by channel_array_ptr digio_buffer This pointer defines the address of the first data buffer structure Data buffer structures are discussed in chapter 9 reserved2 4 This unsigned short integer array is reserved for the future expansion of DAQDRIVE For maximum compatibility the application should initialize all reserved variables to 0 trigger_source This unsigned short integer value specifies the trigger source for this request Trigger selections are discussed in chapter 10 DAQDRIVE Constant Value Description INTERNAL_TRIGGER 0 internal software trigger TTL_TRIGGER 1 TTL trigger ANALOG_TRIGGER 2 analog trigger DIGITAL_TRIGGER 3 digital value trigger trigger_mode This unsigned short integer value defines the trigger mode Trigger selections are discussed in chapter 10 DAQDRIVE Constant Value Description CONTINUOUS_TRIGGER 0 only one trigger is required to start the output operation ONE_SHOT_TRIGGER 1 a trigger is required for each output scan trigger_slope This unsigned short integer value defines the slope for TTL and analog triggers trigger_slope is ignored for all other trigger sources Trigger selections are discussed in chapter 10 DAQDRIVE Constant Value Description RISING_EDGE 0 for TTL and analog triggers only specifies a low to
212. oes not require all of the CPU time in this mode and returns control of the CPU to the application after the request is triggered 5 2 6 Clock Sources The clock_source field is used to define the source of the timing signal for requests acquiring multiple samples 5 2 6 1 Internal Clock When the clock source field is set for an internal clock the timing for the request is provided by the adapter s on board timer circuitry The clock_rate field is unused with the internal clock source and any value provided in the clock_rate field is ignored 5 2 6 2 External Clock Setting the clock_source field to external indicates the timing for the request is provided by a signal input to the adapter as defined by the hardware device The clock_rate field must be used to define the frequency of the external clock signal in Hertz 5 4 5 2 7 Sampling Rate The sampling rate specifies the number of samples second Hz to be input from the hardware device The application specifies a desired sampling rate in the sample_rate field of the request structure On most hardware devices only a finite number of sampling rates are achievable When DaqAnaloginput configures a request the closest available sampling rate is selected and the sample_rate field is updated with the actual rate at which the data will be input 5 2 8 Number Of Scans The number_of_scans field determines the number of times the channel s specified in the channel list are proce
213. ogical_device if status 0 printf Error closing device Status code d n status return status H 13 59 13 19 DaqGetTimerCfgInfo DaqGetTimerCfgInfo returns the configuration of the counter timer channel specified by timer_device on the adapter specified by logical_device unsigned short DaqGetTimerCfgInfo unsigned short logical_device unsigned short timer_device struct timer_configuration far timer_info logical_device This unsigned short integer value is used to define the target hardware device This is the value returned to the application by the DaqOpenDevice command timer device This unsigned short integer value is used to select one of the counter timer channels on the target hardware device timer info This structure pointer defines the address of a counter timer configuration structure where the configuration of the specified counter timer channel will be stored struct timer_configuration unsigned short data_size double internal_clock_rate double min_rate double max_rate data_size This unsigned short integer value specifies the size of the counter timer channel in bits internal_clock_rate This double precision floating point value specifies the frequency of the on board clock input to the counter timer min_rate This double precision floating point value specifies the minimum output frequency of the counter timer when using t
214. ogoutput unsigned short logical device unsigned short channel number void far output value logical device This unsigned short integer value is used to define the target hardware device This is the value returned to the application by the DaqOpenDevice command channel_number This unsigned short integer value is used to specify which D A converter channel on logical_device is to receive the output data output_value This void pointer specifies the address of the data to be output to the D A converter output_value is declared as a void to allow it to point to data of any type It is the application program s responsibility to ensure the data pointed to by output_value is the correct type for the target hardware as listed in the table below Resolution Configuration data type 1 to 8 bits unipolar unsigned char bipolar signed char 9 to 16 bits unipolar unsigned short bipolar signed short 17 to 32 bits unipolar unsigned long bipolar signed long DAQDRIVE User s Manual 13 82 include daqdrive bi include daqopenc h include userdata h include daql200 h unsigned short main unsigned short logical_device unsigned short status unsigned short DAC_channel short output_value char far device type DAQ 1201 char far config_file c daq 1201 daq 1201 dat k Open the DAQ 1201 logical_device 0 status DaqOpenDevice DA
215. on programs varies with the application language The following sections describe the steps required to load the TSRs into memory and generate an application in each of the supported languages 2 4 1 Loading The TSRs Into Memory The DAQDRIVE installation program installs the TSR driver into the DAQDRIVE TSR directory The first step in creating applications which use the DAQDRIVE TSR is to load the driver into memory using the command line DAQDRIVE In this mode DAQDRIVE searches software interrupts 60H through 64H for an available interrupt If an unused interrupt is located DAQDRIVE takes control of this interrupt and displays a message indicating the installation was successful and which software interrupt is being used If there are no available interrupts in this range an error message is displayed and the DAQDRIVE TSR is not installed If the user wants to control the software interrupt number or if all of the software interrupts between 60H and 64H are used the user may specify a software interrupt with the following command line DAQDRIVE I interrupt where interrupt specifies the software interrupt number in hexadecimal format If the user specified interrupt is not available an error message is displayed and the DAQDRIVE TSR is not installed Examples DAQDRIVE 1 63 installs DAQDRIVE on interrupt 63H DAQDRIVE I 4F installs DAQDRIVE on interrupt 4FH DAQDRIVE User s Manual 2 7 DAQDRIVE I b9 in
216. onfiguration Status code sd n status exit status Step 7 Close Hardware Device EKR status DagCloseDevice logical device if status 0 printf Error closing device Status code d n status return status DAQDRIVE User s Manual 12 8 12 1 5 Example 5 This example inputs 100 000 samples from A D channel 0 and stores the data in a disk file Input 100 000 samples from A D channel 0 and write to disk EKR lt conio h gt lt graph h gt lt stdlib h gt lt stdio h gt includ includ includ includ ooo O userdata h daqdrive h daqopenc h dagp h includ includ includ includ ooo O When defined global or static structures are RHR automatically initialized to all 0 Zeg struct DAQDRIVE buffer my_data 4 struct ADC_request user_request unsigned short main unsigned short logical device unsigned short request handle unsigned short channel unsigned short status unsigned short current_buffer unsigned short i short buffer 4 1000 float gain unsigned long event mask char far device type DAQP 208 char far config file daqp 208 dat FILE output file Step 1 Initialize Hardware logical_device 0 status DaqOpenDevice DAQP amp logical_device device type config file if status 0 printf Error opening device Status code d n status exit status
217. operation is to write 100 samples to a single D A channel To perform this operation the application must first allocate enough memory to hold 100 samples Assuming a 12 bit D A converter operating in bipolar mode the samples are each size short Therefore the memory allocation may be done as simply as short output_data 100 The next step is to allocate and configure a DAQDRIVE _buffer structure data_buffer is set to point to the array defined above Its length is 100 points the buffer will be processed only once buffer_cycles 1 and there are no other structures so next_structure is set to NULL struct DAQDRIVE _buffer my_DAC_data my_DAC_data data_buffer output_data my_DAC_data buffer_length 100 my_DAC_data buffer_cycles 1 my_DAC_data next_structure NULL The next step is to allocate and configure a DAC_request structure The DAC_request structure is beyond the scope of this chapter and will not be discussed here except for the DAC_buffer and number_of_scans fields which directly relate to the data structure configuration For this example DAC_buffer is set to point to our DAQDRIVE _buffer structure and the number_of_scans is set to 100 scans 1 channel scan struct DAC request my DAC request my DAC request DAC buffer my_DAC_request number of scans my DAC data 100 The final step is to set the BUFFER_FULL status in the buffer status field Once BUFFER_FULL is set and the request is armed the appl
218. ort DaqFreeMemory unsigned short memory_handle void far memory pointer memory handle This unsigned short integer specifies the handle of the allocated memory block This is the value returned by the DaqAllocateMemory procedure memory pointer This void pointer specifies the starting address of the allocated memory block Thisis the value returned by the DaqAllocateMemory procedure DAQDRIVE User s Manual 13 34 include daqdrive bi include userdata h JEKKAKKKAKKKKKKKKKKKKK e hh KKKKKKKKKK KKK KA KKKKKKKKKAKAKAKKKKKKKKKKKKKKKKKKJ Input 5000 points each from 2 analog input channels E JEKKKKKAKKKKKKKKKKKKKKAKAKKKKKKKKKKKK e hh k e A A e e A AE e e k hh IIIA k k k k k k k d unsigned short main unsigned short logical_device unsigned short request_handle unsigned short channel_num 2 float gain_settings 2 unsigned long memory_size unsigned short memory_handle void far memory_pointer unsigned short status n struct ADC_request user_request struct DAQDRIVE buffer data_structure Open the device see DaqOpenDevice REPRE L k Allocate memory for the input data LER ERS 5000 samples channel 2 channels 2 bytes sample KERKERS memory size 5000 2 sizeof short status DaqAllocateMemory memory_size amp memory_handle amp memory_pointer if status 0 printf Error allocating data buffer Status code d n status DaqCloseDevice logical_d
219. ple 1 DC Voltage Level Output Purpose Output a single value to each of three analog output channels struct struct KKK KK KKK KK unsigned short channel_list unsigned short output valuesil my request Channel array ptr my_request array_length my request DAC buffer my request trigger source my_request IO mode FOREGROUND_CPU my_request number_of_scans my_request scan_event_level my_request calibration my_request timeout_interval my_request request_status my_data data_buffer my_data buffer_status 4 0 1 1024 0 512 DAC_request my_request DAQDRIVE buffer my_data Construct the request structure BER EK channel_list 3 my data INTERNAL TRIGGER 1 0 NO_CALIBRATION 0 NO_EVENTS Construct the data buffer structure ERAT output_values my_data buffer_length 3 my_data buffer_cycles 1 my_data next_structure NULL BUFFER_FULL Variations on example 1 To change the number of channels from three to five re define channel_list and output_values then set my_request array_length 5 my_data buffer_length 5 To change the trigger mode to a TTL trigger set my_request trigger_source TTL_TRIGGER my_request trigger_slope RISING_EDGE To enable calibration for the request set my_request calibration AUTO_CALIBRATE or my_request calibration AUTO_ZERO or my_request calibration AUTO_CALIBRATE AUTO_ZERO
220. put If the configuration is successful request_handle will be assigned a unique non zero value by the DaqAnalogInput procedure If the application modifies a previously configured request the application must call DaqAnaloginput using the previously assigned request_handle All parameters except the channel list may be modified using a reconfiguration request To modify the channel list the present request must be released DaqReleaseRequest and a new configuration requested DAQDRIVE User s Manual 13 4 T ADC_request unsigned short far channel_array ptr float far gain_array ptr unsigned short reserved1 4 unsigned short array_length struct DAQDRIVE buffer far ADC_buffer unsigned short reserved2 4 unsigned short trigger source unsigned short trigger mode unsigned short trigger_slope unsigned short trigger channel double trigger voltage unsigned long trigger value unsigned short reserved3 4 unsigned short TO mode unsigned short clock_source double clock_rate double sample rate unsigned short reserved4 4 unsigned long number_of_scans unsigned long scan event level unsigned short reserved5 8 s s 1 nn Nn unsigned short calibration unsigned short timeout_interval unsigned long request status Ve Figure 10 Analog input request structure IMPORTANT 1 Once the request is armed using DagArmRequest the only field the application can modify is
221. put data Prepare Buffer Structure my_data data_buffer sinewave set pointer to output data SCH my_data buffer_length 60 number of points in buffer kj my_data buffer_cycles 1000 1000 cycles through buffer ay my_data next_structure NULL indicate no more buffers ay my_data buffer_status BUFFER_FULL indicate buffer full ready X Prepare the D A request structure KKK user request channel array ptr amp channel array of channels SCH user_request array_length 1 number of channels ki user request DAC buffer amp my_data pointer to data I user request trigger source INTERNAL TRIGGER internal trigger kj user request trigger mode CONTINUOUS_TRIGGER output all points Ki user request 10 mode BACKGROUND_IRQ background mode ty user_request clock_source INTERNAL CLOCK use on board clock 12 15 user_request number_of_scans 601 10001 60000 scans user_request scan_event_level 0 no scan events user_request calibration NO_CALIBRATION no calibration S user request timeout interval 0 disable time out user_request request_status 0 initialize status L request_handle 0 new request Ke status DagAnalogOutput logical device amp user_request amp request_handle if status 0 printf D A request error Status code Sd n status DaqCloseDevice logical_device exit status
222. put procedure DAQDRIVE User s Manual 3 15 unsigned short MySingleDigitalInput unsigned short logical device unsigned short channel_number void far input value struct digio_request my_request struct DAQDRIVE buffer my_data unsigned short request_handle unsigned short status Construct the request structure TKN my_request channel_array_ptr amp channel_number my_request array_length 1 my_request digio_buffer amp my_data my request trigger source INTERNAL TRIGGER my request 10 mode FOREGROUND CPU my request number of scans 1 my_request scan_event_level 0 my_request timeout_interval 0 my_request request_status NO_EVENTS Construct the data buffer structure KR my data data buffer void huge input value my data buffer length 1 my_data next_structure NULL my_data buffer_status BUFFER_EMPTY Execute the request KERERE request_handle 0 status DaqDigitalInput logical device my_request amp request_handle if status 0 return status x If no errors arm the request KAKKKJ status DagArmRequest request handle if status 0 DaqReleaseRequest request_handle return status Jenni If no errors software trigger the request KKK status DaqTriggerRequest request handle if status 0 DaqStopRequest request_handle DaqReleaseRequest request_handle return status JAKAKA If no
223. put_values 500 NULL BUFFER_EMPTY my_data data_buffer my_data buffer_length my_data next_buffer my_data buffer_status Variations on example 2 1 To change the number of points from 500 to 650 re define input valuesi and then set my_request number_of_scans 650 my_data buffer_length 650 2 To notify the application every time 100 scans are complete set my_request scan_event_level 100 DAQDRIVE User s Manual 7 7 This page intentionally left blank 8 Digital Output Requests In chapter 3 some special purpose procedures were presented to help the user get familiar with DAQDRIVE s digital output interface The key to understanding and utilizing DAQDRIVE however is to understand its request structures This chapter will present the digital output request structure and provide examples to illustrate how this structure is configured for some common applications 8 1 DaqDigitalOutput DaqDigitalOutput is DAQDRIVE s digital output interface Any digital output operation is possible with the proper configuration of the request structure The format of the command is shown below unsigned short DaqDigitaloOutput unsigned short logical device struct digio_request far user_request unsigned short far request_handle DaqDigitalOutput performs the configuration portion of a digital output request For a new configuration the application program sets request_handle to 0 before calling Da
224. qDigitalOutput DaqDigitalOutput then analyzes the data structure specified by user_request to determine if all of the parameters are valid and if the requested operation can be performed by the device specified by logical_device If the requested operation is valid DaqDigitalOutput assigns request_handle a unique non zero value This request handle is used to identify this request in all future operations If the application program modifies the contents of user_request after executing DaqDigitalOutput the structure must be verified again To request re verification of a previously approved request the application executes DaqDigitalOutput with request_handle set to the value returned by DaqDigitalOutput when the request was first approved All parameters except the channel list may be modified after the initial configuration To modify the channel list the existing request must be released using DaqReleaseRequest and a new configuration requested DAQDRIVE User s Manual 8 1 8 2 The Digital Output Request Structure The power of DaqDigitalOutput lies in the application s ability to modify a single data structure and execute a single procedure to perform multiple digital output operations The elements of the digital output request structure are discussed on the following pages ae digio_request unsigned short far channel_array ptr unsigned short reserved1 4 unsigned short array_length struct DAQDRIVE buffer far digio_b
225. que non zero value This request handle is used to identify this request in all future operations If the application program modifies the contents of user_request after executing DaqDigitalinput the structure must be verified again To request re verification of a previously approved request the application executes DaqDigitalinput with request_handle set to the value returned by DaqDigitalInput when the request was first approved All parameters except the channel list may be modified after the initial configuration To modify the channel list the existing request must be released using DaqReleaseRequest and a new configuration requested DAQDRIVE User s Manual 7 1 7 2 The Digital Input Request Structure The power of DaqDigitalInput lies in the application s ability to modify a single data structure and execute a single procedure to perform multiple digital input operations The elements of the digital input request structure are discussed on the following pages fe digio_request unsigned short far channel_array ptr unsigned short reserved1 4 unsigned short array_length struct DAQDRIVE buffer far digio_buffer unsigned short reserved2 4 unsigned short trigger source unsigned short trigger mode unsigned short trigger_slope unsigned short trigger channel double trigger_voltage unsigned long trigger value unsigned short reserved3 4 unsigned short TO mode unsigned short clock source double clock rate
226. quest printf Acquiring data This will take 100 status DaqTriggerRequest request_handle if status 0 printf Trigger request error DaqReleaseRequest request_handle DaqCloseDevice logical device fclose output file exit status Step 6 Wait for completion or error current_buffer 0 event mask COMPLETE EVENT do if my_data current_buffer buffer_status for i i lt 1000 0 i my datalcurrent bufferl buffer status Status code my datal131 data buffer amp buffer 3 0 set pointer to data array my_data 3 buffer_length 1000 number of points in buffer my_data 3 next_structure amp my_data 0 point to next buffer my_data 3 buffer_status BUFFER_EMPTY buffer empty ready Prepare the A D request structure KR user_request channel_array_ptr amp channel array of channels user_request gain_array_ptr amp gain array of gains user_request array_length 1 number of channels user_request ADC_buffer amp my_data 0 pointer to data user_request trigger_source INTERNAL_TRIGGER internal trigger user_request trigger_mode CONTINUOUS_TRIGGER input all points user request 10 mode BACKGROUND TRO background mode user_request clock_source INTERNAL_CLOCK use on board clock user_request sample_rate 1000 1 KHz input rate user_request number_of_scans 100000 100000 scans user_request scan_event_level 0
227. quest my_request struct DAQDRIVE buffer my data unsigned short request handle unsigned short status Construct the request structure KE my_request channel_array_ptr channel array my request array length array length my request digio buffer amp my_data my_request trigger_source INTERNAL_TRIGGER my_request 1I0O_mode FOREGROUND_CPU my_request number_of_scans 1 my_request scan_event_level 0 my_request timeout_interval 0 my_request request_status NO_EVENTS Construct the data buffer structure KA my data data buffer void huge output_array my_data buffer_length array_length my_data buffer_cycles 1 my_data next_buffer NULL my_data buffer_status BUFFER FULL Execute the request KKK request handle 0 status DaqDigitalOutput logical device my request amp request_handle if status 0 return status Tf no errors arm the request ERSE S status DaqArmRequest request_handle if status 0 DaqReleaseRequest request_handle return status Jenni If no errors software trigger the request AER ER status DaqTriggerRequest request_handle if status 0 DaqStopRequest request_handle DaqReleaseRequest request_handle return status RRKKK If no errors release the request and return KAKKKJ status DaqReleaseRequest request handle return status DAQDRIVE User s Manual 3 25 3 26 4 Pe
228. quest_status NO_EVENTS Construct the data buffer structure KA input values 3 NULL BUFFER_EMPTY my_data data_buffer my_data buffer_length my_data next_structure my_data buffer_status Variations on example 1 1 To change the number of channels from three to eight re define channel_list and input_values then set my_request array_length 8 my_data buffer_length 8 2 To change the trigger mode to a TTL trigger set my_request trigger_source TTL_TRIGGER my_request trigger_slope RISING_EDGE 3 To enable a time out if no data is available after 5 seconds set my request timeout interval 5 7 6 7 3 2 Example 2 Multiple Value Input Purpose Input 500 points from a single digital input channel at 1 second intervals unsigned short channel_number unsigned char input_values 500 struct digio_request my_request struct DAQDRIVE buffer my_data Construct the request structure RAKI gchannel number 1 my data TTL_TRIGGER RISING_EDGE BACKGROUND_IRQ INTERNAL_CLOCK p my_request channel_array_ptr my_request array_length my_request digio_buffer my_request trigger_source my_request trigger_slope my_request IO_mode my_request clock_source my_request sample_rate L my_request number_of_scans 500 my_request scan_event_level 0 my_request timeout_interval 0 my_request request_status NO EVENTS Construct the data buffer structure RAAT in
229. r the request is triggered 8 2 6 Clock Sources The clock_source field is used to define the source of the timing signal for requests containing multiple data values 8 2 6 1 Internal Clock When the clock source field is set for an internal clock the timing for the request is provided by the adapter s on board timer circuitry The clock_rate field is unused with the internal clock source and any value provided in the clock_rate field is ignored 8 2 6 2 External Clock Setting the clock_source field to external indicates the timing for the request is provided by a signal input to the adapter as defined by the hardware device The clock_rate field must be used to define the frequency of the external clock signal in Hertz 8 4 8 2 7 Sampling Rate The sampling rate specifies the number of samples second Hz to be output to the hardware device The application specifies a desired sampling rate in the sample_rate field of the request structure On most hardware devices only a finite number of sampling rates are achievable When DaqDigitalOutput configures a request the closest available sampling rate is selected and the sample rate field is updated with the actual rate at which the data will be output 8 2 8 Number Of Scans The number_of_scans field determines the number of times the channel s specified in the channel list are processed For example to output 100 samples to a single digital output channel number_of_scans mus
230. r_request request_status NO_EVENTS Jenni Indicate data buffer ready for input KKKKKJ data structure buffer status BUFFER EMPTY Request digital input ERREF f request_handle 0 status DaqDigitalInput logical device amp user_request amp request_handle XL I St SI SC XL 13 27 13 8 DaqDigitalOutput DaqDigitalOutput is DAQDRIVE s generic digital output interface DaqDigitalOutput does not configure any hardware but acts simply to confirm that all parameters are valid and that the type of operation requested is supported by the target hardware unsigned short DaqDigitalOutput unsigned short logical device struct digio_request far user_request unsigned short far request handle logical device This unsigned short integer value is used to define the target hardware device This is the value returned to the application by the DaqOpenDevice command user_request This structure pointer defines the address of a digital I O request structure containing the desired configuration information for this operation This structure is discussed in detail on the following pages request_handle This unsigned short integer pointer is used to identify this digital output request For a new configuration request_handle is set to 0 by the application before calling DaqDigitalOutput If the configuration is successful request_handle will be assigned a unique non zero value by
231. racter array string which describes the hardware device to be opened The target hardware s appendix of the DAQDRIVE User s Manual Supplement contains the valid settings for device_type config_file This pointer defines the starting address of a character array string which defines the name of the DAQDRIVE configuration file to be used This character string must contain the drive path filename and extension of the desired configuration file DAQDRIVE User s Manual 13 70 include daqdrive h include dagqopent h include userdata h unsigned short main unsigned short logical_device unsigned short status unsigned short TSR number 0xf005 char far device type DAQP 16 char far config_file c daqp 16 dagp 16 dat Open the DAQP 16 logical_device 0 status DaqOpenDevice TSR_number amp logical_device device type config file if status 0 printf Error opening configuration file Status code d n status exit status T Perform any DAQP 16 operations here Zens LKK Close the bAGOp IG AKRAKJ status DaqCloseDevice logical device if status 0 printf Error closing device Status code d n status return status include daqdrive h include daqopent h include userdata h unsigned short main unsigned short logical_device unsigned short status unsigned short TSR_number 0xf006
232. rated every time the channel array is processed 50 times DAQDRIVE events are discussed in detail in chapter 11 7 2 10 Time out The timeout_interval field is used primarily during foreground mode operations to instruct DAQDRIVE when to abandon the processing of a request When DAQDRIVE has control of the CPU and is waiting for an event to occur i e waiting for a trigger or waiting for the digital input channel to become ready DAQDRIVE will wait timeout_interval seconds and if the event has not occurred the request will be aborted 7 2 11 Request Status The request_status field provides a mechanism for the application to monitor the state of a request The request status is an integral part of DAQDRIVE s event mechanisms and is discussed in detail in chapter 11 DAQDRIVE User s Manual 7 5 7 3 Digital Input Examples 73 1 Example 1 Single Value Input Purpose Input a single value from each of three digital input channels unsigned short channel_list 0 1 2 unsigned char input_values 3 struct digio_request my_request struct DAQDRIVE buffer my_data Construct the request structure ki my request channel array ptr my request array length my request digio buffer my data my request trigger source INTERNAL TRIGGER channel list my request 10 mode FOREGROUND CPU 3 my_request number_of_scans my_request scan_event_level my_request timeout_interval my_request re
233. reate and or edit these configuration files directly Operating instructions for the DAQDRIVE Configuration Utility are provided in Appendix A of the DAQDRIVE User s Manual Supplement 2 2 2 3 Creating DOS Applications Using The C Libraries 2 3 1 Microsoft Visual C C To generate application programs using Microsoft Visual C C the applications must be linked to one of the following DAQDRIVE libraries AND one or more hardware dependent libraries These libraries MUST match the memory model selected for the application program The DAQDRIVE installation program installs the following files into the DAQDRIVE C_LIBS directory DAQDRV CS LIB small model DAQDRIVE library DAQDRV CM LIB medium model DAQDRI VE library DAQDRV CC LIB compact model DAQDRIVE library DAQDRV CL LIB large model DAQDRIVE library Three additional files are installed in the DAQDRIVE C_LIBS directory for the programmer s convenience These files contain the prototypes of all the DAQDRIVE procedures the DAQDRIVE data structure definitions and the DAQDRIVE constants mentioned throughout this document These files must be included in all application programs DAQDRIVE H procedure prototypes DAQOPENC H DaqOpenDevice definition for C USERDATA H data structures and pre defined constants 2 3 1 1 The hardware dependent include file The C library version of the DaqOpenDevice procedure is implemented as a macro using the token pasting oper
234. request status All other fields in the request structure must remain constant until the operation is completed or otherwise terminated 2 If the request structure is dynamically allocated by the application it MUST NOT be de allocated until the request has been released by the DaqReleaseRequest procedure In addition applications using the VVindovys DLL version of DAQDRIVE should use DaqAllocateMemory if dynamically allocated request structures are required 13 5 channel_array_ptr This pointer defines the address of an unsigned short integer array specifying the logical analog input channel s to be operated on by this request gain_array_ptr This pointer defines the address of a floating point array specifying the gain for each channel in the array pointed to by channel_array_ptr There must be a one to one correspondence between the values specified by channel_array_ptr and the values specified by gain_array_ptr reserved1 4 This unsigned short integer array is reserved for the future expansion of DAQDRIVE For maximum compatibility the application should initialize all reserved variables to 0 array_length This unsigned short integer value defines the length of the arrays pointed to by channel_array_ptr and gain_array_ptr The arrays must be of equal length ADC_buffer This pointer defines the address of the first data buffer structure Data buffer structures are discussed in chapter 9 reserved2
235. request_handle if status 0 printf D A request error Status code d n status DAQDRIVE User s Manual 12 18 Step 7 Release the Request status DaqReleaseRequest request_handle if status 0 printf Could not release configuration Status code sd n status exit status Step 8 Close Hardware Device KKK status DagCloseDevice logical device if status 0 printf Error closing device Status code d n status return status 12 19 12 3 Digital Input Examples 12 3 1 Example 1 This example inputs a single value from a single digital input channel include lt conio h gt include lt graph h gt include lt stdio h gt include lt stdlib h gt include userdata h include daqdrive bi tinclude daqopenc h tinclude dagp h unsigned short main unsigned short logical_device unsigned short status unsigned short channel unsigned char input_value if status 0 printf n nDigital else printf Channel gt d printf Press lt ESC gt to while getch 0x1b input error while channel 99 Step 4 Close Hardware Device ET status DaqCloseDevice logical device if status 0 printf Error return status closing device Status code Input a single point from a single digital input channel char far device type DAQP 16 c
236. rforming An Acquisition DAQDRIVE uses a data defined rather than a function defined interface What this means is that each data acquisition operation is defined by a series of configuration parameters and requires very few function calls to implement These parameters which are contained in a data structure are hereafter referred to as a request structure or simply a request and define such parameters as channel numbers sampling rate number of scans trigger source etc The key to unlocking the power and flexibility of DAQDRIVE lies in the understanding of these request structures A utility program DAQTUTOR EXE is provided to aid the user in understanding DAQDRIVE request structures DAQTUTOR EXE is a Microsoft Windows application that allows the user to specify a DAQDRIVE request using a set of configuration windows After the request is defined DAQTUTOR EXE allows the user to view print or cut and paste the equivalent C code required to implement the information as a DAQDRIVE request structure For details on the operation of DAQTUTOR EXE consult Appendix B of the DAQDRIVE User s Manual Supplement Another parameter which the user needs to become familiar with is DAQDRIVE s use of request handles which are used to identify valid request structures When a request structure is passed into one of the configuration routines DAQDRIVE verifies the contents of the structure and confirms that the target hardware can perform the
237. riables to 0 trigger_source This unsigned short integer value specifies the trigger source for this request Trigger selections are discussed in chapter 10 DAQDRIVE Constant Value Description INTERNAL_TRIGGER 0 internal software trigger TTL_TRIGGER 1 TTL trigger ANALOG_TRIGGER 2 analog trigger DIGITAL_TRIGGER 3 digital value trigger trigger_mode This unsigned short integer value defines the trigger mode Trigger selections are discussed in chapter 10 DAQDRIVE Constant Value Description CONTINUOUS_TRIGGER 0 only one trigger is required to start the output operation ONE_SHOT_TRIGGER 1 a trigger is required for each output scan trigger_slope This unsigned short integer value defines the slope for TTL and analog triggers trigger_slope is ignored for all other trigger sources Trigger selections are discussed in chapter 10 DAQDRIVE Constant Value Description RISING_EDGE 0 for TTL and analog triggers only specifies a low to high transition is required FALLING_EDGE 1 for TTL and analog triggers only specifies a high to low transition is required trigger_channel This unsigned short value specifies the channel to be used as the input for the analog or digital trigger sources trigger_channel is undefined for all other trigger sources Trigger selections are discussed in chapter 10 Figure 13 Analog output request structure definition DAQDRIVE User s Manual
238. rnal input clock_rate This double precision value defines the clock frequency of the external clock clock_rate is ignored for internal clock sources sample_rate This double precision value specifies the output data rate in samples second Hz for multiple point operations reserved4 4 This unsigned short integer array is reserved for the future expansion of DAQDRIVE For maximum compatibility the application should initialize all reserved variables to 0 number_of_scans This unsigned long integer value defines the number of times the channels specified in channel_array_ptr will be written Setting number_of_cycles 0 will cause the channels to be scanned continuously scan_event_level This unsigned long integer value defines the frequency at which scan events are reported to the application For example setting scan_event_level to 100 causes a scan event to be generated each time 100 scans are completed reserved5 8 This unsigned short integer array is reserved for the future expansion of DAQDRIVE For maximum compatibility the application should initialize all reserved variables to 0 Figure 13 continued Analog output request structure definition 13 13 calibration This unsigned short integer value specifies the type of calibration to be performed for this request The calibration methods are dependent on the type of hardware installed Consult the hardware specific app
239. ror_code respectively The error code is set to 0 for all events except the run time error event where it is used to specify the type of error encountered as defined in chapter 14 13 73 13 23 DaqReleaseRequest The DaqReleaseRequest releases a previously defined request allowing the configured channels to be re used This is the reverse of the DaqAnaloginput DaqAnalogOutput DaqDigitalinput and DaqDigitalOutput procedures DaqReleaseRequest may be used on configurations that were never armed DaqArmkRequest on requests that have been completed or on requests that have otherwise been terminated unsigned short DaqReleaseRequest unsigned short request_handle request_handle This unsigned short integer variable is used to define which request is to be released This is the value returned to the application by the configuration procedures DaqAnaloginput DaqAnalogOutput DaqDigitalInput or DaqDigitalOutput DAQDRIVE User s Manual 13 74 include daqdrive bi include userdata h BRR RK KK KK II e hh I A ARR e hh A e e A Ae EE e hh KKK e k k k k d Output a 20 point waveform to a D A channel ti JEKKAKKKAKAKKKKKKKKKKKKKAKAKKKKKKKKKAKAKAKKKKKKKKKKKKKAKAKKKKKKKKKKKKKKKKKKKJ unsigned short main unsigned short logical_device unsigned short request_handle unsigned short channel unsigned short status unsigned short error unsigned short i short data_array 20 unsigned long event_mask struct DA
240. rovides the memory address of the first channel in the list using the channel_array_ptr field and must specify the length of the list in the array_length field 7 2 3 Data Buffers digio buffer defines the request s data buffer structure s to be used for storing the data input from the specified channel s The application program must define these buffers within the guidelines provided in chapter 9 7 2 4 Trigger Selections The trigger selection determines how the requested operation will be initiated after being armed Six fields are required to define and configure the trigger for the request trigger_source trigger_mode trigger_slope trigger_channel trigger_voltage and trigger_value Because the trigger selection is an integral part of the operation and is common to all of DAQDRIVE s request structures trigger configurations are discussed separately in chapter 10 7 2 5 Data Transfer Modes The request structure field IO_mode determines the mechanism that will be used to input the data from the hardware device In general the foreground modes provide the highest data transfer rates at the expense of requiring 100 of the CPU time In contrast background mode operations generally provide lower data transfer rates while allowing the CPU to perform other tasks 7 2 5 1 Foreground CPU mode This mode uses the CPU to input the data from the hardware device From the moment the request is triggered DAQDRIVE uses all of the CPU
241. rt trigger_slope unsigned short trigger channel double trigger voltage unsigned long trigger value unsigned short reserved3 4 unsigned short TO mode unsigned short clock_source double clock_rate double sample_rate unsigned short reserved4 4 unsigned long number_of_scans unsigned long scan_event_level unsigned short reserved5 8 s 1 unsigned short timeout interval unsigned long request status Hi Figure 14 Digital input request structure IMPORTANT 1 Once the request is armed using DagArmRequest the only field the application can modify is request status All other fields in the request structure must remain constant until the operation is completed or otherwise terminated If the request structure is dynamically allocated by the application it MUST NOT be de allocated until the request has been released by the DaqReleaseRequest procedure In addition applications using the VVindovys DLL version of DAQDRIVE should use DaqAllocateMemory if dynamically allocated request structures are required 13 23 channel_array_ptr This pointer defines the address of an unsigned short integer array specifying the logical digital input channel s to be operated on by this request reserved1 4 This unsigned short integer array is reserved for the future expansion of DAQDRIVE For maximum compatibility the application should initialize all reserved variables t
242. s with only enough buffer space to hold 20 000 samples is in the use of the BUFFER_FULL and BUFFER_EMPTY bits Before arming the request the BUFFER_EMPTY bits in the buffer_status fields are set my_ADC_data 0 buffer_status BUFFER_EMPTY 9 10 my_ADC_data 1 buffer_status BUFFER EMPTY DAQDRIVE User s Manual 9 11 The application may not modify the DAQDRIVE _buffer structures or the data buffers until the operation is halted or until DAQDRIVE sets the BUFFER_FULL bit If this is a background operation the application may sit in a loop waiting for BUFFER FULL and processing each buffer as it becomes available wait in dead loop until buffer 0 is full while my_ADC_data 0 buffer_status amp BUFFER_FULL 0 buffer 0 is full process data clearBUFFER_FULL and re set BUFFER_EMPTY when done my ADC datal0 buffer status BUFFER EMPTY wait in dead loop until buffer 1 is full while my_ADC_data 1 buffer_status amp BUFFER FULL 0 buffer 1 is full process data clearBUFFER_FULL and re set BUFFER_EMPTY when done my ADC datalll buffer status BUFFER EMPTY repeat until 500 000 samples are processed Another option for background mode operations is to monitor the BUFFER_FULL_EVENT bit in the request_status field of the ADC_request structure The application may assume the BUFFER_FULL bit is set before the BUFFER_FULL_EVENT is generated and that the applic
243. se procedures are discussed on the following pages Step 4 Close The Hardware Device When all operations on the hardware are complete the device should be closed using DaqCloseDevice to free any resources used by that device System integrity can not be guaranteed if the application program exits without closing the hardware device DAQDRIVE User s Manual 3 1 3 1 Analog Input For analog input DAQDRIVE provides two special purpose procedures DaqSingleAnaloginput and DaqSingleAnaloginputScan The intent of this section is to provide an overview of these procedures For details on the implementation of the procedures consult the alphabetical listing of commands in chapter 13 3 1 1 DaqSingleAnalogInput One of the simplest cases of analog input is to input a single sample from a single A D channel under CPU control DAQDRIVE provides a simplified interface for this operation through the DaqSingleAnalogInput procedure The format of this command is shown below unsigned short DaqSingleAnalogInput unsigned short logical_device unsigned short channel_number float gain_setting void far input_value DaqSingleAnaloginput sets the gain of the A D channel specified by channel_number on the adapter specified by logical_device to the value specified by gain_setting A single sample is then input from this analog channel and stored in the memory location specified by input_value The following example shows the usage of DaqS
244. setting This floating point value defines the gain setting for the channel specified by channel_number input_value This void pointer specifies the address where the value input from the A D converter is to be stored input_value is declared as a void to allow it to point to data of any type It is the application program s responsibility to ensure the data pointed to by input_value is the correct type for the target hardware as listed in the table below Resolution Configuration data type 1 to 8 bits unipolar unsigned char bipolar signed char 9 to 16 bits unipolar unsigned short bipolar signed short 17 to 32 bits unipolar unsigned long bipolar signed long DAQDRIVE User s Manual 13 78 include daqdrive bi include daqopenc h include userdata h include daql200 h unsigned short main unsigned short logical device unsigned short status unsigned short ADC_channel short input_value float gain_setting char far device type DAQ 1201 char far config_file c daq 1201 daq 1201 dat k Open the DAQ 1201 logical_device 0 status DaqOpenDevice DAQ1200 amp logical_device device type config file if status 0 printf Error opening configuration file Status code d n status exit status Input one value from A D channel 7 with a gain of 1 KERRE ADC_channel 7 gain_setting 1 0 status DaqSingle
245. ssed For example to input 100 samples from a single A D channel number_of_scans must be set to 100 To input 50 samples each from 6 A D channels 300 points total number_of_scans is set to 50 5 2 9 Scan Events DAQDRIVE generates a scan event each time the number of scans specified by scan_event_level are completed For example if scan_event_level is set to 50 a scan event is generated every time the channel array is processed 50 times DAQDRIVE events are discussed in detail in chapter 11 5 2 10 Calibration Selections The calibration field allows the application to specify the type of calibration to be performed if any by the hardware device s during the requested operation In general enabling calibration results in lower throughput rates while providing greater accuracy 5 2 10 1 Auto calibration Enabling auto calibration instructs the hardware device to perform one or more calibration cycles on the A D converter s specified by this request The results of auto calibration vary with different hardware devices Consult the hardware user s manual and the appendices in the back of this document for details about how auto calibration operates on the device in use 5 2 10 2 Auto zero Enabling auto zero instructs the hardware device to perform one or more zero offset adjustment cycles on the A D converter s specified by this request The results of auto zeroing vary with different hardware devices Consult the hardware user
246. st R te Sie ats aa te Shara RA Se Salon ty RE Sect a 12 2 12 Me Example Z see oar T ee a Bae a ea eked TE eRe a tn ga 12 3 12 1 3 Example EE 12 5 12 14 Example ENER 12 7 12 1 5 Example EE 12 9 12 2 Analog Output D A Examples 000 12 12 221 Example T caste eh Saati Ek da kua Pal be Ae ee at 12 12 EE age See e Ber ee egen E 12 13 1223 Example 3 oa Siva ai sid Sterne aes Seat t Sa i 12 15 12 24 Example aba tice tie deeg Ree Roi Se SS 12 17 12 3 Digital Input Examples gavicuson ing or do 12 20 D Example Ls cid hig eg e Ake Da Me aia hed de hee doe duet 12 20 123 2 NIPI qe rn Seatac gh Ghats See Ghats Sethe at 12 21 124 Digital Output Examples Jena A SC seals ees ees 12 24 241 Example I e eege ee eee kine Ree HOO SE 12 24 124 2 Example 2 So sn gus wees Gwe e See Uy wae See CSUR REES s 12 25 13 Command Reference 00 cence 13 1 13 1 DagAllocateMemory 13 2 13 2 DaqAnaloglnput sea Yas EE 13 4 13 3 DagAnaloeOutput vjen kosa tiss erd tire tanh eww as 13 10 13 4 DaqArmRequest e ia dun vd oo eddie sch EE EEN 13 16 13 5 DaqBytesToWords word WEES KG WS REG RGR Me ar ct 13 18 13 6 DanC RE 13 20 18 7 DagDigitallnput as serr wre A E shes meagre aed 13 22 13 8 DaqgDigitalOutp t xc Rg E oe 13 28 13 9 DaqFreeMemory ac sdi e SAG Ee Ne RG ER OS 13 34 13 10 DagGetADCie EE 13 36 13 11 DagGet A DGamlnto svi cha vere ts KR erg Rat wae Re 13 40 13 12 DaqGetDACfglnfo EEN 13 42 13 13 DaqGetDAGain nfo gr sin ar ae Suse
247. stalls DAQDRIVE on interrupt B9H After the DAQDRIVE TSR has been loaded the user must load one or more TSRs for the hardware device s to be accessed The DAQDRIVE installation program installs the TSR driver s for the selected hardware device s into the DAQDRIVE TSR directory For this discussion we will assume the hardware driver s TSR name is HARDWARE EXE To load this TSR simply execute the command HARDWARE The hardware TSR will search for the DAQDRIVE TSR in memory and if it is located will install itself using the same software interrupt If DAQDRIVE was not previously installed the hardware TSR will respond with an error message and will not be installed Multiple TSR drivers may be installed for multiple devices by repeating the above process for each hardware driver 2 4 2 Removing The TSRs From Memory The DAQDRIVE and hardware device TSRs may be removed from memory using the R option to make additional memory available to other applications The only restriction is that the TSRs must be removed in the reverse order of their installation Consider an example where the following TSRs have been loaded DAQDRIVE installs the DAQDRIVE TSR DAQPTSR installs the DAQP 208 TSR IOP 241 installs the IOP 241 TSR To remove these TSRs from memory the user simply reverses the installation order and adds the R option to each command line IOP 241 R removes the IOP 241 TSR DAQPTSR R removes the DAQP 208 TSR D
248. t 2K using the CLEAR command Note that the CLEAR command also clears all data memory and should therefore be used at the beginning of the application program In addition application programs written using Quick Basic 4 5 allocate all available DOS memory for use as a local heap This causes DAQDRIVE to report an error 300 memory allocation error when the application attempts to open a device The application must reduce the size of the heap using Quick Basic s SETMEM function before executing DaqOpenDevice As a guide the application should reduce the heap by 10 000 bytes for each hardware device opened and once the DaqOpenDevice procedure has been executed the allocated heap space must not be returned to Quick Basic until the DaqCloseDevice procedure has been completed VK KKK KKK KKK KKK KKK KKK KKK KKK KKK kk kk kk KKK KKK KK KKK KKK kk kk kk KKK KKK KKK KKK KKK KK KK KKK Increase the size of the Quick Basic stack by 2K VK KKK KKK KKK KKK KKK KKK KKK KKK KKK KK KKK KKK KKK KKK KKK KKK kk kk kk KKK KKK KKK KKK KKK KK KK KKK CLEAR 2048 VKKKKKK KKK KKK KK KKK KA KA KA KA KA KKK KA KA KA KA KA KKK KA KA KA KA KKK KKK AKA KA KA KKK KKKA KA KKK Decrease the size of the heap so DAQDRIVE can allocate required memory VKKKK KK KK KK KA KKK KKK KA KA KA KA KA KKK KA KA KKK KKK KKK KKK KKK KA KKK KKK AKA KA KA KKK KK KK KA KKK HeapSize SETMEM 10000 NAKKAKAKAKAKAKK KKK KA KA KA KA KA KKK KA KA KA KA KKK KKK AKA KA KKK AK KKK KA KA
249. t Device DaqResetDevice returns the specified hardware device to its power up state In situations where more than one application program is using the target device performing a reset could corrupt other tasks Under these circumstances DaqResetDevice will return an error indicating the device could not be reset in a multi user environment unsigned short DaqResetDevice unsigned short logical_device logical_device This unsigned short integer value is used to define the target hardware device This is the value returned to the application by the DaqOpenDevice command NOTE Not all hardware devices respond to DaqResetDevice in the same manner Consult the target hardware s appendix in the DAQDRIVE User s Manual Supplement to determine the exact operation of this procedure DAQDRIVE User s Manual 13 76 include daqdrive h include daqopenc h include userdata h include da8p 12 h unsigned short main unsigned short logical_device unsigned short status char far device_type DA8P 12B char far config_file c da8p 12b da8p 12b dat Open the DA8P 12B logical_device 0 status DaqOpenDevice DA8P 12 amp logical_device device_type config_file if status 0 printf Error opening configuration file Status code d n status exit status Perform DA8P 12B operations here Ee k Reset the DASP 12B status DaqResetDevice lo
250. t be set to 100 To output 50 samples each to two digital output channels 100 points total number_of_scans is set to 50 8 2 9 Scan Events DAQDRIVE generates a scan event each time the number of scans specified by scan_event_level are completed For example if scan_event_level is set to 50 a scan event is generated every time the channel array is processed 50 times DAQDRIVE events are discussed in detail in chapter 11 8 2 10 Time out The timeout_interval field is used primarily during foreground mode operations to instruct DAQDRIVE when to abandon the processing of a request When DAQDRIVE has control of the CPU and is waiting for an event to occur i e waiting for a trigger or waiting for the digital output channel to become ready DAQDRIVE will wait timeout_interval seconds and if the event has not occurred the request will be aborted 8 2 11 Request Status The request_status field provides a mechanism for the application to monitor the state of a request The request status is an integral part of DAQDRIVE s event mechanisms and is discussed in detail in chapter 11 DAQDRIVE User s Manual 8 5 8 3 Digital Output Examples 8 3 1 Example 1 Single Value Output Purpose Output a single value to each of two digital output channels unsigned short channel_list 1 Ui unsigned char output_values 0 255 struct digio_request my_request struct DAQDRIVE buffer my_data Construct the reques
251. t channel_num 4 0 1 6 3 unsigned short status unsigned short data_array 400 unsigned short array_index unsigned short error unsigned long event mask struct digio request user request struct DAQDRIVE buffer data structure k Open the device see DaqOpenDevice SEET k x x Prepare the digital input request structure PERK Request digital input see DaqDigitalInput SET k Arm the request see Daq rmRequest KKAKKJ fxxkxkxk Trigger the request ERREK status DaqTriggerRequest request_handle if status 0 printf Trigger request error Status code d n status DaqStopRequest request_handle DaqReleaseRequest request_handle DaqCloseDevice logical device exit status Wait for completion or error XL event_mask COMPLETE_EVENT RUNTIME_ERROR_EVENT while user_request request_status amp event_mask 0 if user request request status amp RUNTIME_ERROR_EVENT 0 status DaqGetRuntimeError request_handle amp error exit error Un pack the values for display EK EK DagqBytesToWords data_array data_array 400 Display the input values as integers RARER for array_index 0 array index lt 400 array_index printf digital input 4x n data_array array_index 13 19 13 6 DaqCloseDevice DaqCloseDevice informs DAQDRIVE that the specified logical device is no longer r
252. t far channel array unsigned short array length void far output array logical_device This unsigned short integer value is used to define the target hardware device This is the value returned to the application by the DaqOpenDevice command channel_array This pointer specifies the address of an unsigned short integer array containing the analog output channels on logical_device to be written array_length This unsigned short integer value defines the length of channel_array and output_array output_array This void pointer specifies the address of an array containing the data to be output to the analog output channels output_array is declared as a void to allow it to point to data of any type It is the application program s responsibility to ensure the data pointed to by output_array is the correct type for the target hardware as listed in the table below DAQDRIVE User s Manual 13 84 Resolution Configuration data type 1 to 8 bits unipolar unsigned char bipolar signed char 9 to 16 bits unipolar unsigned short bipolar signed short 17 to 32 bits unipolar unsigned long bipolar signed long Figure 25 output_array data types as a function of analog output channel type include daqdrive h include daqopenc h include userdata h tinclude dagp h unsigned short main unsigned short logical_device unsigned short status unsigned short channel_array
253. t handle a unique non zero value This request handle is used to identify this request in all future operations If the application program modifies the contents of user_request after executing DaqAnalogInput the structure must be verified again To request re verification of a previously approved request the application executes DaqAnaloginput with request handle set to the value returned by DaqAnaloginput when the request was first approved All parameters except the channel list may be modified after the initial configuration To modify the channel list the existing request must be released using DaqReleaseRequest and a new configuration requested DAQDRIVE User s Manual 5 1 5 2 The Analog Input Request Structure The power of DaqAnalogInput lies in the application s ability to modify a single data structure and execute a single procedure to perform multiple analog input operations The elements of the analog input request structure are discussed on the following pages e ADC_request unsigned short far channel_array ptr float far gain_array ptr unsigned short reserved1 4 unsigned short array_length struct DAQDRIVE buffer far ADC buffer unsigned short reserved2 4 unsigned short trigger source unsigned short trigger mode unsigned short trigger_slope unsigned short trigger channel double trigger_voltage unsigned long trigger value unsigned short reserved3 4 unsigned short IO_mode unsigned short clo
254. t indicates the expansion board input is unipolar input_mode This unsigned short integer value specifies the expansion board input mode Value Description Ox0001 When set to 1 this bit indicates the expansion board input is differential Ox0002 When set to 1 this bit indicates the expansion board input is single ended num_mux_channels This unsigned short integer value specifies the number of multiplexer channels on the expansion board max_sample_rate This floating point value specifies the maximum single channel sampling rate supported by the expansion board max_scan_rate This floating point value specifies the maximum multi channel scanning sampling rate supported by the expansion board gain_array_length This unsigned short integer value specifies the number of available expansion board gain settings The application must allocate an array of length gain_array_length before executing DaqGetExpGainInfo Figure 22 Analog input expansion board configuration structure definition 13 53 Quatech Inc include daqdrive bi include userdata h include daql200 h unsigned short main unsigned short logical_device unsigned short ADC_device unsigned short exp_device unsigned short status struct exp_configuration exp_info char far device type DAQ 1201 char far config_file c daq 1201 daq 1201 dat Open the DAQ 1201 see
255. t my_request struct DAQDRIVE buffer my data unsigned short request handle unsigned short status Construct the request structure TKN my_request channel_array_ptr amp channel_number my_request array_length 1 my_request digio_buffer amp my_data my request trigger source INTERNAL TRIGGER my request 10 mode FOREGROUND CPU my request number of scans 1 my_request scan_event_level 0 my_request timeout_interval 0 my_request request_status NO_EVENTS Construct the data buffer structure SE ee my data data buffer void huge output_value my_data buffer_length 1 my_data buffer_cycles 1 my_data next_structure NULL my_data buffer_status BUFFER_FULL Execute the request LER ERY request_handle 0 status DaqDigitalOutput logical_device my_request amp request_handle if status 0 return status Jenni If no errors arm the request KAKKKJ status DagArmRequest request handle if status 0 DaqReleaseRequest request_handle return status Jenni If no errors software trigger the request PER ESS status DaqTriggerRequest request_handle if status 0 DaqStopRequest request_handle DaqReleaseRequest request_handle return status T RRKKK If no errors release the request and return KAKKKJ status DaqReleaseRequest request handle return status H 3 22 3 4 2 DaqSingleDigitalOutputScan
256. t number_of_scans 18000 To change the square wave portion of the output from 45 cycles to 300 cycles change the corresponding buffer_cycles to 300 and number_of_scans to 50 360 300 2 30 75 my_DAC_data 1 buffer_cycles my_DAC_request number of scans 300 20850 If the triangle wave is redefined to have 60 samples change the corresponding buffer_length to 60 and number_of_scans to 50 360 45 2 75 60 my_DAC_data 2 buffer_length 60 my_DAC_request number_of_scans 22590 9 20 9 3 6 Example 6 Outputting Large Amounts Of Data The multiple buffer operation of example 4 can be extended for the application that needs to output large numbers of points Assume 500 000 points need to be read from a file and output to a 12 bit D A converter If all of the samples are input from the file at once 1 Megabyte of memory would be required to hold the data An alternative solution may be to allocate two buffers with 25 000 points each unsigned short output_data0 25000 unsigned short output datall2500015 The next step is to allocate and configure two DAQDRIVE buffer structures The data buffer fields are set to point to the arrays defined above and the buffer length fields are set accordingly The first structure has its next structure field set to point to the second structure The second structure has its next structure field set to point to the first structure forming a circular buffer struct
257. t structure LEERY my_request channel_array_ptr my_request array_length my_request digio_buffer my_request trigger_source my request IO mode my request number of scans channel list 2 amp my_data INTERNAL_TRIGGER FOREGROUND_CPU my_request scan_event_level 0 my_request timeout_interval 0 my_request request_status NO EVENTS Construct the data buffer structure SE my data data buffer output_values my_data buffer_length 2 my_data buffer_cycles 1 my_data next_structure NULL my_data buffer_status BUFFER_FULL Variations on example 1 1 To change the number of channels from two to three re define channel_list and output_values then set my_request array_length 3 my_data buffer_length 3 2 To change the trigger mode to a TTL trigger set my_request trigger_source TTL_TRIGGER my_request trigger_slope FALLING_EDGE 8 6 8 3 2 Example 2 Simple Pattern Generation Purpose Output 100 cycles of a digital pattern defined with 128 points per cycle with 10ms between samples struct struct RRKKK KKK KK KKK KK my_request channel_array_ptr my_request array_length my_request digio_buffer my_request trigger_source my_request trigger_slope my_request I0O_mode my_request clock_source my_data buffer_status unsigned short channel number unsigned char pattern 128 digio_request my_request DAQDRIVE buffer my_data Assume data valu
258. t_data 1000 unsigned long event_mask char far device type IOP 241 char far config file iopr241 dat Step 1 Initialize Hardware logical_device 0 status DaqOpenDevice IOP241 amp logical_device device_type config_file if status 0 printf Error opening device Status code d n status exit status Step 2 Input data channel 0 Prepare Buffer Structure my_data data_buffer input_data set pointer to output data my_data buffer_length 1000 number of points in buffer my_data next_structure NULL indicate no more buffers my_data buffer_status BUFFER_EMPTY indicate buffer empty ready Prepare the digital input request structure HK user_request channel_array_ptr amp channel array of channels user_request array_length 1 number of channels user request digio buffer amp my_data pointer to data user request trigger source INTERNAL TRIGGER internal trigger user request trigger mode CONTINUOUS_TRIGGER input all points user request 10 mode BACKGROUND_IRQ background mode user_request clock_source INTERNAL_CLOCK use on board clock user_request sample_rate 100 100 Hz input rate user_request number_of_scans 1000 1000 scans user_request scan_event_level 0 no scan events user request timeout interval 0 disable time out near remest ramiaet stafue N Jr initialize stafu
259. t_handle ai ERY k k Define events to be notified BEERS event mask TRIGGER EVENT COMPLETE EVENT RUNTIME_ERROR_EVENT Install notification procedure MAIR status DaqNotifyEvent request_handle my event procedure event mask if status 0 printf Error installing notification n k Arm the request See Daq rmkRequest XA T Jenni Trigger the request See DaqTriggerRequest RARER DAQDRIVE User s Manual 13 64 13 21 DaqOpenDevice DaqOpenDevice reads the adapter description file generated by the DAQDRIVE configuration utilities initializes the hardware device according to the contents of the file and prepares DAQDRIVE for use with the device DaqOpenDevice is the only procedure that is implemented differently depending upon the type of interface between DAQDRIVE and the application program The following sections describe the DaqOpenDevice procedure for linking C applications directly to the DAQDRIVE libraries for applications using the DLL version of DAQDRIVE under Windows and for applications using the DOS memory resident TSR version of DAQDRIVE 13 65 13 21 1 DaqOpenDevice C Library Version The C library version of DaqOpenDevice is intended for DOS applications that are written in C and linked directly to the DAQDRIVE libraries Consult the target hardware s appendix in the DAQDRIVE User s Manual Supplement for the required settings of PROCEDURE the device_typ
260. ta Buffers 9 16 9 3 5 Example 5 Creating Complex Output Patterns 9 17 9 3 6 Example 6 Outputting Large Amounts Of Data 9 19 10 Trigger Selections 00 c cece eens 10 1 10 1 Trigger Sources eer Sia dood wed See Reka dea ege eg 10 1 10 1 1 Internal Trigger ada Dankan De EE ewe as 10 1 IO TTE Trigger arr nude e ge dd P e A 10 1 10 1 3 A a log Trigger da ss pin d tata wate Sha 10 2 101 4 Digital Trigger adm S RR mke aes d edi 10 2 10 2 Trigger Modes ma buk nde d 10 3 10 2 1 One shot Trigger Mode nda esi Ve V 10 3 10 2 2 Continuous Trigger Mode 10 3 11 DAQDRIVE Events 11 1 11 1 Event Descriptions esi ask Do hind Coren wha Roca Rie 11 1 DAQDRIVE User s Manual Vv ST Hp K T Event HT 11 1 11 1 2 Complete Event EE 11 1 11 1 3 Buffer Empty Event q data pn sete a ya s Ye iy sepa a 11 1 ELA Butter Full Event 24 28 tae ea eae eta aa Rak ae yal 11 1 Tele Scam Event i aa eae Gea Sie iy Ge i Sn See Sh 11 2 11 1 6 User Break Event i jua civ ge beatae Sia v eel iau eka 11 2 11 1 7 Time out Event 11 2 11 1 8 Run time Error Event iii 11 2 11 2 Monitoring Events Using The Request Status 11 2 11 3 Monitoring Events Using Event Notification 11 5 11 4 Monitoring Events Using Messages In Windows 11 9 12 Common Application Examples 12 1 12 1 Analog Input A D Examples sic dua d dE aa pee mjeko du 12 2 TZN LEX AMON NG turi
261. ta_structure trigger source is internal XL trigger mode is continuous output using IRQs in background use internal clock output 1 point every 500ms 2Hz K repeat all buffers once do not signal buffer scan events I do not implement time out XI JEKKKKKAKKKKKKKKKKKKKKKAKAKKKKKKKKKKKKAKAKKKKKKKKKKKAKAKKKKKKKKKKKKKKKKKKKKJ user request channel array ptr channel num user request array length 3 user request DAC buffer data structure user request trigger source INTERNAL TRIGGER user request trigger mode CONT INUOUS_TRIGGER user request 10 mode BACKGROUND_IRQ user_request clock_source INTERNAL_CLOCK user_request sample_rate 2 user_request number_of_scans 1 user_request scan_event_level 0 user_request timeout_interval 0 user_request request_status NO_EVENTS k Indicate data buffer ready for output E 1 data_structure buffer_status BUFFER_FULL Request digital output XL request_handle 0 status DaqDigitalOutput logical_device amp user_request amp request_handle if status 0 printf Digital output request error Status code d n status DaqCloseDevice logical_device exit status 13 33 13 9 DaqFreeMemory DaqFreeMemory is a DAQDRIVE utility function used to free memory previously allocated by the DaqAllocateMemory procedure All allocated memory should be freed before the application program terminates unsigned sh
262. tatus code Sd n status DaqCloseDevice logical_device exit status Step 3 Arm the Request status DagArmRequest request_handle if status 0 printf Arm request error Status code d n status DaqReleaseRequest request_handle DaqCloseDevice logical device exit status Step 4 Trigger the Request status DaqTriggerRequest request_handle if status 0 printf Trigger request error Status code d n status DaqReleaseRequest request_handle DaqCloseDevice logical_device exit status Step 5 Wait for completion or error SE _clearscreen _GCLEARSCREEN event mask COMPLETE_EVENT RUNTIME_ERROR_EVENT do if user request request status amp BUFFER FULL EVENT 0 _settextposition 10 10 printf The current value is 6d current sample my data buffer status BUFFER_EMPTY buffer empty ready user_request request_status sz BUFFER_FULL_EVENT while user_request request_status amp event_mask 0 wait for event if user_request request_status amp RUNTIME_ERROR_EVENT 0 DaqGetRuntimeError request_handle status printf n n nRun time error Error code d Operation aborted n status DaqReleaseRequest request_handle DaqCloseDevice logical device exit status xxx Step 6 Release the Request status DaqReleaseRequest request_handle if status 0 printf Could not release c
263. teger value is used to define the target hardware device This is the value returned to the application by the DaqOpenDevice command ADC device This unsigned short integer value is used to select one of the A D converters on the target hardware device gain_array This pointer defines the first element of an array of floating point values where the available A D gain settings will be stored The application must allocate the array used to store these gain settings The length of the array is determined by the gain_array_length variable returned by the DaqGetADCfgInfo command DAQDRIVE User s Manual 13 40 include daqdrive bi include userdata h include daql200 h unsigned short main unsigned short logical_device unsigned short ADC_device unsigned short status unsigned short i struct ADC_configuration ADC_info float far gain_array char far device type DAQ 1201 char far config_file c daq 1201 daq 1201 dat Open the DAQ 1201 see DaqOpenDevice KREKKJ k k Get the A D configuration REA ERY ADC_device 0 status DaqGetADCfgInfo logical_device ADC device SADC info Create an array to hold the gain settings RES RRS gain_array _fmalloc ADC_info gain_array_length sizeof float Get the available gain settings RERE status DaqGetADGainiInfo logical device ADC device gain array if status 0 printf Error getting A D gain settings
264. tes the request has completed successfully BUFFER_EMPTY_EVENT 0x00000004 When set to 1 this bit indicates at least one of the specified output data buffers has been emptied BUFFER_FULL_EVENT 0x00000008 When set to 1 this bit indicates at least one of the specified input data buffers has been filled SCAN_EVENT 0x00000010 When set to 1 this bit indicates the number of scans specified by scan_event_level have been completed at least once USER_BREAK_EVENT 0x20000000 When set to 1 this bit indicates the request has terminated due to a user break TIMEOUT_EVENT 0x40000000 When set to 1 this bit indicates the request has terminated because the specified time out interval was exceeded RUNTIME_ERROR_EVENT 0x80000000 When set to 1 this bit indicates the request has terminated because of an error during processing The application can determine the source of the error using the DaqGetRuntimeError procedure Figure 11 continued Analog input request structure definition DAQDRIVE User s Manual 13 8 include daqdrive bi include userdata h JEKKAKKKAKKKKKKKKKKKKKKKAKKKKKKKKKKKAKAKAKKKKKKKKKKKAKAKAKKKKKKKKKKKKKKKKKKJ Input 500 points each from 2 analog input channels E JEKKKKKAKKKKKKKKKKKKKKKAKKKKKKKKKKKAKAKAKKKKKKKKKKKAKAKKKKKKKKKKKKKKKKKKKKJ unsigned short main unsigned short logical_device unsigned short request_handle unsigned short channel_num 2 0 1 33 float gain_settings 2 1 unsig
265. the analog input configuration procedure DaqAnalogInput arming the requested configuration DaqArmRequest and triggering the operation DaqTriggerRequest For users interested in learning more about DAQDRIVE s analog input interface the following example program creates the equivalent of the DaqSingleAnaloginputScan procedure 3 6 if status 0 return status x If no errors arm the request KAKKKJ status DagArmRequest request handle if status 0 DaqReleaseRequest request_handle return status Jenni If no errors software trigger the request status DaqTriggerRequest request_handle if status 0 DaqStopRequest request_handle DaqReleaseRequest request_handle return status Jenni If no errors release the request and return status DaqReleaseRequest request_handle return status H unsigned short MySingleAnalogInputScan unsigned short logical device unsigned short far channel array float far gain array unsigned short array length void far input array struct ADC_request my_request struct DAQDRIVE buffer my data unsigned short request handle unsigned short status Construct the request structure Ee my_request channel_array_ptr channel_array my_request gain_array_ptr gain_array my_request array_length array_length my_request ADC_buffer amp my_data my_request trigger_source INTERNAL
266. the application wishes to be notified of event_mask is defined as a bit mask setting a specific bit to logic 1 enables notification of the corresponding event The bit definitions of event mask are given below DAQDRIVE constant Value Description NO_EVENTS 0x00000000 Disable all event notification TRIGGER_EVENT 0x00000001 Enable notification of trigger events COMPLETE_EVENT 0x00000002 Enable notification of complete events BUFFER_EMPTY_EVENT 0x00000004 Enable notification of buffer empty events BUFFER FULL EVENT 0x00000008 Enable notification of buffer full events SCAN_EVENT 0x00000010 Enable notification of scan events USER BREAK EVENT 0x20000000 Enable notification of user break events TIMEOUT_EVENT 0x40000000 Enable notification of time out events RUNTIME_ERROR_EVENT 0x80000000 Enable notification of run time error events window_handle This unsigned short integer value is the handle of the application program window HWND DAQDRIVE User s Manual 13 72 13 22 1 The Event Message When an event occurs DAQDRIVE uses the Windows PostMessage procedure to send an event message to the window specified by window_handle HWND The message number uMsg is the sum of the event value specified in figure 8 and the pre defined Windows constant WM_USER The two message specific arguments LPARAM and WPARAM are used to specify the request s request_handle and an event er
267. the initial configuration To modify the channel list the existing request must be released using DaqReleaseRequest and a new configuration requested DAQDRIVE User s Manual 6 1 6 2 The Analog Output Request Structure The power of DaqAnalogOutput lies in the application s ability to modify a single data structure and execute a single procedure to perform multiple analog output operations The elements of the analog output request structure are discussed on the following pages Hose DAC_request unsigned short far channel_array ptr unsigned short reserved1 4 unsigned short array_length struct DAQDRIVE buffer far DAC_buffer unsigned short reserved2 4 unsigned short trigger source unsigned short trigger mode unsigned short trigger_slope unsigned short trigger channel double trigger_voltage unsigned long trigger value unsigned short reserved3 4 unsigned short TO mode unsigned short clock_source double clock_rate double sample_rate unsigned short reserved4 4 unsigned long number_of_scans unsigned long scan event Level unsigned short reserved5 8 s s 1 unsigned short calibration unsigned short timeout_interval unsigned long request status Hi IMPORTANT 1 If the application program modifies the contents of the request structure after executing DaqAnalogOutput the updated structure must be re verified by DaqAnalogOutput before the
268. ther trigger sources Trigger selections are discussed in chapter 10 Figure 11 Analog input request structure definition DAQDRIVE User s Manual 13 6 trigger_voltage This double precision value defines the trigger voltage level for the analog trigger trigger_voltage is ignored for all other trigger sources Trigger selections are discussed in chapter 10 trigger_value This unsigned long value defines the value required on the digital input for a digital trigger to be generated trigger_value is ignored for all other trigger sources Trigger selections are discussed in chapter 10 reserved3 4 This unsigned short integer array is reserved for the future expansion of DAQDRIVE For maximum compatibility the application should initialize all reserved variables to 0 IO_mode This unsigned short integer value specifies the method of data transfer clock_source DAQDRIVE Constant Value Description FOREGROUND_CPU 0 DAQDRIVE takes control of the CPU until the request is complete BACKGROUND_IRQ 1 hardware interrupts are used to gain control of the CPU and input the data FOREGROUND_DMA 2 DMA is used to input the data the CPU monitors controls the DMA operation BACKGROUND DMA 3 DMA is used to input the data interrupts are used to monitor control the DMA operation This unsigned short value selects the clock source to provide the timing for multiple point input operations DAQDRIVE Consta
269. to two integer values a segment address and an offset address An example of this is the channel array variable in the ADCRequest structure unsigned short far channel_array_ptr which becomes ChannelArrayPtrOffset AS Integer ChannelArrayPtrSegment AS Integer For an array named Channel the application fills in the array s address using the VARSEG and VARPTR procedures as follows DIM Channel 10 AS Integer ADCRequest ChannelArrayPtrOffset VARPTR Channel 0 ADCRequest ChannelArrayPtrSegment VARSEG Channellol 2 4 6 5 Dynamic memory allocation To prevent Visual Basic for DOS from dynamically relocating variables it is good practice to declare all variables before the first instruction of the application program 2 18 2 4 7 Turbo Pascal DAQDRIVE supports applications written with Turbo Pascal version 7 0 and newer through the unit files DAQDRIVE TPU and DAQDATA TPU installed in the DAQDRIVE TSR PASCAL directory by the DAQDRIVE installation program DAQDRIVE TPU defines the Turbo Pascal interface to the DAQDRIVE functions while DAQDATA TPU defines the DAQDRIVE data structures Pascal records and constants mentioned throughout this document In order to access DAQDRIVE s functions data structures and constants all application programs must include the following statement USES DAQDRIVE DAQDATA 2 4 7 1 Turbo Pascal and floating point math The Turbo Pascal floating point emulation library only supports
270. type of operation requested If the request structure is valid a request handle is assigned to the structure and all future operations on this request are referenced using its request handle The following steps define the sequence required to perform an operation using DAQDRIVE s data defined interface DAQDRIVE User s Manual 4 1 Step 1 Define The Hardware Configuration DAQDRIVE determines the configuration of a device from the data file specified when the device is opened These configuration files are created using the DAQDRIVE configuration utility as described in Appendix A of the DAQDRIVE User s Manual Supplement Step 2 Open The Hardware Device Before the application program can use an adapter it must first open the device using the DaqOpenDevice command The application must provide the open command with the adapter type and specify the name of a configuration file generated in step 1 which describes the target hardware s configuration If the open command completes successfully DAQDRIVE assigns a logical device number to be used for all future references to the adapter Step 3 Define The Request Structure And Data Buffers With the device successfully opened the application must now allocate and define all of the parameters associated with the operation to be performed These parameters include such variables as the channel number s trigger source and sampling rate DAQDRIVE s request structures are covered i
271. ucture definitions and the DAQDRIVE constants mentioned throughout this document These files must be included in all application programs DAQQB45 INC procedure declarations USERDATA INC data structures and pre defined constants 2 4 5 1 Quick Basic s on line help Although undocumented the Quick Basic 4 5 on line help appears to use software interrupt 60H and may interfere with the DAQDRIVE TSR If suspicious errors occur while using Quick Basic users are advised to install DAQDRIVE on software interrupt 61H 62H 63H or 64H IMPORTANT Although undocumented the Quick Basic 4 5 on line help appears to use software interrupt 60H and may interfere with DAQDRIVE 2 4 5 2 Quick Basic and the under score character One difference between the Quick Basic version and other versions of DAQDRIVE is that Quick Basic reserves the underscore character The underscore character appears in data declarations and constants throughout this document but has been removed from the Quick Basic version of DAQDRIVE 2 12 2 4 5 3 Adjusting the size of Quick Basic s stack and heap DAQDRIVE uses the application program s stack for storing local variables and for passing variables between DAQDRIVE procedures By default Quick Basic 4 5 only allocates 2K of memory for the application s stack which may be insufficient under come circumstances It is recommended that the user increase the size of the application s stack by at leas
272. ue Input 7 7 8 Digital Output Requests 8 1 8 1 DaqDigitalOutput lt 4 suo nie Sone yh EE SSS Boe Pw aes 8 1 8 2 The Digital Output Request Structure 8 2 8 2 1 Reserved Fields udi veg dre Siew kt 8 3 8 2 2 Channel Selections dun sir wa a aa ee eae we 8 3 8 23 Data Buffers A ai I Ra ee bain PM 8 3 i narru n nrn urren 8 3 8 2 5 Data Transfer Modes 8 3 8 2 6 Clock Sources e 8 4 8 2 7 Sampling Rate hare tee ce orale e ep ae a Goes EA 8 5 8 2 8 Number Of Seans E tS AEK N N 8 5 8 2 9 Scan EventS 0 cee ccc eee eens 8 5 8 2 MEET AeA et ae Se aot A 8 5 8 2 1 REGUCSE Status e E TR ee eA eS 8 5 8 3 Digital Output Examples sil 208 SC ade ng iia h ee H 8 6 8 3 1 Example 1 Single Value Output i iaiis 8 6 8 3 2 Example 2 Simple Pattern Generation 8 7 9 Defining Data Buffers aaa 9 1 9 1 Multiple Channel Operations z j dje WENN ee none xe eee EEN 9 5 9 2 Input een SEENEN 9 7 9 2 1 Example 1 Single Channel Analog Input 9 7 9 2 2 Example 2 Multi Channel Analog Input 9 8 9 2 3 Example 3 Using Multiple Data Buffers 9 9 9 2 4 Example 4 Acquiring Large Amounts Of Data 9 10 9 3 Output Operation Examples 9 13 9 3 1 Example 1 Single Channel Analog Output 9 13 9 3 2 Example 2 Creating Repetitive Signals 9 14 9 3 3 Example 3 Multi Channel Analog Output 9 15 9 3 4 Example 4 Using Multiple Da
273. uest For users interested in learning more about DAQDRIVE s analog output interface the following example program creates the equivalent of the DaqSingleAnalogOutput procedure DAQDRIVE User s Manual 3 9 unsigned short MySingleAnalogOutput unsigned short logical_device unsigned short channel_number void far output_value struct DAC_request my_request struct DAQDRIVE buffer my_data unsigned short request_handle unsigned short status Construct the request structure TKN my_request channel_array_ptr amp channel_number my_request array_length 1 my request DAC buffer bm data my request trigger source INTERNAL TRIGGER my request 10 mode FOREGROUND CPU my request number of scans 1 my_request scan_event_level 0 my_request calibration NO_CALIBRATION my_request timeout_interval 0 my_request request_status NO_EVENTS Construct the data buffer structure ERER my_data data_buffer void huge output_value my_data buffer_length 1 my_data buffer_cycles 1 my_data next_structure NULL my_data buffer_status BUFFER_FULL Execute the request CEE ERT request_handle 0 status DaqgAnalogOutput logical_device my_request amp request_handle if status 0 return status x If no errors arm the request KAKKKJ status DagArmRequest request handle if status 0 DaqReleaseRequest request_handle return status Jenni
274. uest far user_request unsigned short far request_handle logical device This unsigned short integer value is used to define the target hardware device This is the value returned to the application by the DaqOpenDevice command user request This structure pointer defines the address of a digital I O request structure containing the desired configuration information for this operation This structure is discussed in detail on the following pages request_handle This unsigned short integer pointer is used to identify this digital input request For a new configuration request_handle is set to 0 by the application before calling DaqDigitalinput If the configuration is successful request_handle will be assigned a unique non zero value by the DaqDigitalInput procedure If the application modifies a previously configured request the application must call DaqDigitalinput using the previously assigned request handle All parameters except the channel list may be modified using a reconfiguration request To modify the channel list the present request must be released DaqReleaseRequest and a nevy configuration requested DAQDRIVE User s Manual 13 22 Ge digio_request unsigned short far channel_array ptr unsigned short reserved1 4 unsigned short array_length struct DAQDRIVE buffer far digio_buffer unsigned short reserved2 4 unsigned short trigger source unsigned short trigger mode unsigned sho
275. uest s request_status field as shown in figure 7 DAQDRIVE does not rely on the information contained in this field nor does it ever clear any of the event bits to 0 Therefore the application should initialize request_status during the configuration process and may modify its contents at any time DAQDRIVE User s Manual 11 2 DAQDRIVE constant Value Description NO_EVENTS Ox00000000 This constant does not represent an event status It is provided to the application for convenience TRIGGER_EVENT 0x00000001 When set to 1 this bit indicates the specified trigger has been received COMPLETE_EVENT 0x00000002 When set to 1 this bit indicates the request has completed successfully BUFFER_EMPTY_EVENT 0x00000004 When set to 1 this bit indicates at least one of the output data buffers has been emptied BUFFER_FULL_EVENT 0x00000008 When set to 1 this bit indicates at least one of the input data buffers has been filled SCAN EVENT Ox00000010 When set to 1 this bit indicates the number of scans specified by scan event level have been completed at least once USER_BREAK EVENT 0x20000000 When set to 1 this bit indicates the request has terminated due to a user break TIMEOUT_EVENT 0x40000000 When set to 1 this bit indicates the request has terminated because the specified time out interval was exceeded RUNTIME ERROR EVENT 0x80000000 When set to 1 this bit indicates the request has terminated because o
276. uffer unsigned short reserved2 4 unsigned short trigger source unsigned short trigger mode unsigned short trigger_slope unsigned short trigger channel double trigger voltage unsigned long trigger value unsigned short reserved3 4 unsigned short 10 mode unsigned short clock_source double clock_rate double sample_rate unsigned short reserved4 4 unsigned long number_of_scans unsigned long scan_event_level unsigned short reserved5 8 unsigned short timeout_interval unsigned long request status N se IMPORTANT 1 If the application program modifies the contents of the request structure after executing DaqDigitalOutput the updated structure must be re verified by DaqDigitalOutput before the request is armed 2 Once the request is armed using DaqgArmRequest the only field the application can modify is request_status All other fields in the request structure must remain constant until the operation is completed or otherwise terminated 3 If the request structure is dynamically allocated by the application it MUST NOT be de allocated until the request has been released by the DaqReleaseRequest procedure In addition applications using the Windows DLL version of DAQDRIVE should use DaqAllocateMemory if dynamically allocated request structures are required 8 2 8 2 1 Reserved Fields The fields reserved through reserved5 are provided for expansion of the digital output r
277. ure for digital input XKE L AAA put data in data array data_array is 400 points long next_structure NULL no more structures JEKKAKKKAKKKKKKKKKKKKKKAKAKKKKKKKKKKKKAKAKAKKKKKKKKKAKAKKKKKKKKKKKKKKKKKKKKJ data structure data buffer data array data structure buffer length 1000 data_structure next_structure NULL Jenni Prepare the digital input request structure Ze JEKKAKKKAKKKKKKKKKKKKKKAKAKKKKKKKKKKKKAKAKKKKKKKKKKKKKKAKAKKKKKKKKKKKKKKKKKKJ channel list is in channel num channel list length is 4 use data structure for data trigger source is internal trigger mode is continuous input using CPU in foreground use internal clock sample at 100 Hz scan channels list 100 times do not signal buffer scan events do not implement time out JEKKAKKKAKKKKKKKKKKKKKKAKAKKKKKKKKKKKKAKAKKKKKKKKKKKAKAKAKKKKKKKKKKKKKKKKKKJ user request channel array ptr channel num user request array length 4 user_request ADC_buffer data_structure user_request trigger_source INTERNAL_TRIGGER user_request trigger_mode CONT INUOUS_TRIGGER user request 10 mode FOREGROUND CPU user request clock source INTERNAL CLOCK if status 0 printf Digital input request error Status code d n status DaqCloseDevice logical_device exit status vi user_request sample_rate 100 user_request number_of_scans 100 user_request scan_event_level 0 user request timeout interval 0 use
278. us k Arm the request See Daq rmRequest KEREK Jenni Trigger the request See DaqTriggerRequest HERE Wait for complete FERRY Jenni Free allocated memory EA RK status DaqFreeMemory memory_handle memory_pointer if status 0 printf Error de allocating memory Status code d n status DaqCloseDevice logical_device exit status Close the device See DaqCloseDevice EREE H 13 3 13 2 DaqAnalogInput DaqAnaloginput is DAQDRIVE s generic A D converter interface It does not configure any hardware but acts simply to confirm that all parameters are valid and that the type of operation requested is supported by the target hardware unsigned short DaqAnalogInput unsigned short logical_device struct ADC_request far user_request unsigned short far request handle logical device This unsigned short integer value is used to define the target hardware device This is the value returned to the application by the DaqOpenDevice command user request This structure pointer defines the address of an A D request structure containing the desired configuration information for this operation This structure is discussed in detail on the following pages request_handle This unsigned short integer pointer is used to identify this analog input request For a new configuration request_handle is set to 0 by the application before calling DaqAnalogin
279. variables of type real To use the single and double precision variables required byDAQDRIVE the 8087 floating point math mode must be enabled by selecting Options Compiler 8087 80287 or by defining the numeric coprocessor switch N 2 4 7 2 Adjusting the size of the Turbo Pascal heap By default application programs written using Turbo Pascal allocate all available DOS memory for use as a local heap This causes DAQDRIVE to report an error 300 memory allocation error when the application attempts to open a device The user must reduce the size of the application s heap by selecting Options Memory sizes and setting the High heap limit option to a value less than 655 360 640K As a guide reduce the heap by 10 000 bytes for each hardware device to be opened by the application IMPORTANT The user must modify the default Turbo Pascal heap settings to prevent the application from allocating all available DOS memory at start up DAQDRIVE User s Manual 2 19 2 4 7 3 Using other Turbo Pascal versions When using a version of Turbo Pascal other than 7 0 the user must create new unit files TPUs by re compiling the source files DAQDRIVE PAS and DAQDATA PAS These files along with the interface library DAQTSR OBJ are also installed into the DAQDRIVE TSR PASCAL directory by the DAQDRIVE installation program 2 20 2 5 Creating Windows Applications DAQDRIVE supports Windows application programs written in most
280. ve bi include userdata h void far pascal my_event_procedure unsigned short request_handle unsigned short event_type unsigned short error_code switch event_type case EVENT_TYPE_TRIGGER k k process trigger event EE break case EVENT_TYPE_COMPLETE process complete event EERE KE break void main unsigned short request_handle unsigned short status unsigned long event mask Open the device see DaqOpenDevice RARER Request an operation gets a request handle KER ERY x x Define events to be notified BEERS event_mask TRIGGER_EVENT COMPLETE_EVENT Install notification procedure PERE L status DaqNotifyEvent request_handle my event procedure event mask if status 0 printf Error installing notification n k Arm the request See DagArmRequest HEREBY Jenni Trigger the request See DaqTriggerRequest RARER DAQDRIVE User s Manual 11 8 11 4 Monitoring Events Using Messages In Windows DAQDRIVE provides an additional procedure for Windows applications which provides event notification by posting messages to the application window This procedure DaqPostMessageEvent installs a pre defined messaging procedure using the DaqNotifyEvent mechanism discussed in the previous section Therefore DaqPostMessageEvent and DaqNotifyEvent can not both be used on the same request unsigned short DaqPostMessageEvent unsigned short
281. vice command DAC device This unsigned short integer value is used to select one of the D A converters on the target hardware device gain_array This pointer defines the first element of an array of floating point values where the available D A gain settings will be stored The application must allocate the array used to store these gain settings The length of the array is determined by the gain_array_length variable returned by the DaqGetDACfgInfo command DAQDRIVE User s Manual 13 46 include daqdrive bi include userdata h include da8p 12 h unsigned short main unsigned short logical_device unsigned short DAC_device unsigned short status unsigned short i struct DAC_configuration DAC_info float ref_voltage float far gain_array char far device_type DA8P 12B char far config_file c da8p 12b da8p 12b dat Open the DASP 12B see DaqOpenDevice Zei k Get the D A configuration RES J DAC_device 1 status DaqGetDACfgInfo logical_device DAC_device SDAC info k Create an array to hold the gain settings RA gain array _fmalloc DAC_info gain_array_length sizeof float 5 k Get the available gain settings See status DaqGetDAGainInfo logical_device DAC_device gain_array if status 0 printf Error getting D A gain settings Status code d n status exit status Display the available gain settings Ze printf
282. w configuration file using the DAQDRIVE configuration utility End Of File encountered reading configuration file The end of the configuration file was reached unexpectedly If there are no problems with the disk drive generate a new configuration file using the DAQDRIVE configuration utility Invalid configuration file version The configuration file specified in the DaqOpenDevice procedure is too old for this version of DAQDRIVE Create a new configuration file using the DAQDRIVE configuration utility Error loading DLL An error occurred while loading the hardware dependent dynamic link library DLL Verify the drive path and DLL file name are correct 31 35 39 50 51 60 70 Cannot locate the DAQDRIVE DLL open command This is an internal DAQDRIVE error If this error is received contact Omega s technical support department If possible have the hardware device type and software version numbers available when calling Cannot locate the DAQDRIVE TSR driver This error occurs when the hardware specific TSR is loaded before the DAQDRIVE TSR When using the TSR drivers the DAQDRIVE TSR must be loaded before any hardware TSRs DAQDRIVE is out of date The hardware specific driver in use requires a newer version of DAQDRIVE to operate If you did not receive the latest version of DAQDRIVE contact Omega s technical support department for assistance Auto configuration support not available Th
283. ware e g DaqResetDevice Invalid channel number One or more values in the request s channel list is out of range Invalid array length The specified array length is 0 or larger than the maximum allowable array size Duplicate entries in channel list A logical channel number appears in the channel list more than once Each channel may appear in the channel list only once for the type of operation requested Invalid channel sequence The sequence of channels specified in the channel list is not supported by the hardware Consult the hardware specific appendices for restrictions on channel lists sequences Invalid gain The adapter can not be configured for the gain requested Consult the hardware specific appendices for valid gain selections DAQDRIVE User s Manual 14 6 1300 1320 1350 1351 1352 1400 1401 1410 1411 Invalid data buffer length The data buffer must be defined to hold an integer number of scans of the channel list For example if the channel list contains three channels the data buffer must be defined to hold 3 6 9 samples Invalid output value One or more values specified for output is not in the valid range for the corresponding channel s DMA mode data buffer crosses page boundary One or more data buffers allocated for the DMA mode operation span a physical page boundary Data buffers must be contained in a single memory page for DMA use DMA mode data buffer
284. ype of calibration to be performed for this request The calibration methods are dependent on the type of hardware installed Consult the hardware specific appendices for specifics on adapter calibration DAQDRIVE Constant Value Description NO_CALIBRATION 0x0000 No calibration requested AUTO_CALIBRATE 0x0001 Perform auto calibration on this request AUTO_ZERO 0x0002 Perform auto zero on this request timeout_interval This unsigned short integer value defines a time out interval in seconds for foreground mode processes The input operation will abort if the input can not be read every timeout_interval seconds Setting timeout_interval 0 disables the time out function and causes the routine to wait indefinitely request_status This unsigned long integer value provides the application with the current status of the request DAQDRIVE does not rely on the information contained in this field nor does it ever clear any of the event bits to 0 Therefore the application should initialize request_status during the configuration process and may modify its contents at any time DAQDRIVE Constant Value Description NO_EVENTS 0x00000000 This constant does not represent an event status It is provided to the application for convenience TRIGGER_EVENT 0x00000001 When set to 1 this bit indicates the specified trigger has been received COMPLETE_EVENT 0x00000002 When set to 1 this bit indica

DAQ-800

Contents

Download Pdf Manuals

Related Search

Related Contents