Thanks @felmue , I did notice that too so I used continuity tester to see if andy of the RS-485 terminal screws were directly connected to the header pins that connect to the Atom's 33/23 pins I did't detect any continuity. I want to connect a Nextion Display that uses a Serial connection to the Atom Switch and was hoping to utilize Pins 33/23. I'm thinking I may need to purchase something like the MAX485 RS-485 module to attach to the Nextion display and run my serial connection over this RS-485 connection. Think I have some reading to do. ;)

Hello @solders-soul_0z from what I understand the GPS module only supports one antenna at the time connected to the connector labelled IPEX. It looks to me that currently the internal antenna is connected (gray cable). Have you tried to switch and connect the external antenna (black cable) instead? Thanks Felix

If you use UIFLow you can make a loco controlled via a mobil phone easy however, the PWM lacks a H-Bridge and so will only work in one direction. I have started a model railway series using M5Stack controllers here: https://www.hackster.io/AJB2K3/m5stack-model-railway-part-1-b109f7

You need to detect when the device is disconnected and then reconnected in order to stop and restart communication. RS232 is not made for Hotswapping.

@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!

It appears that ENABLE is indeed the RESET pin. I use it to connect SPI OLED RESET signals, and that works.

Hello @torntrousers if you use GPIO 13, 14 in your code (as suggested) then in the COM.NB-IoT module you'll need to set dip switches for GPIO 16, 17 to on (the other four to off). The GPIO numbering in modules are (so far) always matching the numbering in M5Stack (Base, Gray, Fire) devices but unfortunately M5Core2 uses some different GPIOs on the M5 bus. This comparison I've put together a while ago might help. Thanks Felix

Hello @maxstack I am not sure. Stamp Pico can be use after you use M5 burner to connect to M5 server. And after that, you can use it in UI Flow Website by connect the MacAddress.

@felmue Thank you.

@siva Old thread but yes, however I had to send commands to the bala2 manually as there is no module for it at the moment. However I am seeing some odd problems with power, everything is fine when USB is connected but without it, eventually the combined grey+bala2 (or core2+bala2) gets in to a state where the power button cannot turn it on anymore until the controller is briefly removed and stacked on again. Once that is done it immediately can be turned on again. This doesn't seem to be a UIFlow issue though as ESP-IDF and Arduino sketches do the same thing.

Hello @macsbug there should be no need to cut traces in the GPS module. For M5Core2 defining GPIO13 and GPIO14 in UiFlow (instead of GPIO16 and GPIO17) should do the trick. Or am I missing something? Thanks Felix

@sirtet thanks for the reminder, I forgot to add this to my UIFlow book!

They actually operate on the same register, this block is used to operate independent wheels, there may be some translatione problems ( use pulse less accurate ). The parameter range is -127 to +127. we will update it later, thank you feedback.

Hello @em glad to hear. And thanks for reporting back. Thanks Felix

I received my Core2 and GRBL 13.2 module and it works due to @felmue 's hints: https://community.m5stack.com/post/16551