Samuel Alpha Gian

Hello everyone, I am using MCC Board models 172 and 128 on my Raspberry Pi for a project. I have recently attempted to integrate a digital sensor that communicates via SPI. Unfortunately, I've encountered what appears to be a conflict that affects the performance of both the sensor and the MCC boards when they are used simultaneously. Technical Details: MCC Boards: 172 and 128 Sensor: Digital, communicates over SPI Raspberry Pi Model: Raspberry pi 4 model B Questions: Has anyone experienced similar issues with using SPI-based devices alongside MCC boards on a Raspberry Pi? What are the best practices for managing multiple devices on the same Raspberry Pi to avoid conflicts, particularly involving SPI? Are there specific configurations or modifications to the board setup that could prevent these issues? I am looking for any advice or suggestions on how to manage these devices together without interference. Insights from those who have navigated similar challenges would be greatly appreciated.

Hello everyone, I have an important update regarding the issue I shared previously about inconsistent voltage readings from my MCC 128 device when using the continuous_scan.py Python script. After more tests, I decided to connect four channels to four different voltage sources. Surprisingly, both the DAQHats application and the Python script are now providing accurate and consistent readings across all channels. Here are the details: Test Configuration: Connected four channels to separate voltage sources. Results: Accurate readings from both the DAQHats app and the Python script across all channels. Attached Screenshots: Showing the results from both the app and the Python script. Could anyone help explain why there were discrepancies in the readings with fewer connected channels? It seems that the device or software behaves differently based on the number of connected channels. Any insights or similar experiences would be really helpful! Thank you all for your continued support and looking forward to your responses!

Hi everyone, I'm currently facing an issue with my MCC 128 device when trying to read voltages in differential mode from a function generator with an amplitude of 4 Vpp. When using the DAQHats app, everything works as expected, and the voltage readings are accurate. However, when I switch to using the continuous_scan.py script for continuous scanning in Python, the readings are incorrect. . Here are the specifics: Mode Used: Differential Function Generator Output: 4 Vpp Expected Behavior: Voltage readings should match those shown in the DAQHats app. Observed Issue: Voltage readings are inconsistent and incorrect when using the Python script. Has anyone else encountered this issue? Any advice on how I might be able to fix this? It seems like a configuration or software-related problem.

Hello everyone I am currently using a setup that includes two MCC 172 boards and one MCC 128 board. The MCC 128 is set to differential mode with a scan rate of 5,000, and the MCC 172 boards are configured with a scan rate of 50,000. Despite this configuration, I am experiencing frequent buffer overruns. Could you please provide guidance on how to effectively manage and configure these boards to prevent buffer overruns? I am particularly interested in any recommended settings or adjustments that would allow continuous data recording and storage on an SD card without losing data integrity due to these overruns. Thank you for your assistance. Samuel Alpha Gian code : ch = [1, 2, 3, 4, 5, 6, 7, 8] channels = [0, 1] channel_mask = chan_list_to_mask(channels) channels_128 = [0, 1, 2, 3] channel_mask_128 = chan_list_to_mask(channels_128) samples_per_channel = 0 options = OptionFlags.CONTINUOUS #Einstellung scan_rate_172 = 50000.0 scan_rate_128 = 5000.0 read_request_size_172 = int(scan_rate_172 * 0.01) # Increase this value to read more data in each call read_request_size_128 = int(scan_rate_128 * 0.01) # Increase this value to read more data in each call sensitivity_ch1 = 10.99 * sqrt(2) #board 0 ch 0 in mV/ms^-2 sensitivity_ch2 = 10.75 * sqrt(2) #board 0 ch 1 in mV/ms^-2 sensitivity_ch3 = 10.55 * sqrt(2) #board 1 ch 0 in mV/ms^-2 sensitivity_ch4 = 37.0 * sqrt(2) #board 1 ch 1 in mV/ms^-2 duration = 600 #in seconds (maximum 600 seconds for 1 GB file size) iepe_enable = 1 #Einstellung MCC_128 input_mode = AnalogInputMode.SE input_range = AnalogInputRange.BIP_10V hat0.a_in_scan_start(channel_mask, samples_per_channel, options) hat1.a_in_scan_start(channel_mask, samples_per_channel, options) hat_128.a_in_scan_start(channel_mask_128, samples_per_channel, scan_rate_128, options) start_time = time.time() while time.time() - start_time <= duration: read_result0 = hat0.a_in_scan_read_numpy(read_request_size_172, timeout) read_result1 = hat1.a_in_scan_read_numpy(read_request_size_172, timeout) read_result_128 = hat_128.a_in_scan_read_numpy(read_request_size_128, timeout)