Mjx Bugs 3

Just put the test build on my V2 Plus and it works fine.

The "101d" value on the telemetry test page is RSSI. The Volt1 value will be 8.40 when the bugs is not sending a low voltage alarm, and will change to 6.00 when the bugs sends the low voltage indicator. For audible alerts set up the Telemetry config on the Model menu. For example, set Volt1 <= 7.00 to get a voltage alert.

Learning about Telemetry. So far, I'm OK with seeing RSS1 and Volt1 on the monitor.
I've also found my way into Telemetry config and set values from presets for 2s.
Model menu | Main page config. gives me a screen I don't know what to do with -
I get here trying to enter values for RSSI and Volt1. I attach pics of these 3 screens.
Any advice welcomed.
I fly FPV, and want to hear beeps to warn me of low voltage and low RSSI without looking at the monitor.

davdrone1 wrote: Hi C0ckpitvue 777,
Here's a link to a YouTube video I made that may help, although I use a Jumper T8SG Tx.
It explains how the number for the Fixed ID field is obtained, and towards the end I display
the code I use for the model.ini to arm a switch to turn the motors on/off for the Bugs 3.

Uhm... I flashed my T8SG v2 plus, using latest nightly (deviation-t8sg_v2_plus-v5.0.0-d90cb3b)
I don't have Bugs3 protocol in the list...

Did you use the defuse tool to update the dc7544a dfu file in your transmitter in update mode?

I used dFuse 2.3.1 to flash deviation-t8sg_v2_plus-v5.0.0-d90cb3b.dfu file extracted from deviation-t8sg_v2_plus-v5.0.0-d90cb3b.zip file.
Flash succeded and when I switch on the tx I can see t8sg_v2_plus-v5.0.0-d90cb3b version showed on display.

What's wrong?

I followed Seby Docky's guide:

Go into a new model menu, then model set up scroll down until you see the protocols it's to the left of the bind or reinit option,once it's highlighted use the r and L button to scroll through the models until you see bugs3,please keep the forum informed either way as many other can use this information,it's greatly appreciated.

Tried again.
Before starting from a loaded model, now with a new one.
Bugs3 protocol is not there.

Do you see the other models?

I have all other usual protocols, including MJXq.
I tried flying my whoops (bayang protocol) and they work.

Install the bugs3 test build . It's not in the nightly build yet.

hexfet wrote: Install the bugs3 test build . It's not in the nightly build yet.

Thanks, now it's there!
Ok, now I have to make it work

It works!

I flown just a couple of minutes, I had battery at storage Voltage.
Now I have to setup low battery and range alerts.

Thanks a lot, this Will make me fly my B3 again!

C0ckpitvue 777 wrote: When using full pitch and ail with the bugs 8 pro you might experience oscillation,I added 3 rates and scaled the highest rate down to 80 which resolved the oscillation.I also scaled the pitch ele channel back to 90 on the bugs 3 do to awesome but to excessive pitch.I also scaled the yaw down a bit.Here are devo 10 and 7e model inis with dual rates.Devo 10 mix0=high,mix1=medium and mix2=low.
Devo 7E,swa0=high,swa1=medium and swa2=low

Bugs 3 Devo 10-http://www.mediafire.com/file/6pqqr27y9uman4z/model28.ini/file
Bugs 8 Devo 10-http://www.mediafire.com/file/k3gzd2d223v6zdq/model26.ini/file
Bugs 3Devo 7E-http://www.mediafire.com/file/z6l20z5zq6w5n0l/model23.ini/file
Bugs 8Devo7E-http://www.mediafire.com/file/z6l20z5zq6w5n0l/model23.ini/file

I took your B3 devo 7 model.
I changed ch5 complex mixer to a simple min/max to manage arm and disarm.
Everything works ok, it just has a little oscillation while hovering.
What was ch5 mixer doing in your model? I'm still not so good in undestanding mixer, it's my first deviation tx.

My channel 5 is for arm and disarm also,I also set the swa switch for 3 rates,I don't know if you did the 3X2 mod on the devo 7e,you can also scale down the rate to around 75 to stop the oscillation.

I don't knows what the "3X2 mod on the devo 7e" is.
I'll look better in your ch5 setting then.
When I tried the first time, nothing happened, then I changed it to the simple min/max and it worked.
Yes, I tried the 3 rates on swA, the higher rate toggles leds off too.

For now I'm really happy, tomorrow I'll check it better.

Test build is updated (50f6e42). Found a bug while looking into why my receiver seemed to work with the wrong id. Turns out the captured fixed id wasn't being used. This is fixed, and mmakai's algorithm does produce a value that works for my receiver. Testing further it seems it is possible to have multiple radio id values that work. Not sure why. I don't expect this build to break any model files, but it is possible you may need to re-bind.

For my receiver the value of fixed id after binding is -1530565964. Anyone else have this value?

Woke up feeling silly looking back at my last post on telemetry. Went back in and set some initial telemetry values to try.
Next step will be to set different notes or time between beeps to know which alarm condition applies.

Are you going to do a how to telemetry Jay drone?

Hello, what is the minimum RSSI recommended to set ? Or try until it falls ? And another question, is there a "autobind" when switching on the TX ?

Seem to have it all working - here's the video.