MicroPython-LoRaWAN (nunomcruz)

End Devices (Nodes)
1

Hardware: 1.TTGO Tbeam V.1.1 LoRa 32 SX1276 AS923
2.TTGO Tbeam V.1.2 LoRa 32 SX1276 AS923

Firmware: GitHub - nunomcruz/micropython-lorawan: MicroPython with LoRaWAN support · GitHub

I build my firmware v.1.5.3-lorawan. It works fine with Tbeam V.1.1 LoRa 32 SX1276 but not with Tbeam V.1.2 LoRa 32 SX1276.

The lorawan module kept detecting the board as SX1262 although Tbeam.detect() reported it was SX1276.

MPY: soft reboot
tbeam: HardwareInfo(radio=sx1276, pmu=axp2101, irq=26, busy=None, gps_rx=34, gps_tx=12, oled=True)
lorawan module version: 1.5.0
lorawan: radio=SX1262 (reg42=0x09)
lorawan: LoRaMacInitialization start
lorawan: LoRaMacInitialization returned 0
lorawan: RX2 using region default
lorawan: init done
nvram restored, joined = False
starting OTAA join…
sx1262 TX: power=16 freq=923399999Hz syncword=0x0000 irq=0x1405 err=0xf034
lorawan: OTAA join request sent
lorawan: OTAA join attempt failed (status=2), retrying
sx1262 TX: power=16 freq=923399999Hz syncword=0x0000 irq=0x1405 err=0x0000
lorawan: OTAA join attempt failed (status=2), retrying
sx1262 TX: power=16 freq=923199999Hz syncword=0x0000 irq=0x1405 err=0x0030
lorawan: OTAA join attempt failed (status=2), retrying

How can I fix this error?

2

You’re definitely best off asking this in a GitHub issue on that repository, as the author will have much more experience than all of us combined given how new that is..

I’ve taken a quick look and the library tells you you have an SX1262 if a certain register doesn’t hold the expected value for SX1276. With that logic, a failed read will still say there is a 1262. The printed value 0x09 does look like it did read something but no clue if it read the right thing. Really, I’d ask the author instead.

3

The author closes issue option on his github so I cannot raise the issue.

4

Oh wow I see, that’s… something.
You can always find someone’s GitHub email address by opening a specific commit and adding .patch to the URL. No guarantee that they look at that inbox or want to respond then, but it’s still probably more helpful than asking here.