RAK 5205 tracker

wistrio%20box here is the package we will provide soon come with Wistrio LoRa Tracker boards

2 Likes

Yes, interreting the new package. It’s similar concept same SodaqOne with a solar panel.

I read in the documentation, WisTrio has two ports for IPEX connectors LoRa and GPS. But I see only one hardware version with only SMA connectors.

I also noticed about the connectors. Let’s see if someone can provide information. I think that the boxed version should be provided with IPEX or internal antennas

os%20rak

2 Likes

4 posts were merged into an existing topic: TOOLS for TINKERERS

Thanks, yes, I have seen that … after more experiments, I have narrowed this down to the DEVEUI ( 60 C5 A8 FF FE 00 00 00). Entering that DEVEUI provokes the message. I will see if I can set the actual DEVEUI to something else on the device (some AT command ?) … This could be due to my repeated attempts to get this working and that DEVEUI being caached somewhere in the TTN Backend?? A bit out of my depth!

And I’ve just noticed that the last 3 bytes of the DEVEUI on the sticker on the device (6D 00 7E) differ from what is squirting out of the serial port

RAK5205 BreakBoard soft version: 1.1.6
LIS3DH init success
Move Detected INT1 src:0x00
ACC X:-688mg Y:-448mg Z:-624mg
BME680 init success
T: 27.12 degC, P: 1030.73 hPa, H 29.67 %rH , G: 7172 ohms
region = EU868
app_interval = 120
gps_stime = 60
msg confirm = 0
power save = 1

Selected LoraWAN 1.0.2 Region: EU868

Move Detected INT1 src:0x42
ACC X:-16mg Y:-16mg Z:0mg
OTAA:
Dev_EUI: 60 C5 A8 FF FE 00 00 00

you copy that Dev_EUI from the manual ?

Thank you, I have received my device today and was stuck trying to modify the APP EUI.

I was looking at the documention on their github and it is incorrect :thinking:

The right at command to modify the APP EUI is
at+app_eui=xxxxx

and not at+set_config=app_eui:xxxxx which was giving an ERROR

I was also trying the basic command at+version but it seems that it is not implemented in the loaded firmware. “RAK5205 BreakBoard soft version: 1.1.6”

My device is now connected on TTN :grinning:

1 Like

Yes, manual says use the DEVEUI on the label on the board. The problem is that the label disagrees with what the board reports on the serial port, and using what the board reports gives me the error I reported earlier. I am going to try to change via AT commands!

Ah! How do you get the board into a mode where it will accept AT commands, and is there an AT command to make the settings sticky (so they survive a power cycle)?

I have used the dev eui value from the console output to register the device on TTN and it worked fine

Just press the rest button and wait for the boot message

RAK5205 BreakBoard soft version: 1.1.6
LIS3DH init success
Move Detected INT1 src:0x00
ACC X:208mg Y:-48mg Z:-976mg
BME680 init success
T: 27.70 degC, P: 1027.01 hPa, H 28.86 %rH , G: 10676 ohms

You can then enter your at command.

You have to do it before the JOIN process has started

What DEVEUI are you getting ? My device reports 60 C5 A8 FF FE 00 00 00 but the sticker says 60 C5 A8 FF FE 6D 00 7E

Perhaps DEVEUI needs to be globally unique? And that is what provokes my error message?

Great!! Thanks for this info … I will try now :slight_smile:

In my case the dev eui from the terminal output and the sticker are the same.

Ok, I cannot get it to accept AT commands. I am using putty … the at_dev_eui … is not echoed to the screen.

Do I have to set any special end-of-line characters ? Half duplex etc? Set any jumpers?

Manual says …

at+dev_eui=60C5A8FFFF1C****\r\n

for example … so I enter four “*” characters after the DEVEUI and then press enter?

Sorry … have tried lots of combinations, none work!!

Success. Up and running on TTN now … used this sofrware as termnal (on windows 10) to issue AT commands https://www.compuphase.com/software_termite.htm with these settings and it all worked fine …

image

1 Like

Incidentally I don’t know what those asterisks are in the manual, but they are NOT required.

I am not familiar with putty as a console terminal.
I am using linux, but on windows, I used to like the terminal software called Tera Term (open source)

after each command you need to send a CR (carriage return) + LF (line feed). This is why you have the \r\n at the end of the example.
The way to enter the CR + LF depends on the software you use as a terminal. You can usually configure your software to automatically send CR + LF when you press enter.

So you need in fact only type this: at+dev_eui=60C5A8FFFF1C****
And you need to replace the stars by your real dev eui.

I think the correct value for your device should be the one on your sticker.
But the most important is that the dev eui that you are setting on your device matches the one you have entered on TTN when you registered the device.