Skip to content

Error Codes

Jump to bottom
Mictronics edited this page Jan 20, 2025 · 3 revisions

Meshtastic firmware error Codes that are shown in debug log.

Critical Errors

Source mesh.pb.h

  • 0 NONE
  • 1 TX_WATCHDOG A software bug was detected while trying to send lora.
  • 2 SLEEP_ENTER_WAIT A software bug was detected on entry to sleep.
  • 3 NO_RADIO No Lora radio hardware could be found
  • 4 UNSPECIFIED Not normally used
  • 5 UBLOX_UNIT_FAILED We failed while configuring a UBlox GPS.
  • 6 NO_AXP192 This board was expected to have a power management chip and it is missing or broken.
  • 7 INVALID_RADIO_SETTING The channel tried to set a radio setting which is not supported by this chipset, radio comms settings are now undefined.
  • 8 TRANSMIT_FAILED Radio transmit hardware failure. We sent data to the radio chip, but it didn't reply with an interrupt.
  • 9 BROWNOUT We detected that the main CPU voltage dropped below the minimum acceptable value
  • 10 SX1262_FAILURE Selftest of SX1262 radio chip failed.
  • 11 RADIO_SPI_BUG A (likely software but possibly hardware) failure was detected while trying to send packets. If this occurs on your board, please post in the forum so that we can ask you to collect some information to allow fixing this bug.
  • 12 FLASH_CORRUPTION_RECOVERABLE Corruption was detected on the flash filesystem but we were able to repair things. If you see this failure in the field please post in the forum because we are interested in seeing if this is occurring in the field.
  • 13 FLASH_CORRUPTION_UNRECOVERABLE Corruption was detected on the flash filesystem but we were unable to repair things. NOTE: Your node will probably need to be reconfigured the next time it reboots (it will lose the region code etc...) If you see this failure in the field please post in the forum because we are interested in seeing if this is occurring in the field.

Routing Errors

Source mesh.pb.h

  • 0 NONE This message is not a failure.
  • 1 NO_ROUTE Our node doesn't have a route to the requested destination anymore.
  • 2 GOT_NAK We received a nak while trying to forward on your behalf.
  • 3 TIMEOUT
  • 4 NO_INTERFACE No suitable interface could be found for delivering this packet.
  • 5 MAX_RETRANSMIT We reached the max retransmission count (typically for naive flood routing).
  • 6 NO_CHANNEL No suitable channel was found for sending this packet (i.e. was requested channel index disabled?).
  • 7 TOO_LARGE The packet was too big for sending (exceeds interface MTU after encoding).
  • 8 NO_RESPONSE The request had want_response set, the request reached the destination node, but no service on that node wants to send a response (possibly due to bad channel permissions).
  • 9 DUTY_CYCLE_LIMIT Cannot send currently because duty cycle regulations will be violated.
  • 32 BAD_REQUEST The application layer service on the remote node received your request, but considered your request somehow invalid.
  • 33 NOT_AUTHORIZED The application layer service on the remote node received your request, but considered your request not authorized (i.e you did not send the request on the required bound channel).
  • 34 PKI_FAILED The client specified a PKI transport, but the node was unable to send the packet using PKI (and did not send the message at all).
  • 35 PKI_UNKNOWN_PUBKEY The receiving node does not have a Public Key to decode with.
  • 36 ADMIN_BAD_SESSION_KEY Admin packet otherwise checks out, but uses a bogus or expired session key.
  • 37 ADMIN_PUBLIC_KEY_UNAUTHORIZED Admin packet sent using PKC, but not from a public key on the admin key list.

RadioLib Errors

