It seems you are testing on bench and losing connection between the radio and onboard transmiter. Move the radio further away as if they are too close they will loose the connection.
Usually I put the radio 1m+ away.
actually that was the first thing I tested, and no it doesn’t work. Connection is also not a problem, I tested with INAV with both S.Port SBUS and F.port.
This looks very similar with SBUS & Frsky passthrough when I switched from 4.0.7 to 4.1.x.
with 4.1.0 only F.port works, if I use SBUS with S.Port then connection only last for a few second, then no RC in or telemetry.
SERIAL6_OPTIONS=15 or 3
SERIAL6_PROTOCOL=23
this results in RC input and no telemetry
SERIAL6_OPTIONS=7
SERIAL6_PROTOCOL=10
this results in telemetry over s.port, but then cut off 1 second after startup tone
I cannot verify any RC input during boot up
using F.Port with these param:
SERIAL6_OPTIONS=15 or 3
SERIAL6_PROTOCOL=23
this results in RC input and no telemetry
SERIAL6_OPTIONS=7
SERIAL6_PROTOCOL=23
got both telemetry and RC input, until about 2 seconds after startup tone, then both got cut off.
I badly wanted to use 1.4.x on this board, but this hurdle I cannot break for months
With the most recent Fport receiver firmware for ACCST there is a known bug in the firmware where it is not emitting well-formed telemetry packets. Maybe it’s affecting ACCESS too? I downgraded to an earlier version to get it working for ACCST.
When using S.port you need to use two separate UARTs, one for Sbus for RC input and one for S.port for telemetry. Both need to be inverted.
The S.port one should connect to a TX pad and use SERIALx_PROTOCOL = 10, SERIALx_OPTIONS = 15.
ah, I haven’t tested s.port with separate serial ports since I’ve used up all of them. Last time I tested them in 4.1.0 it didn’t work.
yes, I can confirm with ACCST F.Port it has lots of problems, until recently I upgraded to ACCESS then F.Port is pretty stable. The only reason I used f.port is because last time when I tested on 4.1.0, S.Port stopped working, only F.Port worked.
I’ll try to free up 1 more serial port and test it with SBUS and S.Port. If still not working, then my only solution with this FC is either downgrade to 4.0.7 (worked with both SBUS S.port, and with F.Port) or use INAV (worked ok, but not as sophisticated as ardupilot), or just give up yaapu telemetry (OSD only).