Hi Peter,
we have discussed this briefly, yesterday. In fact I can not tell how many channels a VBar can actually pass through via S.BUS, e.g. 8 or 12 or 16, and how.
I was under the impression that (only) the E1xxx channels were the ones (which would mean 8 channels), but Rainer thought it could also be some of the E2xxx channels.
Maybe Uli or Rainer can find out and tell.
The goal with our S.BUS implementation was not a setup like this, but rather a VBar with one or two extenders, for power distribution, servo ports and receiver redundancy.
S.BUS, in our case, was rather meant to allow controlling a subsequent flight control or flybarless (if that makes any sense), or to allow controlling another n (8?) BUS type servos, which are themselves programmed to listen to the respective channels.
Dosen't mean it's not possible, but there may be limitations, and it might be less simple than expected.
So it could be necessary to do all the setup and macrocell things inside the NEO, and then use the last cell in the chain as an input for the EXyyy cell.
Like CH2 is the left aileron, servo 1, you mirror it to e.g. MC30 for a left aileron servo 2, if it was that, select input CH2 there, type channel (to adjust center, limits, direction) or type curve (same, but to also linearize), then you would use CH2 as the input for one S.BUS channel, and MC30 as the input for the second.
But that's only one part of the problem, the other—I believe—is still that the control surfaces don't re-center?
—Eddi
Born to fly ...
forced to work.
