Jeffrey

Hello @Neil BLT Unfortunately uldaq for Linux does not include support for the DT9813. Here is a link to all the devices supported through uldaq for Linux: https://www.mccdaq.com/PDFs/Manuals/Linux-hw.pdf Regards, Jeffrey

Hello @Jim Bertrand I recommend you download and install the MCCDAQ software found on the download page: https://www.mccdaq.com/Software-Downloads (first item on the page). Install InstaCal and DAQami. Attach your USB-2416, run the software. Here is a link to the MCC DAQ software quick start: https://www.mccdaq.com/pdfs/manuals/QS-MCCDAQ.pdf if you want to use DASYLab, then you must first run the DASYLab Configurator to install the MCC DRV drivers. Here is a link to the Quick start for "Using DASYLab with a Measurement Computing DAQ device: https://www.mccdaq.com/PDFs/Manuals/QS-DASYLab-MCCDRV.pdf Regards, Jeffrey

Hello @Francois Ouellette, I recommend you set one task to external clocking and the other task to internal clocking. Since input follows the output, I would set/start the input task with external clocking so that it waits for the output task to start first. you will need to install a physical wire (not a virtual one ) from the USB-1808X's OCLKO to ICLKI prior to running your vi, starting the output task then the input task. If that does not resolve it for you, then please save a copy of your vi, and then strip out anything not required for me to see to the issue you are referring. Regards, Jeffrey

Hello @Vishank Battar I'm struggling to read the print in the picture. Is that a warning? because if it is then it is not a problem, just a warning. In this case, warnings can be ignored. if it is not a warning. then: What is your computer's OS (windows what version)? What version of InstaCal do you have installed? What version of the MCCDAQ.exe download did you install? What MCC hardware are you using? Thanks, Jeffrey

Keep in mind, the MCC 152 is not capable of streaming output data at a uniform rate. There is no analog output scan function for this device. Instead you must manage the clock timing on your own. The main algorithm for generating a sine wave and writing out each value as generated: for i = 0 To (360- 1) OutputValue = MaxAmplitude * Sin((i * (2 * PI / 360))) + DCOffset //'# create a sine wave in 2PI radians . mcc152_a_out_write(address, 0, AoOptions, OutputValue) Next Where: MaxAmplitude is the max voltage out for your sine wave, such as 5V peak to peak sine wave. DCOffset is where you want the 'zero crossing' level to be. Normally it is set to 0. I ran some benchmarks of my own for the MCC 152, outputting alternating 0V and 5V as fast a possible. Or in other words, the app I used toggled between 0V and 5V on one channel, doing nothing more that that. It did not display anything on the screen because that would slow down the output update rate. My results: C/C++: 56.4 k writes per second. python 3.x: 33 k writes per second. givens: Raspberry pi 3B GNU C and CodeBlocks. Your results may vary. Having stated that, and using the C test result, the maximum sine wave you can output if you use 360 distinct points (of the sine wave): Max Freq = 56,400 writes per second / 360 points per period Max Freq = 151.6 Hz sine wave. "Is it possible to output a higher frequency sine wave (ie make it go faster)?" Yes, but the sine wave form may suffer. You can decrease the number of points per period from 360 to 180: for i = 0 To (180- 1) OutputValue = MaxAmplitude * Sin((i * (2 * PI / 180))) + DCOffset //'# create a sine wave in 2PI radians . mcc152_a_out_write(address, 0, AoOptions, OutputValue) Next Applying the same math, you can output a 303.3 Hz sine wave. but keep in mind it will look a bit like a staircase. Or, at 90 points per sine wave period : ~606 Hz. You can continue to reduce the number of points per sine wave period, but when you get to < 60 points per period, it no longer looks much like a sine wave. Note: the MCC 152 outputs values statically, i.e. one at a time. if you look at the values on an oscilloscope, you will see individual DC levels. Should you prefer a smooth sinewave you will need to add some filtering or smoothing. Easiest way to do that is with RC filter. While the MCC 152 is capable of outputting periodic signals, that was not the designed intent. the designed intent was to just output DC level signals, it just so happens you can change the DC level at a fairly robust rate. So if you want to acquire data using the MCC 128 AND output a sine wave, you will see lags in the sine wave when you are servicing the MCC 128 (to off load data or make decisions on the collected data). Regards, Jeff

