Protocol Stacks

PhracturedBlue wrote: I verified that in the Devo protocol, the servo throw is correct for +/- 100% so if you still don't have enough throw for your GeniusCP that would be quite odd.

It has.
That was my CB100 with the 2401 protocol, that missed some throw, but it has turned out it was mainly a flat battery, however it might miss some...

PhracturedBlue wrote:

FDR wrote: Another one: with the devo protocol I had to reverse the aileron and the rudder channel for the Genius CP, however with the original fw all the channels are normal...

Is this true on the CB100 too?
I checked the WK2801, Devo and Flysky, and in all cases Up and Right move the servos counter-clockwise.
So they are consistent.I then checked the Devo7 Tx with my Devo12Rx and noticed that rudder and aileron should move the servos clockwise when the stick is moved right. That corresponds to what you are seeing, so I reversed the Rudder and Ailerons. Hopefully that will help.

That was the strange part, that when I started to test the fw with the 2401 protocol, I told you to reverse the aileron to match the needed reverse settings for the CB100.
I have to double check it again...

PhracturedBlue wrote:

FDR wrote: Another one: with the devo protocol I had to reverse the aileron and the rudder channel for the Genius CP, however with the original fw all the channels are normal...

Is this true on the CB100 too?
I checked the WK2801, Devo and Flysky, and in all cases Up and Right move the servos counter-clockwise.
So they are consistent.I then checked the Devo7 Tx with my Devo12Rx and noticed that rudder and aileron should move the servos clockwise when the stick is moved right. That corresponds to what you are seeing, so I reversed the Rudder and Ailerons. Hopefully that will help.

So I checked it over:
For my CB100 on the WK2402 all channels are reversed except the throttle.
That's why I asked you the reverse the aileron, because it was not right first. But only after you reversed it I have started to fly my devo compatible Genius CP, which needed aileron and rudder that way, however it shouln't need that: with the devo fw all channels were normal.
It would means that these protocols need different channel reversing, when I searched what channel reverses would needed with the WK2801, and I found, that some needed to reverse only the elevator: so the 2801's channel reverses work like the devo's.

So it is good now..
Sigh!

I don't get it yet.

I already checked in code to reverse the aileron and rudder.
When I plug servos into the WK2802 RX they move in the same direction as for the DEVO RX1202, so both Walkera transmitters use the same direction. Since IA already reversed the aileron and rudder, your genius should now be correct without any reverse needed. If the CB100 still needs reverses, there are 2 possibilities:
1) the 2402 has different servo directions that the 2802.
2) each Walkera Rx in the 2x0x line uses different directional assignments

Yep, that is what I basicly mean, just my english is not up to the task!

So once more:
1. The DEVO is perfect now.
2. The WK2402 and WK2801Pro need different reversing for the same receiver (in this case the RX2406C), but we now behave like a 2801, which is fine. I was confused, because I was not aware of such differences...
(Furthermore some CB100 have different rx, which needs different reversing...)

PhracturedBlue wrote: I implemented support for changing the Tx Power. Range is the full range of the module which is ~100uW to ~150mW
That is one additional step on each side. I hacked up the bitmap to add the extra levels, but the images really need to be fixed to have more bars instead

Corrected the tx power bitmap.
Checked in...

How can I setup and send fixed ID?
Does it simply send the fixed ID packets when I click OK after I typed in the ID? In this case the rx should be bound when doing that, I guess...

FDR wrote: How can I setup and send fixed ID?
Does it simply send the fixed ID packets when I click OK after I typed in the ID? In this case the rx should be bound when doing that, I guess...

You can't.
The binding code does not yet exist

PhracturedBlue wrote: You can't.
The binding code does not yet exist

Oh, I see...
Do you plan to implement them in the first release?

FDR wrote:

PhracturedBlue wrote: You can't.
The binding code does not yet exist

Oh, I see...
Do you plan to implement them in the first release?

Yes.
I added it to the issues list

Somewhere meantime the protocol dependent channel order is gone.
So do you finally fixed the first 4 channel order as Wuselfuzz suggested, or it just doesn't write the right name on the channel mixers?

I made a change to the ini file format a couple days ago that may prevent your models from loading properly (i hope it is the last such protocol change). It is possible that is the issue?
When I look in the emulator, I see the protocol-dependent order
Note that I removed the 'Ch' part since it was getting hard to fit everything in the button.
I can't test it now, but I'm pretty sure it was working in my Tx last night too.

I see EATR in bot the tx and the emulator for all the protocols.
The ini format should be right in the emulator, I guess.
DSM2 should be TAER if I'm right.

yep. Just a typo. fixed now

Thanks!
Are the J6Pro and Flysky all right, because they show EATR too?

FDR wrote: Thanks!
Are the J6Pro and Flysky all right, because they show EATR too?

The flysky Tx is unlabeled so doesn't really matter.
I believe the j6pro is ok, but I'll know once I actually test it out.

Aileron and rudder trims effect in the wrong direction.
I tried DEVO and 2401 protocols, both are the same.
The elevator trim is good, the throttle trim I didn't try, because it has no sense...

FDR wrote: Aileron and rudder trims effect in the wrong direction.
I tried DEVO and 2401 protocols, both are the same.
The elevator trim is good, the throttle trim I didn't try, because it has no sense...

That is because I initially thought that positive was to the right, but that isn't the case. It should be right now, though I only tested in the emulator.

BTW the negative trim steps are displayed as "0.-5"