Rak811 Tracker Board


Is anyone else using these new products?

I’m interested in your experiences building code to run on the Rak811 hardware as they look really nice for a cheap ttnmapper node.

I’m tempted to use a Qi charger receiver and have a rechargeable motion activated mapper

(Frml55) #2

Does anyone know, when the 868MHz version of RAK811 Tracker board will be available?

(Chace) #3

They are open source, you can buy a 915MHz version, and then modify it into your desired Region.

(Jezd) #4

its available now I think, just about to order a couple

(Jezd) #5

ps it was, I ordered the last one I think


a limited quantity available now @868


What environment must be used to program it?
The document Node Location Solution Kit With TTN V1.0.pdf tells a lot, very detailed how to setup ttn & cayenne, but nothing about the programming environment.
In github the explanaitions are rather slimm.
Thanks for a helpful hint


I bought one a few days back but I think I’ll have to install some software.
lots of info on the RAK site
like the user manual


should have CoIDE installed to develop.

(Phil Wilko) #10

There is a huge amount of documentation on their website/GITHUB but finding the right stuff is a challenge!
This manual appears to be where to start.


OK. I managed to install all neede parts, changed Commissioning and the Region and could successfully compile it.
At the end I miss a j-link programmer with the appropriate connector to upload the program :sob:

RAK811 tracker board compilation
documentation	http://www.rakwireless.com/en/download/RAK811%20TrackerBoard/HardWare%20Design
download and install	http://www.coocox.org/software/coide.php									--> CoIDE-V2Beta-20170510.exe
			https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads		--> gcc-arm-none-eabi-7-2017-q4-major-win32.exe

change 			Commissioning.h
change configuration	remove Defined Symbol  --> AS923
			add                    --> REGION_EU868   (not only EU868)
build			F7		
			Program Size:
			text	   data	    bss	    dec	    hex	filename
		78492	   1644	   6736	  86872	  15358	RAK811Breakboard_classA.elf  

upload failed by missing J-Link programmer


(Frml55) #12

Does somone know how to connect RAK811 Tracker to J-Link Adapter (Segger)?
I didn’t find much information about.
My proposal:
JLINK <-> RAK811
1 VRef <-> VCC? (JLINK is 5V, but RAK811 is 3.3V?!?)
6 GND <-> GND
13 TDO/SWO <-> ???


I asked RAKwireless @ aliexpress, but I have no answer jet.
I’ll publish it as I’ll get some information from them

(Tuftec) #14

I would suggest contacting the guys at RAK directly.
They helped me with a binary that I just had to load onto my RAK811 WisNode board to do soe some local coverage mapping (the code was direved from their tracking s/w).

They have been very helpful.




You don‘t need a J-Link debugger. You can compile the sources to get a .bin file. Then you need a piece of software you can download from ST to flash the board. The documentation of RAK explains this.


with what piece of hardware?
the documentation say to use j-tag.
not shure if „flash demonstrator“ could be used.
if you have other experiance, please document your procedure here. thanks


You can use the flash loader demonstrator.

In this document the procedure is explained on page 10. http://docs.rakwireless.com/en/RAK811%20TrackerBoard/Software%20Development/RAK811%20TrackerBoard%20User%20manual%20V1.1.pdf

In CoIDE go to the Configuration window and there to Output.
Make sure that Create BIN File is checked.

When using the flash loader demonstrator make sure you change the file type to .bin in the file selection dialog box when you locate the .bin file from your compile run.

(Kalon33) #18

Does anyone have tried to use a BME280 sensor with the RAK811 trackerboard? How? Any example code? The example code provided by RAK (that doesn’t support it) is a bit strange to understand, is that me or not? Any better examples from your experiments with it?


thanks for your suggestions and tipps.
I could manage to compile and upload via "demonstrator"
That’s the good news
The bad is that

  1. The demonstrator recognizes the board only after several disconnections/connections of the usb.
    (I’ll get a j-tag borrowed. probably that runs better)
  2. The software (classA) has a define which must be deleted in DEVICE_EUI !!!
    #define IEEE_OUI 0x60, 0xC5, 0xA8
    #define LORAWAN_DEVICE_EUI { IEEE_OUI, 0x00, 0x47, … } <-- DELETE IEEE_OUI
  3. The board sends all 60 to 90 sec messages on SF12
    first after join on port 0 a message with 12 bytes, but in the device it shows [not provided]
    19:10:21 867.7 lora 4/5 SF12BW125 1155.10 dev addr:26012D67 payload size:12 bytes --> 19:10:20 0 0 dev id:rak811_tracker_01 payload:[not provided]
    physical pyload from the gateway 40672D012680 09007A35729A first 6 bytes are always the same
    then messages on port 4 , 2 , 4 with 21 bytes
    19:13:09 868.5 lora 4/5 SF12BW125 1482.83 dev addr:26012D67 payload size:21 bytes --> 19:13:09 3 4 dev id:rak811_tracker_01 payload:0267010E0403019B
    cycling through port 0 , x , x , x , 0 , x , x , x , 0 , …

any idea what the meaning of the message on port 0 could be?

(Chace) #20

The data of port 0 is the wrong data sent when GPS acquisition fails. The latest project has been modified.Details you can be in:http://support.rakwireless.com/topic/196/rak811-lora-tracker-test_gps-never-called-in-section-main