Mjx Bugs 3H

Do you need more data?
I don't know if the addresses are changing or not since I only have 1 transmitter and its almost impossible just to get the TX without the drone itself. I'm in London if anyone is up for a quick test maybe?...

I'm using the forum as a notepad
You'll see me keep updating the same post again and again with more and more data that I discover.
There is one strange thing where I'm confused about if you look at the previous post.
Could you redo long dumps of normal and bind modes from power on?

No prob. Here it is.

planger wrote: Could you redo long dumps of normal and bind modes from power on?

I don't quite understand what do you mean by normal and bind mode. If the quad is powered up and I turn on the TX they just bind automatically. The users manual says that if they don't bind, then I need to force the binding by holding the red button( this is normally used for arming and disarming the quad) and turning on the TX like that. This is what I've done in my previous post.

About the 2 different addresses I've got an idea but I might be completely wrong. This TX has some telemetry functionality and if you have a look, the last 2 inputs are RX and TX enable(channel 5 and 6 in logic) and the radio is switching rapidly between transmitting and receiving. What if they are using different addresses for the up and downlink? Just a thought...

What they call "Force bind" is actualy bind. The TX is using a special address and frequencies so the model can find it.
What they call "Bind" is actually connected/linked/normal operation where the model already know the TX (address, ID and frequencies) and will look for it.

I'll look at completing the flags but there is enough information already to imitate your TX. The problem is more going to be how to find the relation address/ID/frequencies. Let's see.

The bugs 3 mini looks to be using the same payload: www.deviationtx.com/forum/protocol-development/7850-bugs-3-mini
The NRF bind address is the same 0x6D,0x6A,0x78,0x52,0x43 but strangely there is one difference in the frequencies, one value is different and inserted at a different spot:
Bugs3 mini: 0x1A,0x23,0x2C,0x35,0x3E,0x17,0x20,0x29,0x32,0x3B,0x14,0x1D,0x26,0x2F,0x38
Bugs3 H : 0x1A,0x23,0x2C,0x35,0x17,0x20,0x29,0x32,0x3B,0x14,0x1D,0x26,0x2F,0x38,0x11

The radio looks exactly the same so I think they are actually identical. Even the pcb looks the same.

The lookup table is not needed anymore in the latest builds

slam dunk yall worked flawlessly shout out to all u guys - yall got one more bugs TO HAVE EM ALL MASTERED THE BUGS 5

ok guys latest no spreadsheet dfu has the pitch foward n back mixed up with pitch left to right any way to correct this in the controller - i will post video in a second I was testing the b3h and then went to the bugs 3 min and both are doing the same

here look same with the 3h