Source RadioLib

  • 0 NONE No error, method executed successfully.
  • -1 UNKNOWN There was an unexpected, unknown error. If you see this, something went incredibly wrong. Your Arduino may be possessed, contact your local exorcist to resolve this error.
  • -2 CHIP_NOT_FOUND Radio chip was not found during initialization. This can be caused by specifying wrong chip type in the constructor (i.e. calling SX1272 constructor for SX1278 chip) or by a fault in your wiring (incorrect slave select pin).
  • -3 MEMORY_ALLOCATION_FAILED Failed to allocate memory for temporary buffer. This can be cause by not enough RAM or by passing invalid pointer.
  • -4 PACKET_TOO_LONG Packet supplied to transmission method was longer than limit.
  • -5 TX_TIMEOUT Timed out waiting for transmission finish.
  • -6 RX_TIMEOUT Timed out waiting for incoming transmission.
  • -7 CRC_MISMATCH The calculated and expected CRCs of received packet do not match. This means that the packet was damaged during transmission and should be sent again.
  • -8 INVALID_BANDWIDTH The supplied bandwidth value is invalid for this module.
  • -9 INVALID_SPREADING_FACTOR The supplied spreading factor value is invalid for this module.
  • -10 INVALID_CODING_RATE The supplied coding rate value is invalid for this module.
  • -11 INVALID_BIT_RANGE Internal only.
  • -12 INVALID_FREQUENCY The supplied frequency value is invalid for this module.
  • -13 INVALID_OUTPUT_POWER The supplied output power value is invalid for this module.
  • -14 PREAMBLE_DETECTED LoRa preamble was detected during channel activity detection. This means that there is some LoRa device currently transmitting in your channel.
  • -15 CHANNEL_FREE No LoRa preambles were detected during channel activity detection. Your channel is free.
  • -16 SPI_WRITE_FAILED Real value in SPI register does not match the expected one. This can be caused by faulty SPI wiring.
  • -17 INVALID_CURRENT_LIMIT The supplied current limit value is invalid.
  • -18 INVALID_PREAMBLE_LENGTH The supplied preamble length is invalid.
  • -19 INVALID_GAIN The supplied gain value is invalid.
  • -20 WRONG_MODEM User tried to execute modem-exclusive method on a wrong modem. For example, this can happen when you try to change LoRa configuration when FSK modem is active.
  • -21 INVALID_NUM_SAMPLES The supplied number of RSSI samples is invalid.
  • -22 INVALID_RSSI_OFFSET The supplied RSSI offset is invalid.
  • -23 INVALID_ENCODING The supplied encoding is invalid.
  • -24 LORA_HEADER_DAMAGED LoRa packet header has been damaged.
  • -25 UNSUPPORTED The requested functionality is not supported for this device.
  • -26 INVALID_DIO_PIN The specified DIO pin does not exist on this device.
  • -27 INVALID_RSSI_THRESHOLD The supplied RSSI threshold is invalid.
  • -28 NULL_POINTER A NULL pointer has been encountered. If you see this, there may be a potential security vulnerability.
  • -29 INVALID_IRQ The requested IRQ configuration is not valid for this module.
  • -101 INVALID_BIT_RATE The supplied bit rate value is invalid.
  • -102 INVALID_FREQUENCY_DEVIATION The supplied frequency deviation value is invalid.
  • -103 INVALID_BIT_RATE_BW_RATIO The supplied bit rate to bandwidth ratio is invalid. See the module datasheet for more information.
  • -104 INVALID_RX_BANDWIDTH The supplied receiver bandwidth value is invalid.
  • -105 INVALID_SYNC_WORD The supplied FSK sync word is invalid.
  • -106 INVALID_DATA_SHAPING The supplied FSK data shaping option is invalid.
  • -107 INVALID_MODULATION The current modulation is invalid for the requested operation.
  • -108 INVALID_OOK_RSSI_PEAK_TYPE Supplied Peak type is invalid.
  • -109 INVALID_BIT_RATE_TOLERANCE_VALUE Supplied Bitrate tolerance value is out of Range.
  • -201 INVALID_SYMBOL Supplied APRS symbol is invalid.
  • -202 INVALID_MIC_E_TELEMETRY Mic-E Telemetry is invalid.
  • -203 INVALID_MIC_E_TELEMETRY_LENGTH Mic-E Telemetry length is invalid (only 0, 2 or 5 is allowed).
  • -204 MIC_E_TELEMETRY_STATUS Mic-E message cannot contain both telemetry and status text.
  • -301 INVALID_SSDV_MODE SSDV mode is invalid.
  • -302 INVALID_IMAGE_SIZE Image size is invalid.
  • -303 INVALID_IMAGE_QUALITY Image quality is invalid.
  • -304 INVALID_SUBSAMPLING Image subsampling is invalid.
  • -401 INVALID_RTTY_SHIFT Supplied RTTY frequency shift is invalid for this module.
  • -402 UNSUPPORTED_ENCODING Supplied RTTY encoding is invalid.
  • -501 INVALID_DATA_RATE Supplied data rate is invalid.
  • -502 INVALID_ADDRESS_WIDTH Supplied address width is invalid.
  • -503 INVALID_PIPE_NUMBER Supplied data pipe number is invalid.
  • -504 ACK_NOT_RECEIVED ACK packet from destination module was not received within 15 retries.
  • -601 INVALID_NUM_BROAD_ADDRS Supplied number of broadcast addresses is invalid.
  • -701 INVALID_CRC_CONFIGURATION Supplied CRC configuration is invalid.
  • -702 LORA_DETECTED Detected LoRa transmission while scanning channel.
  • -703 INVALID_TCXO_VOLTAGE Supplied TCXO reference voltage is invalid.
  • -704 INVALID_MODULATION_PARAMETERS Bit rate / bandwidth / frequency deviation ratio is invalid. See SX126x datasheet for details.
  • -705 SPI_CMD_TIMEOUT SX126x timed out while waiting for complete SPI command.
  • -706 SPI_CMD_INVALID SX126x received invalid SPI command.
  • -707 SPI_CMD_FAILED SX126x failed to execute SPI command. Often this means that the module is trying to use TCXO while XTAL is connected (or vice versa). Make sure your crystal setup (e.g. TCXO reference voltage) matches your hardware by setting "tcxoVoltage" to 0 when using XTAL module, or to appropriate value when using TCXO module.
  • -708 INVALID_SLEEP_PERIOD The supplied sleep period is invalid.
  • -709 INVALID_RX_PERIOD The supplied Rx period is invalid.
  • -801 INVALID_CALLSIGN The provided callsign is invalid.
  • -802 INVALID_NUM_REPEATERS The provided repeater configuration is invalid.
  • -803 INVALID_REPEATER_CALLSIGN One of the provided repeater callsigns is invalid.
  • -901 RANGING_TIMEOUT Timed out waiting for ranging exchange finish.
  • -1001 INVALID_PAYLOAD The provided payload data configuration is invalid.
  • -1002 ADDRESS_NOT_FOUND The requested address was not found in the received data.
  • -1003 INVALID_FUNCTION The function code is invalid. 2 Bits only.
  • -1101 NETWORK_NOT_JOINED Unable to restore existing LoRaWAN session because this node did not join any network yet.
  • -1102 DOWNLINK_MALFORMED Malformed downlink packet received from network server.
  • -1103 INVALID_REVISION Network server requested switch to unsupported LoRaWAN revision.
  • -1104 INVALID_PORT Invalid LoRaWAN uplink port requested by user, or downlink received at invalid port.
  • -1105 NO_RX_WINDOW User did not enable downlink in time.
  • -1106 NO_CHANNEL_AVAILABLE There are no channels available for the requested datarate.
  • -1107 INVALID_CID Invalid LoRaWAN MAC command ID.
  • -1108 UPLINK_UNAVAILABLE User requested to start uplink while still inside RX window or under dutycycle.
  • -1109 COMMAND_QUEUE_FULL Unable to push new MAC command because the queue is full.
  • -1110 COMMAND_QUEUE_ITEM_NOT_FOUND Unable to delete MAC command because it was not found in the queue.
  • -1111 JOIN_NONCE_INVALID Unable to join network because JoinNonce is not higher than saved value.
  • -1112 N_FCNT_DOWN_INVALID Received downlink Network frame counter is invalid (lower than last heard value).
  • -1113 A_FCNT_DOWN_INVALID Received downlink Application frame counter is invalid (lower than last heard value).
  • -1114 DWELL_TIME_EXCEEDED Uplink payload length at this datarate exceeds the active dwell time limitations.
  • -1115 CHECKSUM_MISMATCH The buffer integrity check did not match the supplied checksum value.
  • -1116 NO_JOIN_ACCEPT No JoinAccept was received - check your keys, or otherwise likely a range issue!
  • -1117 LORAWAN_SESSION_RESTORED The LoRaWAN session was successfully re-activated.
  • -1118 LORAWAN_NEW_SESSION A new LoRaWAN session is started.
  • -1119 NONCES_DISCARDED The supplied Nonces buffer is discarded as its activation information is invalid.
  • -1120 SESSION_DISCARDED The supplied Session buffer is discarded as it doesn't match the Nonces.
  • -1121 INVALID_MODE The requested command is unavailable under the current LoRaWAN mode.
  • -1200 INVALID_WIFI_TYPE The selected 802.11 WiFi type is invalid.
  • -1201 GNSS_SUBFRAME_NOT_AVAILABLE GNSS subframe not available in the next 2.3 seconds.
  • -1210 GNSS_DEMOD_OFFSET Offset of GNSS demodulator errors. See LR11x0 datasheet for details on the actual demodulator error.
Clone this wiki locally