Reset RAK7205 Tracker

Is there a way to RESET the RAK7205 tracker through downlink by sending a payload?

Short answer is no, unless itā€™s hidden somewhere in the documentation I havenā€™t seen.

What do you mean by reset? What should the tracker do when you ā€˜reset itā€™? Why do you need it to be reset?

1 Like

@nmcc

I concur, seeing how I probably wrote the documentation, at least partially :slight_smile:
But you are making a good point, reset in what way:
Reboot the board and initiate network join procedure again (power cycle)
Wipe settings with another set of keys, perhaps?
Etc.

Regards
Vladislav

I meant rebooting the tracker node. It would be useful if we have a command to ā€˜resetā€™ the node instead of pressing the RESET button on the PCB.

Dragino LDS01 has that feature.
image

image

Thanks @nmcc
See my comments above :slight_smile:

Hiļ¼
Pradeekaļ¼Œ

I am sorry to tell you that RAK7205 cannot receive the issuing instructions for now, perhaps this is a good suggestion and will be used in the next version of the requirement.
If you are interested, you can also modify the calling RUI code to implement this feature!

Regards

Thanks for the clarification. Which product model I should use in the RUI compiler? RAK811?

Yes,you need choose RAK811.

Please start implementing it and I will keep discussing it with you.

1 Like

Which app? app_5205 or app_RAK811?

Positive choice RAK5205ļ¼ :grin: :grin: :grin:

1 Like

I need some time to understand the codebase. I havenā€™t done ā€˜heavyā€™ programming since 2015 :slight_smile: But I want to give it a try.

I think this is the place we should modifyā€¦

Yes, this is it. I look forward to your success. :fist_right: :fist_left:

1 Like

After selecting the reset instruction, you can call the Reset interface to start it.

1 Like

Why? What is it doing that needs a reset?

Not only for RESET. It is also useful to change the transmission time interval.

This function doesnā€™t get executed when data received. It should output something on the ā€˜RAK SERIAL PORT TOOLā€™ for downlink packets.

void LoRaReceive_callback(RUI_RECEIVE_T* Receive_datapackage)
{
char hex_str[3] = {0};
RUI_LOG_PRINTF(ā€œat+recv=%d,%d,%d,%dā€, Receive_datapackage->Port, Receive_datapackage->Rssi, Receive_datapackage->Snr, Receive_datapackage->BufferSize);

if ((Receive_datapackage->Buffer != NULL) && Receive_datapackage->BufferSize) {
    RUI_LOG_PRINTF(":");
    for (int i = 0; i < Receive_datapackage->BufferSize; i++) {
        sprintf(hex_str, "%02x", Receive_datapackage->Buffer[i]);
        RUI_LOG_PRINTF("%s", hex_str); 
    }
}
RUI_LOG_PRINTF("\r\n");

}

But donā€™t you see any packets when you send them down, does it make a difference?

I sent a packet through downlink.

It appeared in the TTN as:
image

RAK serial port tool - no data

Iā€™m using ABP. Here is the status.

at+get_config=lora:status
Wake up
at+get_config=lora:status
OK.


==============LoRaWAN Status List================
Work Mode: LoRaWAN
Region: EU433
Send_interval: 600s
Auto send status: true.
Send_interval work at sleep
Join_mode: ABP
DevAddr: 26011955
AppsKey: 0A2B85A5E3DA535BE7145C8424A2570C
NwksKey: 711B4BF686DA6771A2E6F547FB264376
Class: A
Joined Network:true
IsConfirm: false
AdrEnable: true
EnableRepeaterSupport: false
RX2_CHANNEL_FREQUENCY: 434665000, RX2_CHANNEL_DR:0
RX_WINDOW_DURATION: 3000ms
RECEIVE_DELAY_1: 1000ms
RECEIVE_DELAY_2: 2000ms
JOIN_ACCEPT_DELAY_1: 5000ms
JOIN_ACCEPT_DELAY_2: 6000ms
Current Datarate: 5
Primeval Datarate: 5
ChannelsTxPower: 0
UpLinkCounter: 10
DownLinkCounter: 0
===================List End======================


You can see the DownLinkCounter is 0.

You can try to change to classC, and then send the uplink, and then send the data, if itā€™s classA, you have to send the data for every uplink.

It doesnā€™t show anything for Class A and C.

NOTE: It shows an error for at+send=ā€¦