Brain2 and FlySky IBUS Integration
Is there going to be telemetry support and Integration between Brain2 and FlySky IBUS Receivers?
With our controllers you can also use FlySky transmitters and receivers without any problems as the S.Bus and PPM+/- protocols are both supported by our flight controllers.
Remember that our flight controllers can record (also in flight) the telemetry values of the connected ESCs and/or thermal sensors. At the end of the flights it is possible to review the graphical trends of the parameters that you have chosen to record.
As far as the issue of managing the telemetry transmission protocol using FlySky's proprietary IBUS protocol is concerned, it is already on our "To Do" list.
However, in order to be able to develop, debug, test, and provide user support for a new protocol (IBUS) in addition to the necessary protocol documentation that must be provided by the developer and owner of the protocol (FlySky), we must also purchase "at least" a transmitter and a receiver. Often it is necessary to buy also the specific sensors.
These significant "investments" in both paid man-hours and hardware equipment to be purchased, are made by us when we receive requests from a sufficient number of users.
In the last 10 years, we have only received two requests.
So, for now, it remains the last of our priorities.
Hi! im not able to make this flysky integration to work. Are you sure about Y cable connetion in the latest update telemetry manual? I have radiomaster boxer 4in1, hw 80A V4 (latest firmware), brain 2 (latest firmware) and flysky ia6b receiver. When i put Y cable to the 2 ibus ports (servo and sens) and CH3/sbus in brain2 there is no chance to make this works. Receiver is binded, motor is beeping but brain gets no signals from channels. When i disconnect sens plug from receiver and leave only ibus/servo channel connected to the ch3 in brain everything seems to work exept telemetry in TX. I get only basic sensor as rssi. Brain is receiving data from ESC but not sending it to the rx and tx. Ive tried every configuration (pwm/ibus, pwm/sbus, ppm/ibus, pwm/ibus) and nothing works as is should according to manual
We are not aware that with the i-bus protocol of FlySky receivers it is possible to handle integration in addition to telemetry.
If we have written such a thing or if we have written something that has led you to believe this, please report to us where you read it so that we can correct or clarify it better.
We attach telemetry document where on page 13 it is described and explained how to activate telemetry. We have reread it and do not seem to have found any references to a possible "Integration".
Since, however, instead of a FlySky transmitter (which would not be able to handle Integrations), you use a RadioMaster transmitter instead, if you want to have on the transmitter in addition to telemetry also Integration with the flight controller, then you will have to use a different receiver such as those FrSky receivers that using Smart.Port or F.Port communication protocols are also able to handle the data flow necessary for Integrations with the flight controller.
PS: Since RadioMaster does not handle the ACCESS radio frequency protocol, the FrSky receiver must be an ACCST receiver.
@customercare thx for fast response! As a matter of fact the whole page 13 makes me believed that i could get telemetry data to my radiomaster TX taken from HW 80A V4 esc via brain 2 and ia6b flysky receiver (in PWM/iBUS mode). You wrote in manual about this components as they should work togheter. What point would be to connect ia6b RX with brain2 via Y cable instead of one sbus or ibus if there is no chance to send telemetry data to TX? Im really confused right now 🙂
@carsonpoland the fact that you have used the word "Integration" has made all this confusion, in Brain2 terms integration means the ability to modify the brain2 parameter from the radio, and for now this feature is not available.
the telemetry should be available though, so you need to clarify to @customercare that you have a problem in the telemetry itself, and don't use the word Integration.
@ahmad-kassem Yes, sorry my mistake. I dont want to have integration with flysky. My goal is to have telemetry data from ESC on TX screen as manual says it is possible: With FlySky i-BUS RX, you can see RPM & ESC live data’s in the main screen of your transmitter
Regarding telemetry, we have just re-verified with the new firmware 3.4.139 and everything works smoothly for us (with the occasion we also updated the PC software and radio firmware from Edge 2.9.0 to Edge 2.9.1)
We ask you to:
- Send us the configuration file of your flight controller
- Send us a picture of how the receiver is connected while it is running (LED on)
- Tell us what version of Edge you are using
- Tell us what version of multi-module firmware you are using
These are the settings and telemetry we see on our transmitter:
Can you send us the same screenshots?
We had asked for a photo of the wired receiver, but if the drawing was done correctly then the problem is identified.
By connecting the wires to the receiver both with the white signal wire in the middle and then connecting them together with each other, the signals from both ports go to ground zeroing.
The correct connection should be made following the drawings on the receiver label, one connector has the signal pin on the inside and the other connector has the signal pin on the outside.
@customercare no no, connection is ok 🙂 two ports SENS and SERVOS have from left GND V+ S and this is connected correctly. Ive misplaced S line on drawing. Are you sure that one line of Y cable shouldnt be connected in PPM/CH1 port in RX instead of SERVO one (2 pic)?
Yes, we are sure. We developed, tested and released it that way and explained it in the instructions.
We used the same connession today by carrying out the verifications which were positive.
Send us the confgiration file we asked for?
@customercare so what else i should check?
Can you send us a clearer picture of this detail where we can't tell from the video?
Can you also take a picture of the receiver label to see if it is identical to ours?
After you disconnected the connector from the SENS socket, and the control unit started to receive the correct i-bus signal and initialization was completed, reconnecting the connector to the SENS socket what happens?
Have you tried re-binding the receiver?
PS: You should never move the sticks during the initialization of the flight controller before it is finished.
@customercare ofc i never touch sticks before initialization ends 🙂 But in this case (Y connection) initialization is not going to finish. Ive tried almost everything and now im pretty sure this issue have something to do with receiver (rx firmware maybe?). My two ia6b rx are 3-4 years old but flysky dont release any firmware updates. So what can i do? Where have you bought your ia6b rx?
Reconnecting the connector to the SENS socket after successful initialization frozes fbl and servos (as with Y connection during initialization). Ive rebinded rx many times also changing signal formats pwm,ppm,ibus,sbus. Nothing works. I'll send you later my brain2 config file.