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)
-   -   Recent castle link software vs Mamba max issue (https://www.rc-monster.com/forum/showthread.php?t=29932)

Mister-T 05.02.2011 01:13 PM

Recent castle link software vs Mamba max issue
 
Hello,
I would like to tell you some issue that may happen with people there old mamba max with the last version of castle link (old enought so they have the old software that require direct USB connection).

To make long story short, I managed to solve the problem myself but I prefer to warn or ,at least, give a possible solution if people run in the same issue as me.

I own 4 CC product and decided to update all my ESC to the last software today.

1 mamba max pro via castle link ---> NO issue
1 mamba Monster V2 (still working :D ) ---> NO issue
2 mamba max ---> problems ...

1 mamba max date back MAY 2007 (updated to fw 1.21) while the other date back from 2009 (fw 1.17)

In both case I run into the same issue.

When I plugged them via castle link, it didn't work, connection couldn't be made as the software didn't support it. My bad ;)
So I direct connect it on USB .

In both case on my main PC (win 7), I heard the usb connection sound but driver couldn't be found an the ESC remain blank, no LED. I did the control panel / reinstall /update driver but windows couldn't find the file

epic fail ...

A reinstall as admin / reboot / run as administrator didn't fix the problem. I tried 3 different USB port, including one from self supplied hub --> fail


So I used my laptop. Under Win vista.
A old version of CC link was installed, both mamba max were detected and running ... closed apps but
I did kept the mamba max plug in (red and green led on) while updating soft to 3.30.3 !
While running the last software, esc is detected but I hear the plug sound of windows.
The esc just did shutdown !
Unpluged/pluged back , Ok led coming back, the software freeze for 4 second I've got a message about incorrect auto lipo setting, click ok,
then the application open a windows about the new firmware availability.

Let's go time for the update.

I see the led blinking
'phase 1' ok,
'waiting for the controller' then
"clink clong USB disconnect sound"
ESC SHUTDOWN
"clink clong USB connect sound" (I didn't touch anything)
LED Coming back
Phase 2 writing OK
Succesfull !
Then the "reading parameter" windows appear but the whole software is frozen
I right click on the CC link in task bar to close it.
A error message about USB connectivity issue and asking to unplug the device wait 30 sec then plug it back.

Even after the firmware update, the esc still on/off when trying to change parameter and upgrade the firmware via USB.

I tried to plug the ESC via castle link interface, everything is OK and smooth running.

It's maybe my computer (connect and detect driver file missing on my main PC ?) but still it looks like that direct USB connectivity as some reliability issue with recent version of castle link software.


EDIT

I did a test again, basically overwriting the last firmware, using onboard MM usb slot and last software on my laptop.
The update work (same pattern as above) but the esc shutdown afterward and software still freeze. Unplugin/plugin usb restart the esc and unfreeze the software as well.
This behaviour does not appear while using castle link interface.

Pdelcast 05.02.2011 01:26 PM

Quote:

Originally Posted by Mister-T (Post 405661)
Hello,
I would like to tell you some issue that may happen with people there old mamba max with the last version of castle link (old enought so they have the old software that require direct USB connection).

To make long story short I managed to solve the problem myself but i prefer to warn or at least give a possible solution if people run it the same issue as me.

I own 4 CC product and decided to update all my ESC to the last software today.

1 mamba max pro via castle link ---> NO issue
1 mamba Monster V2 (still working :D ) ---> NO issue
2 mamba max ---> problems ...

1 mamba max date back MAY 2007 (updated to fw 1.21) while the other date back from 2009 (fw 1.17)

In both case I run into the same issue.

When I plugged them via castle link, it didn't work, connection couldn't be made as the software didn't support it. My bad ;)
So I direct connect it on USB .

In both case on my main PC (win 7), I heard the usb connection sound but driver couldn't be found an the ESC remain blank, no LED. I did the control panel / reinstall /update driver but windows couldn't find the file

epic fail ...

A reinstall as admin / reboot / run as administrator didn't fix the problem. I tried 3 different USB port, including one from self supplied hub --> fail


So I used my laptop. Under Win vista.
A old version of CC link was installed, both mamba max were detected and running ... closed apps but
I did kept the mamba max plug in (red and green led on) while updating soft to 3.30.3 !
While running the last software, esc is detected but I hear the plug sound of windows. The esc just did shutdown WTF.
Unpluged/pluged back , Ok led coming back, the software freeze for 4 second I've got a message about incorrect auto lipo setting, click ok, then the apps open the windows about a the new firmware.
Let's go time for the update.

I see the led blinking
'phase 1' ok the,
'waiting for the controller' then
"clink clong USB disconnect sound"
ESC SHUTDOWN
"clink clong USB connect sound" (I didn't touch anything)
LED Coming back
Phase 2 writing OK
Succesful !
Then the reading parameter windows appear but the whole software is frozen
I right click on the CC link in task bar to close it
A error message about USB connectivity issue and asking to unplug the device wait 30 sec then plug it back.

Even after the firmware update, the esc still on/off when tring to change parameter and upgrade the firmware via USB.

I tried to plug the ESC via castle link interface, everything is OK and smooth running.

It's maybe my computer (connect detect driver file) but still it looks like that direct USB connectivity as some reliability issue with recent version of castle link software.

Mr T -- I sent a link of this thread to our service guys. I'm sure one of them might be able to assist.

Thanx!

Patrick

Thomas Porfert 05.02.2011 01:50 PM

Mr. T,

It sounds like you're having issues with the Mamba Max USB driver on 64-bit computers. Unfortunately we do not have a driver for the Mamba Max that is compatible with 64 bit operating systems; so the side USB port is basically useless. The only solution is to use the Castle Link adapter that hooks to the receiver wire on the ESC.

If you have the older firmware on the controller, you will need to update the firmware on the ESC to a newer version of firmware. The older firmware did not support the Castle Link adapter because it had the side USB port. When we found the side USB driver didn't work on 64 bit, the engineers reprogrammed the Mamba Max to work with the adapter, but you have to update the firmware to enable the feature. Basically you need to hook up the Mamba Max to a 32 bit machine (your laptop with Vista 32 bit) through the side USB and update the controller just one time. Once the controller has been updated, you can then use the Castle Link adapter on the Mamba Max when using a 64 bit operating system.

Please let me know if you have any questions or concerns.

Thomas Porfert
Tech Support
Castle Creations

Mister-T 05.02.2011 02:36 PM

Thanks for the reply and help.

dtnel 05.06.2011 01:53 AM

I had the freeze up on 3.30.3 while updating my 2 mmp motors I bought last year using the link system. I was able to continually manipulate the freeze. I called castle and informed them. This was the first time I had updated these escs since I had initially bought them around a year ago. This all happened the day after I download and installed the 3.30.3 version on a windows 7 starter edition ASUS Netbook. I'm runing 2gb of memory so I dont think memory caused the freeze. I had even rebooted the Netbook several times thinking it was it and it wasn't I was able however to sucessfully write the software to the escs. I remember it had someting to do with trying to load one setting vs another.

dtnel 05.07.2011 02:53 AM

Newer problems yesterday. I went and tried to run both of my mmp escs that are located on 2 different slash 4x4s. I made sure my radio was linked to each rx on each truck. BEING that each truck had the esc software updated I proceeded to calibrated the esc on each vehicle before use. Each vehicles esc would power on but when the trigger on the tx was depressed to start the programming process and no response was indicated by the response from the esc lights. I did have a mmm esc that was able to be programmed per castle guidelines in the drivers rd guide. Any help in why this would be happening would be appreciated. Thanks ! !

DrKnow65 05.07.2011 09:57 AM

Updated my Castle link software last night (Dell M4400, W7 64bit, SSD, 8GB ram) and had it lock then blue screen the computer... Auto dumped data, restarted and worked fine.
Then I tried to update settings to my MMM, no joy. So I figured I'd go ahead and update the MMM's firmware, worked fine. Now I can change settings and all is well.

I've updated both my MMP's, my Phoenix ICE HV, and my MMXL as well. All happy with the latest firmware and latest Castle link software.... I think the trick is a restart after installing the Castle link, then updating the firmware BEFORE trying to manipulate any ESC settings.

dtnel 05.07.2011 03:10 PM

Quote:

Originally Posted by DrKnow65 (Post 405961)
Updated my Castle link software last night (Dell M4400, W7 64bit, SSD, 8GB ram) and had it lock then blue screen the computer... Auto dumped data, restarted and worked fine.
Then I tried to update settings to my MMM, no joy. So I figured I'd go ahead and update the MMM's firmware, worked fine. Now I can change settings and all is well.

I've updated both my MMP's, my Phoenix ICE HV, and my MMXL as well. All happy with the latest firmware and latest Castle link software.... I think the trick is a restart after installing the Castle link, then updating the firmware BEFORE trying to manipulate any ESC settings.

The restart has been done. Even once the day I had a castle tech on the phone and had to turn the computer on and wait for it to boot. This was the morning after I had encountered these errors. I'l be hooking them up to my main, not netbook pc and going through the ropes on that this afternoon as well. I hope it goes well because the weather is nice and I slept al morning which isn't good. We'l se what the day brings................:smile:


All times are GMT -4. The time now is 07:59 PM.

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