[SOLVED] Example Program -4:Join Error
Tagged: mDot join error
- This topic has 5 replies, 2 voices, and was last updated 6 years, 11 months ago by
Brad Rust.
-
AuthorPosts
-
April 4, 2018 at 10:19 am #22996
Brad Rust
ParticipantWhen attempting to use ota_example, I am receiving a ‘failed to join network -4:Join Error’ logged to the serial port.
In the .cpp file, I changed the network id, passphrase, and the sub band to match the .conf file on the mLinux Conduit. Using these same credentials, I am able to join using AT commands and am confident that all information is correct.
I have reduced Tx Power from 30 to 4 (because I am in close proximity during this testing phase to the gateway) but this made no difference.
The following is the output from the at&v command:
Device ID: 00:80:00:00:00:00:eb:37
Default Frequency Band: US915
Current Frequency Band: US915
Frequency Sub Band: 7
Public Network: off
Start Up Mode: COMMAND
Network Address: 00000000
Network ID: 04:c2:17:b9:a2:a9:33:9d
Network ID Passphrase: richmondSFDC
Network Key: 3b.aa.e4.a1.b7.18.da.64.51.4e.6b.18.bf.c9.98.de
Network Key Passphrase: richmondSFDC
Network Session Key: 00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00
Data Session Key: 00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00
Network Join Mode: OTA
Network Join Retries: 2
Preserve Session: off
Join Byte Order: LSB
Join Delay: 5
Join Rx1 DR Offset: 0
Join Rx2 Datarate: DR8 - SF12BW500
Join Rx2 Frequency: 923300000
App Port: 1
Listen Before Talk: off
Link Check Threshold: 5
Link Check Count: 3 packets
Error Correction: 1 bytes
ACK Retries: off
Packet Repeat: 1
Encryption: on
CRC: on
Adaptive Data Rate: on
Command Echo: on
Verbose Response: off
Tx Frequency: 0
Tx Data Rate: DR0 - SF10BW125
Min/Max Tx Data Rate: Min: DR0 - SF10BW125
Max: DR4 - SF8BW500
Tx Power: 30
Min/Max Tx Power: Min: 0
Max: 30
Tx Antenna Gain: 3
Tx Wait: on
Tx Inverted Signal: off
Rx Delay: 1 s
Rx Inverted Signal: on
Rx Output Style: HEXADECIMAL
Debug Baud Rate: 115200
Serial Baud Rate: 115200
Serial Flow Control: off
Serial Clear On Error: on
Wake Mode: INTERVAL
Wake Interval: 10 s
Wake Delay: 100 ms
Wake Timeout: 20 ms
Wake Pin: DI8
Log Level: 4serial info from ota_example.cpp:
[INFO] Initialize radio…
[INFO] Initialize channels…
[INFO] Initialize datarates…
[INFO] Set radio to Private Mode
[DEBUG] Read file from flash: 256 bytes
[DEBUG] Read file from flash: 1024 bytes
[DEBUG] Read file from flash: 256 bytes
[INFO] Set radio to Private Mode
[INFO] mDot Ready
[INFO] mbed-os library version: 144
[INFO] defaulting Dot configuration
[INFO] Initialize channels…
[INFO] Initialize datarates…
[INFO] changing network name from “” to “richmondSFDC”
[INFO] changing network passphrase from “” to “richmondSFDC”
[INFO] changing frequency sub band from 0 to 7
[INFO] changing link check count from 0 to 3
[INFO] changing link check threshold from 0 to 5
[INFO] saving configuration
[INFO] =====================
[INFO] general configuration
[INFO] =====================
[INFO] version —————— 3.0.0-mbed144
[INFO] device ID/EUI ———— 008000000000eb37
[INFO] default channel plan —– US915
[INFO] current channel plan —– US915
[INFO] frequency sub band ——- 7
[INFO] public network ———– Private LoRaWAN
[INFO] =========================
[INFO] credentials configuration
[INFO] =========================
[INFO] device class ————- A
[INFO] network join mode ——– OTA
[INFO] network name ————- richmondSFDC
[INFO] network phrase ———– richmondSFDC
[INFO] network EUI ————– 04c217b9a2a9339d
[INFO] network KEY ————– 3baae4a1b718da64514e6b18bfc998de
[INFO] ========================
[INFO] communication parameters
[INFO] ========================
[INFO] acks ——————— off, 0 attempts
[INFO] TX datarate ————– DR0
[INFO] TX power —————– 30 dBm
[INFO] antenna gain ————- 3 dBm
[INFO] LBT ———————- off
[INFO] attempt 1 to join network
[INFO] Send join request RxDelay: 5 Rx1Offset: 0 Rx2Freq: 923300000 Rx2Dr: 8
[INFO] Configure radio for TX
[INFO] Configure radio for TX
[INFO] Configure radio for TX
[INFO] Rx Window 1
[INFO] Rx Window 2
[ERROR] Failed to join network
[ERROR] failed to join network -4:Join Error
[INFO] waiting 2 s until next free channel
[INFO] attempt 2 to join network
[INFO] Send join request RxDelay: 5 Rx1Offset: 0 Rx2Freq: 923300000 Rx2Dr: 8
[INFO] Configure radio for TX
[INFO] Configure radio for TX
[INFO] Configure radio for TX
[INFO] Rx Window 1
[INFO] Rx Window 2
[ERROR] Failed to join network
[ERROR] failed to join network -4:Join ErrorApril 4, 2018 at 10:38 am #22997Jason Reiss
KeymasterWhat version of mlinux is being used? 3.3.22 is the latest.
Do you have logging enabled in the network server conf?
Check the logs for received packets.If 3.3.22 is installed
> lora-query -x help
> lora-query -x packet recent join
April 5, 2018 at 6:53 am #23003Brad Rust
ParticipantHi Jason,
Upgrading from 3.3.13 is proving very tricky. The file system is a mere ~600MB or so. The /var/volatile drive is only 124MB. Both of the required files total to a little over 240MB. It looks like I’ll have to get a set of start keys and open the thing up to see if I can remove the drive, image it, and either replace with a larger one or temporarily resize the volume in a way that will allow for the upgrade.
In an era where memory is dirt cheap, it’s really frustrating to see such a small drive in a $500 gateway. Even RisingHF ships with 8GB. :-/
Edit: I see that removing the cover allows for media card insertion. The FW upgrade directions state that the files can be placed here instead. Will report back.
April 5, 2018 at 7:39 am #23006Jason Reiss
KeymasterAre you following these instructions?
Sounds like you are trying to copy the source tarball instead of the pre-built image files.
April 5, 2018 at 7:50 am #23007Brad Rust
ParticipantI am indeed following those instructions.
Oops. I also had the mlinux-factory-image-mtcdt-upgrade-withboot.bin which was why the ssh transfer kept failing when I tried to dump the contents of my flash drive into /var/volatile. Thanks for making me double check!
I’ll report back once the update is done.
April 5, 2018 at 7:59 am #23008Brad Rust
ParticipantIndeed, upgrading the firmware did the trick. Thanks for the suggestion and for the error checking!
-
AuthorPosts
- You must be logged in to reply to this topic.