Posted February 15, 20205 yr Hi guys. I'm hitting a wall with my 2 Mecer Inverters. For a year and half, my 2 inverters, in parallels, worked flawlessly. 3 months ago, one of the boards blew. Mustek took 3 attempts to finally fix the board (sic) but didn't flash the correct firmware on the faulty inverter. They ask my provider to flash firmware 74.40 on both inverter. They provided the software. My provider didn't manage to do it, I had to learn how to do it and did it. All is well that ends well... except not so much. Exactly 60 days later, I get the error code 90. So I look a bit up this forum, find the reason, get more pissed at Mustek but they won't open until Monday anyway and it's now loadshedding stage 3. My plan was to reflash the inverters. Not so fast: now, I can communicate to the inverter, using the RS232 cable and a USB adapter, but the communication gets in LINE_FAIL after a couple of seconds. It the same setup than 2 months ago when I flashed them. Same computer, same OS, same Windows 10, same cables, etc. I didn't come here just to vent frustration, you guys don't deserve that. But is there any chance one of you knows its way around this issue? Or does it mean that I need to get those inverters off the wall and bring them back to Mustek on Monday which is going to be an interesting moment, for sure?
February 15, 20205 yr 3 hours ago, Marcel Cerdan said: Exactly 60 days later, I get the error code 90. Sigh. That's the problem with secretive checks like that. You don't tell the people in the field like Mecer, and it causes problems for genuine customers. Quote Mustek but they won't open until Monday anyway and it's now loadshedding stage 3. Yikes. Quote My plan was to reflash the inverters. Not so fast: now, I can communicate to the inverter, using the RS232 cable and a USB adapter, but the communication gets in LINE_FAIL after a couple of seconds. It the same setup than 2 months ago when I flashed them. Same computer, same OS, same Windows 10, same cables, etc. Those error appear to be coming from WatchPower, is that correct? It seems to me that you need to reflash with whatever firmware your machines came with originally, or nearly so. 74.40 assumes a more modern bootloader than what your 2015 machine has, and probably your 2017 machine as well. Another answer would be to use patched firmware version 74.40e, but it's still at least a few days from being checked. I found one missing patch so far, and unfortunately I'm only about half way through the checks. Do you know what firmware your machines came with? Quote ... bring them back to Mustek on Monday which is going to be an interesting moment, for sure? I don't think you should be too hard on them. They're kept in the dark. Edit: and I suspect that all that they can do is offer to sell you two control cards, so you can flash the firmware again, and give yourself 6 months to sort this out properly. Edited February 15, 20205 yr by Coulomb
February 16, 20205 yr Author Thanks a lot for your reply. Your dedication and commitment to this forum are outstanding. You're correct, the errors are from WatchPower. One of the machines came with the following software 72.40. I'm not sure for the other one. Reflash is struggling to established connection. I wonder if the FAIL-LINE I see in WatchPower isn't happening in Reflash too.
February 16, 20205 yr Author You saved the day! Exiting PowerWatch properly was the only way to have Reflash working. That's something I'll never forget again. I thought I had exited PowerWatch but I had just closed the window. After that, Reflash was happy to do it's job. I really owe you one! Best regards. Edited February 16, 20205 yr by Marcel Cerdan
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.