openrcforums

Is there a version of eePskye which supports the updates in the latest ersky9xr builds, specifically the new protocol options for the multi-protocol module? I'm trying to set my models up in eePskye but every time I write the memory back to the Tx I have to modify the protocol settings on the Tx because the FRSKYX protocol isn't available in eePskye. Not a big deal, just wondering if I've missed a test version somewhere.

Second question - could the eePskye simulator show the flight mode? I'm trying to set my switches to show the right flight mode correctly and it would be much easier of I could do it in the simulator.

That said, the software is awesome

I'll post an update on the ersky9x test versions thread later today.

Mike.

Posted!

Mike.

MikeB wrote:Posted!

Mike.

Thanks for the quick response! The flight mode shows up perfectly, but there's something weird happening with the multi-protocol protocol settings...

I have two models, one configured for FrSkyX CH_16, the other configured for Bayang. Both are fully configured in the Tx menu. If I read the memory from the TX, then look at the Bayang model all the sub-protocol options are blank. If I look at the FrSkyX model everything looks right the first time I open it, but if I close the editor and go back the sub-protocol options are all blank.

I've replaced the test version with an updated one, see if that is any better.

Mike.

It is better, but still not quite right. The model configured for FrSkyX works as expected, but the Bayang model is still blank when read from the Tx. If I set it to Bayang and write the EEPROM everything is fine when checked on the Tx.

Ben

It's working OK for me. I configured a model to Multi/Bayang, then read it into eepskye and Bayang was displayed correctly. I've checked this on a SKY board, an AR9X board and a 9XR-PRO.
If you set Bayang on eepskye, write it to the radio then read it back, does it work OK then?

Mike.

OK, I did a bit more testing - the problem only occurs when setting Autobind to Yes.

If I read a model with Bayang protocol and autobind enabled the subprotocol is blank. Likewise, if I create a model and choose Bayang and autobind, close the model and go back in the subprotocol is blank.

This seems to happen for all subprotocols when enabling autobind.

Ben

I should have fixed this "autobind" problem in the version I've just posted.

Mike.

Looks good to me. Thanks so much - I'm blown away by the speed you turned that around. My day job is in IT, and we have paid-for software that doesn't get support this good. How does one send you beer money?

Ben

In eepskye, call up Help|About and there is a "donating" link there!
Or, find one of "JHSA"s posts and there is a link at the bottom.

Thanks.

Mike.

There's a link under my posts for donating to Mike.

João