• Welcome to RCCrawler Forums.

    It looks like you're enjoying RCCrawler's Forums but haven't created an account yet. Why not take a minute to register for your own free account now? As a member you get free access to all of our forums and posts plus the ability to post your own messages, communicate directly with other members, and much more. Register now!

    Already a member? Login at the top of this page to stop seeing this message.

Mamba Firmware V2.02

Who uses the switch?
First thing I do when I get an ESC is cut the switch and solder the wires together. :ror:


My son and I took our Bombers out this weekend to test the new firmware. Very nice control and the switching to Crawler mode was slick. But the noise is too much. We'll be going back on the firmware. When we were on the trail, the noise is not an issue, when we got to the rocks and were sessioning them together, the noise was distracting. Also, I have a backyard course that I love to get off work, crack open a cold-one and take the RCs on the course. The Bomber with the new firmware is too loud for the quiet "unwind-time" I look for on while on the backyard course.


If I recall, the noise is comes from the switching frequency to the motor. Isn't that the reason behind being able to change the switching frequency in the Holmes BLE Pro?
 
That's awesome.. a month old speed controller already losing the switch.. I figured castle would have figured out their switches suck by now and done something about it..

Sent from my iPhone using Tapatalk

We have had a much lower rate of failure on these new switches compared to our old, but we buy the switches from another manufacture and it's hard to enforce quality on something we don't have control of. I was helping in production last week building Sidewinder SV3's and there was a huge failure rate on the latest batch of our old switch, so they had me running 100% preliminary QC on every switch before it assembled into the product. I was getting a 30% failure rate, but normally the failure rate for switches we receive is less than 0.1%. Just part of the process we don't have good control over, but we try to do as best as we can to catch them before they leave our facility. Every product with a switch is run through 2 tests and the switch is supposed to be tested at both steps.

Call up sales and support and I'm sure they can probably replace the wire harness for you and get you a new switch.

The good news is it failed in the on state rather than the off state.
 
We have had a much lower rate of failure on these new switches compared to our old, but we buy the switches from another manufacture and it's hard to enforce quality on something we don't have control of. I was helping in production last week building Sidewinder SV3's and there was a huge failure rate on the latest batch of our old switch, so they had me running 100% preliminary QC on every switch before it assembled into the product. I was getting a 30% failure rate, but normally the failure rate for switches we receive is less than 0.1%. Just part of the process we don't have good control over, but we try to do as best as we can to catch them before they leave our facility. Every product with a switch is run through 2 tests and the switch is supposed to be tested at both steps.

Call up sales and support and I'm sure they can probably replace the wire harness for you and get you a new switch.

The good news is it failed in the on state rather than the off state.



No doubt the pre shipment tests are done, because I have never received an esc with an issue. My switch failures always seem to happen down the road.. never this quick. I'm going to bypass the switch anyway.. not a huge deal to me but I'm sure frustrating for those that prefer the switch


Sent from my iPhone using Tapatalk
 
Who uses the switch?
First thing I do when I get an ESC is cut the switch and solder the wires together. :ror:


My son and I took our Bombers out this weekend to test the new firmware. Very nice control and the switching to Crawler mode was slick. But the noise is too much. We'll be going back on the firmware. When we were on the trail, the noise is not an issue, when we got to the rocks and were sessioning them together, the noise was distracting. Also, I have a backyard course that I love to get off work, crack open a cold-one and take the RCs on the course. The Bomber with the new firmware is too loud for the quiet "unwind-time" I look for on while on the backyard course.


If I recall, the noise is comes from the switching frequency to the motor. Isn't that the reason behind being able to change the switching frequency in the Holmes BLE Pro?

It does come from the switching frequency of the motor. I don't know that the new firmware is technically any louder than the old firmware, but it is more noticeable because it is using a dynamic frequency with high speed modulation in order to increase resolution of the throttle and to reduce the minimum RPM the motor can run at.
 
Here's an idea Castle, like the MMP 1 cell controller, no switch. People really should be unplugging the battery anyways. Then it's a non issue and less bitching on the Internet from lazies but possibly more bitching from lazies because they're gonna bitch about no switch.

From a business standpoint, I'd favor no switch and let them complain.
 
I recently got a Mamba Monster X, the new waterproofed one. Lasted all of 5 minutes of running in the snow, got back inside to turn off and ESC/switch started glitching. Got really worried I destroyed my brand new ESC until I saw that it was such a common issue. Just cut off switch and soldered the leads, no issues since.

On another note, everytime I start up the esc it goes through the typical ESC chime but right after it finishes the startup it lets out one loud long beep with all LEDS lit. After the long single chime it just goes to normal operation. Does anyone know what it means? Can't find anything in the manual.
 
I recently got a Mamba Monster X, the new waterproofed one. Lasted all of 5 minutes of running in the snow, got back inside to turn off and ESC/switch started glitching. Got really worried I destroyed my brand new ESC until I saw that it was such a common issue. Just cut off switch and soldered the leads, no issues since.

On another note, everytime I start up the esc it goes through the typical ESC chime but right after it finishes the startup it lets out one loud long beep with all LEDS lit. After the long single chime it just goes to normal operation. Does anyone know what it means? Can't find anything in the manual.

What radio and receiver are you using? I had a similar issue with a spectrum radio system and a avc receiver. The receiver was not coming online quick enough and the esc was faulting out because it was not receiving a signal. I switched back to using my Futaba 4pls and no more issues.. just another reason I can't stand spectrum products
 
What radio and receiver are you using? I had a similar issue with a spectrum radio system and a avc receiver. The receiver was not coming online quick enough and the esc was faulting out because it was not receiving a signal. I switched back to using my Futaba 4pls and no more issues.. just another reason I can't stand spectrum products

