NET_P1_Protocol issue

ArduRover Rover 4.7
1

Hello Everybody,

I have a rover with a Pixhawk 6C running ardurover 4.7 which I would like to control it over Ethernet using the Cube Node Eth module.
I am trying to send CRSF trames via a remote control (I use a Teensy 4.1 for control) over ethernet.
On the PixHawk the Cube Node Eth is connected to Telem 2 (Serial Port 2/UART5) which is set at 12.5 miliion Bauds and with the PPP protocol selected.

NET_OPTIONS is set on 1 (EnablePPP Ethernet Gateway), the IP adress and port number is of the Remote (192.168.144.20:5556), Net_P1_Type set to 1 (UDP Server) and Net_P1_Protocol set on 23 (RCIN).

Unfortunately, I cannot get the sytsem working i.e I don’t see the cursors working in the Radio Calibration screen of Mission Planner, I have a radio Failsafe message permanently displayed on the HUD and no telemetry.
oh and in mission planner I have the following message: “UDP[21] → connected to 192.168.144.20:5556”

Important note: this very remote control was working previously when connecting via UART on the PixHawk, the only modification to the sketch I did was to replace the UART connection for a UDP.

So the question is: what am I doing wrong? And how can I fix this issue?
Please do not hesitate to ask me if you need clarification or more information from me

Thanks in advance for your time and help
With Kind Regards

Alain

2

why are you using CRSF and not mavlink_msg_radio_rc_channels?

3

Hello,
I think I will definitely use Mavlink but before touching the remote control sketch I wanted to be sure I didn’t miss something in the settings…
And also, out of curiosity now, I wanted to know if CRSF was usable over UDP or not…

4

Hi @Wanderer,

So I guess the Teesy code was updated so that it connects using UDP Client connect to 192.168.144.15:5556? .. and the Teensy’s IP address has been set to 192.168.144.x where “x” can be almost anything except 14 (used by the CubeNodeETH) or 15 (the autpilot).

One more thing to check is that the SERIALx_PROTOCOL used when the system was working using UART has been changed to 0 (instead of 23).

5

Hi @rmackay9

Yes your guess is right and as for the Serialx_Protocol used when system was on UART it has been changed to 0 as well..

6

Hi @Wanderer,

OK txs. So to be clear, it’s working now or still the same issue?

7

Hi @rmackay9 ,
I didn’t get it to work with CRSF so now I am switching to MAVlink and things are moving forward nicely… :wink: