[quote=“vronp, post:8, topic:62242”]If I change this protocol from Mavlink to RCin, do I lose telemetry as I gain RC?
I’m going to test this as soon as I figure out which SERIALn corresponds to the Radio port on the Pixhack. The port is labeled as Radio/Telem1 and I’m making the assumption this is the primary port for this data.[/quote]
AP appears to be always looking for telemetry data on SERIAL1 (and 2 as well I believe). Any OPTIONS set are merely “on top” of that. At least this seems to be the case with CRSF.
there’s multiple ways to combine your crossfire with your FC, as the crossfire supports various protocols. using bidirectional crsf or mavlink protocol will likely be the most attractive options. mind that crsf protocol as for now is supported in ardupilot latest (=master) firmware only.
1.: to use crsf as your RC and telemetry protocol
in your crossfire Rx, set the pins you use to connect to your FC to CRSF_TX and CRSF_RX
in MP set the serial port you use to connect your crossfire Rx to SERIALn_PROTOCOL = 23 (RCIn)
your crossfire’s RC by mavlink setting will have no effect in this scenario, as mavlink is not used
this will bring up crossfire telemetry sensors in your transmitter and, if using the fullsize crossfire transmitter, allow to pass on emulated mavlink downlink telemetry of the most vital avionics (one way only) via the TX’es serial port or bluetooth module
2.: to use mavlink as your RC and telemetry protocol
set your crossfire receiver’s pin functions to MAVLINK_TX and MAVLINK_RX
in MP, set your FC’s respective SERIALn_PROTOCOL to 2 (mavlink2 = default), and the corresponding SERIALn_BAUD to 57
in your crossfire RX, set RC by mavlink “ON”. mavlink2 supports the 12 channel option, while mavlink1 will allow 8 channels only
if using the fullsize crossfire TX, this will allow to pass on full bidirectional mavlink telemetry to your ground control software of choice (serial port or bluetooth)
mind that current crossfire firmware does not fully support mavlink bridging via wifi / udp on the crossfire microTX V2 yet.
Yes you did and I lost track of that somewhere along the way.
Well, I might have a new problem now but I’m not sure. I think this PixHack has the flash error and I can only flash 1 MB on it. I’m not positive yet and I’m still researching. Regardless, I apparently found 4.0.4 that fit so fingers crossed that 4.1.0 will fit otherwise I am ordering a new flight controller.
I think you are onto something. I changed each serial in turn and never saw that message. Then, I went back and disabled the Serial1 line and yet I still get RC via MAVlink. I was sure this would break RC but it did not. I’m assuming this means I am changing the wrong parameters or there is something else I am not doing correctly.
That is a picture of the FC. I have the previous version but the ports are nearly identical. I am connected to the RADIO port. I suppose I could try a connection to Serial 4/5???
Unfortunately I have no experience with Pixhack/hawks, only F4/F7 FCs with UARTs. I can just say that CRSF plus telemetry only worked for me on a port dedicated for telemetry (and not the one recommended for serial receivers).
I guess I can try connecting to other ports and see what happens. I would think, since telemetry and RC worked on this port, albeit with MAVlink, that crossfire would also work but who knows???
I may have the identical issue, just trying to confirm. My FC is the Kakute F7 V1.5 (STM32F745) and the specs say 1Mb flash. Where did you discover that 1Mb flash does not support CRSF? Are you confident this was the ultimate reason for the CRSF rc-in failure?
I’m glad to hear you round a resolution. I had put this particular project to the side for a while. Thanks for the link. When I get back to this, I will give that a try.