Devo7E beta11 + Tactic SLT

This build is for Devo 7E - same as Devo 10, 3.1 beta11 and Tactic SLT.

victzh wrote: This build is for Devo 7E - same as Devo 10, 3.1 beta11 and Tactic SLT.

Thanks

I will test asap

Does this build include the additional switches mod for the 7E

i cant wait to try this out, I have been flying a couple Heli-Max CP's with an anylink i installed into a removable module for my 9X, it was great until I got the 7E and loaded Deviation, (love the radio, and software) anyone know if I can pull the Chip out of a tactic 410 transmitter and transplant it into the 7E

Sorry. I haven't been keeping up on it. Which module do you need to install? And why would the code only work on those devos? I thought the protocol stuff was independant of the base code?

@mpicpu - I don't know what's inside Tactic 410. Open it, make a photo and we'll figure this out. No, it does not have this switches mod - I only made an SLT module and necessary modifications of base software.

@Hexperience - I only have Devo10 and Devo7E, and in my perception they're the most popular (may be because of the price), that's why. I put a link to my fork, you can build for whatever you want. Or you can ask me and I'll build it for you. But I don't have an automated build system, that's why I'm a bit picky

If it's accepted in 3.1 (it was forked intentionally from rbe2012's) it will be available soon in main build line.

I will definitely want to install one of those. Looks pretty straight forward. I never did install my Flysky module because I don't fly them much any more.








____________________
RABI>>>>>>..

So happy to see Tactic SLT getting added. I have one HeliMax Axe 100CP that uses this protocol. I think the last of my aircraft that could not be flown with Deviation.

Thanks for your work on this victzh! Cheers.

I just loaded the Dec 8th nightly: deviation-devo7e-v3.0.0-25435b8

Flashed the firmware. Copied the protocol directory and complete filesystem to the Devo7e radio.

However, after selecting TacticSLT and trying to reinit in the ModelSetup, I get a "Bad/missign protocol modules!" modal box.

I confirmed that slt.mod is in the /protocol directory on the Devo7e.

Any idea what could be wrong? I have the nRF24L01 chip properly enabled in the tx.ini file.

I just tried to the files you uploaded in post 1. And I still get the Bad/missing protocol message.

So obviously, something I am doing wrong?

Does you V202 protocol work? I will try nightly build later today myself, but all these times I never got this message.

I don't have a v2xx quad to bind to at the moment. But if I select that protocol and hit the bind button. The operation seems to complete without error. Versus the SLT protocol which display a "Bad/missing protocol modules!" message immediately.

Perhaps it's a Devo7e problem?

Interestingly, the devo7e emu doesn't give the error. Copied all the files directly over from the devo7e too.

Thank you. I am clear on not to mixing the releases. In fact, both were downloaded specifically with this release.

I start from scratch each time.

I also downloaded the two files Victzh included in the first post. And same error.

I'll redo everything again later just as a sanity check and get to the bottom of this.

I redid all the steps from the manual multiple times. Including the formatting and then copying the file system over. The file system file that matches with the firmware I flashed.

Ensure the /protocol directory is copied over and the slt.mod file exist in it.

/protocol/slt.mod

All the other protocols seems fine. But upon "reinit" the TacticSLT protocol, I get the same "Bad/missing protocol modules!" error.

I have tried the 12/8/2013 Nightly.

I have tried the files attached in Post 1 of this thread.

I have tried the 12/10/2013 Nightly this morning.

Same unfortunately result. Battery in Devo7e is full.

Ah, so glad to see where the issue lies. I think renaming the protocol would be easier than having to rewrite the code to separate the protocol name from the file name.

You never know... I did not test it on my Devo 7E because it is unmodded yet. But I faithfully built it for Devo 7E and tested on Devo 10. Sigh... I have more respect for our QA department now (not that I held them in disrespect in the first place) - I work as a programmer as well.