"To configure the Button, Configuration Mode must be entered. To do that, press Key 1 for three seconds. All blue LEDs will light up and you will have confirmation in the RAK Serial Port Tool."

I have a RAK7201. I can hold that button for 3 minutes and the LEDs won't turn blue.

Thank you.

I ran into several minor issues with the WisDuino RAK811 evaluation board's documentation that made it quite difficult to configure my endpoint correctly. Implementing the following suggestions might help to improve the documentation:

• When configuring OTAA, the quick-start guide says to use the “DeviceProfile_OTAA” device profile in ChirpStack; however, this is not included in ChirpStack by default, and there's no mention of how it should be defined. Steps on how to properly configure the device profile should be included.
• The quick-start guide says ChirpStack does not require the device to have an application EUI set, so I didn't change mine from the default 0x0000000000000000. Unfortunately, if this value is not changed, the device will return ERROR 82 when trying to join the network. Once I figured out what this error code meant (see my next point), I was able to work around it by setting the application EUI to a dummy value (e.g. 0x0000000000000001); I think the documentation could be improved with a note to this effect.
• I couldn't find a listing of the AT command error codes anywhere in the RAK811 evaluation board's documentation. When my endpoint returned ERROR 82, I struggled to find out what that meant until I stumbled upon the error code table in the RAK811 breakout board's AT command manual. In my opinion, it would be better to include a link to that manual rather than the incomplete summary that's currently in the evaluation board's documentation.
• Steps describing how to correctly configure the LoRa channels in the quick-start guide would be helpful. My working assumption is that the channels used by the endpoint should match those used by the gateway.

Hi, I do have the Rak3172 development board and I'm using the example code for the board as well as the code for the gyro https://docs.rakwireless.com/Product-Categories/WisBlock/RAK12034/Quickstart/.
My problem is that I failed to get a timer interrupt working.
The Timer1 library is not working because it's a arduino library. So I thought to use bare metal programming using the cube IDE. Therefore I need to upload the code.

But how am I supposed to connect it to the board?

Or is there any timer based interrupt already implemented in Rui3?

Kind regards Dominik

Hi everyone,
I saw your website recently and it feels pretty good. I have a question about pdf documents.
Can you give me some tips on how to achieve this effect.
I have tried many methods recently without success.
Looking forward to your reply.

hi
Pinmapper :
i cant find the 14xxx E-ink display with it's board in the selection : could you pleas add it ?

thx ! :-)

Hi,

I just received my RAK7248. Is there a how to get started guide?

Hi guys,
can you add to the documentation of all your antennas, the antenna radiation pattern file, such as ant, msi or other?

Hi! Can't find anywhere the dimensjons on the outdoor case, can you upload this or tell me.

For RAK 7200

Current parameter: at+set_config=lora:send_interval:X
Good paramenter:at+set_config=lora:send_interval:X:Y

Set a certain channel on or off.
• X - the channel number, and you can check which channel can be set before you set it.
• Y - 0: off, 1: on

Hi there, I'm currently working on rak3172 in a little humid condition. I was wondering what is the "Operating Humidity" for rak3172 and rak3172-t?
Thanks in advance.

I tried to update my firmware for RAK7258 and after that i am unable to access my gateway via WiFi as it is not showing up in available list

Hello,

Can you please share a tutorial on how we could restore the backup on a bigger SD card?

Thank you,
Bogdan

I see the instructions for RAK3172 low-level development start with the STM32WL example code, then copy a handful of files to patch the resulting project.

This means that every time you run Cube to reconfigure peripherals or the LoRa application, the files need to be patched again, because Cube over-writes them.

Also, this means that the project can not be cloned into a new project using Cube

I did the same thing for the RAK3172-E that I did for the Seeed LoRa-E5 Mini; I created a new STM32CubeIDE project from scratch, configuring it the same as the example code, added BSP file support for the RAK3172 (including real battery level and a bit for the RAK5005 power switch) and then merged in the example code changes in lora_app.c.

This means the project can be re-generated as desired (with the warning that one needs to modify one line of code in lora_app.c to use LocalGetBatteryLevel, this is over-written by Cube), and that new projects can be created as desired using the 'new project from existing IOC' feature.

This is still the LoRaWAN End Node Client example from ST with a few changes for my own hardware, but represents a good starting point for application development when cloned.

Initial testing has proven good so far; I invite the experts at RAK to review my BSP file changes, and I also ask you to consider referencing the still-new repo in your documentation for low-level development.

Repo:

https://github.com/danak6jq/RAK3172

Hi
First things first. Your documentation on how to integrate with AWS IoT server is fantastic.
Since you started supporting mqtt in the gateway products, can you please publish some documentation on how to integrate with mqtt brokers.