Hello,
I have a problem to get the telemetry variables by useing FPort1 Firmware for R161 Receiver...

http://manual.spirit-system.com/index.php?title=FrSky_FPort

Connection to Hobbywing ESC Platinum V4 120 A as described here:
http://manual.spirit-system.com/index.php?title=HobbyWing_Telemetry

I get some telemetry variables only from the receiver RSSI, TQly, A2 etc. but not as wanted the telemetry variables from the ESC as :

RPM [RPM] - Current RPM from the Governor.
Fuel [%] - Vibrations of the model (Reported as Fuel)
RB1V [V] - Main Battery Voltage
RB1A [A] - Main Battery Current
RB1C [mAh] - Main Battery Consumed Capacity
RB2C [V] - BEC Voltage (10x) - set Ratio 25.5
Tmp1 [°C] - ESC Temperature
5120 [μs] - Throttle PWM Value

Did I accidentally forget another connection?

Has anyone solved or gotten a grip on these problems? What has been changed ? Is there an other firmware for the receiver necessary FPort 2 ?
Thanks a lot for your help!

Regards
Matthias

PS.: By the way Integration works perfect -

Config:
Radiomaster TX16S
EdgeTX Black Pearl 2.7.1

Receiver:
Radiomaster R161
Firmware File Name: R161_V1_FPORT EU.frk
Firmware Use : LBT Firmware for F.Port use - D16 v1

FBL:
Spirit GT
Firmware 3.4.1

ESC:
Hobbywing Platinum V4 120 A

Hi. I got ACCST F.port1 up and running. Did you enable telemetry in ESC menu?

Yes, I have enabled telemetry in ESC menu -

Though my experience is with the FCC firmware, I found that the R161 V1 (ACCST V1) F.Port firmware does not have telemetry working correctly. You should try the V2 (ACCST V2, so FrSkyX2 in the TX16S protocol menu) F.Port firmware. Both are still F.Port v1.

Hello rburrow87,
thanks for your reply !

This gives me hope again that it could still work - I had already tried to flash the firmware on another R161 today, but strangely enough it didn't work at all, there was an error message and it aborted -
To be on the safe side, I wanted to leave the configuration in my heli untouched (FPort1) - I have now ordered the STK tool and will then test it on my second R161, if that didn't work then it would probably be a problem - only then I would want to flash the inbuilt R161 in the heli - strangely enough, flashing always worked in Opentx 2.4.3 without problems before, now somehow not under Edgetx, but it can also be coincidence and the other receiver is simply defective - I can only report in a few days whether it worked , until the STK tool is in my house -

Thank you in advance for your tip, I will try that !


Regards
Matthias

I encounter the same flashing problem every now and then. Sometimes it'll work if I just try later! Must be caused by sun spots

Hi, caused by sun spots that's an good one !
But seriously, do you have Opentx or edgetx on your transmitter? Maybe that's an unknown problem of edgetx ?

Regards
Matthias

EdgeTX 2.7.1, TX16S MKII (but I used the original TX16S for a long time too)

I haven't really found a reason for why it fails. It usually works, but every now and then it'll just fail over and over. I've read that twisting wires can help, but the R161 wires are already twisted. If you have another wire, it could be worth trying too.

Hi,
that sounds not very well because random errors are almost impossible to find, since there are no reproducible errors - Where did you read/heared about this problem?
I have definitely ordered the STK tool (FrSky) and hope that it will work -
I will report as soon as I have this part -

Regards
Matthias

The STK tool should work nicely.

I noticed the problem on my own setup and have seen it from a couple others I've spoken with trying to do the same thing. All with R161 specifically, not sure about flashing other receivers.