Hello @Youmin, Yes, you can use MCC 172's and MCC 128's at the same time on one RPI board. Neither of those have analog outs. Perhaps you are referring to the MCC 152?

Yes that is very do-able from the same app/script on one raspberry Pi. No, it will not 'mess up' the GPIO. Here is a link to the GPIO pin definitions for MCC RPI hats: https://kb.mccdaq.com/KnowledgebaseArticle50812.aspx Regards, Jeff

moving this conversation to private forum messaging.

This message will be responded to via private forum post...

Hello @JG2222 I understand this is the internal DIO test, but this test must be done with nothing connected to the digital IO. Please confirm this is how you performed the test, or if you did not, please repeat the test with all external connections removed. if it still fails, the please provide the devices serial number. Thanks, Jeff

Hello @Vishank Battar Unfortunately, you do need to have access to the hardware to add the devices to InstaCal and then to use them in LabVIEW. Regards, Jeff

This conversation is being moved to a private message.

This conversation will be continued via Private messaging.

Hello @Clay Measurement Computing does not provide our products' schematics for any reason.

Hello @Nathan Kumar Unfortunately, Measurement Computing only provides support for the PCI-QUAD04 when used on Windows OS. We do not provide drivers nor support for INtime. You are welcome to use the 3rd party drivers provided by Warren Jasper on Github: https://github.com/wjasper/Linux_Drivers if you have any issues using his driver please contact him directly, his contact information is listed on the above gibhub.com page.

As requested... Vendor_Questionnaire_COV_Info_MCC_172.docx

Hello @Thomas Beaumont As an option, you can use the PCIe-DIO96H with a C100FF-5 and 2x CIO-MINI50's. Those items will not be going EOL. If you would still like to return them, please contact one of our Sales Engineers to discuss, at 508-946-5100.

This thread will be continued with LSI_Lab in private forum messaging.

Hello, "Is there a reset?" There is no reset button or option other than to unplug the unit from the USB connector, external power if used, unplug the screw terminal headers, and let it settle out (give it a couple of minutes), then re-attach the headers, USB and external power if used. I recommend you test your USB-1616HS with InstaCal's Loopback and scan tests. If that does ntot resolve the issues you are having, what is the serial number of your USB-1616HS?

What is the make and model number of your PMT or photodiode?

yes, that will work nicely.

The reason you see a voltage on unterminated inputs is due to the design requiring an active front end circuit. A/D converters can only make measurements within the limits of their power supplies. The MCC 118 is powered by 5VDC and ground. To make it operate and make measurements within the range of +/-10V, an additional circuit is added to the front end. The only side effect is when the inputs are left to float, they read 1.75ish VDC. if you short the input to ground it will read 0.0 VDC. This is similar to the design of our USB-1208FS-PLUS and USB-1408FS-PLUS, in that when the inputs are left unterminated, they float to ~ 2.4 VDC. Sorry, schematics even partials are not available.

Hello @TomE Yes that is a feature of the Pro version of TracerDAQ. However, you cannot acquire 12 channels of temperature data using thermocouples using the USB-2408 and USB-1208LS. When used with thermocouples, the USB-2408 can be configured for only 8 channels. The USB-1208LS cannot be used with thermocouples, it has insufficient resolution, does not have a +/-78 mV range (required for thermocouples) and does not contain any CJC sensors.

Measurement Computing does not offer a recommendation for Raspberry Pi version, nor the amount of on board RAM. However, I have successfully used models version 3, 3B and 4B with MCC DAQHats. I have found the newer models such as the Raspberry Pi 4B is my preferred model with 4 GB RAM. My reasoning has nothing to do with MCC DAQHats performance, but rather the software development packages I can fit on the device. For development I use PyCharm and CodeBlocks for Python and C respectively. Both IDEs fit comfortably on the RPi 4B, with room to spare for all the misc. files I use and/or generate.

Hello @ddavis, The Instacal tests (both loopback test and scan test) are my go to's when I don't know if a board is not functioning properly. The picture you provided for the Scan test, sums it up for me. The device is not responding. There is either a problem with the PCI-DAS6013 or there is a problem with the computer. First questions: What version of InstaCal are you running (click on Help >> About InstaCal, to find the installed version)? What version of Windows are you running? Once I know this, I can better help you. Regards, Jeff