Forum Replies Created
-
AuthorPosts
-
May 4, 2021 at 8:06 pm in reply to: Failed multiplexer, got replacement from lab maker, error still persists #1176wilsonhParticipant
I wrote a python script to switch the multiplexer to the correct bioreactor manually and then took apart the reactor and manually supplied 3.3V to where the regulator should have been giving it. After running
i2cdetect -y -r 2
and I was able to see two other devices:root@beaglebone:~# i2cdetect -y -r 2 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- 1b -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: 60 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: 70 -- -- -- 74 -- -- --
I am now just trying to figure out if the
0x60
and0x70
I am seeing are valid, I’m thinking that the the0x60
is the (PCA9685) PWM chip and I cannot figure out what theB1
is on the PCB, but maybe that is the other one? The zip on the website that contains the PCB files are all V1.0, while my bioreactor is V1.2. Would I be able to get the updated files in a.zip
so that I could know what these parts are?Also, a weird thing that I am running into is after attempting to run
bash cb.sh
and it failing the no I2C device works until I unplug the beagle bone and re-power it back up. Must be that when ICTRL-C
some master device is holding onto the bus? Any ideas on why this might be?April 21, 2021 at 2:33 pm in reply to: Failed multiplexer, got replacement from lab maker, error still persists #1166wilsonhParticipantI also ran
i2cdetect -l
to see what i2c busses were present. Here is the output from runningi2cdetect 0; i2cdetect 1; i2cdetect 2
:root@beaglebone:~/chibio# i2cdetect 0; i2cdetect 1; i2cdetect 2 Warning: Can't use SMBus Quick Write command, will skip some addresses WARNING! This program can confuse your I2C bus, cause data loss and worse! I will probe file /dev/i2c-0. I will probe address range 0x03-0x77. Continue? [Y/n] y 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: 10: 20: 30: -- -- -- -- 34 -- -- -- 40: 50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: 70: Warning: Can't use SMBus Quick Write command, will skip some addresses WARNING! This program can confuse your I2C bus, cause data loss and worse! I will probe file /dev/i2c-1. I will probe address range 0x03-0x77. Continue? [Y/n] y 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: 10: 20: 30: -- -- -- -- -- -- -- -- 40: 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: 70: Warning: Can't use SMBus Quick Write command, will skip some addresses WARNING! This program can confuse your I2C bus, cause data loss and worse! I will probe file /dev/i2c-2. I will probe address range 0x03-0x77. Continue? [Y/n] y 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: 10: 20: 30: -- -- -- -- -- -- -- -- 40: 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: 70: root@beaglebone:~/chibio#
-
AuthorPosts