I've just received a new MMM ESC from CC.
But the new ESC is acting very strange.
10-20 percent of fwd and reverse throttle range the motor has a lot of lag (cogging). Passing the 10-20 percent the motor is working fine.
I had tried:
Other tx and rx > no luck.
Recalibrate the ESC > no luck.
Other lipos > no luck.
Othe motor > no luck.
It's the firmware- this problem affects many people and is covered alot- can we get a sticky please ( "Having throttle issues with your Castle Esc? Read this first.." )?
You need to check which version is loaded onto the esc ( under the software tab in the castlelink program ), then try upgrading or downgrading it. Anything newer than v1.24 can cause cogging with many MMM escs, so downgrade to that version and try each new one to see if it is also stable or not.
This is something that the engineers are starting to look into. The problem seems to be fairly random, but specific to the Mamba Monster. I agree with Neil, we need to start a thread about this issue and make it a sticky. The engineers need to see the problem occur, so I am working on getting them a setup that shows the problem. I am thinking it may be specific to a version of the Monster, but I was hoping to get some feedback from you guys and see if I can find a common element. We are now actively working on this issue, and I will keep everyone informed as to the progress. Please check the top of the forum for a sticky on this issue. Thanks!
Thanks I will send it back.
Then you can test it:-).
No need to send it back, I believe we already have one that is affected from a customer that stopped by the office last week. I'm going to try putting it in one of my setups this weekend and see if I can recreate the problem. When we do fix the problem, it will just be a firmware update; so for now just run V1.24 until we release a fix.
I've just called my brother.
Hmm he has already sended the MMM ESC back to CC hahaha.
O well i will wait, luckely I have still the V3 ESC:-).
I am curious for the soultion.
I've just called my brother.
Hmm he has already sended the MMM ESC back to CC hahaha.
O well i will wait, luckely I have still the V3 ESC:-).
I am curious for the soultion.
You dont pay much attention to what people actually tell you, do you- read my post again:
Quote:
You need to check which version is loaded onto the esc ( under the software tab in the castlelink program ), then try upgrading or downgrading it.Anything newer than v1.24 can cause cogging with many MMM escs, so downgrade to that version and try each new one to see if it is also stable or not.
All you had to do was try an earlier firmwear version and I guarantee it would have fixed the problem.
I upgraded my Sidewinder SCT last night and had a problem with it. It didn't really cog though it just would cut out for a second like the rx lost power then come back on just fine. It was always about 1/4 throttle. I backed the firmware up to the last non beta version which I beleive was the first version and it worked just fine after.
You dont pay much attention to what people actually tell you, do you- read my post again:
Yes I did, but I was at not home when started this topic.
I was curious what the problem could be
O well thanks anyway for your help guys.
I've lost some shippingcosts, but the ESC is in goods hands when arrived
I have two that are v3s (I believe?), one demonstrated the issue and the other didn't (actually you guys should have the one that didn't as I sent it in for repair work). How can we tell which version is which and is their minor revisions within a version?
Quote:
Originally Posted by Thomas Porfert
This is something that the engineers are starting to look into. The problem seems to be fairly random, but specific to the Mamba Monster. I agree with Neil, we need to start a thread about this issue and make it a sticky. The engineers need to see the problem occur, so I am working on getting them a setup that shows the problem. I am thinking it may be specific to a version of the Monster, but I was hoping to get some feedback from you guys and see if I can find a common element. We are now actively working on this issue, and I will keep everyone informed as to the progress. Please check the top of the forum for a sticky on this issue. Thanks!
There is no 'problem'- read the previous posts. Certain revisions of the castle esc don't react well to certain firmware updates due to different hardware being used inside the esc wiht each revision.
If you try a version of firmware which causes the esc to behave strangely ( like low throttle stuttering for example ), then try a different version of firmware until the 'problem' stops = problem solved. There is nothing wrong with the esc, and nothing wrong with most of the firmware version as such- it's just an unfortunate coincidence that firmware and hardware don't always play nicely together.
Quote:
Originally Posted by thzero
Thomas,
I have two that are v3s (I believe?), one demonstrated the issue and the other didn't (actually you guys should have the one that didn't as I sent it in for repair work). How can we tell which version is which and is their minor revisions within a version?