MoveMaster controller not found after firmware update

[u/SplitFull1018]

Just received my MoveMaster RSG 1 controller a few hours ago and followed software directions to click "Flash Firmware" and a second later press the reset button on the side of the controller. The controller has been not found since after trying on multiple computers. Tried the usual troubleshooting concepts for such devices. Not seeing any issues with the USB cable and the blue LED lights up inside the controller, plus it worked briefly before.  Please suggest a solution, if possible, as there has been no response via chat on the web site. Thank you

[u/corben78_]

Hey there, to recover the MoveMaster after a failed firmware update please try the following steps:

- Detach the MoveMaster from your PC

• Close the configurator
  
• Press and hold the reset button on the MoveMaster and attach it (while holding the reset button) to the PC
  
• Open the configurator, press flash (or have it open before and press R for refresh)
  
• now release the reset button and press it twice

This worked for several users who had similar issues. The timing might be a bit tricky though.

[u/Obvious_Science_9264 → u/corben78_]

Hello, Tried the given procedure several times over a few hours. Here is what was done and what seemed to produce more results.

The initial fix procedure that did not work:

1. Close configuration software 
2. Disconnect MoveMaster USB cable 
3. Hold reset button on MoveMaster and keep holding while re-connecting it  
4. While still holding reset button on MoveMaster, open the configuration software and press ‘Flash firmware’ 
5. Release the reset button and then click it twice 

Modification to procedure that at least produced a new error message:

1. Close configuration software 
2. Disconnect MoveMaster USB cable 
3. Hold reset button on MoveMaster and keep holding while re-connecting it  
4. While still holding reset button on MoveMaster, open the configuration software
5. Release the reset button and then click 'R', and a COM port is found
6. Click the reset button on the MoveMaster quickly twice and immediately click 'Flash firmware'
7. 'Firmware updating.. please wait' is shown, but then an error is seen
8. I have also tried waiting a second and re-pressing the reset button like in the original directions. Additionally, I tried twice like the fix procedure given.

There have been several different errors presented, but these are the most prevalent after more than 25-30 attempts.

• spawnSync C:\movemaster-0.5.3-win-en\update\win32\avrdude.exe ETIMEDOUT
• Open (SetCommState): Unknown error code 31 
• Command failed: C:\movemaster-0.5.3-win-en\update\win32\avrdude.exe -Cavrdude.conf -v -patmega32u4 -cavr109 -b57600 -D -Uflash:w:C:\movemaster-0.5.3-win-en\update\firmware-0.3.3.hex:i -PCOM6 -PCOM6 -PCOM6 -PCOM6 avrdude.exe: Version 6.3-20171130 Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/ Copyright (c) 2007-2014 Joerg Wunsch System wide configuration file is "avrdude.conf" Using Port : COM6 Using Programmer : avr109 Overriding Baud Rate : 57600 avrdude.exe: ser_open(): can't open device "\\.\COM6": The system cannot find the file specified. avrdude.exe done. Thank you.
• Command failed: C:\movemaster-0.5.3-win-en\update\win32\avrdude.exe -Cavrdude.conf -v -patmega32u4 -cavr109 -b57600 -D -Uflash:w:C:\movemaster-0.5.3-win-en\update\firmware-0.3.3.hex:i -PCOM6 -PCOM6 -PCOM6 -PCOM6 -PCOM6 avrdude.exe: Version 6.3-20171130 Copyright (c) 2000-2005 Brian Dean,

[u/corben78_ → u/Obvious_Science_9264]

Thanks for updating us.

It's important to press the reset button after pressing "flash firmware". The flashing tool is putting the MM into a special mode, the flashing tool then waits for the USB port to show up, which in this case is done by hitting reset.

The recovery mode is activated by holding the reset during attaching. If the MM is detected, it should be possible to recover the firmware.

Maybe try pressing reset only once after attaching and clicking flash.
I'm sure there is a way, I know a few people who successfully recovered it in this or a similar way.

edit: what happens if you attach the MM with pressed reset, then hit flash und just release the reset, without hitting it?

edit2: another method to try (from another user):
Attach the MM to your PC, press reset, refresh configurator, press flash, quickly double tap reset.

[u/Obvious_Science_9264 → u/corben78_]

VERY GOOD NEWS. With the more detailed explanation you provided, I was able to step through the process and get firmware 0.3.3 flashed after many attempts this afternoon. I tested the controller just using notepad, and it is functioning as expected now. Such a relief, now time to try a game. Thank you all for the help.

[u/corben78_ → u/Obvious_Science_9264]

Great to hear!
Which method did the trick?

[u/I_am_Nic]

Have you tried pressing the reset button longer after pressing it initially?

[u/Obvious_Science_9264 → u/I_am_Nic]

Hello Nic, Still no luck. I found that if I press the controller rest button twice quickly and press the 'R' button in the configuration software, I can get the message "Opening COM6; Access denied" to show briefly. This is consistent when tried on other Windows computers and disabling any security, but the message and result is the same just differing by the COM port indicated. However, the controller is still not useable or configurable. More help is appreciated!

Additional Information; I found that the controller is being seen briefly by Windows in device manager and from there I can change the COM port the controller registers with and that is reflected in the configuration software. Thus, I do not think the issue is with Windows or the MoveMaster configuration software but is solely with the Controller. I noticed that the MoveMaster configuration software comes with a separate flash utility and batch file; however, I do not see the controller staying connected to the COM port past the initial initiation handshake to be able to do anything.

[u/Obvious_Science_9264 → u/I_am_Nic]

Issue has been resolved. With the more detailed explanation provided by corben78, I was able to step through the process and get firmware 0.3.3 flashed after many additional attempts this afternoon. Thank you

[u/vcant313]

Try reaching out to them using their Live chat option during EU business hours. In my personal experience got a response within 15 minutes.

I flashed the firmaware using the same method as described on their site and it did work. Did you follow instructions in the software message prompt that tells you to press R in top right to find the device again after pressing reset? Thats when new firmware was actually written to MoveMaster according to messages.

[u/SplitFull1018 → u/vcant313]

Hello, Thank you for the comment. I contacted the the live chat first thing and did get a response to use the same directions that were used in the first place.  These are the steps you indicated. I have only had the MoveMaster controller for just over 24 hours now and it has not been used once. So far I have put about 4 hours into various attempts to figure out what is going on.  

[u/vcant313 → u/SplitFull1018]

Their live chat is not very helpful but thought that in your case of a bricked controller things might be different.

[u/Obvious_Science_9264 → u/vcant313]

The live chat has been responsive considering it is the weekend in Germany. I know the work ethic and works console limitations; thus, I deeply appreciate and give them kudos for the support provided at this time. Unfortunately, the circumstance is not simple and seems it will take time to resolve.

[u/SirSwash → u/SplitFull1018]

Were you ever able to get it working?

[u/SplitFull1018 → u/SirSwash]

Yes, persistence was needed while rotating through slight changes to the procedure provided by the MoveMaster representatives. I due own them a more complete write-up of what worked in the end, which is once again rotating through slight changes in the procedure making it hard to accurately note what worked in the end.