Jump to content
  • 0

Issue with Continuous Scan Using Python in MCC 128


Samuel Alpha Gian

Question

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.
image.png.12ac9d14436bb80328c30e8a2f39d4fa.png
However, when I switch to using the continuous_scan.py script for continuous scanning in Python, the readings are incorrect.
image.png.26838e3850b95b3515ba35a2aef7b9ef.png.

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.

Link to comment
Share on other sites

2 answers to this question

Recommended Posts

  • 0

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.
image.png.e3a714bc320a891bdd5cce203fb55c65.pngimage.png.30dbdddf7ac285892b4f8629218fe764.png

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!

Link to comment
Share on other sites

  • 0

The MCC 128 uses a multiplex scheme to switch each channel to the A/D converter for the measurement. The multiplexer IC chip is nothing more than a bunch of analog switches firing in rapid succession. However, between each switch is some capacitance that allows for a stray charge to transfer to the next channel. The stray charge is not a problem when the input is connected to a low-impedance source, like a function generator. Open or unconnected channels have high impedance, so the charge hangs around and appears as stray voltage. In short, turn off unconnected channels or connect them to the ground pin. 

The MCC DAQ HAT Manager reads each channel using a_in_read(), whereas continuous_scan.py uses a_in_scan_start(), which results in faster channel switching and different amounts of stray voltage. 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...