Joshua_W

I am using a raspberry pi 4B on Raspbian 11. I rm'ed all the files in that directory and than ran the command again. It regenerated all the files that I deleted. Another interesting side affect is that 2 MCC's are unable to sync clocks if one is in master mode and the other in slave. Regardless of which one is which, but are both able to configure their clock locally.

I tried moving all the eeproms_#.bin 's to another location and there is nothing to my knowledge that is communicating with the hats. I then again tried running 'daqhats_read_eeproms" and again it lists that it is connected to boards 0-7. Oddly enough however, I then call 'daqhats_list_boards' and it reports that there are 0 boards connected. I also tried uninstalling and reinstalling the daqhats library to no avail.

When I run the command 'sudo daqhats_read_eeproms' on my raspberry pi connected to 2 MCC172's with addresses 0 and 1 respectively, the command says that there are mcc's on addresses 0-7. Clearly this is incorrect and unfortunately breaks my code which relies on the list_hats command. It seems like all data collection on these MCC's works fine. But clearly this should not be happening. Is there any way I can fix this?

As far as I am aware from my testing all this setting does is apply some multiplicative factor to the data collected. It does not preform any amplification afaik.

I have 2 MCC 172's that were purchased under a year ago that have stopped working for reasons unknown to me, with different symptoms. I have tried contacting you 3 different ways about getting replacement for them going back 3 weeks and have heard nothing in return. Can I please get help with getting replacements as covered under warranty. Thanks

Hi, I purchased 3 MCC 172's a while ago for use with IEPE accelerometers. Of the three 172's when I run the same code on 2 of them that is supposed to record data to a .csv, it works however on the third it hangs. I have tracked the issue down to the specific 172's inability to sync the clock and set the sampling rate. For each run I have changed the address of the MCC 172 python is talking to so there shouldn't be an issue with addressing. Any recommendations as to how to fix this would be great. Thanks