Quick update - this firmware can now be downloaded from FrSky site. It was added to X4RSB ACCTSv2 firmware folder.
1. The S.Bus protocol is a one-way protocol in which signals are always reversed. This with any type of Futaba (R2008SB) or FrSky (X6R) receiver. The S.Bus signals of Futaba and FrSky receivers even if not identical are very similar.
In almost all FrSky receivers there is a pad where you can pick up the non-reversed S.Bus signal, but this is no longer the S.Bus protocol.2. The Smart Port protocol is also a protocol in which signals are inverted but unlike the S.Bus protocol, the Smart Port protocol provides bidirectional communication (like Futaba's S.Bus2 protocol which however has completely different formats).
3. Brain2 can handle inverted protocols such as S.Bus, Sbus2, Smart.Port but only when the correct icons of the protocols to be used are selected. All other known protocols used by all other unidirectional, bidirectional and/or telemetric sensors (not FrSky) are not inverted.
4. The F.Port protocol is a non-inverted and bidirectional protocol but is a different protocol from both the S.Bus protocol and the S.Port protocol.
Sorry for whining but I'm asking simply out of curiosity.
As we know FrSky has totally screwed up with their new Archer line by not giving us access to uninverted F.Port (except for little RS receiver which has inverted s.port pad which translates into normal F.Port). All F.Port capable receivers have an S.Port output which translates into inverted F.Port with proper firmware or when selected from the menu. I know it's not MSH's fault and it looks like FrSky doesn't really know where they'd like to go with their protocols and outputs/inputs. What they did with this new product line is just stupid.
But, if the Brain2 can accept inverted signals on CH3, such as S.Bus and bi-directional S.Port, why can't it accept inverted F.Port signal? Is it some kind of physical/hardware limitation?
I have the same question. I have a FrSky Archer R6 and have been unsuccessful at getting the F.Port protocol to work with my Brain2.
The new "Archer RS" receiver gives direct access to the non-inverted F.Port (labeled on connector as uninverted S.Port).
Moreover with the firmware of the new "Archer RS", radio transmissions of telemetry data and data reception with the Integration LUA app are much, much, much faster than previous ACCST receivers modified to operate in F.Port mode.
Faster than Jeti, Spektrum, Graupner integrations.
Thanks for the input. I know RS has ready output and works well (I guess I'm the one who gave you the hint on FB to use RS for testing purposes)
But this doesn't really answer my question.
I have the same question. I have a FrSky Archer R6 and have been unsuccessful at getting the F.Port protocol to work with my Brain2.
Below you'll find a location of uninverted s.port pin on R4 receiver. I don't have the same guide for R6 but I suppose it will look very similar.
The leg is IMO too small to solder it properly and to do it in a safe manner. I wouldn't trust this solution. I guess the RS is the only solution for now.
Thanks for the input. I know RS has ready output and works well (I guess I'm the one who gave you the hint on FB to use RS for testing purposes)
But this doesn't really answer my question.
If your question is:
"But, if the Brain2 can accept inverted signals on CH3, such as S.Bus and bi-directional S.Port, why can't it accept inverted F.Port signal? Is it some kind of physical/hardware limitation?"
The (short) answer is:
Not possible.
Yes there are limitations.
I suggest to contact FrSky that when I raised the question and put my doubts, he sent me a wiring diagram of how to build an expensive bidirectional inverter, asking him when they will produce in China at high volumes and then at low price the accessory "bidirectional inverter" for all their new Archer receivers.
Thanks for an answer.
That's no mystery that FrSky doesn't really know where to go with this new protocol which is a shame, considering the fact that this could be a fast and simple way of connecting all things together.
I've asked them if they will update sensors to be F.Port compatible and they don't know an answer. Now if I use F.Port to connect Rx to Brain I cant use their temperature sensor anymore for my nitros.
..... Now if I use F.Port to connect Rx to Brain I cant use their temperature sensor anymore for my nitros.
Surely you already know this, but you can connect a Jeti MX300 thermal sensor to the Brain2 as explained in the telemetry instructions.
Sure, I know, but I already have FrSky RPM sensor temperature probes glued into my engines very well and I'm not sure if it's possible to remove them without using dremel cutting wheel. ?
BTW - is there a chance for a future Brain update allowing for the use of s.port sensor the same way as JETI and Futaba temperature sensors?
Yes, it may be possible to do so. I would have to buy a FrSky thermal sensor first though.
But I don't want, that once I finish the job, I find out that FrSky has put them out of production because it comes with new sensors compatible with Smart Port, F.Port and F.Port2 in which communication becomes bidirectional and different because at the beginning must be recognized the protocol with which to communicate.
I would send one to you, but since it costs around $22 includding shipping from China that wouldn't be economically viable to send it across Europe back and forth ?
Hi,
I'm new to all this stuff. I happened to buy a R-XSR receiver, Brain 2 bluetooth, frsky adapter cable, YGE Saphir ESC.
I followed the first wiring option listed here: https://www.msh-electronics.com/forum/general-discussions/r-xsr-wiring-options/ to get the receiver connected.
And then I've split the YGE telemetry cable up into rpm signal and moved the middle pin of the blue connector to the top pin.
So far, everything seems to be working fine (there's some weird mAh value, that I have to figure out, still). The update rate of telemetry values is pretty low, though. I'm sometimes getting "sensor lost" warnings on my radio. So I came across this thread and read, that F.port would be much faster, but it's up to frsky to get it working on the R-XSR.
My receiver came with firmware 2.1.1 EU LBT. On the frsky website I saw, that this firmware was released in January. The changelog states something about F.port.
Any chance this may be the long awaited firmware for proper F.port support on the R-XSR?
BR,
Markus
Thank you for reporting the new firmwares.
We just now found the time to test both versions:
The ACCST 2.1.1_Fport_LBT one
The ACCESS 2.1.7 one
There is bad news and good news:
The bad news: The F.Port signal present on pad "P" indicated (also by FrSky) as "uninverted Smart Port" continues to be unidirectional. The receiver transmits the channel frames to the control unit and the channels are regularly recognized, but that pad does not "hear" or "listen" to the telemetry frames transmitted from the control unit to the receiver. In practice that pad does not correspond to the uninverted Smart.Port bidirectional signal (half duplex) but it is only a part of that signal, it is the only output of the uninverted Smart.Port signal that does not work as an input (it is not the full half duplex signal).
The good news: in the meantime we have completed the development also of the decoding of the new FrSky F.Port2 protocol. But not only that, we have also introduced the possibility to directly manage the signal of the two protocols F.Port and F.Port2 both in uninverted and inverted format (signal present on standard Smart.Port connectors), this without the need of any special inverter cable.
And from tests made with our new firmware the F.Port and F.Port2 inverted protocols work perfectly with the new R-XSR firmwares (with ACCST only F.Port, but with ACCESS both protocols can be selected and both work).
In conclusion the problem with R-XSR receivers has always been a hardware problem and therefore not solvable with firmware updates. These R-XSR receivers, unlike all other receivers, lack the possibility to pick up the bidirectional uninverted F.Port signal.
As for the new firmware for our receivers, it is already in the hands of beta testers and if at the end of the tests will not be found problems, it should not miss much to the release.
The good news: in the meantime we have completed the development also of the decoding of the new FrSky F.Port2 protocol. But not only that, we have also introduced the possibility to directly manage the signal of the two protocols F.Port and F.Port2 both in uninverted and inverted format (signal present on standard Smart.Port connectors), this without the need of any special inverter cable.
I knew you can do it ! ?
