What causes a DATA_DOWN_GATEWAY error?

jcwren · April 21, 2024, 7:26pm

I’ve had Chirpstack V3 running for ages with no issues. I added a second gateway on April 1st, no issues at all. I happened to take a look at some of the applications I have running and as of April 13th, I’m now seeing DATA_DOWN_ERROR errors showing up in the Errors graph. Since adding the gateway I haven’t made any other changes. Googling for this error didn’t yield any useful results.

What are these, and why would I suddenly start seeing them?

brocaar · May 2, 2024, 10:26am

Under the device events tab, you will probably log items with more details. In general causes can be:

github.com

Lora-net/packet_forwarder/blob/master/PROTOCOL.TXT#L418


      
          	"txpk_ack": {...}
          }
          ```
          
          That object contain status information concerning the associated PULL_RESP packet.
          
           Name |  Type  | Function
          :----:|:------:|------------------------------------------------------------------------------
          error | string | Indication about success or type of failure that occured for downlink request.
          
          The possible values of "error" field are:
          
           Value             | Definition
          :-----------------:|---------------------------------------------------------------------
           NONE              | Packet has been programmed for downlink
           TOO_LATE          | Rejected because it was already too late to program this packet for downlink
           TOO_EARLY         | Rejected because downlink packet timestamp is too much in advance
           COLLISION_PACKET  | Rejected because there was already a packet programmed in requested timeframe
           COLLISION_BEACON  | Rejected because there was already a beacon planned in requested timeframe
           TX_FREQ           | Rejected because requested frequency is not supported by TX RF chain
           TX_POWER          | Rejected because requested power is not supported by gateway

jcwren · May 4, 2024, 12:23am

Maybe I don’t know what I’m looking for, but I don’t think v3 has a device events tab?

Also, the DATA_DOWN_ERROR doesn’t appear in the list of errors there? Unless that’s a high level error type, and the sub-error type would be one of those.

brocaar · May 9, 2024, 1:34pm

Please see Event logging - ChirpStack open-source LoRaWAN<sup>®</sup> Network Server.

As an alternative, you can also temporarily turn on JSON encoding (in the ChirpStack Gateway Bridge config) and inspect the gateway ack events.

system · July 20, 2024, 7:26pm

This topic was automatically closed after 90 days. New replies are no longer allowed.