Hello @water5 today I got my gesture unit and I can confirm that it works fine with M5Core2 but fails to work with M5AtomLite using UiFlow firmware 1.9.8. What I found however is, that the gesture unit starts to work with M5AtomLite as soon as I add another I2C unit. I also double-checked with an I2C scan: only gesture unit connected to M5AtomLite and the scan finds nothing. Gesture unit and PbHub connected to M5Atom and the scan finds both. Go figure... Thanks Felix

Hello @Treadbrook in my experience the link light only indicates that there is an electrical connection between two Ethernet devices. The link light, however, does not give an indication about whether a device has either a static IP address or received an IP address from a DHCP server. In other words when I connect my POESP32 to a switch where the switch has no further connections (and therefore there is no DHCP server) the link light lights up, but check Ethernet connection returns false. This leads me to think that check Ethernet connection also checks for an IP address and not only for a link. I suggest you try to connect your POESP32, as a test, to your router directly and / or check on your router whether the POESP32 is listed in its DHCP lease list and has received an IP address. Note: if you are in a corporate network environment it is possible that the network administrator has setup port security which means an Ethernet device can only participate in that network after it has been whitelisted by said network administrator. Regarding documentation - I assume you've seen this page? Thanks Felix

Hi @fredz, I'm trying to do localization by connecting UWB with M5stack core2, I'm trying to do one base one tag, but unfortunately; I have no measurement appears in my screen, I'm still struggling to solve this issue, but hope if possible get some advice from you

Hello @emsea22 sorry, I don't have a tutorial. But no, you don't need to attach an FTDI dongle to the iEXT.IO2 unit - the I2C address can be changed via an I2C command sent from the host, e.g. 0xFF, <new I2C address>. (At least that is my understanding from reading the documentation.) Thanks Felix

@m5stack Could you please correct the UnitCamForUIFlow firmware as follows? Set the WROOM-32 clock to XCLK=8MHz and the ov2640 clock to twice the current clock. This solution has been found by Sohtamei in the following thread; https://community.m5stack.com/topic/3649/unitcam-hw-issue-cannot-stream-video/8 Thanks a lot.

Hello @robjasey I am glad to hear you got it working to your liking. The forum allows to upload pictures (cloud symbol with arrow) or you could post the resulting python code. Thanks Felix

Makes not difference if indoors or outdoors. Since it is connected to portA and not to portC as it is supposed to, do I need to make any modifications? Eg like here: https://community.m5stack.com/topic/1312/gps-unit-with-m5stack-fire-not-working/5 Thx

@bartblommaerts said in multiple 4-Relays on same I2C bus: Oh the PaHub>2< Unit :/ its not available yet in the local stores. And the Pa.Hub (version 1) is sold out. You're better off ordering direct from M5Stack

Hello @ve2dx try something like this: M5.Axp.SetLDOVoltage(3, 2500); the second parameter is the brightness. Max is 3300. Thanks Felix

@aafortinet A mate of mine had the same issue -- seemed not to work until he used it within the 2-150cm parameters. The all good.

@tuckie nice work, I'm waiting on UIFlow blocks in order to make a project.

The distances I get are really strange: The values are well below or well above the expected ones. For example, for a distance of ~95cm the sensor answers 4.5cm. For a distance of ~110cm, 4.9cm. For ~35cm, 3.7cm etc. The values change for the same distance. So different measures of ~200cm gives 13.7cm or 79.6cm the next time... The command Wire.begin(32,33) seems correct as I realize those are the ports for the sensor on the CoreInk. So, what am I doing wrong?

Hello @jamstooks @ajb2k3 is correct, the PbHub is for analog devices only and cannot be used for UART. Unlike UART, I2C is a bus and can handle multiple units (as long as the units use different I2C addresses). So if you want to connect multiple I2C units to you M5Core2 you can use a Groove-T. However as soon as some units you wish to connect share the same I2C address you need a different solution. You have two options: the units in question allow for the I2C address to be modified use a PaHub (like @ajb2k3 suggested) As for connecting the UnitV2 to your M5Core2 via UART: I would suggest the Battery Bottom 2, which has been designed for M5Core2 and it gives you the UART port needed. The COMMU module should work as well, but as it has been designed for the M5Stack (Basic, Gray, Go, Fire) there seems to be some incompatibility issues like while the COMMU module is stacked to the M5Core2 the M5Core2 cannot be flashed. (Note: I don't have the COMMU module, so I cannot confirm that issue.) Thanks Felix

For anyone finding this. I had to restart the ethernet over usb interface with ifconfig with down and up commands to get connected. Then it worked fine.

Hello @Felix22 I do not have a 4-Relay unit so I cannot test myself. But it sound like the new one might be defect? Thanks Felix