Jeffrey
-
Posts
306 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Posts posted by Jeffrey
-
-
Hello @jpezaris
Unfortunately, InstaCal does not show or have tests for all features of MCC supported devices, and never has.
I see the same as you with a PCIe-das1602/16 installed on my system. There is no digital diagnostic test.
You could use the Universal Library examples ulDI01, ulDI02, ULDO01 and ULDO02 to create your own test apps.
Or, if you just need to test the digital IO as inputs, you can use TracerDAQ.
-
As stated above, no.
The original thinking was User's would use several sensors with the same scaling for the same, custom units. So same multiplier and offset would be applied to any other channels you set to those particular custom units. That was the intent. But thinking beyond that, if you select a different label for your units, you can apply a different offset and multiplier for each channel. At that point you just need to remember the temperature scale you want to use. such as "F"
-
You can apply a scaling multiplier and/or offset for each channel in DAQami.
The default is degrees C. Click on the drop down arrow for Units, and select Custom, the following update to the screen appears.
Once you enter a new label for your units (sorry it cannot be "⁰C" nor the same for all channels), you can enter a multiplier and/or offset to correct for your temperature standard.
-
I recommend you get another computer, one that has not seen an MCC product.
Download and install the mccdaq.exe software, in particular DAQami.
DAQami has a function generator output. I'm using the defaults but set the waveform to sawtooth:
With the USB-1808X configured for single ended analog inputs, I attached a wire from CH0H to AOut0.
I have also sent this analog output of AOut0 to my scope. It shows this:
If you cannot get a similar response from your USB-1808X then it is not operating properly for some reason, yet to be determined.
What are your results?
-
Hello @Mussa
8 minutes ago, Mussa said:MCC 172 measures the voltage of the IEPE sensor, right?
As it states on the webpage, "The MCC 172 is a two channel DAQ HAT for making sound and vibration measurements from IEPE sensors like accelerometers and microphones," so yes.
9 minutes ago, Mussa said:How to convert this data into acceleration and velocity?
The MCC 172 measures voltages over time. Assuming the voltage is some sort of distance or speed measurement...
I recommend you look at the example finite_scan for the MCC 172. It will demonstrate how to set up the MCC 172 for hardware paced data collection. In this example, note the sample rate is 10,240 Hz, meaning a new sample will be acquired every 1/10240 seconds or 97.6 microseconds (or uS). Knowing that, you can calculate acceleration from rate x to rate y by finding the data indexes for X and Y voltages in the collected data, then count the number of samples collected between X and Y. or stated another way, find the data index for Y and subtract the data index for X. This will tell you how many samples it took to get from voltage X to voltage Y. Multiply the resulting difference by 97.6 uS, and you will have how long it took to get from voltage X to voltage Y.
The same is true for velocity. In this scenario, each voltage measured will equate to a certain distance traveled as stated in the data sheet of your IEPE sensor's spec. You would then add the successive samples for a particular number of samples to provide you with a distance. The time is the number of samples * 97.6 uS.
Regards,
Jeffrey
-
Hello @rrojas
The USB-2416 has no components you can adjust for calibration.
According to our records, USB-2416 with serial number 1F5C19B was originally purchased in February 2021, and was later sent in for calibration in December 2021.
That last calibration was all most a year ago. MCC recommends you send in your USB-2416 for a yearly calibration cycle.
If you would like to send it in, please let me know and I will generate a price quote for calibration of your USB-2416.
-
Hello @Saravanakumar
I'll need to know what your "chirp" signal looks like on an oscilloscope. In particular I'll need to know the amplitude and duration of that signal.
Are you looking to capture the chirp or is that just your trigger?
Thanks,
Jeffrey
-
Hello @rrojas
Some questions to help me understand your setup...
What is the serial number of your USB-2416?
What type of thermocouple are you using?
Did you allow the USB-2416 the recommended 45 minute warm up time?
What are you using as a standard, that is telling you the USB-2416 is 8 degrees (C or F?) out of tolerance?
Going forward until this issue is resolved, with regard to software please just use InstaCal and its built in tests.
Regarding the USB-2416 settings (as found in InstaCal). For each channel you have configured for Thermocouple, what is the data rate you have selected? The recommended data rate setting:
60 Hz is recommended to help filter out AC line noise for the very low voltage signal of a TC. Do be sure to set each Thermocouple channel's Data Rate to 60 Hz. For more information on why this setting is important, please see the User's manual, https://www.mccdaq.com/pdfs/manuals/USB-2416.pdf, page 16.
Regards,
Jeffrey
-
Responded via private message
-
Hello John,
Thanks for asking.
DASYLab is a per seat license. You are granted to run your DASYLab license (key) on one computer at any given time.
if you need to run DASYLab on 2 computers then you need to licenses (keys).
Regards,
Jeff
-
And please answer this:
On 11/14/2022 at 10:00 AM, Jeffrey said:Also, please send the output of “uname -a” so we can see if they are running the 64-bit OS.
-
The demo version is the REAL DASYLab Pro release. The only thing "Demo" about it is that it only runs for 2 hours at a time, and it stops working after 28 days unless you enter a valid key.
-
Hello @banksey255
I created a test vi using USB-2416-4AO and LabVIEW 2022 (only version I have installed), followed by converting it an .exe, then a LabVIEW Build spec for deployment.
I followed the steps listed in the ULx for NI LabVIEW help to create a Windows Installer.
Finally, I deployed it to a computer that has never seen a LabVIEW install nor deployment.
As you can see, the channels are shown.
Perhaps you did not right click on the physical channels.vi on the front panel, and select Data Operations >> Make current value default before you saved your vi and went through the process above?
-
Good afternoon John,
Sorry, that is not a service MCC offers.
Regards,
Jeff
-
Response sent via private messaging.
-
Also, please send the output of “uname -a” so we can see if they are running the 64-bit OS.
And check is if you are logged in as a user other than “pi”. The os may not add other users to the gpio group by default.
-
please send your exact OS image so we can check it for any issues. Also please send the output of “cat /etc/rpi-issue”.
-
I sent this on to one of our DAQHats developers, here is his response,
"I found another thing that returns early on bullseye (the dtoverlay command to load the i2c-gpio driver to create the I2C bus for reading the EEPROMs) so I modified daqhats_read_eeproms some more to wait for that to complete. I left the revision at 1.4.0.6 and just changed the command on github.
Have the user download and install this latest version, it should fix the eeprom issue.
For the single value read, have them run “~/daqhats/examples/c/mcc118/single_value_read/single_value_read” as the standard user (not sudo). If that does not work right, we need to see the complete output (cut & paste from the terminal, etc.)"
Please give this a try.
-
-
11 hours ago, banksey255 said:
I have built the application using LabVIEW 2019 SP1 64-bit, then deployed it to the computer connected to the hardware by building an installer.
This is a different problem than what you originally asked. This is a deployment.
The answer to this is found in the documentation installed with LabVIEW. Open you LabVIEW 2019, from the top menu, select Help >> ULx for NI LabVIEW Help...
The ULx for HI LabVvIEW Help appears.
Open the help book, "Distributing a ULx for NI LabVIEW application," and follow the instructions found on the two topics.
-
Assuming the board numbers in InstaCal are the same on new and old computers alike, just copy the worksheet from old computer to new computer, and run it.
This assumes the worksheets were not corrupted. I have no way to know until you test them.
-
Hi John,
With InstaCal and DASYLab completely closed.
Run the DASYLab Configurator, click on the Packages tab, and expand the Data acquisition tree.
If Measurement Computing driver is NOT checked, then check it, click on "OK" button and follow the on screen prompts. Now run DASYLab and look in the Inputs/Outputs folder. Do you see the MCC-DRV folder? Can you add an Analog input module to the worksheet and configure it for your MCC device? if yes, then you are all set.
If Measurement Computing driver IS checked, then un-check it, click on "OK" button and follow the on screen prompts. When it completes, run the DASYLab configurator a second time, click on the Packages tab, and expand the Data acquisition tree. Select/check the Measurement Computing driver, click on "OK" button and follow the on screen prompts. When it completes, run DASYLab and look in the Inputs/Outputs folder. Do you see the MCC-DRV folder? Can you add an Analog input module to the worksheet and configure it for your MCC device? if yes, then you are all set.
-
I was able to get hold of one, here is what works:
This example shows getting 2 channels each (temperature and voltage)
-
13 minutes ago, jp07 said:
Concerning the de-bouncing issue, is there any software solution that can be integrated? - e.g. function in the MCC Universal Library (C#) that can solve this issue?
There is no built in feature to 'tame' debounce, nor a UL library call. It must be done externally.
22 minutes ago, jp07 said:Does MCC offer any other boards/devices with the capability to do interrupts?
The only modern product we offer with interrupt support is the PCIe-DIO24.
https://www.mccdaq.com/pci-data-acquisition/PCIe-DIO-Series.aspx
There is a UL example: ULEV01 for VB.net and C#.net
Updated to DasyLab v16 and now USB_2408 isn't recognized via Instacal
in Measurement Computing (MCC)
Posted
Hello @IMANNA
That is not InstaCal. What you are showing in your post is the list of boards shown by DASYLab.
You launch InstaCal by clicking Start >> scroll to the "M's", open the folder for Measurement Computing >> InstaCal.
Does your device show up there?
if not, then perhaps you need to update your version of InstaCal. You can download it from https://mcc.download.ni.com/downloads/MCCDaqCD/mccdaq.exe
The current version of InstaCal is 6.73