Jeffrey

The USB-2637 does not generate time stamps. With very few exceptions no MCC data acquisition device can generate time stamps. However, when setup for hardware paced analog input scanning, the A/D is rigidly timed by the on board crystal oscillator and clocking circuitry. For example, if the USB-2637 is set for a 1 KHz sample rate, you can be assured the A/D is sampling at 1 mS intervals or 1/SampleRate. Knowing this, you can set your switch to be one of your analog inputs along with your other analog inputs. So that when the switch closure is detected (change in measured voltage from 0V to 5V or vice versa), you know that the next sample acquired in your list of channels will be 1/SamplingRate. If you are looking for the difference in time from when the switch state changes and when something else is affected by it, all you need do is multiple the number of samples acquired between the 2 state changes by 1/SampleRate and you have your answer.

Hi Steve, During your InstaCal set up where you select thermistor as the sensor type, there is a 'Help' button under the three boxes where you would enter the values. When you click it, it provides you with a description of where you should get your Steinhart-Hart coefficients, and also a set of defaults you can use to get going: To be clear, they are not coefficients to use with a real thermistor, but they can get you past the learning curve. I recommend you give them a try.

unfortunately not. You will need to upgrade to a newer version. I recommend you upgrade to the latest version: 6.73. it is a free download, available on https://mcc.download.ni.com/downloads/MCCDaqCD/mccdaq.exe

Hello @Ali.H Unfortunately, MCC 172 support is only provided for use on a Raspberry PI computer running the Raspberry PI OS. As the source code is open source, you are welcome to review it after downloading. Best regards, Jeffrey

Hello @ConnorFultz_BIOPAC, As an alternative, please test the analog output with the mcculw example ULAO01.py. this example demonstrates the recommended implementation of a_out(). You can also test with v_out.py. Regards, Jeffrey

Hello @chessicfo Are you looking for a USB-205 compatible hardware paced example for Windows or Linux? On Windows: Please try a_in_sca_background.py or a_in_scan_file.py On Linux: Please try a_in_scan.py. As these are examples, you will need to modify them to meet your requirements with regard to number of channels, samples per channel, sampling rate, and what to do with the collected data. Regards, Jeffrey

Th PCI-DIO24H is a mature design, and has not changed in a very long time. it is based on the PLX PCI 9052 (PLX is now part of Broadcom). Details regarding resources used can be found https://docs.broadcom.com/docs/pci9052Data-Book_v2_1-08Dec08 or see the attached PCI 9052 User's manual. PCI 9052.pdf

1.4 is the latest version. Sorry, there will be no updates.

Hello Walter, Unfortunately, adding annotations are not currently a supported feature of DAQami. I have added annotations to the list of requested product enhancements.

Per the Developer, the IRQ pins on the 128 and 172 (both share GPIO20) are there in case we want to optimize transfers in the future, but we do not currently use them. Perhaps you have another signal present on that pin from something else?

That is the norm. InstaCal does not nor has ever provided digital IO testing for the PCIM-DAS1602/16. Unfortunately there are no 'canned' apps supporting digital IO testing for this board, however using the UL examples you can create your own diagnostic app. To test the DIO on the 37 pin D connector, you would use ULDI04 or ULDI05 for input, and ULDO04 or ULDO05 for output. To test the DIO on the 40 pin header, you would use ULDI01 or ULDI02 for input, and ULDO01 or ULDO02 for output.

I don't see an error. Syntax error is a bad or wrong variable, bad or incorrect tab/spacing, or a type-o of some kind. this same line of code is in the analog_output_write_all.py example at line 103. That line is reporting there was a syntax error, not exactly where it is. I recommend you study or step through the code to find the error. I also recommend you review the example app analog_output_write.py. This example is different than the one listed above as this one is for a single channel output.

for channel in channels: hat0.a_out_write_all(channel, get_input_values) hat1.a_out_write_all(channel, get_input_values) hat2.a_out_write_all(channel, get_input_values) should be: for channel in channels: hat0.a_out_write(channel, get_input_values) hat1.a_out_write(channel, get_input_values) hat2.a_out_write(channel, get_input_values) I don't know if that will resolve your issue(s) but that is the one that stands out to me. if you are getting any other errors, what is the error?

Measurement Computing Application Engineers will answer focused questions on our software and hardware products. As you are a self proclaimed newbie, I offer you the following: Download and install Pycharm community edition, it is free. Along with the DAQHats library and examples, it will fit on your Raspberry Pi with lots of room to spare. Then load the example analog_output_write_all.py, and run it in debug mode so you can step through the example and see exactly where in the code new value(s) are written out to the DACs. The error in the code you sent, was 2 fold. You placed your code in the wrong place, and function call you used, 'a_out_write_all()' does not take the values you entered. That function takes a 1D array ( or 'list' in python) of 2 values. the line of code you are looking for is on line 102 or the original example. Note there is no parameter for channel as that function writes 1 value out to each of the 2 DACs. Don't forget to study the documentation: https://mccdaq.github.io/daqhats/python.html#daqhats.mcc152.a_out_write_all 'Give a man a fish and he eats today. Teach a man to fix and he eats for a lifetime.' I'm teaching you how to 'fish'. Regards, Jeffrey

