Hello guys

I think the basic idea behind the Groove colors is:

port A (red) : default usage I2C port B (black) : default usage I/O port C (blue) : default usage UART port A/B/C (white) : no default usage (like on the M5StickCPlus)

But it's like @teastain already said: most ports can be used for anything as the GPIOs are mostly configurable.

Thanks
Felix

@teastain I don't have the slightest idea.
All I know is that the S3 / ESP-IDF api's are still in flux.

Stick with M5Burner as you will get the latest version without the need to compile.

Did someone make Lora work for asr6501?
i bought multiple lorawan470 units and feel i am headed nowhere.

Thanks so much, I thought I bricked by cardputer and it is back.

I downloaded and ran the V3 M5 Burner and the AIN_420MA is still not available as a module. Is the something more I need to do?

I confirmed that the sample code works. However, the micro step does not work well. The step width is the same even if I change the settings. Is there a special setup procedure?

I don't see your problem. Just send the data to the according address of your light.
Maybe you do not understand the addressing of DMX lights?
You need to configure an individual start channel (address) for every light with a spacing of at least the number of channels your light support. E.g. your RBGW light is set to 4-channel-mode and its start channel is set to 1, then it listen to the channel 1, 2, 3 and 4. The next light can have the start channel 5 and so on. Some more complex lights like moving heads can have more than 30 channels. It is possible to have up to 512 channels per physical bus (called DMX universe)
You may set several identical lights to the same address but then they all do the same.
Also very important: The last light in the bus should have a terminator plug/resistor. It may work without but often a missing terminator cause strange effects on the DMX bus.

Problem solved: the air pressure is calculated the the altitude of 0m, when the pressure is measured for example in the alps ( as i did) in 800m height, it‘ s signifikant lower.

@m5stickfreakler hi - did you ever solve this? I am having the same problem with both the LAN Module and the LAN Base - it initialises the LAN, gets an IP address, but just won't accept data from a browser when I try the following code:
s = socket.socket()
s.bind(('172.17.15.87',80))
s.listen(1)

I would love to get this sorted!

Cheers,

Hi @fbritop,

The unit is just a comms module i.e. it would need a controller like the Atom Lite. In terms of connecting to HiveMQ it could be used to send out MQTT requests. Perhaps you could expand what you are trying to achieve.

If you have many devices (taking to mean sensors) connected to a Atom Lite controller then this could gather readings and send from a single Atom Lite plugged into this module.

If you have many devices (taking to mean Atom Lites) and you want to concentrate to a single mobile access point. It could probably be done by connecting one Atom to a 7080G unit and then relay from other Atom Lites, but a commonly available Mobile Hotspot (e.g. 5G) device to connect all the Atoms via Wi-Fi would probably be better.

The benefit of this device is its low power consumption and design for mobile data at relatively low volumes (see LTE-M and NB-IoT).

As an example, I have a Core2 and IoT base configured to simply request the current CO2 from electricity production once a day and display it. The SIM costs are minimal a few pounds per year, not per month. It is completely standalone, apart from power. For example, I have used it to collect button presses on a micro: bit via serial and relay them to AWS.