Get data down tx-info error on loraserver log

Hello,

This is my first time using loraserver.io, and I am getting the following (last line) error in the loraserver log.

Mar 15 17:51:12 raspberrypi loraserver[493]: time=“2018-03-15T17:51:12Z” level=info msg=“backend/gateway: rx packet received”
Mar 15 17:51:12 raspberrypi loraserver[493]: time=“2018-03-15T17:51:12Z” level=info msg=“rx info sent to network-controller” dev_eui=0072ab66f0dfb87e
Mar 15 17:51:12 raspberrypi loraserver[493]: time=“2018-03-15T17:51:12Z” level=info msg=“device updated” dev_eui=0072ab66f0dfb87e
Mar 15 17:51:12 raspberrypi loraserver[493]: time=“2018-03-15T17:51:12Z” level=info msg=“finished unary call with code OK” grpc.code=OK grpc.method=UpdateDevice grpc.service=ns.NetworkServer grpc.start_time=“2018-03-15T17:51:12Z” grpc.time_ms=11.747 peer.address="[::1]:60982" span.kind=server system=grpc
Mar 15 17:51:12 raspberrypi lora-app-server[494]: time=“2018-03-15T17:51:12Z” level=info msg=“finished client unary call” grpc.code=OK grpc.method=UpdateDevice grpc.service=ns.NetworkServer grpc.time_ms=16.089 span.kind=client system=grpc
Mar 15 17:51:12 raspberrypi lora-app-server[494]: time=“2018-03-15T17:51:12Z” level=info msg=“device updated” dev_eui=0072ab66f0dfb87e
Mar 15 17:51:12 raspberrypi lora-app-server[494]: time=“2018-03-15T17:51:12Z” level=info msg=“handler/mqtt: publishing data-up payload” topic=application/1/node/0072ab66f0dfb87e/rx
Mar 15 17:51:13 raspberrypi lora-app-server[494]: time=“2018-03-15T17:51:13Z” level=info msg=“finished unary call with code OK” grpc.code=OK grpc.method=HandleUplinkData grpc.service=as.ApplicationServer grpc.start_time=“2018-03-15T17:51:12Z” grpc.time_ms=396.794 peer.address=“127.0.0.1:44886” span.kind=server system=grpc
Mar 15 17:51:13 raspberrypi loraserver[493]: time=“2018-03-15T17:51:13Z” level=info msg=“finished client unary call” grpc.code=OK grpc.method=HandleUplinkData grpc.service=as.ApplicationServer grpc.time_ms=400.25 span.kind=client system=grpc
Mar 15 17:51:13 raspberrypi loraserver[493]: time=“2018-03-15T17:51:13Z” level=info msg=“device-session saved” dev_addr=07bb6d21 dev_eui=0072ab66f0dfb87e
Mar 15 17:51:13 raspberrypi loraserver[493]: time=“2018-03-15T17:51:13Z” level=error msg=“processing rx packet error: run uplink response flow error: get data down tx-info error: lorawan/band: invalid data-rate offset” data_base64="QCFtuweAqQABt3j7apX9MSI6nwQ="

Anyone know why this error appears? I am having problems with the downlink, so maybe this is the reason.

Thanks in advance!

Could you let me know the following?

  • Which version of LoRa Server are you using
  • The configured band
  • Did you OTAA or ABP the device?
  • What is the RX1 data-rate offset in the device-profile
  • What is the rx1_dr_offset value in your loraserver.toml configuration file

Hello,

  • I am using 0.25.0
  • The configured band is US_902_928
  • It is ABP.
  • Set it to 8. (I am not totally sure which value I should enter)
  • It is the default value 0.

The last two values should be the same?

Please refer to the LoRaWAN Regional Parameters specification for valid values. My assumption is that setting them both to 0 solves your issue. This is the data rate offset, not Tue data rate!

Hello,

It did not solve the problem.

Is this data rate offset related to the rx window? According to the LoRaWAN Regional Specification, this values should be in the 0 to 3 range, so I do not know why is sending the error message.

The rx1_dr_offset is the offset applied to the uplink Data Rate to determine the Downlink Data Rate in the RX1 windows.
eg. if the rx1_dr_offset = 0 then a downlink in response to an uplink will use the same DR inside the RX1

Please note that you need to reactivate the device after changing the device profile.

Hello,
… reactivate the device after changing the device profile…

As I am not well versed in Loraserver, what would I need to do to reactivate a device, and where would I be changing the device profile?

Thanks, Richard

Re-activate is either how you would activate an ABP device. Re-activating an OTAA device means it needs to re-join. The device-profile is documented here: https://www.loraserver.io/lora-app-server/use/device-profiles/.

Hello, and thank you.
Would you kindly make the backgrounds to the checkmarks and x’s darker so I can actually see what they are.
You say in the text, “Fields marked with an X are implemented by LoRa (App) Server.”, but did you mean to say fields marked with a checkmark???

Hello Brocaar,

I reactivate the ABP device, and now the error is gone! In fact, now I see that the gateway is sending a ACK downlink message. (I am not receiving the ACK in the device, but that another issue… )

Thank you, for me is closed!

1 Like