-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
FPort support #63
Comments
FPort2 receivers (Archers) can not be configured as smartport as well? So an Archer receiver (like Archer R6) with servos connectors configured with smartport won't do the work as well? An this is compatible with MSRC |
That is true, it can be configured as smart port, but in the cases when you need also channels output (especially channels usually not present as direct outputs on the receivers), then you need to use both smart port for telemetry and sbus for channels. With FPort you manage channels output and telemetry all in one single stream. |
It can be done. Fport telemetry is similar to smartport. Though I'll need to implement sbus as well. I'll add to the todo list, without date |
I've added support for FPort. I've created a specific branch. Could you test the code as I don't have access. You can download from https://github.com/dgatf/msrc/tree/fport You can use any board. Once this is verified, I'll add the pwm signals and merge to master branch |
Any chance to get FPort2 protocol supported ? That being bidirectional would allow to use a single board both for telemetry and ppm demux (obviously with limitations related to available pins)
The text was updated successfully, but these errors were encountered: