DroneNet PPP stuck "reconnecting", can't load params in Mission Planner

General
1

Matek H743-WING V3, custom ArduPlane 4.7.0 with PPP. DroneNet BB-DRN-C-1.

Wiring: DroneNet USART → FC UART7/SERIAL1 (TX,RX,RTS,CTS,GND). CAN → FC CAN. Powered via 5V Input port (5.0V clean).

Params: SERIAL1_PROTOCOL=48, SERIAL1_BAUD=12500000, CAN_P1_DRIVER=1, CAN_D1_PROTOCOL=1, NET_ENABLE=1, NET_OPTIONS=1.

Works: DroneNet shows on CAN as node ID 10, OPERATIONAL. LEDs do normal startup.

Problem: Messages shows constant “PPP[0]: reconnecting” — link never comes up. And in the DroneCAN Parameters screen, Refresh gives an empty table, so I can’t set the DroneNet’s IP.

Questions:

  1. For a Matek (non-CubePilot) board, should the USART be straight-through or crossed?
  2. How do I get the DroneNet params to load so I can set its IP?
  3. Does the DroneNet firmware need updating first?
2

I am seeing the same kind of issue when the CAN node is operational but the PPP session remains stuck at reconnecting. The SERIAL1 protocol and baud values, plus the empty DroneCAN parameter table, make the transport or parameter-service path worth checking separately from the wiring. Could you capture the ArduPlane version, the full PPP reconnect log, and whether the DroneNet firmware expects a different serial baud or CAN parameter setup?

3

1. ArduPlane version:
ArduPlane 4.7.0, git hash 1511f271, custom build with PPP enabled, on Matek H743-WING V3.

2. Full PPP reconnect log — це треба зняти з твого Mission Planner. Одна дія: DATA → вкладка Messages → знайди блок з “PPP” і скопіюй 15-20 рядків навколо нього (не один рядок). Скинь сюди — я оформлю для форуму. Мені треба бачити повний контекст: що йде до і після “PPP[0]: reconnecting”.

3. Whether DroneNet firmware expects a different baud / CAN setup — ось тут чесна відповідь, яку ми якраз з’ясували і яку треба їм передати:

We currently can’t read the DroneNet’s firmware version or parameters at all — the node shows OPERATIONAL on CAN but HW/SW version fields are empty, the name shows as “?”, and the parameter table won’t populate. So we cannot confirm what baud or CAN setup the DroneNet firmware expects, because the node isn’t responding to GetNodeInfo or parameter requests. Current FC side: SERIAL1_PROTOCOL=48 (PPP), SERIAL1_BAUD=12500000, CAN_P1_BITRATE=1000000, CAN_P1_DRIVER=1, CAN_D1_PROTOCOL=1.