RAK10701L Latest Firmware

WisBlock
1

Hi there,

I have a RAK10701L Field Tester that I bought about a year ago. I onboarded it to get it working with AWS IoT Core for LoraWAN back then. When I switch on the tester, it connects to the Wis Gateway and it displays a “Joined” label. Then, it displays a “sending” label, and that’s is all it does. I can confirm that AWS does get the LoraWAN packet because I configured it to send an SMS message each time the tester sends a signal. I do get the SMS message, but the tester does not display RSSI, distance, or anything else.

I read a post on LinkedIn from @carlrowan that a new firmware update was going to be released, so that the field tester could work directly with a RAK WisGate Edge to display information without having to use a backhaul. Is there an update to this?

Much thanks!

2

Welcome to RAK forum @sergio ,

We are finalizing the documentation but I here’s a current draft (not the final one yet).

I do not use AWS but there is section there dedicated for AWS.

You need to use the Field Test extension that will handle the processing of the metadata of uplinks and who will initiate the downlink.

Here’s the Field Test extension guide for AWS - WisGateOS 2 Manual | Customizable LoRaWAN Gateway Software

3

Hi Carl,

Thank you for your prompt response! I followed the steps described on the guide you shared. It didn’t work for me, so I did some troubleshooting and found some errors:

*** Error 1:

The guide mentions that the SQL statement should read:

SELECT * FROM ‘SendFieldTesterDownlink’

So, the Lambda function did not to trigger. After changing it to:

SELECT * FROM ‘RecvFieldTesterUplink’

the Lambda function executed.

*** Error 2

The Lambda code has a few discrepancies in relation to the fields I get from my field tester, so I updated it to look like this:

device_id = event[“deviceID”] >>> device_id = event[“WirelessDeviceId”]
data = event[“data”] >>> data = event[“PayloadData”]
fPort = event[“fPort”] >>> fPort = event.get(“WirelessMetadata”, {}).get(“LoRaWAN”, {}).get(“FPort”)

I also had to update some permissions on the IAM console, but that was a problem with my configuration, not the guide.

After these corrections, I got no luck getting a downstream message to update the info in my field tester. Also, my field tester extension doesn’t show anything:

Screenshot 2025-05-05 at 4.59.35 p.m.
Screenshot 2025-05-05 at 4.59.35 p.m.2470×1272 119 KB

Any pointers on how to solve this issue?

I can confirm that:

  1. The field tester successfully joined the gateway and sends periodic uplink messages
  2. AWS IoT gets the message from the field tester. Subscribing to the “RecvFieldTesterUplink” MQTT topic shows the information sent up-link.
  3. The Lambda function fires, runs, and exits with no error code.
  4. Apparently, downlink messages are being queued, but subscribing to “SendFieldTesterDownlink” shows nothing.
4

Hi @sergio ,

I am checking this now with the team. I’ll let you know as soon as I got any info/update.

5

Hi @carlrowan, any news regarding this topic?

6

Hi @sergio ,

It seems the issue is on the MQTT integration.

I have some questions.

  1. When you said the downlink messages are being queued, did you see this in AWS or in your Gateway logs?
  2. Will you be able to send us your gateway logs?
  3. The Field Tester is working on LinkCheck mode ok right? You can see downlink parameters?
  4. What regional parameters you have?
  5. Can you please share your configuration tab of the Field Test Data Processor.

Btw, you can also raise this issue on [email protected] (just incase you want it in private) and inform that we already have initial conversation here in forum. Our customer support team will tag me on the ticket.