NEW HOBBYWING STOCK SUPERCHARGED SOFTWARE
For those having problems, try knocking the update back of the Program box back to the v1.1 (I think). Don't use the latest version. Seem to have some issues with that, but updates worked fine on the other version.
I'll check what version numbers I'm running on what tonight, and post back up on here.
I'll check what version numbers I'm running on what tonight, and post back up on here.
For those having problems, try knocking the update back of the Program box back to the v1.1 (I think). Don't use the latest version. Seem to have some issues with that, but updates worked fine on the other version.
I'll check what version numbers I'm running on what tonight, and post back up on here.
I'll check what version numbers I'm running on what tonight, and post back up on here.
Tech Apprentice
iTrader: (2)
Joined: Mar 2014
Posts: 85
I develop hardware and software for embedded systems for a living and this is basically what happens when the device is "bricked". It happens when a poorly written bootloader or update mechanism is implemented that allows a failed update to cause an unresponsive state. This is very preventable via well written firmware. Reloading the firmware for the ESC via JTAG would surely bring the ESC back to life.
It makes me a little sad when this stuff happens because I know it is preventable.
Exactly what is going on with me. The programmer just cant connect to the ESC. This makes it so you cant change any settings via the programming box or the USB Link software. It also makes it so that you cant update the firmware on the ESC.
I develop hardware and software for embedded systems for a living and this is basically what happens when the device is "bricked". It happens when a poorly written bootloader or update mechanism is implemented that allows a failed update to cause an unresponsive state. This is very preventable via well written firmware. Reloading the firmware for the ESC via JTAG would surely bring the ESC back to life.
It makes me a little sad when this stuff happens because I know it is preventable.
I develop hardware and software for embedded systems for a living and this is basically what happens when the device is "bricked". It happens when a poorly written bootloader or update mechanism is implemented that allows a failed update to cause an unresponsive state. This is very preventable via well written firmware. Reloading the firmware for the ESC via JTAG would surely bring the ESC back to life.
It makes me a little sad when this stuff happens because I know it is preventable.
Im in the process of doing a video and will post online .
Joined: Aug 2008
Posts: 2,388
From: Medina, Ohio
I did find a copy on line. 3.43 actually seemed to corrupt 3.42 and it would not communicate either. I went to another computer that had 3.42 and no problems. I removed all versions of 3.* and installed a fresh copy of 3.42 that I found online. All appears to be good right now, I just won't update to 3.43 in the near future.
I did find a copy on line. 3.43 actually seemed to corrupt 3.42 and it would not communicate either. I went to another computer that had 3.42 and no problems. I removed all versions of 3.* and installed a fresh copy of 3.42 that I found online. All appears to be good right now, I just won't update to 3.43 in the near future.
Tech Apprentice
iTrader: (2)
Joined: Mar 2014
Posts: 85
The problem is that when the update fails for whatever reason, the ESC is left in an unresponsive state. In my case, when the update failed, nothing out of the ordinary happened. No power glitches, no computer problems, no connection problems. I had just exported the settings from my ESC to the computer so everything was working perfectly. After exporting settings, I attempted to update the ESC firmware and it failed for some unknown reason. This sounds like the case for some of the the other members here as well.
Even after this gets resolved (still waiting on my RMA request) I am going to be a little worried about updating firmware in the future unless Hobbywing acknowledges that there was a problem and they fixed it.
Angelo, thanks for testing. I am sure that 99% of the time, everything goes fine. Have you ever had a failed ESC firmware update? If so, what happened?
The problem is that when the update fails for whatever reason, the ESC is left in an unresponsive state. In my case, when the update failed, nothing out of the ordinary happened. No power glitches, no computer problems, no connection problems. I had just exported the settings from my ESC to the computer so everything was working perfectly. After exporting settings, I attempted to update the ESC firmware and it failed for some unknown reason. This sounds like the case for some of the the other members here as well.
Even after this gets resolved (still waiting on my RMA request) I am going to be a little worried about updating firmware in the future unless Hobbywing acknowledges that there was a problem and they fixed it.
The problem is that when the update fails for whatever reason, the ESC is left in an unresponsive state. In my case, when the update failed, nothing out of the ordinary happened. No power glitches, no computer problems, no connection problems. I had just exported the settings from my ESC to the computer so everything was working perfectly. After exporting settings, I attempted to update the ESC firmware and it failed for some unknown reason. This sounds like the case for some of the the other members here as well.
Even after this gets resolved (still waiting on my RMA request) I am going to be a little worried about updating firmware in the future unless Hobbywing acknowledges that there was a problem and they fixed it.
Tech Rookie
Joined: Aug 2014
Posts: 4
The other night I attempted to update the firmware with the latest USB software.
Successful firmware update on my new Multifunction LCD Program box. As for my Hobbywing Stock V3.1 ESC, the update failed -- received a communication error. Once that happened my ESC will no longer work. Seems to power up fine but no power to the motor and no longer make a connection to the LCD Program box -- also will not calibrate to my radio. It simply won't work now.
I have two of these and I fear it may happen again when updating the firmware in the future. Anyone know what to do if this happens again?
Successful firmware update on my new Multifunction LCD Program box. As for my Hobbywing Stock V3.1 ESC, the update failed -- received a communication error. Once that happened my ESC will no longer work. Seems to power up fine but no power to the motor and no longer make a connection to the LCD Program box -- also will not calibrate to my radio. It simply won't work now.
I have two of these and I fear it may happen again when updating the firmware in the future. Anyone know what to do if this happens again?
Joined: Aug 2008
Posts: 2,388
From: Medina, Ohio
What happened was I ran the update to 3.43. It would not communicate with the programmer or esc. I then tried to use 3.42 and it would not communicate either. I removed 3.43 hoping that would fix 3.42 but it did not. I used another computer with 3.42 and everything is fine there. My next test is to go back to the first computer where I removed all versions of 3 series software and installed 3.42 from a jump drive. I wont get to test that until later today. Just for info the computer having the problem is a XP machine.
I have updated 3 HW v3.1 to the latest version, 3.43, with no issues. I removed all other HW software installed 3.43 and updated, win7



4Likes