gavin67890
@gavin67890
Posts made by gavin67890
-
RE: (PM2.5 + SHT30) and ENV III
See https://docs.m5stack.com/en/product_i2c_addr
I think you might have a clash either way:Depending on chip, ENV III (QMP6988) with PaHUB:
Or ENVIII (SHT30) and the cradle base with the SHT30 in it.
https://shop.m5stack.com/products/btc-standing-base-for-m5-core-with-sht30
"Once M5Stack Core has been attached to BTC, it can not connect to an ENV Unit. This is to avoid I2C address conflict with built-in SHT30 sensor of BTC Base."ENV III UNIT
0x44(SHT30)
0x70(QMP6988)PM2.5
0x40(SHT20)DLight UNIT
0x23(BH1750FVI)M5Core
0x75(IP5306)
0x68(MPU6886)
0x6C(SH200Q)
0x10(BMM150)PaHUB UNIT
0x70(TCA9548A)
PaHUB2 UNIT
0x70(PCA9548AP)You can confirm chip on ENV III from the sticker on the back. If conflict is with SHT30, try with Core out of the cradle.
-
RE: Wired communication between MULTIPLE Atom unit?
Hi,
I'm not able to assist on this one directly, but I wondered if it would help to outline what you are trying to achieve a little more.
AtomS3 --|
AtomS3 --|
AtomS3 --|
AtomLite or Matrix? -|Which is the main processor?
Are you using UART or I2C for communications?
Are you thinking I2C from the 3x AtomS3 via PaHUB to Atom (as central processor)?
Are you thinking UART from the 3x AtomS3 via PbHUB to Atom (as central processor)?
If using I2C, might it be possible to change addresses of each device and connect on a common bus (Atom Master -| 3x AtomS3 Slave)? -
RE: StickC Plus + PaHUB + 3 Ultrasonic I2C units
Continuing my tale-of-woe about the PaHub:
I have now tried using G0 and G26 (StickC) to connect as custom I2C to PaHUB with the ENV III attached, which works on Port A.
Via the PaHUB using the top hat pins (the pins an I2C hat uses). I get "Pahub unit maybe not connect", fine on Port A.
-
RE: M5StickC connectivity
Hi @rambinator, Yeah, I missed the 2x, very sorry.
Let's try again. I've got some kit, so I'm going to try and see where it takes us.
Home > Store > Sensors > Hat(s) > ENV III – the picture gives G0 I2C-SDA, G26 I2C-SCLI have the ENV III unit, not hat, so I used a Groove2Dupoint and made the connections to I2C on the unit (plus 5V and GND). In UIFlow, I added the unit on custom pins 0 and 26 and made the simplest temp label 1 sec loop. Run and temp reading appeared, nice.
Next I have the PaHUB (I2C-to-I2C), so I added the hub with custom G0 I2C-SDA, G26 I2C-SCL and ENV III to PaHUB|#0
Run and "Pahub unit maybe not connect", not shocked – read my other posts.Switch PaHub from custom GPIO to Port A (bottom), Run and ta-da temp reading ok on screen via the hub. And that's my concern for you with the PbHUB option (my issue might just be because I2C devices/PaHub). Now, the hub is quite cheap, so you could try it, maybe use Port A and put the 8-encoder on the top (custom pins 0 and 26).
There are 3 pins at the top (0, 26, 36), which I would have said should suffice for proto hat option. However, I don't think all the PIN ports at the top are the same. I'm speculating here – @felmue help please – but I think the following for I2C.
G0 - Fine SDA/SCL
G26 - Fine SDA/SCL
G36 - Couldn't find the unit because it's ADC, but it might be fine for the limit switch, risk with the angle units.In conclusion, I'd go for the PbHUB try it through the hat connection G0, G26, and connect angle units (GPIO) and limit switch (GPIO) to it. Use the bottom Port A for the 8-encoder. If you get error messages about the hub, swap top to bottom (fingers crossed).
PS You might want the proto hat as well. The Dupont to top of StickC next to each other are a little tight. Might also save you the buy of Groove2Duponts because you will get one cable with each device (cut one in two to give bare cable to Groove).
-
RE: M5StickC connectivity
@rambinator, Looking at your list:
1 x U153: 8-Encoder Unit (I2C) --> I'd go for bottom I2C port
2 x U005: Angle Unit / Potentiometer --> I think you only actually need 1 GPIO pin, so you could use top (hat) set of pins from proto hat (either solder in header pins and use dupont2groove or strip and solder cables in).
1 x U145: Limit Switch (optional) --> There is the hub option, however, the I2C base port is already in use. In theory, you could chain the hub to a hub and tree down, but staying with the proto hat, there is also a 3V3 output on the hat row output. Looking at the schemes for the limit switch you could potentially bring that 3V3 in on pin 2 after the voltage divider instead of 5V (a minor cable mod inside) then back via the same GND as the angle unit via proto hat. Again it only needs the one GPIO.I think you could do it with 2x dupont2grooves and 1x proto hat
1 5V (Angle) (Alt leave Limit Switch as factory and take a 2nd 5V from proto)
1 3v3 (Limit switch with internal cable mod)
2 GND (Angle and Limit switch)
1 G26 Angle Unit
1 G36 Limit SwitchAlt Alt option Pb.Hub to top hat pins then set as custom 26/36 and daisy chain limit switch and single angle unit on (no solder option). I'm a bit wary of the hubs, so maybe hedge and order the proto hat as well (they're cheap).
-
RE: More colors for enclosures
ABS+PC = PC/ABS (Polycarbonate/Acrylonitrile Butadiene Styrene)
-
RE: StickC Plus + PaHUB + 3 Ultrasonic I2C units
Anyone got any more thoughts? My intension is to raise it as a bug (I think we've exhausted our best ideas).
-
RE: More colors for enclosures
Does anyone know what plastic the enclosures are made of, particularly the white sensors?
Nylon can be dyed with Rit or Dylon.