RC-Monster Forums

RC-Monster Forums (https://www.rc-monster.com/forum/index.php)
-   Castle Creations (https://www.rc-monster.com/forum/forumdisplay.php?f=34)
-   -   New Mamba software (beta) posted today (https://www.rc-monster.com/forum/showthread.php?t=27583)

ravin 08.26.2010 08:57 PM

Quote:

Originally Posted by molak (Post 377642)
I think that the difference is in the castle link software and not in the firmware..

Castle link 3.255 may show you the KV..

How do I go back to 3.255?

Lucariel 08.27.2010 08:59 AM

Quote:

Originally Posted by kostaktinos_mt (Post 377523)
ok, here is my issue:

1.29 doesnt run at all. mamba max starts fine, beeps and all, then a red led flashes rapidly. no throttle response, no extra beeps, no nothing.

i flashed back to 1.28, problem solved.
flashed again to 1.29, same thing again. reloaded the settings, nothing changed. default settings, nothing changed. i pretty much tried everything.
1.28 works fine [other than the random startup hesitations], but 1.29 refuses to work.

any ideas?

same probrem...

new feature signal the over voltage in the esc..
is possible remove this

I use the sidewinder in the my 1/16 e-revo in 4s configuration....
:whip::whip::whip: is possible remove this :whip::whip::whip:

why this version not show the KV motor?

sorry for my bad english...
tanks in advance Luca

suicideneil 08.28.2010 11:53 AM

Over voltage detection feature is to prevent people from blowing up their escs by using them outside of specification. :rules:

The kv detection feature was removed to stop people from phoning up asking why their 2200kv neu motor was being reported as a 4400kv motor; the feature is designed for 2 pole motors, the user has to do the math based on how many poles their motor actually has = lots of stuid people didnt understand this and kept phoning up castlecreations to ask for help. No more kv feature = no more phone calls. The kv should be on the motor/ label anyway. :rules:

Roll the firmware back to an earlier version if you dont like the current features. :neutral:

scooterboy 09.08.2010 03:34 PM

How are people getting on with the torque control as opposed to punch control? I'm still using 70% punch to reduce wheelspin but don't like the time lag effect it gives and am hesitant about trying torque control as i wont be able to adjust it at the track.

scooterboy 09.14.2010 04:13 PM

Is no one using torque control?:whistle:

Freezebyte 09.14.2010 05:06 PM

Quote:

Originally Posted by scooterboy (Post 380154)
Is no one using torque control?:whistle:

For those of use who have the Blur version of the MMM, HPI has not allowed Castle to release the newest firmware with that feature yet.

SpEEdyBL 09.20.2010 04:33 AM

1.29 Feedback:

Firmware does not work with 6s and the Tekin 1400kv motor w/o the sensors. (haven't tried the sensors yet.) Even with torque control disabled, the motor will have no torque and spin at about one rotation per second, even at full throttle. Another person had the same problem with 4s using the Tekin 2050 also without the sensors. In my case I am able to run the 1400 with 4s with an occasional glitch (delay in throttle followed by a sudden burst of power). No issues running the 1400 on just 2s :lol:.

I've installed and reinstalled V1.29 three times with the same result. Esc is the MMP.

bryan 09.20.2010 01:39 PM

Quote:

Originally Posted by SpEEdyBL (Post 380782)
1.29 Feedback:

Firmware does not work with 6s and the Tekin 1400kv motor w/o the sensors. (haven't tried the sensors yet.) Even with torque control disabled, the motor will have no torque and spin at about one rotation per second, even at full throttle. Another person had the same problem with 4s using the Tekin 2050 also without the sensors. In my case I am able to run the 1400 with 4s with an occasional glitch (delay in throttle followed by a sudden burst of power). No issues running the 1400 on just 2s :lol:.

I've installed and reinstalled V1.29 three times with the same result. Esc is the MMP.

I had the same problem with my MMP/TEKIN 1700kv sensorless. Its smooth as silk running sensored now. On the other hand i have 2 MMM that i upgraded the firmware on have that problem also. I also have two other MMM that i didnt upgrade the firmware and they are fine.

Arct1k 09.20.2010 02:42 PM

Quote:

Originally Posted by Freezebyte (Post 380159)
For those of use who have the Blur version of the MMM, HPI has not allowed Castle to release the newest firmware with that feature yet.

I don't have a flux etc to test it on but pretty sure that would take me about 5 mins to change if you were interested... :whistle:

V0RT3X 09.20.2010 02:51 PM

Is it a Castle Link registry mod or do you need the ESC to do the mod on?

thzero 09.20.2010 02:52 PM

Quote:

Originally Posted by V0RT3X (Post 380824)
Is it a Castle Link registry mod or do you need the ESC to do the mod on?

Probably just a db update.

Arct1k 09.20.2010 03:10 PM

Changed it to a 5 min update but it would be all done on your PC - I'm NOT going to post it up though unless I get an OK wink from the castle guys...

They always do good by me and I don't want to upset them or anything they have with HPI or Axial.

suicideneil 09.20.2010 09:21 PM

We've bought them enough pizza....

:lol:

Arct1k 09.20.2010 09:30 PM

Haha I've sent more since then Neil :)

They'll get another batch soon when the next project is completed for sure... I owe Lee, Thomas and Patrick big time...

thzero 09.20.2010 10:05 PM

OH yeah, totally a small db mod. :)


All times are GMT -4. The time now is 06:05 PM.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, vBulletin Solutions Inc.