Wio-E5 with Helium Network

Products & Technology LoRa
#1

Hey,

I’m looking to run my custom board with a Wio-E5 module on the Helium network.

  1. I have a Helium gateway at home, everything is ok
  2. I’ve created a device on the Helium console, everything should be ok, it’s not the first time I make devices communicate on it.
  3. I’ve used the LoRaWan_End_Node example code, I’ve managed to compile and push the .hex onto the module. (GitHub - Seeed-Studio/LoRaWan-E5-Node at qian)
  4. I set the Helium App Key (lsb format) to AppKey and NwkKey in the se-identity.h file.

This is what I get from the module:

APP_VERSION:        V1.1.0
MW_LORAWAN_VERSION: V2.3.0
MW_RADIO_VERSION:   V1.1.0
###### OTAA ######
###### AppKey:      2B:7E:15:16:28:AE:D2:A6:AB:F7:15:88:09:CF:4F:3C (myHeliumAppKey)
###### NwkKey:      2B:7E:15:16:28:AE:D2:A6:AB:F7:15:88:09:CF:4F:3C (myHeliumAppKey)
###### ABP  ######
###### AppSKey:     2B:7E:15:16:28:AE:D2:A6:AB:F7:15:88:09:CF:4F:3C 
###### NwkSKey:     2B:7E:15:16:28:AE:D2:A6:AB:F7:15:88:09:CF:4F:3C
###### DevEui:  00:00:F9:00:52:00:B5:00 (myHeliumDevEui)
###### AppEui:  00:00:F9:00:8F:00:4A:00 (myHeliumAppEui)
###### DevAddr: 00:3B:BD:76
0s036:TX on freq 868300000 Hz at DR 0
1s522:MAC txDone
6s555:RX_1 on freq 868300000 Hz at DR 0
6s753:IRQ_RX_TX_TIMEOUT
6s753:MAC rxTimeOut
7s555:RX_2 on freq 869525000 Hz at DR 0
7s753:IRQ_RX_TX_TIMEOUT
7s753:MAC rxTimeOut

###### = JOIN FAILED
30s040:temp= 57
30s041:VDDA= 254
30s044:TX on freq 868100000 Hz at DR 0
31s531:MAC txDone
36s564:RX_1 on freq 868100000 Hz at DR 0
36s762:IRQ_RX_TX_TIMEOUT
36s762:MAC rxTimeOut
37s564:RX_2 on freq 869525000 Hz at DR 0
37s762:IRQ_RX_TX_TIMEOUT
37s762:MAC rxTimeOut

###### = JOIN FAILED

Some questions :

  • Is it normal to have the temp at 57? On the internet I see more coherent values like 22.
  • Isn’t the “LoRaWan” version of the module too high to work with Helium Network?
    I have :
APP_VERSION: V1.1.0
MW_LORAWAN_VERSION: V2.3.0
MW_RADIO_VERSION: V1.1.0

And I see : “The Helium Network supports any LoRaWAN capable device meeting the v1.0.2, v1.0.3, or v1.0.4 specification.” Here Helium Devices | Helium Documentation

If yes, is it possible to downgrade the LoRaWan version of the module?

  • Do these logs tell you anything?

Thank you

#2

I’m not much familiar with programming of that device but that message looks like there is a problem of communication/i-o declaration in your program that prevents to communicate with Lora hardware :confused:

1 Like
#3

i am just getting ready to explore this module right now so any information you can send my way would be great i am currently working on a water meter relay from out on the field to xiao round display in house point to point

regards!

1 Like
#4

So it’s more a hardware problem with my custom PCB than a software problem?

#5

Difficult to say without seeing the design ! but did you try to reverse in your program TX/RX for the Lora module ?

#6

Ok I have some news where they can confirm that my custom PCB (hardware) is able to join the “Helium Network”. I have change the current Wio-E5 on the PCB with an another wich he has the command AT firmware and it’s ok see the following pics. Maybe the previous Wio-E5 was uncorectly soldered. But I have to investigate again with the other Wio-E5 that I want to put an custom firmware.

Screenshoot1

Screenshoot2
Screenshoot21852×220 18.7 KB