Error DOWNLINK_PAYLOAD_SIZE on US915 Region

Hello friends,

I was trying to send some order to device, but I’ve got the error:
Code: DOWNLINK_PAYLOAD_SIZE
Level: ERROR
image

I read that the payload size is specified by the channel, but i don’t know why the maximum size is 11.

The Device profile is:

The region configuration is: `
[[regions]]

  # Name is an user-defined identifier for this region.
  name="us915_1"

  # Common-name refers to the common-name of this region as defined by
  # the LoRa Alliance.
  common_name="US915"

  # Gateway configuration.
  [regions.gateway]

    # Force gateways as private.
    #
    # If enabled, gateways can only be used by devices under the same tenant.
    force_gws_private=false

    # Gateway backend configuration.
    [regions.gateway.backend]

      # The enabled backend type.
      enabled="mqtt"

      # MQTT configuration.
      [regions.gateway.backend.mqtt]

        # Event topic template.
        event_topic="gateway/+/event/+"

        # Command topic template.
        command_topic="gateway/{{ gateway_id }}/command/{{ command }}"

        # MQTT server (e.g. scheme://host:port where scheme is tcp, ssl or ws)
        server="tcp://mqtt-server:1883"

        username=""
        password=""

        # Quality of service level
        #
        # 0: at most once
        # 1: at least once
        # 2: exactly once
        #
        # Note: an increase of this value will decrease the performance.
        # For more information: https://www.hivemq.com/blog/mqtt-essentials-part-6-mqtt-quality-of-service-levels
        qos=0

        # Clean session
        #
        # Set the "clean session" flag in the connect message when this client
        # connects to an MQTT broker. By setting this flag you are indicating
        # that no messages saved by the broker for this client should be delivered.
        clean_session=true

        # Client ID
        #
        # Set the client id to be used by this client when connecting to the MQTT
        # broker. A client id must be no longer than 23 characters. When left blank,
        # a random id will be generated. This requires clean_session=true.
        client_id=""

   # Region specific network configuration.
  [regions.network]
    
    # Installation margin (dB) used by the ADR engine.
    #
    # A higher number means that the network-server will keep more margin,
    # resulting in a lower data-rate but decreasing the chance that the
    # device gets disconnected because it is unable to reach one of the
    # surrounded gateways.
    installation_margin=10

    # RX window (Class-A).
    #
    # Set this to:
    # 0: RX1 / RX2
    # 1: RX1 only
    # 2: RX2 only
    rx_window=0

    # RX1 delay (1 - 15 seconds).
    rx1_delay=10

    # RX1 data-rate offset
    rx1_dr_offset=0

    # RX2 data-rate
    rx2_dr=0

    # RX2 frequency (Hz)
    rx2_frequency=923300000

    # Prefer RX2 on RX1 data-rate less than.
    #
    # Prefer RX2 over RX1 based on the RX1 data-rate. When the RX1 data-rate
    # is smaller than the configured value, then the Network Server will
    # first try to schedule the downlink for RX2, failing that (e.g. the gateway
    # has already a payload scheduled at the RX2 timing) it will try RX1.
    rx2_prefer_on_rx1_dr_lt=0

    # Prefer RX2 on link budget.
    #
    # When the link-budget is better for RX2 than for RX1, the Network Server will first
    # try to schedule the downlink in RX2, failing that it will try RX1.
    rx2_prefer_on_link_budget=false

    # Downlink TX Power (dBm)
    #
    # When set to -1, the downlink TX Power from the configured band will
    # be used.
    #
    # Please consult the LoRaWAN Regional Parameters and local regulations
    # for valid and legal options. Note that the configured TX Power must be
    # supported by your gateway(s).
    downlink_tx_power=-1

    # ADR is disabled.
    adr_disabled=true

    # Minimum data-rate.
    min_dr=2

    # Maximum data-rate.
    max_dr=8

     # Enabled uplink channels.
      #
      # Use this when ony a sub-set of the by default enabled channels are being
      # used. For example when only using the first 8 channels of the US band.
      # Note: when left blank / empty array, all channels will be enabled.
    enabled_uplink_channels=[8, 9, 10, 11, 12, 13, 14, 15, 65]

    # Class-B configuration.
    [regions.network.class_b]

    # Ping-slot data-rate.
    ping_slot_dr=8

    # Ping-slot frequency (Hz)
    #
    # set this to 0 to use the default frequency plan for the configured region
    # (which could be frequency hopping).
    ping_slot_frequency=0`

Please someone could help us or if you need some extra info, let us know.

Hey :wave:,
Check this out: https://lora-alliance.org/wp-content/uploads/2020/11/2015_-_lorawan_specification_1r0_611_1.pdf page 41
For DR0, the maximum application payload is 11 bytes

1 Like

These don’t look right for US915. Are you intending to not use ADR? If so, the device being at DR0 (11 bytes), as noted above, looks correct - depending on what your firmware does.

We cant use ADR because our IOT Device is going to move. How can change the DR0 configuration in Chirpstack 4?
image

That is right, I wan to use DR3, how can i do it in Chirpstack4?

If you’re not going to use ADR, I believe your device firmware will need to dictate what DR it’s running at.

1 Like

This is the device configuration:

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