I’m sorry to say but the new firmware 3.1.0.6 is not working very well.
It is working less comparing with 3.1.0.5. On my trip to work I’ve got only 1 valid TTN mapper GPS hit.
Also without GPS the hit performance is terrible even with external antenna. As previous reported the node is not connecting always to a gateway (in range).
Issues:
GPS not always valid, 1 out of 10 is sent (during movement)
LED’s are not working
Not connecting to gateways within range (TTGO-T-beam at the same moment it is) (during movement)
I had all kinds of issues with the LPP decoder not working properly on that version.
I’ll upgrade to 3.1.0.6 and see what happens, but I’ve got to say I’m less than impressed with this device so far, it really does feel like Alpha quality instead of the finished product that I paid for.
It seems that the latest firmware works well and the GPS can be shown in Cayenne correctly.
But there is still an issue, the GPS position are changing all the time even if we don’t move the device.
We’ll debug this issue ASAP.
The tracker works indeed when you are NOT moving, as soon as you are moving causes no GPS lock after wake up.
During fixed position sometimes you will have an incorrect lock. Indeed the same as you discovered.
See below:
Happy to test it but I need to have my laptop installed in my car otherwise I cannot get the statements from the UART.
Not able to perform it today but tomorrow I can and will let you know.
Any updates, news with regards the other reported issues?
In your cayenne dashboard I see you’ve got a temp/baro sensor working with the 7200. Is this a different hardware version as you reported the versions currently shipped doesn’t have this sensor?
Anyone else testing this device in the US? I’m having problems with it connecting to a known good Lora access point. I get the join packet, the serial interface states it joins successfully (OTAA), but then when it tries to send GPS data, I get a Unknown Network Error: 8, then (as of firmware 3.1.0.6) the 7200 says it sends GPS data but nothing is received at the access point. It’s never successfully transmitted GPS since I got this device. One thing I’m noticing is that no matter how far/close I am or with multiple antennas (factory or add on) the device seems to be hitting the max duty cycle time of 371 seconds at SF 10. The TTN console reports that any packet no matter the distance from the AP is using 370.7 seconds to transmit. I’m wondering if that has something to do with this issue?
Also, when masking out channels, a restart is required for it to save and use them - you may want to add that to the AT command directions.
I’m in the identical situation as you here in the US. Using 3.1.06 I can join okay and it shows up on the TTN console. But no data is sent. I get Unknown Network Error: 8 and then [LoRa]: Send out <data_len:32bytes>. All the channel assignments look correct (8 – 15 are on) others are off, except 64 – 71 are also on. I think only 64 should be on, so I disabled 65 – 71, verified channels and then did a restart as you mentioned. After it came up 64 – 71 were back on again. I should mention I’m inside and the GPS is not locked.
Had some success sending data (32 bytes worth). The default data rate of 0 doesn’t allow sending a payload that large. I set my RAK to a data rate of 1 using “at+set_config=lora:dr:1”. Now all the data gets to the TTN console. Hope this helps.
Is there a way to access the LoRa modem AT commands? I need the LoRa network signal strength RSSI, SNR etc. I see we have a limited AT command exposure.
I tried what you described moving the DR from 1-5 with the same result. There was a small change at the TTN console though. The airtime moved from 370.7 to 28.7 when the 7200 moved to the 500khz bandwidth channel, but either way, it was never able to do anything more than it did before. I’m still getting the Network Error: 8. Also, once the device sends the first data transmission - it never sends a second one. I figured I would post my lora:status to see if maybe something differs from yours.
==============LoRaWAN Status List================
Region: US915
Send_interval: 5s
Auto send status: true.
Join_mode: OTAA
DevEui: ***************
AppEui: *************
AppKey: *******************
Class: A
Joined Network:true
IsConfirm: true
Work Mode: LoRaWAN
AdrEnable: true
EnableRepeaterSupport: false
RX2_CHANNEL_FREQUENCY: 923300000, RX2_CHANNEL_DR:8
RX_WINDOW_DURATION: 3000ms
RECEIVE_DELAY_1: 1000ms
RECEIVE_DELAY_2: 2000ms
JOIN_ACCEPT_DELAY_1: 5000ms
JOIN_ACCEPT_DELAY_2: 6000ms
Current Datarate: 0
Primeval Datarate: 1
ChannelsTxPower: 0
UpLinkCounter: 0
DownLinkCounter: 0
===================List End======================
