It may be. It sound like the address system has changed as they should have been 0-24 for a total of 25 leds

Hello @iot
You might want to check for the battery output/voltage before deciding whether to use it or change to a longer lasting battery supply or even a switch. Bear in mind that the weather conditions such as heavy rain should be taken into consideration as there are devices and wires involved because you don't want to shock the device/battery. Another tip is that the material of the box should withstand any weather and temperature. All the best in your project!

@david-bethesda mentioned Solar parts, which is a good idea too.

Hi @jburt

should be this one.

Thanks
Felix

Solved this finally. The Atom Lite does not seem to have a pullup or pulldown resistor. By applying a resistor the problem seems to be solved and it is possible to detect Rising, Falling and Change states.

@happyuser I believe the Atom printer uses standard Rolls of 57x40mm Thermal Printing Paper. Quite cheap, you can get 4 rolls for about £7 on eBay.

Hello @tgprivate

glad to hear it worked. And thank you for reporting back.

Thanks
Felix

@felmue said in ATOM TF-CARD Kit SPI pins are not default SPI pins?:

sd.info()

Hi Felix,
Thanks a lot.
Your solution also works for me.

Hi @felmue

Many thanks for your rapid reply and your helpful "debugging" questions.

My M5 Atom is working just fine now, even the GPIOs I thought I might have fried :-)

Cheers,
Philip

@felmue That makes sense, but (i think) the configuration box for other devices does not have a API key at the top, so maybe it's something to do with UART settings. (like being able to send UART commands during boot to change settings.)

Thank you very much for your reply. Very helpful.

Hello @LiRM35M4419

to be on the safe side I use a non PoE port while developing and with USB connected.

Thanks
Felix

Hello @MDCB

ok, you made me curious, so I've setup a Helium account and was able to join with a COMX.LoRaWAN868 module using a couple of AT commands. Unfortunately the COMX.LoRaWAN868 module has a different AT command set than the Atom DTU LoRaWAN base so the AT commands I used won't help you much. Also the COMX.LoRaWAN868 module is not covered in UiFlow which means I had to send the AT commands using the UART blocks. Essentially I had to choose LoRaWAN, OTAA, set DevEui, AppEui and AppKey (all three copied verbatim from the Helium Console) and then issue a Join command.

However what I can share is the output of the COMX.LoRaWAN868 module when I switch it over to LoRaWAN mode:

Copyright @2019-2020 Heltec Automation.All rights reserved. AT Rev 1.3 +AutoLPM=0 +LORAWAN=1 +KeepNet=0 +OTAA=1 +Class=A +ADR=1 +IsTxConfirmed=1 +AppPort=2 +DutyCycle=15000 +ConfirmedNbTrials=4 +ChMask=0000000000000000000000FF +DevEui=0123456789012345 +AppEui=0123456789012345 +AppKey=01234567890123450123456789012345

From that I think you might want to try a different class (A instead of C) and a different channel mask (0xFF instead of 1).

Thanks
Felix

Hello @Dieter_P

thank you - I appreciate you letting us know about the implication regarding power safe and usage of BLE and WiFi.

Thanks
Felix

@felmue ah okay, perfect! Thanks!

@ajb2k3 thanks for the tip but unfortunately I can't access the USB port in my setup, so I'll have to go through the pins anyway.

Hi @felmue and thanks for the quick reply.

I also looked at the datasheet and came to the same conclusion. It might be easier to find a fan that supports 0 rpm with lower (<10%) PWM duty cycles.