fpandpf

Thank you, Fausto.

Any inputs from MCC staff? thank you!

Hello MCC Folks, I am currently using MCC DAQ HATs for data acquisition with a Raspberry Pi, and they have been working well for my project. However, I am exploring the possibility of using these HATs with other single board computers (SBCs) that might offer different features or performance advantages. My question is: Has anyone successfully used MCC DAQ HATs with any SBCs other than the Raspberry Pi? If so, which SBCs have you used, and what was your experience in terms of hardware and software compatibility? I'm particularly interested in knowing about any necessary software adaptations or modifications that were required to get everything working smoothly. I appreciate any insights or recommendations you can provide!

Thank you, Fausto. Below is my understanding, let me know if it is correct. If the HAT's SPI frequency is limited to, for example, 4 MHz, the Raspberry Pi will set the SPI bus speed to 4 MHz when communicating with that HAT. Even though the Raspberry Pi's SPI bus can operate at speeds up to 125 MHz, it will adhere to the 4 MHz limit set by the HAT to ensure reliable communication. Is my understanding correct?

Thank you for sharing the document, Fausto! Do you think the Raspberry Pi 5 will have a higher throughput?

Hi, I've been using mcc128 hats for data aquisition, but as I increase the total number of hats to 4. My data aquisition code will encounter overrun error more frequently. Hope to get some suggestions to solve this issue. My setup: Raspberry Pi 4 with four stacked MCC 128 hats, all of them were read with sampling rate of 100 kS/s in continuous mode, and data were saved every second. All hats were were synchronized by connecting the CLK pins together and using flag EXTCLOCK. For the function a_in_scan_start(channel_mask, samples_per_channel, sample_rate_per_channel, options), i set the samples_per_channel = 100k, sample_rate_per_channel=50k (my understanding is this parameter is only for buffer size). Now after start my data aquisition code with the set up described above, I usually encountered the buffer overun error or hardware overrun in a few minutes. However, when I had the 3-hats setup (one hat less than the current setup), such issue was much less frequent, I usually see a buffer overrun error after tens of hours. Could anyone share insights on why i am seeing such error for 4 hats setup while no issue for my 3 hats setup? Also, can someone explain in detail what exactly buffer overrun and hardware overrun errors are? what's the difference between those two errors? Thank you!

to add on this, i just found out when OptionFlags.NOSCALEDATA is enabled, the returned reading are actually not integer (see below), actually has one decimal 51323 51329.1 51290.3 51285.2 51307.7 51305.6 51293.4 51292.4 51332.1 51335.2 51338.2

Hi, i am using mcc-128 hat, I would like to record the data in 16 bit integer with OptionFlags.NOSCALEDATA enabled just to redece size of the file, 16bit integer instead of 64bit float after conversion to volts. for example: if the input range is selected to be -/+ 5v voltage_resolution = =10V / 65536= 0.00015258789 V=(adc_value - 32768) * voltage_resolution Just want to make sure that's how you convert it to volt as well if OptionFlags.NOSCALEDATA is not enabled? Thanks for your time.