JRys

Support for Raspbian Bookworm and the Pi 5 is still in testing, and no release date has been given.

The MCC 128 uses analog multiplexing to gate each channel, one by one, to the A/D converter. Internally, the input multiplexer (DG508) has a capacitance between each channel. When it switches, the voltage difference from one channel to the next appears as an AC signal and passes through to the next channel. However, as long as the input signal has a low impedance, the charge dissipates, allowing the input signal to charge the input to the correct value before the following A/D conversion. Long story short, do not scan open channels or use resistor dividers. The recommended signal source impedance is 100 ohm or less.

TracerDAQ cannot configure a device for an external TTL clock but will capture data from two USB-1608G. When the acquisition is finished, choose Save As to save the captured data using the CSV format. https://digilent.com/shop/mcc-usb-1608g-series-high-speed-multifunction-usb-daq-devices/

I'm unfamiliar with the CB-7076. However, the CB-7520 is an RS232-to-RS485 converter and was a rebranded device from ICP DAS that MCC sold. There's no software driver because RS232 support is built into Windows. Please get in touch with ICP DAS for additional information. https://www.icpdas.com/en/product/guide+Remote__I_O__Module__and__Unit+RS-485__I_O__Modules+I-7000

Please install the required software from the Omni CD. Then look for the C examples in C:\Program Files (x86)\Data Translation\Win32\SDK\Examples\.

TracerDAQ Pro supports up to 48 channels but only one million samples per channel. Each column in a CSV data file would be a channel and it could have no more than one million rows. The number of channels determines the sample speed. If you're using 16 channels, the high rate is 250k hz divided by 16. You could purchase the USB-1608GX for more speed because it is twice as fast as the USB-1608G. So it would be 500k hz divided by 16. TracerDAQ works with multiple devices but does not have the necessary code to synchronize two USB-1608G devices using the external clock from one to the other. Our DAQami, DASYLab, and LabVIEW support don't either. DASYLab, however, allows the device to be set to use the external clock input to pace the acquisition if you can supply the TTL clock.

There is no mechanism to dump multiple layouts into a single file. You can use a DASYLab Switch and Action module to save or print a layout to JPEG or PNG. There are third party PDF printers that install to look like a Windows printer so that when you print, the print is sent to a PDF. If you can set it up to print to the same PDF, there might be a way to cycle through N number of actions to automate the DASYLab print process.

I have duplicated the Windows 11 crash using QuickDAQ 3.7.0.49 and will report it to the engineering group. Unfortunately, I don't have a workaround other than using Windows 10 or safeguarding the USB cable.

The clamp you have referenced can be set to either 1mV/A or 10mV/A and the output is a 60Hz waveform. The datasheet doesn't say, but I suspect the output signal has higher than typical output impedance, making it more challenging to use more than one. You need a simultaneous 24-bit device with a low input range and can sample fast enough to capture 60 Hz. 24-bit devices use delta-sigma converters that oversample to achieve high accuracy. A side effect of oversampling is that it acts like a low-pass filter to remove unwanted noise. The DT9824 meets these requirements. It comes with the QuickDAQ software; however, consider the DASYLab software because it would provide better control over how data is logged to the file.

The MCC DAQ HAT boards do not come with a ready-to-use software program. Instead, examples are provided for C and Python coding. Therefore, I would recommend some programming experience and familiarity with the Linux operating system. If you're comfortable with C, our MCC-118 data logger example displays a couple of channels graphically and saves the data to a file.

The digital IO is controlled strictly by software -there's no hardware pacing available.

We have an example that demonstrates using the device without having to run InstaCal. It is DaqDevDiscovery01, in the following folder: \Public\Documents\Measurement Computing\DAQ\C\Sample32\. If you lack examples, reinstall InstaCal from our CD download. You will still need to install InstaCal because that is how our drivers and DLLs are installed.

The QuickDAQ software has two upgrade paths, the FFT and the Advanced FFT option. To try out these features, we enable them for two weeks after the initial installation. Purchasing the FFT Analysis option will enable the digital filter. The datasheet shows a breakdown of the features.

I'm glad to hear that it's working.

Here is a LabVIEW vi (attached below) that maintains a one minute buffer (6,000 scan at 100 Hz) that is constantly being updated with new data. It always has the most recent data. A loop counter counts to 6000 x 6 to enable the file write operation. Therefore, every six minutes, one minute of data is written to the text file. After one hour, the file holds 60,000 rows of data. CircularBuffer.vi

DAQami has not included support for the encoder channels (ctr 2 & 3). Please consider upgrading to the DASYLab software for support. If you know the C or Python languages, you could create a custom program, too.

Yes, they can be configured individually. When configured for thermocouples, use the 50 or 60 Hz Data Rate filter for best results. Use InstaCal to configure the channels unless you use the DAQami software.

Calibration reports, as well as data, were kept from being made available. Some customers do require data to meet specific requirements. For those, we recommend sending it to a calibration facility for verification with data.

AGND and GND are connected internally on the USB-1608GX. To minimize ground current noise, AGND is routed to keep digital switching ground noise away from sensitive analog measurements. For example, you could control a relay using a transistor to sink current. The transistor should be connected such that current flows into the GND ground trace. What little current flows from analog input signals will use AGND, and then both GND and AGND combine and are connected to the USB ground.

There is much more to making it work than just including the mccdaq.dll. There's also the cbw32 and cbw64 dll, and you need to be able to install a device driver. Instead, leave the mccdaq.dll out and compile the program to an exe. On the target PC, install InstaCal first, and then your program should work. If the program does not use device discovery, then also run InstaCal with the USB-201 attached so that it gets added to the board list. Lastly, delete any mccdaq.dll files that you may have installed previously. Our files should be in one place only, and that is C:\Program Files (x86)\Measurement Computing\DAQ\.

The requirement to use the MCC 134 is a Raspberry PI 3 or 4, and the Raspbian OS. We have not released support for the Bookworm version, so Bullseye is recommended. For Ubuntu, you could use our Linux driver, uldaq, and one of the supported USB devices, like the USB-TC. https://github.com/mccdaq/uldaq

MccMinilab.dll is not an MCC library file. It's likely from another company that built a software product around miniLab-1008.

The manual Labeling drop-down setting displays the current date-time on the axis. The Manual Label check button sets the label spacing. The only options are block number, seconds since measurement start, time, and date-time.

To find out what Raspberry PI resources are used by the mcc172, review the Interface Specifications section in the following datasheet: https://mccdaq.github.io/daqhats/_static/esmcc172.pdf

This is the closest one I could find: https://www.phoenixcontact.com/en-us/products/solid-state-relay-module-emg-17-ov-ttl-24dc2-2943259?type=pdf As shown below, you could also use a MOSFET transistor to control a solid-state relay.