Yaaaayy!! Finally. Ended up dual boot with Windows 8.1 after all, and that worked! Firmware successfully updated on both my chargers. The thought of trying different OS's just for this is a bit too much bit at last. lol
Ok, i can see how the screensaver can get annoying really fast because of the beep. For now, i turned off the screensaver.
It would be interesting to know if the PC-Link software runs ok under safe mode? If the PC-Link software functions under safe-mode indicates something being enabled, and/or loaded upon a normal boot-up that's preventing your USB to work normally. Safe-mode starts Windows in a basic state, using a limited set of files and drivers, IIRC should have USB support.
Try holding the SNB. That will pulse some voltage into the battery.I have a eneloop that I've accidentally ran down to a very low voltage and the MC3000 will not recognise it. I'm assuming that there is nothing in the settings that can be modified to get this cell visible on the MC3000?
I have some Tenergy RCR123A 3.0V batteries I would like to charge with my MC3000. What is the safest way to determine the maximum voltage I should charge them to?
ProgressiveRC is well-known in the RC world for top-notch customer service, as a search will quickly confirm (see here or here for a couple random examples).
However, one thing to be aware of is that they seem to have changed their warranty terms on the MC3000. Initially it was lited as "limited lifetime" but now it is only "1 year" - a bit disappointing.
Get your facts straight. ProgressiveRC originally offered a "limited lifetime" warranty both on their Amazon page and their website. But now it has been downgraded to "1 year". There is no "conspiring". Only facts - which may be useful in purchasing decisions.
I believe if you boot the device with enter pressed down (unplug all power, hold down enter, plug in power) you can reflash it.
Just tried updating my firmware to v 1.11 and the process stopped with this error: "start vector err1".
I'm using a laptop with Win XP SP3, so should not be an OS issue.
I tried the above method to reflash my firmware but it is not working.
Note my original firmware was v 1.02.