Nothing really wrong. A known issue where if the TX is right next to the RX it will lose connection. I've seen several people experience this behavior, as I also have this happen under the same circumstances. I've seen some folks turn off a setting on the MT12 that reduces the output from the TX that prevents this from happening. This "issue" doesn't affect the radios ability to operate a vehicle under normal usage conditions.

Kind of silly that a setting known to cause issues is the default. Who doesn't have their radio sitting next to their car when they bind it? It's a recipe for failure. Then again, this is exactly the kind of oversight I've come to expect from this radio.

I agree it's a bit dumb, but I've heard (haven't personally experienced it) this is not uncommon for radios with tremendous range. Overall everyone will have their own opinion, but this is such a minor issue that is so easy to avoid, I hope it doesn't deter the folks who really see the value this radio provides.

What was the known issue? What setting was this? I haven't experienced this yet and I've spent maybe ~100 hours with the radio on next to the receiver, but I would really like to know for my own safety.

I like to keep it closer to 50%, but it takes steel discipline :)

I still think this is for the tinkering RCer, not the racing or bashing type.

A quote I have read many times for sure about driving nitro spoken out by electric drivers and even most not with any own experience. And that only goes about the part of wrenching and driving. And yet, I over the whole internet I do not see people spending time to look up and read information, most just dump a question on several places and wait for an answer.

My quote is always "why change if something works?" As in this topic I do see it with other transmitters as well. Beside people spend too much time doing an upgrade not reading the manual correctly like the limitation of the SDcard memory but also the small chance the update goes wrong and does not power on and here in this topic people facing errors in the new software.

​​​​
I used to install wireless networks and It's a simple explanation regarding the wavelength of the transmitted signal. Being the signal is a wave, it crosses over 0 at 1/2 and 1 times the wavelength. When you place the rx perfectly you can get crazy behaviour..for 2.4ghz one wavelength is 12 cm.

I am way oversimplifying things here and there are other factors like reflected signals to take into account.

For anyone that still listens to the radio in their car, this is the same phenomenon that causes station to drop out and come.back when you roll forward a few inches. Yes I'm that old, and I still play with toy cars.

Sure, it's great for tinkering, but that's not needed. It's pretty much ready to go right out of the box. For a vehicle with only two channels, you really only need to set your steering endpoints. Sure, that's SLIGHTLY more complicated but only because the terminology is different, but that's like a few minutes of confusion one time. And even binding is dead simple and flexible because all it takes is to log-in to the receiver to enter your binding phrase. Done. (it supports the old-fashion way of binding too)

And I would argue it is for racing or bashing. Racing because ExpressLRS is insanely low-latency and the radio is so configurable, it can do anything the top radios can do -- and so much more. It's great for bashing too. It allows you to run so many of your vehicles -- especially the older ones. I'm now able to run a 2S LiPo pack on my MT4 FT even though the Novak GTB ESC doesn't have a low voltage cut-off feature because the receiver included with the MT12 has telemetry and could read the battery voltage. Just a few seconds to add the parameter in the telemetry screen and I have a live read-out of my pack voltage. A few minutes of programming a logical switch and now I have an audible and tactile (vibration) warning along with a voice call-out of the voltage when the pack reaches the threshold. A few more minutes of setting up a drive mode and now in low voltage mode, it can automatically limit my throttle to just 20%.

I was also able to set-up an "arm" switch, so I don't get accidental throttle runaways when powering up vehicles. Holding the switch at the back of the base for >1 second will "arm" and "unarm" the throttle.

Now I'm finally getting around to picking-up LUA and starting to make some pretty custom telemetry screens.

I also have plans for projects to get GPS, ground-speed, rpm, & battery current telemetry -- just for fun. And maybe even design my own receiver with all the features I want. All this is possible because the hardware and the software is all open source. And it's glorious!

Oh, and it allows you to "loan" your models out... so if you have friends or just a fleet of vehicles and a few ExpressLRS radios that you share among your kids, you can connect to your model and enable "loan" mode and the receiver will instantly go into bind mode allowing your buddy to bind their radio temporarily and "return" it after they are done... Great for bashing with buddies.

And I've only just started to play with this radio like 3 weeks ago. So much more I haven't explored yet. And when Companion finally adds MT12 support, I'm going to be able to work much quicker.


Not sure I fully understand you. What limitation of the SD Card? Update can't really go that wrong. Hardware-wise, the Radios are just Arduinos. You really can't brick them. And backing up your settings is as easy as plugging it into the computer and dragging and dropping the entire SD card contents to your computer (I use a NAS that is backed-up nightly offsite).

Yeah, I don't think that's not how things work.. The radio is emitting electromagnetic waves. Those waves propagate through space. They are not confined in a way that would cause reflections that generate standing waves with nodes that would cause a signal drop.. And if somehow that's true, then you'd have the same problem with ANY radio system. Most modern ones have the same 2.4GHz fundamental frequency and would have the same distance between nodes in a standing wave situation.

Most simple SD card slots have a limit of 32Gb, as example it is clearly mentioned in the Futaba manual and yet on a weekly base in the Futaba Facebook group people are asking what they are doing wrong using a 64 or even a 128Gb card. Also about a background picture it is clearly stated it has to be a certain pixel size in a specific file format and color depth. People can spend hours and still not doing it right.

I'm pretty sure the SD Card capacity is the 32GB limit of SDHC, not 32Gb (big difference). But 32GB is insanely large for what you need in a transmitter. The only thing that would take tons of storage is if you are logging a high number of telemetry sensors at an extremely high rate for a very long duration. Still, 32GB is plenty.

3D data
 

Hello

thanks for your great work,
Can you share all your 3d models in STEP format please.
I want to make small modifications and its easier in STEP.

And I will try to make 3d model for a larger grip too, if needed i'll share this here.

thank you

Can you open it? Please feel free to let me know if you have any problems.

I also want to modify the grip. Please share your data.

I would like you to try this too.

https://cimg6.ibsrv.net/gimg/www.rct...4fab35ae60.jpg

thank you
yes i can open it.

Ok i will share the file of the larger grip when I did it.