Jeffrey
-
Posts
306 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Posts posted by Jeffrey
-
-
This conversation has been moved to private messaging....
-
The DT9829-8 is a popular product. we have no other reports of this so I don't think it is the DataAcqOMNI ._V7.8.9.zip
Perhaps you have a bad download or there is something amiss with that computer/OS.
I recommend you download a fresh copy (https://mcc.download.ni.com/downloads/DTSoftware/Omni-CD/DataAcqOMNI_V7.8.9.zip)
uninstall the software you are now using and try the fresh download, or just as a test try this new download on another computer.
-
Yes they should but I've recently seen when they do not.
This particular customer was not using LabVIEW, he was running an analog input scan using the default options, it was the sample count that was the problem. Once that was corrected, the PLUS version operated without any problems.
I agree with your diagnostics, running some very simplified vis to find the offending function.
-
-
What is the serial number of the bad USB-1808X?
-
-9000 = device not ready.
-9999 = open thermocouple.
What is the serial number of your USB-TC?
-
14 minutes ago, John Brock said:
I don't use the packaged software...
So I'll assume Python on Windows OS.
-
I recommend you run your USB-TC with InstaCal for now, not DAQami.
fyi, it is already on your system, accessible from the windows start menu.
Let me know what the results are and we can take it from there.
-
you need not 'change' to another PC, but I would definitely use a another PC just as a test.
Trouble shooting suggestions:
- run windows update
- run a virus scan
- un-install all MCC software, delete any remaining files and folders.
- use an earlier windows restore point.
- Confirm the USB-2416 use by itself works.
- remove any USB cable extenders
- be sure the USB-2416 is plugged in DIRECTLY to the computer using a USB cable no longer than 3 meters. -do NOT use any external hubs or cable extenders, nor USB ports on a computer's monitor nor docking stations.
Failing that, it would helpful to know:
What version of Windows?
What version of InstaCal?
How does the USB-2416 show up in the device manager?
-
Both devices have the same 2 digital IO "PORTs" FirstPortA and FirstPortB, so it should work.
I say should because we no longer offer support UL for LabVIEW. I cannot install it to test this for you because it would require 32 bit LV and I only have 64 bit.
Perhaps you have more than one copy of cbw32.dll on your system? there should be only one, and it should be found in c:\Program files\Measurement Computing\DAQ for a 32 bit windows OS, or c:\Program files\Measurement Computing (x86)\DAQ for 64 bit Windows OS.
Start your search at C:\ so that you are searching the ENTIRE hard drive.
if you find more than one copy of cbw32.DLL, not found in the locations listed above, I recommend you delete them or at least rename them to something like cbw32.OLD.
-
I recommend you run a single channel scan for just channel 8 and see if that works correctly.
Also, you can use one of our examples such as ulai01 or vin01 as a test just to see how that particular channel responds.
-
we know this version of MCCDAQ.exe (6.74) works with LabVIEW 2022. Please give it a try...
-
Measurement Computing is no longer providing active support for Windows XP embedded. Microsoft terminated support for that OS on January 12, 2016.
It is unfortunate.
InstaCal 5.72 (2007) was released many years before there was a USB-1208FS-PLUS (2012). It was first released in InstaCal 6.24. That version is available for you to try:
https://mcc.download.ni.com/Archive/InstaCal/Archive_6.24/icalsetup.exe
2 hours ago, Rhodes said:Is it possible to configure a USB-1208FS-Plus such that UL LabVIEW treats it exactly like a USB-1208FS?
Sorry no, though they are very similar, there is no way to configure the USB-1208FS-PLUS to be a USB-1208FS.
-
The USB-CTR04 cannot measure analog signals. the inputs can only measure digital, TTL level signals. It can measure the frequency of a TTL level pulse(s).
There are no mcculw (python for Windows) examples for the USB-CTR04, but there are some Python on Linux examples, perhaps those would be of help to you.
Included is an example for period mode. Take the reciprocal of the period and you have the frequency.
There are also examples for pulse counting (aka Totalize mode). You can use the various counter on the USB-CTR04 to implement both of these functions at the same time.
In case you need it, here are:
Link to the User's manual: https://www.mccdaq.com/pdfs/manuals/USB-CTR04.pdf
and Link to the python library help file: https://www.mccdaq.com/PDFs/Manuals/UL-Linux/python/index.html
and Windows UL help file (including Python support): https://www.mccdaq.com/pdfs/manuals/Mcculw_WebHelp/ULStart.htm
-
When was the last time your two FLUKE calibrators calibrated?
One of them must be out of cal, no?
You can send in the UISB-2416 for calibration at our facility, it is NIST traceable.
I would need to start by knowing the serial number of the USB-2416 you want to sent in.
-
DASYLab uses the settings made in InstaCal only.
You cannot override them in DASYLab.
-
You can use the UL functions cbInByte() and cbOutByte() where
BoardNum is the board number in InstaCal,
PortNum is the register you want to read/write for this device that is from hex 300 to Hex 400,
PortVal (for cbOutByte() ) is the value you want to write,
For cbInByte(), the returned value is the contents of the register requested.
You can write your custom cal constants there, but they will not be automatically applied when reading analog inputs.
For more information on using these functions, see the ULHELP file already installed on your system, or https://www.mccdaq.com/pdfs/manuals/Mcculw_WebHelp/ULStart.htm
Sorry, there are no included examples.
-
The default channel settings are all all analog inputs are differential, voltage, 3750 Hz data rate.
-
1 minute ago, robertoweninc said:
If we replace the pair with spares will both be associated in Board0 as before, or will we need to add the AI-EXP32 to the USB-2416 in InstaCal?
if replacing, then new USB-2416 will still be board 0, and the AI-EXP32 will expand the total number of channels shows for the USB-2416.
3 minutes ago, robertoweninc said:Also, using with DASYLab. If we get the pair setup in InstaCal as above, I assume no changes needed in DASYLab, is that correct?
Assuming you set the the channels EXACTLY the same as they were for the older USB-2416 & AI-EXP32, then yes that is correct.
-
To control /monitor the PCIe-DIO96H with free/included software, you can use the Universal Library with a supported programming language as shown on https://www.mccdaq.com/daq-software/universal-library.aspx, see examples ULDI01, ULDI02 for input, and ULDO01, ULDO02 for output.
or try https://mcc.download.ni.com/downloads/example_programs/Diagnostics/DAQWare DIO.msi
Or, you can use DASYLab or LabVIEW (those require an additional purchase).
-
To utilize the digital IO of the USB-2416 series, I recommend you try DAQami. It is free and included with https://mcc.download.ni.com/downloads/MCCDaqCD/mccdaq.exe
Measurement Computing does not offer support for MATLAB. Please contact The Mathworks directly as they wrote their own interface.
-
All you need do is register for your free key here: https://www.mccdaq.com/support/daqamikey.aspx
Then click the "Enter Key", enter your key and you are good to go.
-
Sorry no, there are no plans to support the USB-230 series in Linux.
-
Hello @luigi.abbate
You can use DAQami with the USB-2001-TC to continuously log temperature data without required intervention. Just set it up and let it run. It will acquire data until the hard drive is filled or until you, the user stops it.
DAQami generates binary files in the TDMS (Technical Data Management Streaming) format. there is no automation in the software to continuously convert and parse these TDMS files to csv. That is something you would need to do manually.
A solution would be to use DASYLab (Lite would be adequate) to acquire data and log it to a csv file, and you can set it up to change to a new file every hour or day (at mid night for example).
A Question About USB-1608GX
in Measurement Computing (MCC)
Posted
your source looks good to me.
Though I would make the following changes:
long Options = BACKGROUND + CONTINUOUS + RETRIGMODE + EXTTRIGGER;
Add BURSTMODE. Scans from LowChan to HighChan are clocked at the maximum A/D rate in order to minimize channel to channel skew. Scans are initiated at the rate specified by the Rate argument. So you get the same amount of data in less time.
long Options = BACKGROUND + CONTINUOUS + RETRIGMODE + EXTTRIGGER + BURSTMODE;
Also,
Sleep(100); //means you are looking for a trigger event 10 times per second, but you are expecting new data (retrigger) at 20 times per second, so this is too long a delay.
I would set it to:
Sleep(25); every 25 mS, so you won't miss a trigger.