Jump to content
  • 0

MCC134- "Invalid Board Type"


Agnerle

Question

Hello! I am currently having an issue with two of my boards. I have three boards on my raspberry pi: an MCC128, and two MCC 134's. These boards are in address 0, 1, and 2 respectively. I'd also like to note that when I run the device manager, it is reading all of the boards in correctly and it seems like they are all recognized.

For my MCC128, it is unable to "open", according to the device manager tool. I have tried updating the firmware for this board, but the update gets stuck on "checking device..." and it will never display the firmware version.  When I use the example code for the MCC128, it says that the board is not responding. 

Additionally, one of my two MCC134's is having a strange issue. Again, my two MCC134's are in address 1 and 2, but only one of them is working. If I run the "single_value_read.py" example for the MCC134, and select on the board in address 1, then it will say that it is an "invalid board type". Similarly to the MCC128, I am unable to open the channels on this board, even when using the device manager. However, everything works just fine on the MCC134 in address 2. 

If anyone has any suggestions, then please let me know! I have ensured that SPI and I2C is enabled, but that was just about the only information I could find online. I have also tried changing the order of the boards, and setting up one at a time, but it does not help. Is it possible that i'm i having an issue with my raspberryPi? 

 

Thanks!

Sorry I didn't add pictures. I took some, but they are too big to attach! 

Link to comment
Share on other sites

2 answers to this question

Recommended Posts

  • 0

If the DAQHAT driver was installed before mounting the boards, you must run the read eeproms utility.

sudo daqhats_read_eeproms

Close the DAQ HAT Manager and run the command. If you change the address jumpers, you must do this again. If you've done this but only two boards work, the problem is probably a bad board.

 

Link to comment
Share on other sites

  • 0

Thanks! Yeah, i tried reading the eeproms a couple times and tried stacking them differently. I finally just tried using new boards and those worked fine! I'm assuming that the boards are both bad.

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...