| Next FAQ Page | Previous FAQ Page |
The following are compiled from the support emails without going through our editing department. Please contact support@dataq.com if you have a quesiton.
1) I wish that the FFT could at least have a linear
option or maybe instead of log
2) My DI-194 doesn't run under XP, any suggestion?
3) The wave shown in WWB has a solid blue area on
top of the wavefor, what is it?
4) We used WinDaq to convert file *.wdq to file
*.prn to perform analysis in a home made software. Recently we
upgraded to windaq pro+ (rev 2.13). However file transformed in
PRN format cannot be used by our home made program and are not
recognised correctly. Any fix?
5) Can the # of y axis gridlines be changed for
easier scaling? Engineering has requested recorded
documentation of a trace with a 500 value / division y
axis. Our full scale setting was 0 - 4000. 8 grid
lines would be preferred, is this possible?
6) I have to extract data from Windaq waveform
browser.After taking the FFT of a selected part of the
waveform,I tried to export the data by using the "output
frequency data" option which is given as one of the
options in the "Transform" tab.But when I
clicked on this option,it gave me four sub-options as to how to
save the data.One of the four options was DB,MAG.Now I know
that Power difference in DB=20 Log(Voltage A / Voltage B)
.Since I am taking the data from only one channel,I don't know
what VoltageA and VoltageB are.I hope u understood my doubt and
hope u will clarify it.
7) I need to use the digital output on my DI-720.
How can I do it?
8) My WinDaq doesn't record automatically, why?
9) I can't use my digital camera after installing
WinDaq/194
10) I don't see 0 when I connect the input to ground
on my DI-194
11) I use Dataqsdk ActiveX with my DI-730. Could you
show me how the gain index associates with the input range.
12) I need to use the DI-154RS for repeatability test
for one of our devices but one thing -Would I be able to
change the cursor time interval to say 100ms? Right now it
is at 267ms and the time grid spacing is at 333ms.
13) I am using DI-200, looking at 2 channels sampling
at 1000/sec. I have waveform A on channel 0 and waveform B
on channel 1. The waveforms randomly switch back and forth
between the two channels. Turning record to standby and
back will trigger it, but it also occurs spontaneously. It occurs
at different sample rates, though I did not observe it at 200
samples/sec. I have a 1+ gigaHz Athlon CPU and 512M RAM so
the computer's speed should not be a problem.
14) I am having trouble finding out of there is an
area under the curve analysis function in your WinDaq v 2.15
software
15) I have installed windowXP from windowsNT and
reloaded the windaq browers from the web. But I'm unable to
find "report" or "peak" when I'm running
calculate.
16) I am having trouble with my AdvCODAS, it failed
to read the WWB file generated by WinDaq/Pro+. Where can I find
the update?
17) Please advise me as to how the
frequency( in Hertz or Khz) of a signal is calculated in the
Windaq software.
18) I have trouble starting my DI-410 under
Windows 95
19) How to modify the date of my Windaq file after it
is generated from .CSV file?
20) My DI-194 doesn't work, please help
21) The font displayed on my WinDaq screen is a big
mess.
I wish that the FFT could at least have a linear option or maybe instead of log
WWB FFT does not have a linear plot option because frequency spectra typically have a strong component that causes the others to plot near the zero baseline. If you want to generate a linear plot of FFT magnitude against freqency, you can use Transform Output FRQ data to export the magnitude data to a .CSV file with Frequency File Type "FRQ DB MAG" for use by a spreadsheet or another program.
If you use a text editor to remove the header information at the start of the .CSV file, you can even open it in WWB in format "2) Spreadsheet print file (ASCII)", converting it to another WinDaq file, entering a phony sample rate equal to the original sample rate per channel divided by the number of points, and units of Hz, DB, Volt. The linear plot would appear in channel 3, with both the TBF value and channel 1 displaying frequency.
My DI-194 doesn't run under XP, any suggestion?
The DI-194 is supported under Windows XP. It does draw some power from the COM port DTR and RTS modem control lines, a little more than a serial mouse. These signals are not activated until the port is opened, and a defective or poorly-designed laptop might not protect these signals against overload.
To determine whether it is a Dataq software problem, unplug the DI-194, click Start, Programs, Accessories, Communications, HyperTerminal. Double click on Hypertrm.exe, and enter DI-194 as the connection name. Click OK, then click the down arrow at the right of the Connect Using box. Click "Direct to Com1" or other port to which the DI-194 is connected, and click OK. Change the Port Settings to read 4800, 8, None, 1, None and click OK. If your computer freezes, perhaps you have an IRQ conflict with another port, such as a modem connected to the Internet or a serial mouse. COM1 and COM3 share IRQ4, and COM2 and COM4 share IRQ3.
Now plug in the DI-194. If the computer freezes, the DI-194 is drawing more power than the port can tolerate. Unplugging the DI-194 may unfreeze the computer if it does not draw too much power. Each DI-194 is tested before it is shipped. Try installing it on another computer of a different type, and if it fails call Dataq for an RMA number to exchange it. If it works on the second computer, try connecting a serial mouse to that port on the first computer (while the power is off, unplugging any bus mouse). If the serial mouse fails, you may want to return the computer if it is under warranty.
If plugging in the DI-194 does not freeze HyperTerminal, you can actually start it scanning from HyperTerminal. Hold down Ctrl while pressing Break, then type S1. If a stream of characters is displayed, typing Ctrl+Break and S0 should stop the characters. If this works, please reply, preferably with a phone number to expedite diagnosis of a software problem.
The wave shown in WWB has a solid blue area on top of the wavefor, what is it?
The blue color area may be removed by unchecking Options Event Marks. However, this also disables the display of Event Marks as spikes in the first channel data at the locations shown by View Event Markers.
If the device remote storage input is not left floating or held high during acquisition when both Options Remote Storage and Options Remote Events are unchecked, the remote control inputs, which are passed to WinDaq in the low order two bits of data for the first enabled channel, are written directly to disk and interpreted as Event Marks on every point by WWB, with the marks going up from the graph when the remote events input is also low, or down from the graph when it is high. To allow Options Event Marks to display spikes where intended, the user must disconnect these inputs when they are not in use. Having the device or WinDaq remove them when not in use would impair the ability to operate at high sample rates.
The waveform may be smoothed by the Moving Average function in our $595 Advanced CODAS software package, which may be invoked from WWB via File Calculate.
Pairs of waveforms from different channels may be displayed overlapped in the same strip using View Format Screen and View Assign Channel, but file you attached only has a single channel. If you want to overlap waveforms recorded at different times, the new Copy Channel function in Advanced CODAS can be used to combine waveforms from different files or acquired at different times in the same file.
We used WinDaq to convert file *.wdq to file *.prn to perform analysis in a home made software. Recently we upgraded to windaq pro+ (rev 2.13). However file transformed in PRN format cannot be used by our home made program and are not recognised correctly. Any fix?
I am assuming that you are using File Save As in format "5) Spreadsheet print (CSV)" to convert the files. Although we have added checkboxes to control some new options, if you check only "Sample Rate" and "Comments" and uncheck the other boxes you should get the same file format as previously.
In WinDaq/EX Playback before V1.36, these files ended with Ctrl+Z as an end-of-file character, but when it was discovered that this caused trouble with the MATLAB software cvsread command, we decided to omit it by default, but provided an option to retain it for compatibility if the setup file CODASPAR.BIN has the least significant bit set in the byte at file offset 3B7 hexadecimal.To enable this option, click Start, Programs, Accessories, Command Prompt and type:
C:\WINDOWS>CD \WINDAQNT (or other folder where WinDaq resides)
C:\WINDAQNT>DEBUG CODASPAR.BIN
-E 4B7 1
-W Writing 02AAE bytes
-Q
C:\WINDAQNT>EXITThis also affects files produced by File, Note.
The normal comma delimiter between values may be changed to a space if setup file CODASPAR.BIN has a 1 insead of a zero in the byte at file offset 305 hexadecimal. Perhaps your software requires a space, and your previous setup file was configured that way. Take a look at one of your old files and one of your new ones with Notepad or another text editor to determine if this guess is correct.If you are getting commas but require spaces, click Start, Programs, Accessories, Command Prompt and type:
C:\WINDOWS>CD \WINDAQNT (or other folder where WinDaq resides)
C:\WINDAQNT>DEBUG CODASPAR.BIN
-E 405 1
-W Writing 02AAE bytes
-Q
C:\WINDAQNT>EXITThis change will also affect files created by File Note, View Statistics, or Transform Output FRQ Data.
Can the # of y axis gridlines be changed for easier scaling? Engineering has requested recorded documentation of a trace with a 500 value / division y axis. Our full scale setting was 0 - 4000. 8 grid lines would be preferred, is this possible?
Since WWB 1.99, Options Grid Spacing allows you to change the spacing between grid lines in pixels, which was previously fixed at 20. Resizing the screen vertically allows you to change the number of vertical pixels in the graphics area, View Format Screen allows you to change the number of strips into which those vertical pixels are divided, and Scaling Limits allows you to set the data range displayed in each strip. A bug in View Format Screen that was fixed in V2.08 caused the grid spacing to revert to 20 pixels, so download a free WWB upgrade from www.dataq.com if yours is earlier that that.
After setting the above items to your satisfaction, use File Save to save them back to the file header. To force all strips have the same number of pixels, make sure that the vertical size is a multiple of the number of strips. If scaling accuracy is important, it should also be a multIple of the grid spacing. Accurate vertical resizing may be accomplished by patching the 2-byte value stored in the file header at offset 12 hexadecimal, least significant byte first. If the file size does not exceed 600 KB, this may be done from an MS-DOS or Command prompt by patching the file using DEBUG, which loads the file starting at address 100 hexadecimal. For example, you can change the vertical graphics size of C:\WINDAQM\SAMPLE.WDQ to 400 pixels (190 hexadecimal) by typing: C:\WINDOWS>DEBUG C:\WINDAQM\SAMPLE.WDQ -E 112 90 -E 113 1 -W Writing 0A125 bytes -Q C:\WINDOWS>
Can the x axis value be changed for easier viewing? Engineering has requested the x axis value to be 00.10 sec /division. The current display is showing 00.08 sec / division. Can this be changed?
The spacing between light horizontal lines is fixed at 20 pixels, and every fifth line is darker to make it easier to count samples. The number of samples per pixel is determined by Edit Compression, with negative values -2 through -10 zooming in to replicate each sample a number of times equal to the absolute value of the compression. To achieve the scale you want, you would have to acquire the file at a sample rate 80% of its current value, or increase it to 160% of its current value and double the Edit Compression setting.
If your acquisition program is earlier than V2.45 and you found it necessary to change Options Grid Spacing in WWB, download an update from www.dataq.com before attemtping the following. To avoid having to repeat changes for each file, in Acquisition use File Open Reference File on a modifed file to make the graphics look that way, and File Save Default Setup to cause acquisition to start up the same way next time. Then files recorded in the future will be ready for viewing.
I have to extract data from Windaq waveform browser.After taking the FFT of a selected part of the waveform,I tried to export the data by using the "output frequency data" option which is given as one of the options in the "Transform" tab.But when I clicked on this option,it gave me four sub-options as to how to save the data.One of the four options was DB,MAG.Now I know that Power difference in DB=20 Log(Voltage A / Voltage B) .Since I am taking the data from only one channel,I don't know what VoltageA and VoltageB are.I hope u understood my doubt and hope u will clarify it.
In FAST FOURIER TRANSFORMS FROM ADVPOST (see above), the paragraph starting with "The default zero decibel reference" explains what Voltage B is. Voltage A is a sinusoidal component of the signal in strip 1 that was transformed. A pure sine wave barely reaching the A/D converter limits at one of the frequencies plotted would be 90.31 decibels above this reference if a DFT is done over an integral number of cycles. Transform Scale DB (Shift+F4) will change the zero decibel reference to the level for the bottom screen crosshair, which is placed on the highest peak by default. This document, which was considered too technical to include in the manual, describes the MS-DOS predecessor of WWB, whose transform algorithms (and accelerator keys where possible) are the same. The mean of the digital signal is subtracted from each input value (before applying the window for an FFT) to optimize the precision of the 16-bit fixed-point transform. The mean value is not added to the zero-frequency magnitude displayed on the screen (for consistency with the decibel value). The mean is added to inverse transforms, and added to the zero frequency magnitude or cosine (but not reflected in the decibel value) when output to an ASCII file.
I need to use the digital output on my DI-720. How can I do it?
Here is the codes extracted from a VB sample.
Private Sub Timer1_Timer()
'Send out the square wave according to Timer interrupt.
'You can reach around 20Hz update rate here.
'The lower 8 bits will go to the Non-Mux side connector if you use parallel interface
'The lower 8 bits will go to the Mux side connector if you use USB interface
If sw = True Then
DataqSdk1.DigitalOutput = 0
Else
DataqSdk1.DigitalOutput = -1
End If
sw = Not sw
End SubNote: If your DI-720 has a built-in USB option, you will lose bit 1, 2 & 3 because it is used in the USB configuration. To re-enable them in parallel port mode, you will have to contact DATAQ for instruction.
My WinDaq doesn't record automatically, why?
The file probably has no data because Options Remote Storage 0 was checked and the remote storage input (Pin 6 on the secondary 37-pin connector with channels 17-32 for a DI-720, or the DI1 input of a DI-205 box connected to it) never went low. The * after RECORD will be become a space when storage actually begins.
Since the DI1 input is pulled up on the DI-2X0 board, it should float high if unconnected because of a bad connection or defective screw terminal. Remove the cable to the startle system and connect your voltmeter between pins 6 and 7 on the back end of the DI-705. If you have a good connection to the screw terminal, you should see your control signal there, or a high signal from the pullup on the DI-2X0 card if you have a bad connection or DI-705 card. Since Options Remote Storage 1 never stores, I am guessing you system is holding that line low, and you also have a bad connection or faulty DI-705 that allows your control signal to still go high at the DI-705. Try using Options Remote Storage 1 with the peripheral system disconnected. If it stores with no asterisk at least when your control signal is high, that would confirm that your system was driving that input low. You can also confirm that the software is not defective by checking Options Remote Storage 0 instead.
I can't use my digital camera after installing WinDaq/194
The only changes our WinDaq/194 installation makes in the registry are to provide in uninstall under Control Panel Add/Remove Programs. It makes no changes to the COM port, and only uses the port number with the -N switch on the Target: command line of the shortcut that launches WinDaq acquisition. I think you can convince yourself that the installation does not affect the port by running it, then downloading images from your digital camera before running WinDaq.
My guess is that the old digital camera software you have been running for years assumes that the COM port will not be used by anything else, while WinDaq sets it to 4800 Baud, 8 data bits, 1 stop bit, no parity, and no flow control. It is modern common practice for each application to open the port, set its state as necessary, and close it without restoring its state. Does the problem you are observing really persist after shutting down and restarting the computer with the camera plugged in instead of the DI-194? If not, updating your digital camera software will probably solve the problem.
I don't see 0 when I connect the input to ground on my DI-194
Common Mode Voltage damage is the number one cause. If you connect a high CMV signal to 194, the resistor will burn out, opening the inputs. As the result, you don't see 0 when you short the inputs to ground.
GainIndex: 0, 1, 2, 3, 4, 5 for input range of 10V, 1V, 100mV, 10mV, 1000V and 100V
The DI-154 time scale is determined by the sample rate, number of channels, compression, and baud rate using the equations:
sec/DIV = 20*(Compression)*(# of channels)/(Sample Rate)
Sample Rate = (Baud Rate)/(20*N)
N is any integer from 1 to 32767.Vertical grid spacing may be set by Options Grid Spacing, but the horizontal grid spacing of 20 pixels per line is fixed to allow two characters of user annotation to fit between any pair of lines. Baud Rate is set to 4800 by default, but if your computer has a FIFO-buffered COM port or sufficient speed you can change it to 9600 by clicking Start, Programs, MS-DOS Prompt or Start, Programs, Accessories, Command Prompt and typing:
C:\WINDOWS>CD \DATAQ
C:\DATAQ>DEBUG CODASPAR.BIN
-E 4BA 80
-E 4BB 25
-W
Writing 00AAE bytes
-Q
C:\DATAQ>EXITYou can then set Edit Sample Rate to 480, after which enabling 3 channels will result in .125 sec/Div, or enabling 2 channels will result in 83.3 ms/Div.
If during disk storage you get a gap count displayed to the right of the "% used" field, the data points affected by the gaps may be found in WWB by selecting channel 1 and using Search Next Mark or Search Previous Mark to locate the downward-going spikes in the channel 1 data. To avoid gaps you can refrain from user activity during disk storage or restore the baud rate to 4800 using the above procedure but entering the values:
-E 4BA C0
-E 4BB 12
I am using DI-200, looking at 2 channels sampling at 1000/sec. I have waveform A on channel 0 and waveform B on channel 1. The waveforms randomly switch back and forth between the two channels. Turning record to standby and back will trigger it, but it also occurs spontaneously. It occurs at different sample rates, though I did not observe it at 200 samples/sec. I have a 1+ gigaHz Athlon CPU and 512M RAM so the computer's speed should not be a problem.
Many modern machines, if they have an ISA bus at all, give their other buses priority over DMA operations on the ISA bus, causing the DI-200 to lose data. When the DMA request is not serviced fast enough, a data word is dropped, the data for the next channel appears in place of that for the current channel, and the rotation persists until another word is dropped, causing the data for all channels to rotate upward again, or become correct when scanning only 2 channels.
Reducing Edit Preferences Maximum Sample Rate sufficiently will solve the problem, but set that value as an upper limit for Edit Sample Rate and reduces its closeness to certain desired values. Minimizing activity on the other buses will help. Disconnect from the Internet and avoid running other applications. If checking Options Pause Graphics allows you to store to a file at the desired rate without channel rotation you can experiment with reducing the graphics traffic through another bus so you can have at least some waveform display. Right click the desktop and click Properties, Settings. Try reducing the number of colors and Screen area. WinDaq requires only 16 colors and 640x480. In WinDaq, make sure Options Oscilloscope Mode is checked instead of Scroll Mode. Resize the window to the smallest you can tolerate. Increase Edit Compression as much as possible. Set Edit Preferences Update Interval to 54 to update 18.2 times/sec, or to 109 to update 9.1 times/sec. Use File Save Default Setup to retain any settings that work.
If you cannot get adequate graphics at your required sample rate, try an older computer. The problem first appeared on a few i486 machines and about 20% of the older Pentiums. You can also call Dataq for a quote on a trade-in for a DI-400 ISA card or DI-720P parallel-port unit, which do not use DMA but can go faster and work with the same DI-205 box. However, WinDaq does not allow the DI-400/PGL to operate at a gain of 1000.
The WinDaq Waveform Browser View Statistics command computes the area under the curve for the selected channel relative to the zero level between the Time Marker and cursor inclusive. This signed value for the selected channel is displayed to the right of AREA in engineering units times seconds. It is equal to the mean value of the waveform over all the data values from the cursor through the time marker (including all the data values comprising the compressed points under the cursor and Time Marker), multiplied by the time difference between the next uncompressed sample to the right of those included in the mean and the leftmost uncompressed sample that was included in the mean).
All statistics values may be copied to the clipboard or written to a file. WWB V2.06 or later, if no channel is selected (after pressing 0), displays no statistics on the screen, but can write statistics for all channels to a file.
If you need to generate a waveform plotting the area under another waveform (such as total flow from flow rate), the WWB File Calculate command can execute our $595 Advanced CODAS calculation package, whose Integral function can accomplish that.
WinDaq Waveform Browser WINDAQ32.EXE looks for CALCU.EXE, the menu portion of Advanced CODAS, in the same folder as itself. As long as CALCU.EXE is is V3.18 dated 6/24/94 or later, it looks in the same folder as itself for PEAK.EXE and REPORT.EXE. If your Advanced CODAS software is older than that, you can work around the problem by adding the appropriate folder to the "PATH=" statement in C:\AUTOEXEC.BAT, or add that statement or create the file if it does not exist. AUTOEXEC.BAT is processed even under Windows XP to set up environment variables. If this does not solve the problem, please reply with a phone number to expedite diagnosis.
If you use Advanced CODAS earlier than V3.23 under Windows XP for other functions, it may refuse to add channels to files which reside on disk partitions with more than 2 GB of free space. You can download an upgrade to install a 32-bit version that also performs better, but if your Advanced CODAS installation password is more than 3 years old, a new one will cost $100.
Even the latest version of Advanced CODAS cannot operate directly on packed files from WinDaq Pro+ which have multiple sample rates, but the WWB File Save As command in format "2) Binary (with CODAS header)" or "8) CALC" will unpack the resulting file, allowing Advanced CODAS to operate on it. Be sure to set Edit Compression to 1 before saving the file to make sure it contains uncompressed data between the Time Marker and cursor position.
Under Windows NT4/2000/XP, your old version of Advanced CODAS will often refuse to add channels to files which reside on disk partitions with more than 2 GB free space. A $100 upgrade to Advanced CODAS will solve that problem by installing a 32-bit version which can operate on files up to 4 GB.
A packed file header differs from that of an unpacked file in that data bit 6 is set at file byte index 101, the byte starting 31 bytes from the start of each channel structure contains its sample rate divisor, and the 4-byte field at file offset 8 specifies the number of data bytes the file would contain if it were unpacked.
The format of the data portion of the file is like that of a Dataq device whose scan list contains different sample rate divisors, but the bit combination 01 in the least significant two bits signifies a compressed point containing both upward and downward going event marks (generated in channel 1 with Options Triggered Mode checked), and the last point in the file contains data values for all channels even if some of the averages represent fewer than the usual number of samples.
WWB can display the frequency of a cycle of a waveform by setting Options Select Marker Display to "Hz for Cycle to Marker". Set Edit Compression to 1 and move the cursor to a well-defined point on one cycle of the input signal by dragging with the mouse in the bottom annotation line, then press F4 to set Options Time Marker until part of this line reads "on Hz (TM)". Then move the cursor to the same point on the next cycle and read the frequency for that cycle in the same part of the annotation line. To average the frequency over several cycles, move the cursor to the same point on the N-th cycle from the Time Marker, then divide the result displayed to the left of "Hz (TM)" by N.
Another way to compute frequency that does not depend on the user deciding where to place the Time Maker and cursor uses the Transform Windowed FFT command. If the "Number of Points=" left set to its default value, the center half or more of the visible portion of the waveform displayed in strip 1 (type 1=C to use View Assign Channel to display channel C there) is transformed to display its frequency spectrum with a crosshair cursor in the frequency spectrum plotted at the bottom of the screen placed on the strongest peak and its frequency displayed at the left end of the annotation line between the top and bottom screen. The dotted cursors in the top screen plot show the limits of the data which contributed to the result, but the Data Window reduces the effect of the data near those limits. Transform Inverse Transform plots reconstitues the input waveform in strip 2, showing the effect of the Data Window. The attached text file ADVPOST.DOC gives further details if you are interested. It describes the FFT and DFT as implemented in the DOS-based playback program ADVPOST.EXE, for which the width of the screen was always was 640 pixels (including left and right annotation margins). The algorithm was ported to Windows leaving accelerator keys unchanged where practical, and WWB produces exactly the same results, but is also capable of windowed transforms of as few as 64 points if the window is shrunk horizontally.
The resolution of the frequency calculation may be improved to less than the adjacent frequency spacing of the frequency spectrum plot by using Transform High Pass Filter to discard everything to the left of the valley to the left of the highest peak and Transform Low Pass Filter to discard everything to the right of the valley to the right of the highest peak. Then Transform Average Power will display the Average Power Frequency, a better estimate of the frequency of the remaining peak.
Generating a waveform proportional to frequency and displaying it along with other acquired channels in WWB may be accomplished using our $595 Advanced CODAS package. By peak capturing the spikes in the frequency channel and using them as an External reset for the Integral of a constant 1.0 signal (with no Time or Zero crossing reset) and Sample/Hold on the integrated waveform, a signal proportional to period (delayed one cycle) may be generated. Before using the Advanced CODAS Arithmetic Operations function to divide a constant 1.0 signal by the waveform of the period channel to generate a channel proportional to frequency, it would be necessary to use WWB File Save As in format "8) CALC" to extract the portion of the file after the first complete cycle on the frequency channel to avoid dividing by zero through the first peak or including bogus data from the period channel held from the partial cycle ending with the first peak, which would adversely affect the resolution of the rest of the frequency channel.
I have trouble starting my DI-410 under Windows 95
If your old DI-410 board was 13.5 inches long and running AT-CODAS software under DOS, it is not supported by WinDaq/Lite. You can press F8 within 1 second of "Starting Windows 95...", boot to a command prompt, and run AT-CODAS software from the Command Prompt before Windows starts if the device is configured for an I/O address range and IRQ which do not conflict with other hardware. In Windows 95 Control Panel, System with Computer highlighted, click properties to locate available resources. After shutting down, setting the jumpers, and booting to Command Prompt only, run CONFIG to configure the software. Try running ADVPOST to look at SAMPLE.WDQ to make sure you do not get a vertical retrace timeout error before running ADVPOST acquisition. You can use WWB inside Windows to review files acquired by AT-CODAS, but AT-CODAS will not run from an MS-DOS Prompt inside Windows.
WinDaq/Lite only supports the new 8.5 inch long DI-410 board that uses DIP switches instead of jumpers for address configuration if chip U30 is installed between the DIP switches and edge connector, or by Plug and Play if there is a square chip in the U29 socket. If an appropriate free range of 8 addresses agrees with the DIP switches (2 and 3 off with the rest on for address 180 hexadecimal), the device should work after uninstalling and reinstalling the software appropriately. In Control Panel, System, Device Manager in the Computer Properties box, the Reserve Resources tab may be used to reserve the address range for the DI-410 against encroachment by Plug and Play devices added in the future.
How to modify the date of my Windaq file after it is generated from .CSV file?
Please download and unzip SETWDQDT.ZIP to the folder where your data files reside and read SETWDQDT.TXT for instructions on using it to change dates and times in WinDaq files. The 32-bit SETWDQDT.EXE is included, along with the source file SETWDQDT.C, makefiles SETWDQDT.MAK (32 bit) and SETWDQDT.MKE (16 bit), and header files. If compiling with 16-bit Microsoft C other than V7, replace the definition of FIX1970 in the source with: #define FIX1970 0
My DI-194 doesn't work, please help
What error message are you getting when starting WinDaq 194? Don't assume that just because you have only one COM port it is called COM1. In Control Panel, System, [Hardware], Device Manager click the + sign to the left of "Ports (COM and LPT)" to make sure WinDaq is not trying to communicate with your internal modem. Click each COM port and click Properties, Resources to make sure the port with the DI-194 does not share an IRQ line with another port that is in use.
Perhaps your laptop does not supply enough current on the DTR an RTS lines to power the device. Click Start, Programs, Accessories, Communications, HyperTerminal. Double click on Hypertrm.exe, and enter DI-194RS as the connection name. Click OK, then click the down arrow at the right of the Connect Using box. Click "Direct to Com1" or other port to which the DI-194RS is connected, and click OK. Change the Port Settings to read 4800, 8, None, 1, None and click OK. A voltmeter between a floating CH1 input and GND should read 3.3 Volt or more. If it is too low, on www.dataq.com/misc, see the end of the section under Serial Device for instructions on externally powering the DI-194RS. If there is enough voltage you can actually start a DI-194RS scanning from HyperTerminal. Hold down Ctrl while pressing Break, then type S1. If a stream of characters is displayed, typing Ctrl+Break and S0 should stop the characters.
The font displayed on my WinDaq screen is a big mess.
In order to interleave annotation characters with graphics grid lines, WinDaq acquisition and WWB both use fixed fonts from file C:\WINDOWS\FONTS\COURE.FON. This is not distributed with our application because it is normally installed as part of Windows. Note that both the folder and file are hidden, but from an MS-DOS Prompt you can list the hidden fixed font files by typing:
C:\WINDOWS>CD \WINDOWS\FONTS
C:\WINDOWS\FONTS>DIR *.FON /A:HIf you are missing this file, please reinstall it from your Windows' CD