I have a micro Spirit that I am trying to configure. When Frsky Fbus is selected as the receiver type, a message is displayed stating that is only available on newer units.
My questions are whether Frsky Fbus actually is available on the micro Spirit units? If so, I just bought this unit last week, and just received it. If it is an option, is there a means to update the controller, other than the firmware? It is currently loaded with 3.6.2.

New version 3.7.0 released!

.... FrSky F.BUS protocol:
MicroSpirit units can use F.BUS protocol with FrSky integration cable.
FrSky Integration cable for microSpirit is recommended.

_________________
Spirit System (Spirit W1, RS & GTR & all the others)
Spirit Wave & JETI DS 12
http://www.habada.cz

I really appreciate the response.

When I returned from flying, last night, I saw there was a new release. Indeed, 3.7 resolved that issue.

I have a couple Spirit GTs, and just started working with the micro. I know that I need an integration cable, but one more question.

Does the wiring on the micros from the integration cable go straight to the RUD port, or do I move one wire to the Aileron pin?

Also, there is the standard integration cable, and one for micros with a JST… is it true for both types of cables?

Yes, you can buy FrSky integration cable for microSpirit and for other Spirits. But if you have already JST-Servo adapters, you can use standard version too.
Or if you will write order message to ship FBus version, we can modify it for you.

_________________
Spirit System developer

My apologies for taking your all's time, but I need a little further assistance.

FBUS is functioning on the micro Spirit, and I have correct control over aileron and elevator servos. I have telemetry from the receiver, and the Spirit. There is a 5 second delay on the pitch, and a very limited range on the servo. I assume it is the connection that I have made. The servo functions correctly on CH1 or 2, and other servos fail to function correctly on CH3.

The receiver is a FRSKY Archer R6. I have the Integration adapter connected to V+ to the red wire, V- to Brown, and the orange wire is connected to S-Port on the receiver. There is a separate power source to the receiver from CH4 on the micro Spirit. The brown and yellow JST two pin from the Integration adapter is connected to the Rudder connection, and the red wire is connected to the A pin of P/E/A.

Additionally, I need to verify that the dual ESC should connect to AUX, and the yellow single wire from the dual ESC should connect to CH4 signal. Should throttle be assigned?

Again, I apologize for my questions. I have a GT functioning quite well on a MA Whiplash. It was rather simple to get operational, but this little Blade is beating me up, a little.

Am I off track in thinking that there is interference on the P/E/A pins on the unit, even when selecting FBUS as the protocol?

I have reset to factory settings a couple times, and no change. It does appear that the FBUS signal on the A pin is affecting the function of the A input, (P in my case), on channel 3 as if it is still trying to read a PWM input.

I finally ran across a thread of a similar report.

It is resolved with3.7.0-r2



Many thanks for the FBUS and integration on the micro units. Pretty cool. The GT in the other heli has been flawless, too.