Dromida Ominus protocol?

this may be off topic

on the anylink2
i have gotten this far

the protocol must be PPM
while binding is possible in walkera
[[on the anylink red light positiom A]

channel sequence is wrong

you must use the custom setting, which allows you to move sticks and set channel function
[caution may still be reversed]

even so
attempting to bind
yields nothing but flashing lights on the quad

on the presented ini files
Thank you , thank you
change protocol to ppm
[your using the trainer cord and an external module]


to eliminate the channel three warning.
on safety,
change auto to the actual channel number
imo

thank you again for the 7e ini file

using that file
but changing the protocol to ppm

Binds the quad
goes thru the whole sequence and ends with lights constant and rear red light flashing

but still no action, nada
all controls and switches do nothing
?


missed somthing
lol
and the ini search begins

changed safety scalar to 100
moved throttle trim to full low

no luck

trying to run the channels as normal now

as i preprogramed the directions on the anylink2

still having fun
what a puzzle
lol


edit
reversed throttle, centered trim

works correctly with normal position on the channel monitor
meets -100 value for throttle and t-hold works
on the monitor

binds but no fly

any idea's?
please

If I'm reading your profile right, it seems like you should flip the HOLD switch before/during binding to get the Ominus to bind. It actually looks like quite a few things are tied to the use of the HOLD switch - timer resets, as well as CH6 manipulation (which determines angle/acro mode). Try taking away some of those other assignments perhaps, and stick those functions on other switches. I never use the throttle trim switch, so that might be a good one for resetting your timers.

From your description of what the quad's lights are doing it sounds like the only thing holding you back is getting the Tx to report 0 throttle to the quad. Try taking your stock Tx and put the throttle stick halfway up before switching everything on and you'll get the same light pattern, and complete lack of binding. This at least helps us narrow down what's going on.

Another thing to try might be (un)reversing your throttle channel. Since you're using the AnyLink it might handle throttle stuff differently than the NRF chip. I had to reverse it on the 8S w/ NRF but that may not be correct when using the AnyLink. One way to test that without changing your profile would be to put the throttle stick all the way up during binding, but it's probably better to just tap the reverse button in the model setup on the Tx.

Thank you, for the help

put throttle to normal
disconnected other hold functions

binds normally now
fmod works, can switch



modes

still no throttle
lol

Cool, glad it's binding now. That's progress! Just remember, whenever you install that NRF chip you'll need to reverse it again or it'll try to go through your roof

But it still won't take off? Sounds like there's still a throttle safety switch involved somewhere. Actually, looking at your ini I can see that HOLD1 is still set as throttle safety. Flip that switch and see what happens.

yes, feel like progress is being made
appreciate the support

i have been binding it with the "hold1" position chosen.
to guard against instant throttle up

then switch to "hold 0"

think, i will disable that, and mount the ominus in a vice
for safety

without props,
i find it difficult to tell if ailerons and elevator are the correct orientations

Thanks again voyn

Still no go?

buying nf module from bangood and will continue to tinker til then
any ideas
will be appreciated

throttle hold somewhere but cant find it

tried a slightly different ini file
binds but still no throttle

with protocol switched to ppm
and throttle set to normal



has anyone you know been successful using anylink2 and the deviation software?

Sorry man, I'm fresh out of ideas. The fact that it's binding means that the quad's seeing *something* as a throttle signal, and that it's equal to 0, but the only thing I can think of is that there's still a throttle safety that's messing with you.

Maybe try to build a profile from scratch? Perhaps if you build a new profile from scratch it will not be enabled.

Another option might be to go into the ini that you just posted, and delete the line that says "safetysw=RUD DR1" under Channel 3.Be sure to use a program called Notepad++, because the standard Windows text editors will jack up the formatting (or so I've heard). Delete that line, delete any empty lines that you might have just created, save it to your Tx, and try again with that.

Thanks voyn

tried a fresh 4 channel setup
left it as is

except for the ppm protocol

same thing
lol

perhaps in the custom channel setting on the anylink2
it did not pick up the throttle

now i think the problem is in my anylink setup
the deviation software seems un-involved



i'll give them a call
and report back

and Thanks again for the nfr ini's
can't wait till bangood sends mine
at least i know that works
lol

btw
flies fine on the rtf transmitter

Well, it was worth a shot I guess Hope the AnyLink folks can help you get it sorted. If nothing else, I'm sure once you get your NRF chip in it'll solve it. I tried searching for AnyLink here on the forums and it didn't come up with a whole lot that seemed helpful, but then again it might not have known what to look for since I am not familiar. I have a feeling that it's some sort of communication thing between the 7E and the AnyLink - not sure how all of that should be set up. Perhaps something in this section:

[protocol_opts]
Center PW=1100
Delta PW=400
Notch PW=400
Frame Size=22500

Maybe those parameters are set wrong, but probably only the AnyLink folks could tell you what they should be.

One thing I just noticed about your new ini - it says "type=plane" at the top. I really don't know what difference it would make, but try switching it to "multi" perhaps?

Keep us posted!

If you still can't get it working, it might be worth posting a question in the General Discussions forum. The issue might get more visibility there.

Hey guys,
Wondering if you can help. I have the NRF24L01 module installed in my Devo 10 and trying to bind to my Dromida.
I have the SLT protocol selected in the menu, but instead of a "bind" option it shows "re-int". Can you tell me what this means?
Thank you.

I've wondered this same thing before.
From the user manual:
Section 9.1:
Bind/Re-Init: Depending on the protocol and Fixed-ID setting, the transmitter may bind with the model on start-up, or may need to be manually bound once.
See 10 Protocols for more on specific protocols.
If the protocol does not support binding, the button will show ‘Re-Init’, which can be used to switch protocols without power-cycling the transmitter.

10.15. Protocol: *SLT
The SLT protocol supports up to 6 channels, and only supports auto-binding. The fixed ID can be used, but does not prevent auto-binding during power-on.

Some protocols support a "bind" capability as well as a "connect" capability. Connecting just means the transmitter can control the craft. When you "bind" them, the craft will then only connect to that transmitter and vice versa, which is a nice safety feature.

Binding may or may not be required, may or may not require some special action to trigger (aka "auto-binding"), may or may not leave the craft and transmitter connected, and may or may not require some special action to clear, depending on the protocol and receiver.

Those that can connect without binding generally do so if the Bind ID is left empty. This is the same procedure the transmitter goes through to init the connection, so the button label is changed from "bind" to Re-init" if there is no bind ID. This is not always correct, add protocols that require a bind will still bind even though the button says Re-init.

As a final note, the SLT protocol implementation is known to have issues. Not clear how many different drevices it's been tested with.

Thanks for your help and information.

I purchased a Dromida Ominus once the price dropped to $60 about a month ago. An extra 10% off made it a no brainier. I also purchased my Devo 7E and modded the stock TX to enable the Power Amp (PA), added two 3-Position switches, and added the NRF24L01 TX Module.

I've read though this post several times and I am impressed with the information you guys have shared.

Today, I figured out how to setup Dual Rates on SWA for all three positions. I've also tweaked some misc. settings and I'm now a fan of this combo. I associated the THR to this same switch, but at the moment, I left the rates at 125% for all three. I however have the Expo set respectively from mild to flat out 1:1 for the Highest Rate mode on the switch. At first, I used caution and respected the FMode switch as it controls how the Ominus uses the accelerometers. I found SWA did what I wanted, but I didn't get the aggressive pitch I was looking for. So, with some testing, I found the benefit of moth modes. I may move this feature to SWB to provide an intermediate setting. But for now, I'm pleased.

The Ominus is now "Alive" for a lack of better words.

Thank you!

Here's what I have so far:

Hi folks, I recently got a good deal at Amazon on a Ominus FPV model. I have tried the .ini files on this topic and none of them will work. I have the Devo 7e with deviation ver. 4. It appears to bind, but the red light on back flashes and it will not throttle up. I have tried several things to no avail. Anyone have any ideas? This a good flying little drone and I would love to be able to fly it with a real controller.