HW telemetry issues using FrSky F.Port
I have an issue with HW-Brain2 telemetry connection.
As soon as I connect the pin 5 in Brain with pin P in my HW80v4 the Brain loses Tx signal and ESC disarms.
When I connect them first and then turn the power on - Brain won't initialize and ESC won't arm - no beeps at all. With the telemetry wire disconnected everything works fine.
I'm trying to make it work with new FrSky ArcherRS receiver, using F.Port connection (F.Port to CH3). I can see the telemetry readings from Brain (all at 0 cause it isn't talking to ESC) the integration LUA script works fine, servos are moving. As long as the telemetry wire isn't connected. Connecting Pin5 (Brain) with pin P (HW80) kills all communication between Rx and Brain
Previously I had it all setup using 2 wires from X4RSB receiver (one for inverted s.bus to SAT1 and second for s.port to CH3). The ESC was then connected to Pin6, as per manual and everything worked fine.
Of course I have selected F.Port in receiver type selection card and Hobbywing telemetry in Brain software.
It seems that Rx-Brain2 talks to each other without any problems, but adding HW ESC to equation ruins the party.
What may be the cause of this?
We have ordered an Archer RS from FrSky european distributor paying this time for a fast shipping within one week (it costs more shipping than the receiver) so, we can test your problem.
The other day we received the receiver Archer RS that we had purchased also to be able to respond to this report and to which we soldered a cable on the S.Port inverted pin and power supply.
We were very pleasantly surprised by the telemetric data transmission speed (the update asterisks are constantly on fixed) and the data communication speed with the LUAC application (pages load almost instantly). With this receiver in F.Port mode, Telemetry and Integration are now the fastest compared to all other systems (Jeti, Spektrum, Graupner, Multiplex).
Finally FrSky has managed to realize routines that work perfectly with the Archer RS firmware. It works much better than the firmware for all other FrSky receivers running with the appropriate hardware modifications in F.Port mode.
We used a Brain2 with Firmware 3.3.031, an Archer RS receiver with factory firmware (1.2.0/2.1.2 No firmware updates for this receiver are yet available on FrSky website), an ESC Hobbywing 120A with BEC and a Taranis X9D 2019 transmitter with OpenTX 2.3.10 and ISRM 1.10/2.1.0EU with which we activated the F.Port protocol (not F.Port2) on the receiver.
We receive 10 telemetry parameters without problems and at high update rate:
Temp1, Temp2, VFAS, CURR, RB1C, RB2C, RPM, VFR, RSSI, RxBt.
The loading of the integration pages is very fast.
We suggest to check again both the configuration of the control unit and the ESC <-> Brain2 connection because our tests show that everything works perfectly.
Check also and above all to have not mistakenly loaded in the ESC the firmware specifically dedicated to work only with Vbar control units but the last "Generic" firmware available for the ESC.
Just as an update - RS works very well with Brain using F.Port.
My Brain2 unit was faulty, having PIN5 shorted with CH3 signal pin. After reflowing bad solder joints on pcb it all works well.
Hello, When using the Archer-RS receiver, do you still need the MSH51645? to get full telemetry? or can this receiver wired directly to the Brain2?
If you use the F.Port protocol you don't need to connect S.Bus signal to the SAT1 port and therefore you don't need the MSH51645 cable.
To connect with the F.Port protocol, just select this protocol in the receiver from the transmitter, then select in the configuration software of our control unit the icon of the F.Port communication protocol of the receiver and follow the scheme that appears after this selection in the next page of the Wizard (only one cable from the receiver to the CH3 connector).
At the receiver you will have to connect the signal cable to the "inverted S.Port" output and obviously the GND and VIN.
If you prefer to connect the old way using both the S.Bus output and the bi-directional S.Port signal, then you will need to connect to both the S.Port and SAT1 connectors of our control unit and you will need the MSH51645 cable for the S.Bus signal connected to SAT1.