Interesting. I was thinking about getting one of these transmitters with an ELRS setup. I see this problem could be in 1 or 2 places. Or a combination of them both. 1. The receiver is browning out due to power issues. If the cap solves the issue. This is likely to be the case. So it is a hardware issue on the receiver. Something that RadioMaster should sort out. However, if it’s browning out. The receiver wouldn’t be sending instructions. So I don’t understand why it would command full throttle. Unless that’s something the ESC will do with no signal? 2. Failsafe isn’t obeying the correct failsafe parameters. This would be an issue with ELRS and nothing to do with RadioMaster. However, I would have thought if that was the case. It would be raised as an issue on ELRS’ GitHub at very least. It would be a pretty important bug, so should have been fixed if it were an ELRS issue. Out of interest. What happens if you set the car on fire a block so it can’t drive. Power everything up normally. Give a little throttle, so you know the motor is working. Then switch off the transmitter? If the throttle stays neutral and the steering straight. It would appear that failsafe is behaving correctly. And the issue is the receiver hardware design. However, if it goes full throttle. It would point to a bug in ELRS. I hope you get to the bottom of it.
Known issue but easy fix. Either install a glitch buster cap, or better yet, power your receiver with a dedicated nano BEC. This is an example of drone engineers designing for surface. We have much higher draw rigs and the chip browns out. It’s just too sensitive to the power drops caused by high loads and the built in BEC in the ESC or a separate BEC that also powers servos not being able to keep up with demand.
Glitch buster and external bed doesn’t fix it. This damn elrs system caused a 1500 dollar drag to runaway at full tilt on a pass. Causing a lot of damage.
Same issue here wrecked a mini b and a stampede this week. Happens inside and out. I am using the elrs version of the mt12. And 3 4 and 5 channel radiomaster receivers. Love the transmitter otherwise, but I expect to stay in control this is not acceptable.
I have the 4 in 1 version and had my 5th scale Kraton 8s runaway at full throttle once too. Lucky for me my neighbors tree stopped the truck from moving forward, but I had to do a little lawn repair where it went full gopher until I got to it and decided how to address that situation
It sounded like you lost telemetry / connection between transmitter and receiver. There are 2 possibilities, 1 transmitter lost connection, 2 receiver lost connection. What’s strange is either way, the receiver should have a failsafe mode that puts throttle at 1500 center / off. You can test this by having the car blocked up and go full throttle while removing the transmitter battery. If you get throttle runaway then your receiver failsafe is not correctly set up. Now as for the signal loss there is a question of what receiver are you using? Sorry I didn’t read all posts. Some receivers require RF Frequency Fine Tuning. See if that is available on your internal RF settings.
One interesting thing that jumps out at me reading after watching the video, and reading through all the comments, is the insistence that the MT12 is the issue... when in point of fact this has not been established all. What you appear to have demonstrated is that either due to the impact, or possibly undervoltage, the receiver disconnected/rebooted. The transmitter is even telling you that, when it says the telemetry is lost, and then recovered. i.e. if the issue is with the receiver, not much the transmitter can do about it, and it is completely wrong to blame that. I'm not denying there could be a problem on the handset, or that saying this is correct behaviour of the system. I just don't see this proving the handset is where the issue lies. On the ER5C-i, CH2 and CH3 have secondary special uses (i.e. they are the serial TX/RX lines for programming the MCU)... and one of the lines can put out garbage info when the MCU reboots... so it would be interesting to know what you have plugged into those channels... i.e. is the ESC getting garbage rather than no signal, so thinks it should still be doing something. Could a cap on the bus fix it? If it is brownout related, sure. Is that an acceptable fix? That depends... as this has been an acceptable "fix" for a long time now for other receivers and systems, and had been around for way longer than ELRS has existed. Several stabilisers and even car stuff that I have had over the years have come with a plug in capacitor for the receiver bus line for this reason. However, I think the ESC needs to stop, rather than keep going. I've been using the RM (and other brands) PWM receivers for some time now, and have them in cars also, and have yet to have any issue with them, or with the MT12. However, I don't do tricks and jumps and stuff, so haven't put the ESC's BEC/power harness through any major strain, so could just be fortunate, or it could even be a clash with that exactly combination? Incompatibles do exist with certain combinations of hardware for pretty much every RC control link system. PS: Can you test the failsafe *properly* next time do you a video like this, pretty please? 😆 Sure, you say it is calibrated and such, but you are doing a video to prove the hardware is at fault... and didn't turn the transmitter off when you had the model propped up, to prove that it would go from running / with steering locked over, to neutral/straight. 'cause you know, people will immediately say "you didn't set it up right dude". Don't give them the ammo. 😉
Problem with the receiver vs problem with the transmitter - it's a distinction without a difference. Doesn't change the fact it's a radio I can't use because it doesn't have a functioning failsafe. And I did test the failsafe. The radio connection failed. The car ran off. It did not fail safely. It's that simple. As far as I can tell no amount of evidence would ever be sufficient to convince the ELRS fanatics - the goalposts will simply be moved and I'll be met with a brand new reason for why it's still my fault. And using the cheap $30 radio this car came with completely fixes the problem. So why should I waste any more of my time on this?
@nick_cnc Distinction without a difference it is most definitely not... as you are potentially casting the blame on the wrong thing entirely. How did you "test the failsafe"... as what you did in the video is not a test of the failsafe. That would be simply turning the transmitter off, and observing what happens. Turn it on again, wait for it to lock on, rinse repeat. That would demonstrate if the issue is in the failsafe, or some other scenario where the RX is browning out, and unable to failsafe. The distinction matters, as then you can start to figure out if it is a solvable problem, or system incompatibility. Unfortunately that will always be the case, whatever radio system you use... fanboys will refuse to listen. However, you are not doing yourself any favours with a video like this and the claim you say it backs up, as it most definitely does not. Whether you spend time to figure out what is the root cause is a decision only you can make. If the system it came with is good enough for you, great. I wish you much enjoyment with it.
@@pfeerick I can only assume you are creating your own definition of what failsafe means as a way to pretend the MT12 doesn't have a problem, because a failsafe that only works under normal conditions and lets the car runaway when things go wrong is, by definition, not a failsafe. It's obvious there's an issue with the MT12/ELRS system that even a cheap POS radio has managed to avoid.
@@nick_cnc The method to test failsafe is, and has always been, turning off the transmitter. If you turn off the transmitter and the throttle/steering go to neutral, you have a transmitter problem. If you turn off the transmitter and get anything other than what you set as the failsafe position, it's a receiver problem, likely brownout. Changing the radio entirely doesn't test the problem, because you changed too many variables. I've tested mine several times with as much load as possible on a cheap BEC I stuck in a truck with a ton of extra stuff (lights, winch, etc.), and couldn't get it to do anything weird, but that's not applicable to your situation, because I have a Radiolink receiver and 4n1 MT12. The only times I can get it to disconnect are when I'm right next to the truck with the transmitter set to full power, and when I have the tuning way, way off (like 75 points from peak RSSI). This is exactly the same thing I had happen with my Wraith several times 10 years ago when I switched from Futaba to Spektrum (and then back within a month). Two large caps fixed it entirely. A 10 pound truck with a 13.5t motor taking off at full power is way too exciting for me. I'm not defending the MT12. I have one (not ELRS, though), and I like it, but I drive crawlers and have the radio set to low power mode since I'm standing on top of the thing while driving. I switched from Radiolink to Radiomaster after seeing all the RC8X runaway videos, and I've been watching for similar problems with the MT12.
I got a partial throttle runaway with my transmitter on the multi module bound to a Kyosho RX. It was doing weird things, the steering servo inverted direction and I had to reset steering end points after setting it all up weeks prior.
Concerning for sure. Admittedly I’ve only used mine on one esc so far (reedy 510r) but I have not had an issue. 1. Have you tried a second receiver in this car? In a previous video you noted it happens often with this car. 2. Could it be at all related to throttle being set to 333hz? I have my steering on 333 but from my (limited) understanding there isn’t any benefit to going from default/50 to 333 for the majority of speed controls
It does this with every receiver I test. I believe this to be an inherent flaw in the system. I've run the same electronics with other radios at even higher PWM rates and never ran into these issues.
Crazy question I went scouting on some forums and I believe it's a mix of the devs not caring and possible hard issues that could be stemmed from how it reacts to voltage changes. Someone tested by doing a few voltage dips got it to go into a telemetry lost runaway. I am not defending the receiver or transmitter but I think that might be something. I am curious if you put a capacitor or a BEC on it would that possible help?
That person was me. A BEC cap is a bandaid solution. I've tried other radios in this car, including the incredibly cheap rlaarlo radio that came with it, and none behave the way the MT12 does. At worst they will stop momentary before picking right back up and get going again - so quick you almost think its cogging from the sensor wire coming unplugged. A BEC brownout/fault is exactly the type of scenario where a failsafe is supposed to step in and prevent the car from running away. If a failsafe only works when the system is operating under nominal conditions, it is not a failsafe.
@@nick_cnc This just sucks. I was really hoping to get ones of these eventually but I might as well just forget it and go with something else like a Dumbo DDF-350.
@@nick_cnc bandaid or not it would help understand the failure condition. Is the issue that the receiver is losing power or rebooting for some reason and then this happens.
Woh, shouldn't be losing link like that for sure (he said stating the obvious). Only thing I've heard of that might be causing it is the transmitter power being set too high and causing a brown out due to close proximity. SO stupid question but have you tried turning the receiver power down to auto? I will say I've been running my MT12 set up for 1/10 off road racing this season gone and not had your issue, so though your clearly having it, I don't think it's an intrinsic flaw. I hope you can find a solution.
This happens with every receiver I test and it has happened at close as well as far distances. This does not happen with other radios I put in the car. It is most certainly a systemic flaw in the platform. And I have found a solution for this. I have replaced the radio with a Noble NB4+. This video is merely proof for people who tell me I'm full of shit when I advise other to stay away from this radio.
@@nick_cnc Ah, I see. Well sorry you had to go through all this, it's crap when you have issues and the support doubts you at every turn. I hope the NB4+ is problem free for you.
Couple ideas and an empathetic comment... Def frustrating to failsafe in that situation for sure, not sure what the issue is but as someone mentioned may be a bit overpowered for the proximity of the RX and TX. The one thing that jumps out at me (and it may just be a phone audio thing on my end), but to me it doesn't sound like a full throttle runaway, but rather partial throttle. Possibly the esc isn't calibrated to the mt12 quite right or your tx has some curves adjusted? Either could cause a partial throttle rather than neutral if Rx is sending 1500 as a failsafe. Though, again... could just be my phone's crummy audio. I think the issues in general are a direct result of elrs originating from drones which don't use pwm, nor having ESCs that "calibrate" independently of the tx/rx like most surface RCs do. On a high note this should all be ironed out eventually. I absolutely agree it's super frustrating that Radiomaster would sell a product on the elrs hype, without ironing out these bugs first though, so def understand your pain. Edit: just saw the comments concerning brownout and a cap solving it, absolutely would cause the failsafes if the ESC is drawing so much current that there's voltage drop causing the BEC to output less than 4.5v
The MT12 is outputting 1500us when the throttle trigger is in the neutral position. The ESC is also properly calibrated. The rx is simply not going into a failsafe state like it should be.
Oof, that's rough. Sorry to hear it man, figured you'd run it through the gamut, but figured I'd toss it out there just in case. Absolutely awesome stuff on the mid motor bandit by the way, super cool project!
Just another idea... I noticed the fail safe happened when turning. Meaning servo was active. Servos are notorious for electro magnetic interference in rf systems. I also noticed your Rx was mounted on top of the servo. May be stretching, but could be that the servo is causing interference. Possible that the elrs receivers are more sensitive to it... Maybe give it another test with the ex places further away? Not sure how that would cause a bad failsafe state, but who knows?
@@bollio I'll keep returning to the simple fact that the MT12 is the only radio I have that behaves this way in this scenario. To me it is simply unacceptable for any radio that is supposed to be "top of the line" to behave in this manner, especially considering a cheap $30 radio is not susceptible to whatever is causing the MT12 to lose connection and runaway.
Good find, and great video covering the issue. That being said this vitriol is wildly misplaced. No one but the idiot fanboys(found in every camp of every hobby) thinks you finding this is bad or some dunk though... The whole point of an opensource project like this is to work with the devs and make a better project together. Like file a bug report and start working with the community to lift us all up.Y'all surface guys are honestly weird AF with this attitude you have against any open standards in your portion of the hobby. You seem more than willing to suckle on HorizonHobby and Traxxas's trash without understanding that doing so is exactly why your portion of the hobby looks like it's 2013 in terms of technology and pricing. It's cool though y'all keep on keeping on so I can keep doing stuff like selling you $.30 3D printed parts for $20.
@@CDRaff the fanboys in this case are the devs. I posted this issue on the GitHub months ago. I was made to feel like I was stupid and ultimately ignored. Had I got a more receptive response from the beginning, this video never would have been necessary.
@nick_cnc that's not the point. Your posting information that can be easily resolved with some troubleshooting. It's going to be operator error and your going to look silly. The devs over on the discord channel told me to send you over there so they can walk through it with you.
@@zg6038 I've done plenty of testing and troubleshooting - including setting PWMs to 50hz. Nothing has solved this. I've even posted on the ELRS github where I was basically dismissed and ignored. I'm not going to the discord just to get more of the same treatment.
@@nick_cncI don't think many people use the discussions area - the discord server is where most of the support happens for ELRS, and there are usually quite a few people around. But it was actually the EdgeTX discord that we wanted you to come over to. I think more testing is needed before can definitively say what the actual issue is, based on what I have seen on this video, and on discussion thread #2882
This is the receiver issue. There ruclips.net/video/OfxvGxojPYc/видео.htmlsi=jqV_vfQKWhrOtO8q (Somewhere in midle) You can find ch1 and ch2 waveforms while power on procedure. It is really strange behavior, but explains that happens:( seems right way is using ch3 as Throttle channel, neither ch1 nor ch2. And probably to config motor control to use some arming sequence if possible. This is defenetly bug in fw. Elrs is more complex system to compare with cheap rx/tx and more easy make mistakes, but elrs and edge tx have more feture and flexibility.
@@andreygolikov7583might explain it -I've noticed sometimes on powering up the car the steering or throttle might blip real quick. Very not normal behavior. But being complex doesn't excuse making obvious mistakes. If anything it just confirms my suspicion that the devs don't know or care enough about surface applications to even get the basics right. Because what good do advanced features really do if the car is running off out of control?
@nick_cnc This is an opensource project. The bad part is that it usually doesn't have a process, QA and etc... The good part is that you can fast change anything. You have to report this issue, and it will be fixed. I think it is critical enough to have high priority. But if you do not say to the developer about the problem, whey will not to know about. It is open source. And to clear radiomaster are not developer, they support and use, elrs developer should to know.
@andreygolikov7583 brought this up months ago on the GitHub. Nothing happened. Honestly I blame RadioMaster more than anything. They're a for-profit business selling radios with severe bugs and as far as I can tell, offer absolutely no contributions to the open source projects they're based on. RadioMaster should be the ones doing QA and testing before seeming a product.
You may have watched this before, but maybe it might help, around the 9:55 mark he mentions the failsafe settings, ruclips.net/video/OA7FozAr2S8/видео.htmlfeature=shared < I understand your frustration in that you were ignored on github, but some of the people who've commented in this chat are genuinely trying to get to the bottom of this problem and help. It may well be a hardware fault, but if it were me, I'd explore every avenue before I sent stuff back asking for a refund. Good luck Nick...
i just don't know what to even say. did you not see my failsafe settings set exactly the same as he did at 9:55? I swear you guys ignore everything I say and do just to find a new way to tell me i'm wrong.
Ha, your people skills are sadly lacking...only trying to help, I'm new to ELRS myself, using it on fixed wing. It's so much cheaper and performance/stability blows everything else away. it's the future. Seems like ELRS isn't for you as there is a learning curve involved. In my short time using the protocol, I swear that 99.9% of faults are 'finger problems' with the user having a setting wrong. Fortunately, I wasn't too proud to ask for help and post screenshots of my setups, you obviously are for some reason. Anyhow, enjoy the hobby, after all it's your cash, so spend it as you deem fit...
@sirtrumpington4779 I literally have video proof that I have the "fixed" fw's installed and that my failsafe settings are set correctly and you're still trying to blame it on me? You get that you're basically calling me stupid, right? And then you have the nerve to tone police me? GTFO with that.
Sorry buddy, but I was genuinely trying to help. I'm not saying you're an idiot, just that I had a few brain farts at first thinking I was doing everything by the book. And regarding your 'tone' and 'gtfo' statements...your reply to my first post set the tone, so don't play the martyr here. As I said above, maybe you simply don't have the patience to try and remedy the problem...anyhow, I'm done here, you seem to be fairly stubborn about you can't have a setting wrong or memic type problem with your hardware...no harm no foul, on my part the intention was purely honourable in trying to help somehow...👍
Question and I'm not being a douchebag.... Why do you need such an elaborate radio system? Just get yourself a regular 2.4 like a spectrum or something like that and your problems will all be solved...🤔
I don't. After using this thing for 6 months I couldn't find anything it could do that made dealing with the frustrating UI worth it. Honestly I've been thinking about doing a fun video showing how much work it takes to do simple things compared to my NB4+.
Interesting. I was thinking about getting one of these transmitters with an ELRS setup.
I see this problem could be in 1 or 2 places. Or a combination of them both.
1. The receiver is browning out due to power issues. If the cap solves the issue. This is likely to be the case. So it is a hardware issue on the receiver. Something that RadioMaster should sort out. However, if it’s browning out. The receiver wouldn’t be sending instructions. So I don’t understand why it would command full throttle. Unless that’s something the ESC will do with no signal?
2. Failsafe isn’t obeying the correct failsafe parameters. This would be an issue with ELRS and nothing to do with RadioMaster. However, I would have thought if that was the case. It would be raised as an issue on ELRS’ GitHub at very least. It would be a pretty important bug, so should have been fixed if it were an ELRS issue.
Out of interest. What happens if you set the car on fire a block so it can’t drive. Power everything up normally. Give a little throttle, so you know the motor is working. Then switch off the transmitter? If the throttle stays neutral and the steering straight. It would appear that failsafe is behaving correctly. And the issue is the receiver hardware design. However, if it goes full throttle. It would point to a bug in ELRS.
I hope you get to the bottom of it.
This is why I run a Dumbo or a GT5. Never had any problems. Have fun with you super complicated radios!!!
Known issue but easy fix. Either install a glitch buster cap, or better yet, power your receiver with a dedicated nano BEC. This is an example of drone engineers designing for surface. We have much higher draw rigs and the chip browns out. It’s just too sensitive to the power drops caused by high loads and the built in BEC in the ESC or a separate BEC that also powers servos not being able to keep up with demand.
That's not a fix, it's a bandaid. Better made radios, and even cheap POS radios, do not exhibit this behavior.
Glitch buster and external bed doesn’t fix it. This damn elrs system caused a 1500 dollar drag to runaway at full tilt on a pass. Causing a lot of damage.
@@SilverbackOrdnance you’re an edge case of extremely high amp draw so it may not work for you unfortunately.
Same issue here wrecked a mini b and a stampede this week. Happens inside and out. I am using the elrs version of the mt12. And 3 4 and 5 channel radiomaster receivers.
Love the transmitter otherwise, but I expect to stay in control this is not acceptable.
I have the 4 in 1 version and had my 5th scale Kraton 8s runaway at full throttle once too. Lucky for me my neighbors tree stopped the truck from moving forward, but I had to do a little lawn repair where it went full gopher until I got to it and decided how to address that situation
It sounded like you lost telemetry / connection between transmitter and receiver. There are 2 possibilities, 1 transmitter lost connection, 2 receiver lost connection. What’s strange is either way, the receiver should have a failsafe mode that puts throttle at 1500 center / off. You can test this by having the car blocked up and go full throttle while removing the transmitter battery. If you get throttle runaway then your receiver failsafe is not correctly set up. Now as for the signal loss there is a question of what receiver are you using? Sorry I didn’t read all posts. Some receivers require RF Frequency Fine Tuning. See if that is available on your internal RF settings.
One interesting thing that jumps out at me reading after watching the video, and reading through all the comments, is the insistence that the MT12 is the issue... when in point of fact this has not been established all. What you appear to have demonstrated is that either due to the impact, or possibly undervoltage, the receiver disconnected/rebooted. The transmitter is even telling you that, when it says the telemetry is lost, and then recovered. i.e. if the issue is with the receiver, not much the transmitter can do about it, and it is completely wrong to blame that. I'm not denying there could be a problem on the handset, or that saying this is correct behaviour of the system. I just don't see this proving the handset is where the issue lies.
On the ER5C-i, CH2 and CH3 have secondary special uses (i.e. they are the serial TX/RX lines for programming the MCU)... and one of the lines can put out garbage info when the MCU reboots... so it would be interesting to know what you have plugged into those channels... i.e. is the ESC getting garbage rather than no signal, so thinks it should still be doing something.
Could a cap on the bus fix it? If it is brownout related, sure. Is that an acceptable fix? That depends... as this has been an acceptable "fix" for a long time now for other receivers and systems, and had been around for way longer than ELRS has existed. Several stabilisers and even car stuff that I have had over the years have come with a plug in capacitor for the receiver bus line for this reason. However, I think the ESC needs to stop, rather than keep going. I've been using the RM (and other brands) PWM receivers for some time now, and have them in cars also, and have yet to have any issue with them, or with the MT12. However, I don't do tricks and jumps and stuff, so haven't put the ESC's BEC/power harness through any major strain, so could just be fortunate, or it could even be a clash with that exactly combination? Incompatibles do exist with certain combinations of hardware for pretty much every RC control link system.
PS: Can you test the failsafe *properly* next time do you a video like this, pretty please? 😆 Sure, you say it is calibrated and such, but you are doing a video to prove the hardware is at fault... and didn't turn the transmitter off when you had the model propped up, to prove that it would go from running / with steering locked over, to neutral/straight. 'cause you know, people will immediately say "you didn't set it up right dude". Don't give them the ammo. 😉
Problem with the receiver vs problem with the transmitter - it's a distinction without a difference. Doesn't change the fact it's a radio I can't use because it doesn't have a functioning failsafe.
And I did test the failsafe. The radio connection failed. The car ran off. It did not fail safely. It's that simple.
As far as I can tell no amount of evidence would ever be sufficient to convince the ELRS fanatics - the goalposts will simply be moved and I'll be met with a brand new reason for why it's still my fault. And using the cheap $30 radio this car came with completely fixes the problem. So why should I waste any more of my time on this?
@nick_cnc Distinction without a difference it is most definitely not... as you are potentially casting the blame on the wrong thing entirely.
How did you "test the failsafe"... as what you did in the video is not a test of the failsafe. That would be simply turning the transmitter off, and observing what happens. Turn it on again, wait for it to lock on, rinse repeat. That would demonstrate if the issue is in the failsafe, or some other scenario where the RX is browning out, and unable to failsafe. The distinction matters, as then you can start to figure out if it is a solvable problem, or system incompatibility.
Unfortunately that will always be the case, whatever radio system you use... fanboys will refuse to listen. However, you are not doing yourself any favours with a video like this and the claim you say it backs up, as it most definitely does not.
Whether you spend time to figure out what is the root cause is a decision only you can make. If the system it came with is good enough for you, great. I wish you much enjoyment with it.
@@pfeerick I can only assume you are creating your own definition of what failsafe means as a way to pretend the MT12 doesn't have a problem, because a failsafe that only works under normal conditions and lets the car runaway when things go wrong is, by definition, not a failsafe.
It's obvious there's an issue with the MT12/ELRS system that even a cheap POS radio has managed to avoid.
@@nick_cnc The method to test failsafe is, and has always been, turning off the transmitter. If you turn off the transmitter and the throttle/steering go to neutral, you have a transmitter problem. If you turn off the transmitter and get anything other than what you set as the failsafe position, it's a receiver problem, likely brownout. Changing the radio entirely doesn't test the problem, because you changed too many variables. I've tested mine several times with as much load as possible on a cheap BEC I stuck in a truck with a ton of extra stuff (lights, winch, etc.), and couldn't get it to do anything weird, but that's not applicable to your situation, because I have a Radiolink receiver and 4n1 MT12. The only times I can get it to disconnect are when I'm right next to the truck with the transmitter set to full power, and when I have the tuning way, way off (like 75 points from peak RSSI).
This is exactly the same thing I had happen with my Wraith several times 10 years ago when I switched from Futaba to Spektrum (and then back within a month). Two large caps fixed it entirely. A 10 pound truck with a 13.5t motor taking off at full power is way too exciting for me. I'm not defending the MT12. I have one (not ELRS, though), and I like it, but I drive crawlers and have the radio set to low power mode since I'm standing on top of the thing while driving. I switched from Radiolink to Radiomaster after seeing all the RC8X runaway videos, and I've been watching for similar problems with the MT12.
The problem is the receiver. It has a glitch in the hardware both 3ch and 5channel.
Could it be a malfunction in the transmitter throttle? Ie it’s sticking in full throttle?
I got a partial throttle runaway with my transmitter on the multi module bound to a Kyosho RX. It was doing weird things, the steering servo inverted direction and I had to reset steering end points after setting it all up weeks prior.
Concerning for sure. Admittedly I’ve only used mine on one esc so far (reedy 510r) but I have not had an issue.
1. Have you tried a second receiver in this car? In a previous video you noted it happens often with this car.
2. Could it be at all related to throttle being set to 333hz? I have my steering on 333 but from my (limited) understanding there isn’t any benefit to going from default/50 to 333 for the majority of speed controls
It does this with every receiver I test. I believe this to be an inherent flaw in the system.
I've run the same electronics with other radios at even higher PWM rates and never ran into these issues.
Crazy question I went scouting on some forums and I believe it's a mix of the devs not caring and possible hard issues that could be stemmed from how it reacts to voltage changes. Someone tested by doing a few voltage dips got it to go into a telemetry lost runaway. I am not defending the receiver or transmitter but I think that might be something. I am curious if you put a capacitor or a BEC on it would that possible help?
That person was me. A BEC cap is a bandaid solution. I've tried other radios in this car, including the incredibly cheap rlaarlo radio that came with it, and none behave the way the MT12 does. At worst they will stop momentary before picking right back up and get going again - so quick you almost think its cogging from the sensor wire coming unplugged.
A BEC brownout/fault is exactly the type of scenario where a failsafe is supposed to step in and prevent the car from running away. If a failsafe only works when the system is operating under nominal conditions, it is not a failsafe.
@@nick_cnc This just sucks. I was really hoping to get ones of these eventually but I might as well just forget it and go with something else like a Dumbo DDF-350.
@@nick_cnc bandaid or not it would help understand the failure condition. Is the issue that the receiver is losing power or rebooting for some reason and then this happens.
Woh, shouldn't be losing link like that for sure (he said stating the obvious). Only thing I've heard of that might be causing it is the transmitter power being set too high and causing a brown out due to close proximity. SO stupid question but have you tried turning the receiver power down to auto? I will say I've been running my MT12 set up for 1/10 off road racing this season gone and not had your issue, so though your clearly having it, I don't think it's an intrinsic flaw. I hope you can find a solution.
This happens with every receiver I test and it has happened at close as well as far distances. This does not happen with other radios I put in the car. It is most certainly a systemic flaw in the platform.
And I have found a solution for this. I have replaced the radio with a Noble NB4+. This video is merely proof for people who tell me I'm full of shit when I advise other to stay away from this radio.
@@nick_cnc Ah, I see. Well sorry you had to go through all this, it's crap when you have issues and the support doubts you at every turn. I hope the NB4+ is problem free for you.
Please test failsafe on bench. Just steer and give a little throttle and power off transmitter.
@@digitaljunk no
Couple ideas and an empathetic comment... Def frustrating to failsafe in that situation for sure, not sure what the issue is but as someone mentioned may be a bit overpowered for the proximity of the RX and TX.
The one thing that jumps out at me (and it may just be a phone audio thing on my end), but to me it doesn't sound like a full throttle runaway, but rather partial throttle. Possibly the esc isn't calibrated to the mt12 quite right or your tx has some curves adjusted? Either could cause a partial throttle rather than neutral if Rx is sending 1500 as a failsafe. Though, again... could just be my phone's crummy audio.
I think the issues in general are a direct result of elrs originating from drones which don't use pwm, nor having ESCs that "calibrate" independently of the tx/rx like most surface RCs do.
On a high note this should all be ironed out eventually. I absolutely agree it's super frustrating that Radiomaster would sell a product on the elrs hype, without ironing out these bugs first though, so def understand your pain.
Edit: just saw the comments concerning brownout and a cap solving it, absolutely would cause the failsafes if the ESC is drawing so much current that there's voltage drop causing the BEC to output less than 4.5v
The MT12 is outputting 1500us when the throttle trigger is in the neutral position. The ESC is also properly calibrated. The rx is simply not going into a failsafe state like it should be.
Oof, that's rough. Sorry to hear it man, figured you'd run it through the gamut, but figured I'd toss it out there just in case.
Absolutely awesome stuff on the mid motor bandit by the way, super cool project!
@@bollio Thanks!
Just another idea... I noticed the fail safe happened when turning. Meaning servo was active. Servos are notorious for electro magnetic interference in rf systems. I also noticed your Rx was mounted on top of the servo.
May be stretching, but could be that the servo is causing interference. Possible that the elrs receivers are more sensitive to it... Maybe give it another test with the ex places further away? Not sure how that would cause a bad failsafe state, but who knows?
@@bollio I'll keep returning to the simple fact that the MT12 is the only radio I have that behaves this way in this scenario.
To me it is simply unacceptable for any radio that is supposed to be "top of the line" to behave in this manner, especially considering a cheap $30 radio is not susceptible to whatever is causing the MT12 to lose connection and runaway.
Call warranty , had siimilar issue with traxxas, after turning on it started to ride on ita own
Good find, and great video covering the issue. That being said this vitriol is wildly misplaced. No one but the idiot fanboys(found in every camp of every hobby) thinks you finding this is bad or some dunk though... The whole point of an opensource project like this is to work with the devs and make a better project together. Like file a bug report and start working with the community to lift us all up.Y'all surface guys are honestly weird AF with this attitude you have against any open standards in your portion of the hobby. You seem more than willing to suckle on HorizonHobby and Traxxas's trash without understanding that doing so is exactly why your portion of the hobby looks like it's 2013 in terms of technology and pricing.
It's cool though y'all keep on keeping on so I can keep doing stuff like selling you $.30 3D printed parts for $20.
@@CDRaff the fanboys in this case are the devs. I posted this issue on the GitHub months ago. I was made to feel like I was stupid and ultimately ignored.
Had I got a more receptive response from the beginning, this video never would have been necessary.
@@nick_cnc I would love to see that bug report, got a link?
Does the 4in1 have this issue?
Antenna routing🤠👍
Does your ESC even accept 333?
I can run it at 400hz with my NB4 and it doesn't do this.
@nick_cnc that's not the point. Your posting information that can be easily resolved with some troubleshooting. It's going to be operator error and your going to look silly. The devs over on the discord channel told me to send you over there so they can walk through it with you.
@@zg6038 I've done plenty of testing and troubleshooting - including setting PWMs to 50hz. Nothing has solved this.
I've even posted on the ELRS github where I was basically dismissed and ignored. I'm not going to the discord just to get more of the same treatment.
@@nick_cnc Then don't post the video. No one gets any good info from github anymore.
@@nick_cncI don't think many people use the discussions area - the discord server is where most of the support happens for ELRS, and there are usually quite a few people around. But it was actually the EdgeTX discord that we wanted you to come over to. I think more testing is needed before can definitively say what the actual issue is, based on what I have seen on this video, and on discussion thread #2882
This is the receiver issue. There ruclips.net/video/OfxvGxojPYc/видео.htmlsi=jqV_vfQKWhrOtO8q
(Somewhere in midle) You can find ch1 and ch2 waveforms while power on procedure. It is really strange behavior, but explains that happens:( seems right way is using ch3 as Throttle channel, neither ch1 nor ch2. And probably to config motor control to use some arming sequence if possible. This is defenetly bug in fw. Elrs is more complex system to compare with cheap rx/tx and more easy make mistakes, but elrs and edge tx have more feture and flexibility.
@@andreygolikov7583might explain it -I've noticed sometimes on powering up the car the steering or throttle might blip real quick. Very not normal behavior.
But being complex doesn't excuse making obvious mistakes. If anything it just confirms my suspicion that the devs don't know or care enough about surface applications to even get the basics right. Because what good do advanced features really do if the car is running off out of control?
@nick_cnc This is an opensource project. The bad part is that it usually doesn't have a process, QA and etc... The good part is that you can fast change anything. You have to report this issue, and it will be fixed. I think it is critical enough to have high priority. But if you do not say to the developer about the problem, whey will not to know about. It is open source. And to clear radiomaster are not developer, they support and use, elrs developer should to know.
@andreygolikov7583 brought this up months ago on the GitHub. Nothing happened.
Honestly I blame RadioMaster more than anything. They're a for-profit business selling radios with severe bugs and as far as I can tell, offer absolutely no contributions to the open source projects they're based on. RadioMaster should be the ones doing QA and testing before seeming a product.
You may have watched this before, but maybe it might help, around the 9:55 mark he mentions the failsafe settings, ruclips.net/video/OA7FozAr2S8/видео.htmlfeature=shared < I understand your frustration in that you were ignored on github, but some of the people who've commented in this chat are genuinely trying to get to the bottom of this problem and help. It may well be a hardware fault, but if it were me, I'd explore every avenue before I sent stuff back asking for a refund. Good luck Nick...
i just don't know what to even say. did you not see my failsafe settings set exactly the same as he did at 9:55? I swear you guys ignore everything I say and do just to find a new way to tell me i'm wrong.
Ha, your people skills are sadly lacking...only trying to help, I'm new to ELRS myself, using it on fixed wing. It's so much cheaper and performance/stability blows everything else away. it's the future. Seems like ELRS isn't for you as there is a learning curve involved. In my short time using the protocol, I swear that 99.9% of faults are 'finger problems' with the user having a setting wrong. Fortunately, I wasn't too proud to ask for help and post screenshots of my setups, you obviously are for some reason. Anyhow, enjoy the hobby, after all it's your cash, so spend it as you deem fit...
@sirtrumpington4779 I literally have video proof that I have the "fixed" fw's installed and that my failsafe settings are set correctly and you're still trying to blame it on me?
You get that you're basically calling me stupid, right? And then you have the nerve to tone police me? GTFO with that.
Sorry buddy, but I was genuinely trying to help. I'm not saying you're an idiot, just that I had a few brain farts at first thinking I was doing everything by the book. And regarding your 'tone' and 'gtfo' statements...your reply to my first post set the tone, so don't play the martyr here. As I said above, maybe you simply don't have the patience to try and remedy the problem...anyhow, I'm done here, you seem to be fairly stubborn about you can't have a setting wrong or memic type problem with your hardware...no harm no foul, on my part the intention was purely honourable in trying to help somehow...👍
Question and I'm not being a douchebag.... Why do you need such an elaborate radio system? Just get yourself a regular 2.4 like a spectrum or something like that and your problems will all be solved...🤔
I don't. After using this thing for 6 months I couldn't find anything it could do that made dealing with the frustrating UI worth it.
Honestly I've been thinking about doing a fun video showing how much work it takes to do simple things compared to my NB4+.
Lots of people have this issue, bin it😂