Topics created by Arno

Thanks Teastain I have the expansion module for CORE 2 I am looking for advice on the mode of communication to use to transfer from CORE2 to the ATOM Display, and how to transmit around 20 digital variables?

Same problem with the CORE2, do you have a solution for this error with M5burner V3 under win10

Hello @Arno I am sorry, I cannot help you on this one - I don't have the EXTEND I/O unit to test. That said, you might get some idea how to talk to it through I2C by looking at the Arduino example? Thanks Felix

@robalstona said in Waterproof temperature probe: Ewentually try this code with your lm35 to check of works (i tested my lm35 sensor with it) I carried out the test on a CORE2, I have very random and non-reproducible values. Thank you for the example under UIflow for ADCs, it will be useful to me with another sensor. I keep the idea of DS18B20, it works perfectly.

Hello @Arno I think the limit is not in UIFlow but in the MQTT unit firmware - probably due so some restricted resources. From the specification: Support 4x Topic subscription, not support MQTTS Thanks Felix

From what Little I understand ------ I2C devices connect to Port A, Make sure the SDA and SCL pins of the new device yo want to use are connected to the correct pins on Port A (White&Yellow wires) Next in UIFlow use: To scan and list I2C devices connected to the ESP32. This list returns values in decimal and so you need to read the devices data sheet to find the hex address and convert the returned decimal list into hex values. Next you need to read the data sheet to find out how to initialise the device and then how to read the device. Once you have a code that returns the data that you need, you need to convert it to a library or driver, download the driver to the esp32 and then create custom blocks in the custom block creator That will allow you new driver/library to work in uiflow.

There's execute code block also

Perfect !

the I2C bug with the PaHub has not been corrected in version 1.7.3 !!!!. Isn't it serious to market products that don't work?

Hi Armo, thank you for your suggestion, and understand your frustration. We will look over it in order to improve our documentation.

I think my proble m is the same

@felmue said in Pahub error with CORE2 with GoPlus2: Hello @ajb2k3 just curious - from where did you get the impression we'd like to connect PaHub to the analog IO ports of the Goplus2? The setup is like this. PaHub is connected to port A of the M5Core2 and works as expected. But as soon as GoPlus2 is stacked the PaHub stops working due to a conflict of GPIO33 which is used for I2C on port A (on M5Core2) as well as for IR_OUT (on GoPlus2). The hardware modification I suggested is to sacrifice IR_OUT (by cutting the trace) so that PaHub (connected to M5Core2) still works when GoPlus2 is stacked as well. Thanks Felix Looks like I missread the posts. I'm going back to bed, Sorry!

I finally found the problem ... putting the screws on my FACE II it works. Probably a false contact

You can send the values as a json string from the ROV to the remote and then separate the values from the sting on the receiving end. I am currently documenting this in my esp-now document.