Mjx Bugs 3

Sorry about that try this. drive.google.com/file/d/1p0d9b0ZyHbu1okz...tVt/view?usp=sharing

None of the signals look like a valid clock. The signals of interest should be on pins 3, 4, and 5. With pin 1 on the left when looking from above with the shield away.

I hope this one is correct.
drive.google.com/file/d/1OSfJzDi8k9iyNOa...p5b/view?usp=sharing

Still no clock signal. What is the logic analyzer input to radio pin mapping?

My bad hexfet,I went back and soldered pin 4 all 7 pins are now hooked to the analyzer in this latest capture,I can't distinguish between any of them except for the ground.
www.mediafire.com/file/kw0tkodqbtrv622/T...0on%20Bind.logicdata

Thanks bro,I'll put them in a new thread bugs 3 mini.

Has anybody besides Jay Drone tried this with a Jumper_v2-plus? I am aware of his getting bricked and getting a replacement board but it is not clear to me why it bricked.
It looks like the new board came with a different build
I have emailed Jumper asking the same, but have not gotten a reply. I have a Bugs 3 and a v2 plus but not sure if I should proceed.

As far as I understand, the manufacturer of jumper -in theory- should publish the source of all revisions of deviation with which they sold the device. If unpublished, that is sort of a GPL violation. On the other hand, law which cannot be enforced does not have too much value. As well -without talking about law-, publishing that source would increase the value of their device in the community, even possibly help their sales. Does anybody has connections there? (Who is at all the manufacturer?) I do not even want to mention https://www.fsf.org/licensing/compliance .

Hello everyone,my bugs 3 just came today,I'm very confused on trying to arm it,my fixed id also came up as 8228 after the bind sequence which gave me a - #-1529638477,I put these numbers in the fixed id as hexfet step by step,the quad binds but I can't arm it or switch the lights on or off because my lack of channel mapping.I want to know by editing the model with a - number what was hexfet referring to,changing the name of the model inside the ini in notepad+?If anyone can assist me in getting this insect to flap it's wings it will be greatly appreciated.I got a devo 10 and a 7e with 2 extra 3 way switches but not a 256 just a regular modded 7e with the a7105 and nfr chips.If anyone has a model ini to share I will be forever grateful,thanks n advance...

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.

Thank you bro....

Hello everyone today I took my bugs 3 out and flew it with the devo 10 for the first time I just want to first say awesome Job.I noticed while flying she was very slow and sluggish with little pitch compared to the high rates on the stock tx,I also noticed she yawed to the left or right when I countered either direction never holding center.I was just wondering,you know us noobs have big imaginations,lolIf I uploaded some more captures with the stock tx in high rates can anyone some how integrate that into the model or is it a way to give it more pitch within the current setup?

Was Just wondering is there any more work being put into this protocol to increase the deviated rate to the high stock rate or is it complete as is,any feedback would be greatly appreciated,thank you in advance....

What version were you flying? That sounds like what someone else reported with the driven trims enabled. Reviewed the captures with emulator output and all the channel values look good. Please try with the current test build (c97afba) if you haven't already.

We can revisit the driven trims to try to get more range too. There was an error in the values previously. Do you have any channels reversed in your bugs3 model file?

I'm not really sure where to go with this code due to the radio id issue. Maybe look at incorporating mmakai's algorithm but that still requires a non-standard procedure.

Hi hexfet,
I'm enjoying flying my Bugs 3s and 6 with the previous version. I'll load and check your new version, and will report back if I see any changes. Setting high rates using the MJX Txs seems to leave my Bugs in high rate when I bring them up with the Jumper.
What I'd like to see next is a version where the Jumper beeps if the Bugs sends out of range or low battery alerts back to the Tx.

Thank you very much for the revision,I will try this out.I wonder why the jumper procedure doesn't works with the stock rates being saved from the stock to deviated versions.

my self i am loving the jumper mjx combo EPIC

Are any channels reversed in the model files?