Hello @Lion Please read this knowledge base article on that topic: https://kb.mccdaq.com/KnowledgebaseArticle50526.aspx. Be sure to configure the input channel of the USB-2416 you plan to use for 4-20mA as differential. Regarding your PT100 RTD, unless you have a signal conditioning module, using the USB-2416 directly with an RTD is not recommended as RTDs require a constant current source a feature not included in the USB-2416. I recommend you check out this doc: https://www.mccdaq.com/pdfs/anpdf/Temperature-Measurement-White-Paper.pdf Measurement Computing does make devices capable of reading RTDs, the USB-TEMP and USB-TEMP-AI (https://www.mccdaq.com/usb-data-acquisition/USB-TEMP-Series.aspx) Thanks, Jeffrey

Hello @Yuji Tanada Unfortunately, MCC does not have 3D cad file for the USB-1608FS-PLUS. All I have: https://www.mccdaq.com/pdfs/drawings/USB-1608FS-Series.pdf Best regards, Jeffrey

Non-volatile EEPROM addressing of the USB-1208FS-PLUS:

Measurement Computing provides you with a host of examples for each type of DAQHat. They are included so that you can edit them to make them do what you want for your needs. When you purchase any of MCC products, It is assumed you know how to create an app or write a program in a supported app. Not only are examples provided by also detailed documentation. For the DAQhats etc the documentation is found here: https://www.mccdaq.com/Manuals I provided you with an additional example demonstrating how to read from 2, MCC 134s for a total of 8 TCs readings. From that example you can expand on it to make read from any number (up to 8, MCC 134s). As stated my my previous post,

The MCC 152 does not have any A/Ds so voltage input is not possible. For the code for analog output, please see the example analog_out_write.py, included in the daqhats software found https://github.com/mccdaq/daqhats

Hello @Pierre-Luc Unfortunately no, UDP or TCP protocols are not directly supported. Access to the E-TC to LabVIEW etc. is only via InstaCal/Universal Library on Windows or via uldaq library on Linux. "The problem I am experiencing is that the device becomes unavailable for another user when using LabVIEW with the universal Measurement Computing library (ULx for for NI LabVIEW)" -That is by design. When MCC's Ethernet devices were being developed, it was decided to lock out any other User's attempting to gain access to the device as they could change the configuration, etc. when the initial user had set it up for their needs. Thinking outside the 'box', you could send the data from the E-TC to a user defined and created database, allowing for other user's to view the data collected by the E-TC.

Hello @elliott.mckee Unfortunately none of MCC's off-the-shelf software provide the ability for that level of control. TracerDAQ and DAQami are made for logging data, they do include some output control but is all done manually by the operator. There is no Linux support for the USB-1616HS series so uldaq is not an option. The USB-1616HS series is only supported on Windows, so you can use the Universal Library in supported language such as VB.NET, C#.NET, C/C++, or Python. Meaning you can create your own app to control the analog output(s) as a function of the analog input(s). Regards, Jeffrey

Per the published spec, update interval is 1 second minimum. That's between reads of the same channel. The example I sent you was based on the single_value_read.py example. When you put it like that, the name of that variable, 'delay_between_reads' is poorly named. it was meant to mean, if you only read one channel repeatedly, you need to wait 1 second between reads. In this case it would really be, read all the channels as fast as the RPi etc can, then wait 1 second before you loop. it is really a 'delay_between_a_scan_of_all_channels', but that's just too long a name of a variable! For you needs, assuming you have the whole 30 seconds, it would loop through all channels, 30 times. You are welcome to try setting a shorter sleep, but you may just get the same data repeated, not updated.

Please see the attached example. regards, mcc_134_x2.py

Please try opening InstaCal again, but not when you have any other software opened, running, or locked up. If InstaCal hangs or gets stuck at the splash screen can be indicative of damaged or less-than-fully-functional USB-TEMP or USB-TEMP-AI. 'Could it be a problem with USB communications?' it is possible. The spec for maximum USB cable length for either of those devices is 3 meters. That is from the USB-TEMP/TEMP-AI to the computer. if you are using any USB cable extenders, USB hubs (powered or not), or various lengths USB-A/B cables so as to pass through bulkheads (for example), I recommend you remove them and just as a test, use a single 3 meter or less USB cable, 1 each to your devices. Please let me know your results. Regards, Jeffrey

Good day @amaningd Your code looks OK to me, Just as a test, I recommend you run our examples: ULTI01.C and VIn01.C I can confirm these 2 example do work correctly using InstaCal/Universal Library 6.73. You can also test your devices functionality using the InstaCal test utility for analog input. If they do not work correctly, please let me know. Regards, Jeffrey