Mjx Bugs 3

The best shot You had of getting the original version was tomtop,I know banggood went through a couple of revisions after reading recent reviews.

Thank you very much again hexfet for your hard work and willingness,it is greatly appreciated by the masses.

I bought my latest Bugs 3 yesterday from GearBest, as they had it on a flash sale.
I noticed the the words "Altitude Hold", on a picture of the Bugs in the advert, but there was nothing in the detailed specs shown.
I've since found a video by Half Chrome on YouTube where he demoed a prototype with Altitude Hold back in late December, but I have not found anything else.
Do you have any more info on this, C0ckpitvue 777?

www.mjxrc.net/mobile/goodshow/bugs-3-pro.html

I would have waited for this instead. But altitude hold.... Hmm tends to make the quad speed/agility decrease

Davdrone it's new to me,never heard of it until you mentioned it but it seems which each revision they tweek the protocols.

It kind of looks like the Jyu Hornets,I also think that protocol also uses the a7105 chip as seby reviewed it a while back.On another note the bugs 3 mini is on ebay for 85.00 usd free shipping.I purchased and will be taking captures for future interest.

Test build (09a0a23) is updated. Added support for 10-bit channel values and packet check byte. Let's see if these changes help with arming. Please make a capture of binding and trying to arm (by setting channel 5 positive).

The check byte seems to be an xor of all the packet bytes and initial value 6d. If the check byte is wrong it probably won't bind anymore.

Have tested deviation-t8sg-v5.0.0-09a0a23.dfu with fixed id 123456 and then 123457.

I had the Jumper Tx waiting in bind mode displaying "Bind B3.. Press ENT to stop."
When I turned on the Bugs 3, Deviation left the waiting to bind screen,
and the front flashing LEDs on the Bugs 3 went to steady on immediately.
However resetting channel 5 and then channel 6 from -100 to +100 had no visible effect on the Bugs 3.
Ran the tests again with Channels 5 and 6 set to +100 before binding. Still unable to arm.

btw i tested hovering at home, it works but the pitch is reversed. i reversed the channel in the deviation mixer and all is good

No way... did you do it!?!?!?

Credits to hexfet not me. I am the tester. But i think we have to check if it also binds and arm for other bugs3. Davdrone1 tried his but wouldnt work? Hmm

Great news Blade81, and of course hexfet!

Now I need to figure out why I'm not getting the same results.
Looking at your latest video, I upped power from 30 to 150 and tried again.
I also tested with my Bugs 6, which works with both my Bugs 3 controllers.
Blade 81, do you get the lights to flash by pulling both sticks down and right
after binding? I don't.
I have channel 5 set to +100 for D1, and -100 for D0 and D2, and the same for
channel 6 on SW B.
These tests were done with fixed id 123456.

That's good progress! The next test build will have pitch reversed so you can change the model back to normal then.

There's still some uncertainty about the arming and disarming. In the video it looked like the quad disarmed (motors stopped) on a different switch than the one used to arm (motors start). And in the stock tx captures when arming happens packet byte 5 changes from 0x26 to 0x66, but on disarm it changes from 0x66 to 0x46. Please make a capture with the stock tx arming and disarming 3 or 4 times. Move throttle up and down once (quickly is fine) while armed to help with identifying the changes in the capture data.

The different behavior davdrone1 is seeing could be caused by a few different things. One possibility is a difference in the model.ini file or the procedure being used to arm. davdrone1 are you using the same procedure shown in the video? Another possibility is the data phase frequencies are determined by the data returned from the quad. Then davdrone1's quad might be expecting different channels than the hard-coded ones being used.

The fixed id setting doesn't matter with the current code. The odd/even difference isn't currently needed.

Davdrone, i had all my switch are setup as 3 position switch. - 100, 0, 100 is my mixer value i think.will double confirm when i am at home tonight.

Channel 5 when switch up. Quad Arm and Blue led turns on.
Channel 6 when switch up, turn off led light.
Channel 7 when switch up, stop motors. Blue Led light remains on. Means its still armed somehow
Channel 8 doesnt seem to do anything. I dont know if it switch modes or perform flips.
Rotary switch i not sure if it doesnt anything.

I am heading to work now i can only perform capture when i reach home. I will give my full support to hexfet as long he need any captures. Or if i can probably share my model file with u and see if it works for u

Awesome news fellas,I just want to thank all you guys,great job hexfet,you're the man bro I can't express enough gratitude to those that made this happen.I just got 1 question,which bugs version is this?

As far as I can see, I am using the same procedure to bind and arm.
Jumper with Bugs 3 model loaded and waiting to bind, then Bugs is powered on, and appears to bind.
Next step is flicking switch D from D0 (-100) to D1 (+100) to arm, with no result.
I'll set up switches C and A for channels 7 and 8.

Yes, Blade81, I'd like to see a copy of your model.ini file when you have time to put it up.

I juz remember i may have set my fine frequency to 100 when we testing the binding sequence and i forgotten to change them back.
Not sure if that affects anything maybe u like to try? I will upload my model file tonight along with the captures hexfet requested

Blade81, just tried with fine freq set to 100. Still no result.

hexfet, I'd expect arm and disarm to have different codes -
Arm is a short press on the red button, while disarm is a long press.

Stock TX capture, arming, throttling up down briefly, disarm. did about 4 times.

My Deviation model.ini uploaded in another zip.

Hope it helps!

It helps. Test build is updated (648a226). Changed the logic for controlling arming and disarming to try to match the capture. It appears that two different bits are involved. One toggles (0 to 1 or 1 to 0) to indicate arming, the other toggles to indicate disarming. Seems over-complicated so I could be wrong.

Likely won't be any new builds till next week. I'm on holiday the rest of this week. Code is here if anyone wants to try changes.