Support for NEURON ...
 
Notifications
Clear all

Support for NEURON series ESC telemetry input


maciej.j.wnuk
(@maciej-j-wnuk)
Eminent Member Customer
Joined: 1 year ago
Posts: 28
Topic starter  

FrSky has released Neuron series ESCs some time ago, featuring built in advanced and accurate telemetry sensors. (much better when compared to HW from my experience)

They come in 40 60 and 80A versions, so they fill the gap left by other manufacturers, as most of other 40-60A ESC don't support current sensing or mAh calculations.

Nenuron ESCs output the telemetry data via additional port using s.port protocol. I'd like to ask for the support of this input, like with other ESCs. This would allow to use those ESCs telemetry features by users of other brands RC systems, as well as enable telemetry parameter logging in Brain, and simplify wiring for FrSky f.port receivers users.

Now only FrSky users may make use of those ESCs and they are forced to use inverted s.bus+s.port hookup instead of f.port connection between Brain and Rx.


Quote
BrainDev
(@customercare)
Member Admin
Joined: 4 years ago
Posts: 708
 

The F.Port protocol does not foresee the use as a data bus and therefore the possibility to connect other devices on the same wires. With F.Port only a master and a slave can be connected together.
What is different is the new F.Port2 protocol, which works as a real bus to which other devices can be connected.
You should therefore write to FrSky if and when they plan to release a firmware for their ESCs using their new F.Port2 protocol.


ReplyQuote
wojtek.02
(@wojtek-02)
Active Member Customer
Joined: 6 months ago
Posts: 1
 

I second to that, I'd also like to make use of this feature of my Neuron ESC


ReplyQuote
maciej.j.wnuk
(@maciej-j-wnuk)
Eminent Member Customer
Joined: 1 year ago
Posts: 28
Topic starter  
Posted by: @customercare

The F.Port protocol does not foresee the use as a data bus and therefore the possibility to connect other devices on the same wires. With F.Port only a master and a slave can be connected together.
What is different is the new F.Port2 protocol, which works as a real bus to which other devices can be connected.
You should therefore write to FrSky if and when they plan to release a firmware for their ESCs using their new F.Port2 protocol.

I'm afraid you didn't understand my request. 

Please look at my drawing, hopefully explaining it more clearly.

neuron telemetry

ReplyQuote
BrainDev
(@customercare)
Member Admin
Joined: 4 years ago
Posts: 708
 

We have ordered an ESC Neuron80.
(We expected FrSky to be more competitively priced than other ESCs as they have it for transmitters).

Since for now the Neuron ESC formware does not yet provide an F.Port2 output protocol, in the classic S.Bus+S.Port configuration we will implement the reading of the telemetry data of the Neuron ESCs connected to the S.Port bus (via "Y" cable) so that we can also log the ESC data together with the other data recorded in the Flight Logs (in real time or in flight).


ReplyQuote
maciej.j.wnuk
(@maciej-j-wnuk)
Eminent Member Customer
Joined: 1 year ago
Posts: 28
Topic starter  

Good news, but this still applies only to FrSky users.
Is there no way to read the s.port signal from the Neuron the same way as with all other ESCs? And then "translate" it in Brain and send to a receiver of choice (other than Frsky)?


ReplyQuote
BrainDev
(@customercare)
Member Admin
Joined: 4 years ago
Posts: 708
 

As you surely know, differently from the protocols used by all the other ESCs, the Smart.Port protocol is bidirectional but it is also "inverted" both for transmitted and received signals. The only port that can handle an inverted bidirectional data flow is CH3.
However, this port is used to connect all models of serial receivers.
So it will be very difficult, if not impossible, to handle at the same time an inverted bidirectional data stream together with a normal or inverted bidirectional data stream (like the S.Bus2 one).
It is for this reason that since the beginning we talked about the possibility to release a Firmware version of these esc with F.Port or F.Port2 protocols that can be managed also in "uninverted" version.
Anyway when we will receive the ordered ESC and we will have the time to start doing the necessary checks and tests, we will see if it will be possible to find a solution. Maybe the data flow starts also without a request and so it works in unidirectional way.


ReplyQuote
Join Waitlist We will inform you when the product arrives in stock. Just leave your valid email address below.
Email Quantity We won't share your address with anybody else.