and as a streched goal get it to run Mbed OS 5
Note that this is the same module as on the DISCO-L072CZ-LRWAN1 board so compiling for that target from Mbed CLI / Online Compiler should give you a binary that can also run Mbed OS on this module. There seem to be drivers for the GNSS module as well from ST: TeseoLocation.
I have received my TTIG, and I am experimenting with a
STEVAL-STRK01, sending a message every minute, but I see that several packets are lost.
Packets are received more like every 2 mn.
And more important, after a while (33 packets) everything is stalled.
Where does the problem come from ?
this is not related to TTIG imho…
I dont understand what you mean.
I wrote that I received 33 packets : so it worked.
The problem is that after a while ( less than one hour), the packets are no longer forwarded.
I see… ok, TTIG is working fine (here) so it must be your node (code)
-is the green led flashing when its no longer forwarding ?
-are you moving around with the node ?
The green led is fixed.
The node does not move.
I want to know how steady the connection can be. Up to now, it is not very successful.
{
“time”: “2019-04-06T14:55:48.642362912Z”,
“frequency”: 868.5,
“modulation”: “LORA”,
“data_rate”: “SF8BW125”,
“coding_rate”: “4/5”,
“gateways”: [
{
“gtw_id”: “eui-58a0cbfffe800301”,
“timestamp”: 129013820,
“time”: “2019-04-06T14:55:48.299748Z”,
“channel”: 0,
“rssi”: -57,
“snr”: 7.5
}
]
}
It seems that packet 4 is missing. Why ?
can you try move it further away from TTIG ?
I move it a little bit further
{
“time”: “2019-04-06T15:25:08.960716565Z”,
“frequency”: 867.1,
“modulation”: “LORA”,
“data_rate”: “SF8BW125”,
“coding_rate”: “4/5”,
“gateways”: [
{
“gtw_id”: “eui-58a0cbfffe800301”,
“timestamp”: 110041692,
“time”: “2019-04-06T15:25:08.616035Z”,
“channel”: 0,
“rssi”: -67,
“snr”: 12.25
}
]
}
The Payload is 37 bytes
what is ADR ( and where ) ?
what do you mean by “lower the interval” ?
Is it because of this fair access policy that my sensor is stalled after 67 packets in TTN ?
No. There must be something else wrong with you code to cause this.
My TTIG has been running uninterrupted for a couple of days receiving data from several nodes without any issue. If a reset of just the node makes things come alive again the error is on the node, not TTIG. If you need to reset TTIG as well it might be an issue with the gateway, but given the information available at this time that seems unlikely to me.
Thanks Jac, this was helpful.
I have set up another node ( again a STEVAL-STRKT01)
As it looked fine, I have also set up a third one and flash again the first one.
Now it seems that everything is OK.
At least it has been running with no problems for more than 3 hours.
which has never been the case before. I will let it run as such for a longer time to test
the devices.
I need now to increase the range.
How do you change the coding rate (coding_rate) on the STRKT01 ?
I have already set the data_rate to the lowest possible :
“data_rate”: “SF12BW125”,
“coding_rate”: “4/5”,
To set the data rate, have a look at the “!loradr” command via USB to set the LoRa Data Rate and “?platformstatus” to double check. Restart the device after this procedure.
You can also change LORAWAN_DEFAULT_DATA_RATE in the main.c and send the “!defaultsettings” to use this new setting. Restart the device after this procedure.
To manage the Adaptive Data Rate (ADR), use the “!loraadronoff” command via USB and “?platformstatus” to double check. Restart the device after this procedure.
You can also change LORAWAN_ADR_STATE in the main.c and send the “!defaultsettings” to use this new setting. Restart the device after this procedure.
I found how to change the data rate ! ( see my post)
What I asked is how to change the coding rate .
“coding_rate”: “4/5”,
Thanks for an answer on this question.