I found that exact issue with our AVC receiver during our sensored motor testing. 2.02 resolves that issue by clearing the error code once the controller fully arms.
 
Yes, I am using the AVC receiver that came in the Losi Rock Rey, might switch it out for a standard spektrum 4 channel receiver to work with my DX4C (need the 4 channels for a future winch and AUX cable for the castle system). I know for me after the update to 2.02 I still get the error but as before it clears up after the first beep and functions normally (looks like as stated by Robert, the ESC clears it up as intented). Other than being annoying not sure if I really need to change out my radio system.

Thanks everyone for the help, I appreciate it!
 
I found that exact issue with our AVC receiver during our sensored motor testing. 2.02 resolves that issue by clearing the error code once the controller fully arms.

Mine was acting up so bad that the esc would not arm.. it would hard fault.. not every time, 7 out of 10 times it would boot up like normal, the other 3 times it would fault and the esc had to be power cycled. Glad 2.02 fixed the issue, but I'm sticking to my futaba radio. Much better imo
 
Mine was acting up so bad that the esc would not arm.. it would hard fault.. not every time, 7 out of 10 times it would boot up like normal, the other 3 times it would fault and the esc had to be power cycled. Glad 2.02 fixed the issue, but I'm sticking to my futaba radio. Much better imo

I tend to agree. I like the options more on the Futaba radios and they just feel better built to me. Admittedly the best Spektrum I have used is a DX4C and I'm used to the feel of my personal radio which is a 4PKSR, but even the cheap Axial Tactic radio feels more solid than a DX4C.
 
Having a switch makes it easier to clear memory or access setting with the transmitter. It can be difficult to plug in a battery and hold the throttle in a certain position but having a switch makes it easy
 
Well I got my monster x in and installed in the bomber, programmed both escs to the rock racer/crawler modes.. really handy to have my 3 position switch controlling it. I have mine set to pos1 0% drag/fbr than pos2 is 50% drag/crawler reverse and pos3 is 100% drag/crawler reverse.

Now I will say the noise this 2.02 makes is annoying as hell. Wasn't extremely noticeable in my 10.2 with the 1:10 X and a roc412, but my bomber with the monster x and HH 3500kv 540xl is a lot worse. I sure hope castle finds a way to quiet this down.

Also my monster x does the arming chime/cell count, than about 1 second later makes one loud single beep with all the lights coming on, than arms like normal. My 1:10 X does not do this.
 
Now I will say the noise this 2.02 makes is annoying as hell. Wasn't extremely noticeable in my 10.2 with the 1:10 X and a roc412, but my bomber with the monster x and HH 3500kv 540xl is a lot worse. I sure hope castle finds a way to quiet this down.

The noise is an unfortunate side effect of the improved drag brake. There are a few more changes that incresse the amplitude as well. A higher drag brake %, certain motosr, heavier vehicle and driving on an incline lead to a more audible noise. Quieting the noise may impact the improvements to low speed throttle response and drag brake; but it is certainly worth attempting.

On another note, everytime I start up the esc it goes through the typical ESC chime but right after it finishes the startup it lets out one loud long beep with all LEDS lit. After the long single chime it just goes to normal operation. Does anyone know what it means? Can't find anything in the manual.

Also my monster x does the arming chime/cell count, than about 1 second later makes one loud single beep with all the lights coming on, than arms like normal. My 1:10 X does not do this.

The long beep after the arming tones is the ESC letting you know it cleared the data logs. So I'm assuming you have the "Automatic Data Reset" function activated. If it's set to "0% (Disabled) it will do that on each startup. "thumbsup"

Thomas Porfert
Tech Support
Castle Creations
 
Last edited:
It sure is nice to have Robert and now Thomas on RCC. Thanks for joining and answering everyones questions! "thumbsup"
 
The noise is an unfortunate side effect of the improved drag brake. There are a few more changes that incresse the amplitude as well. A higher drag brake %, certain motosr, heavier vehicle and driving on an incline lead to a more audible noise. Quieting the noise may impact the improvements to low speed throttle response and drag brake; but it is certainly worth attempting.




Thomas Porfert
Tech Support
Castle Creations


Now if only I could get the high voltage lockout turned off on the microX;-)
 
We have had a much lower rate of failure on these new switches compared to our old, but we buy the switches from another manufacture and it's hard to enforce quality on something we don't have control of. I was helping in production last week building Sidewinder SV3's and there was a huge failure rate on the latest batch of our old switch, so they had me running 100% preliminary QC on every switch before it assembled into the product. I was getting a 30% failure rate, but normally the failure rate for switches we receive is less than 0.1%. Just part of the process we don't have good control over, but we try to do as best as we can to catch them before they leave our facility. Every product with a switch is run through 2 tests and the switch is supposed to be tested at both steps.

Call up sales and support and I'm sure they can probably replace the wire harness for you and get you a new switch.

The good news is it failed in the on state rather than the off state.



My switch failed last night when it got wet, it worked at first this morning at first start up. Would run it for about30 sec and it would just shut off then do all the power up sounds it did this 3 timeso in a row, it would just shut off and then reboot. Any one else have this problem
 
So I ended up getting the Mamba X and will be using it with a HH3500KV Puller Pro.

Reading all the comments about the sound issue, not sure it will affect me but I need some help in setting up my Futaba 4PL to change the mode?
I kinda understand how Rock Race/Crawler mode works but does anyone here have a 4PL that I can share some settings with?

Thanks in advance. I havent updated to the new firmware yet as I want to fully understand
 
Back
Top