Calibration: 0xBDBDBDBF
Unfortunately, the firmware seems to be locked for reading. :-/
This is born out by actually reading it: "00 00 01 01 ... FE FE FF FF" repeated 64 times.
Next, I tried reading the eeprom, hoping to unlock service menu 1 by modifying byte 0x390. The prom data returned "00 01 02 ... FD FE FF" repeated 4 times. I wasn't aware the prom could be protected from reading. Is this true?
Due to laziness and eagerness, I was using eXtreme Burner - AVR v1.41 on Windows. I continued fiddling around with it for a moment, being careful to only use the "read" buttons, not the "write" or "erase".
I clicked the Configure AVR Clock Source button, hoping to see the current chip configuration. Instead, the 4 drop-down menus showed nothing selected. So I clicked the big red cancel button. Which appeared to do nothing. It didn't close the window.
I tried reading the eeprom again, and got a different result: a quick glance showed almost everything was FF. Excited, I quickly pressed "Read -> All" to try to get a dump of the firmware again. This took a long time, then failed. I've forgotten the exact error message. Comms failure, or something similar.
Now nothing worked. Restarting the software and power-cycling the charger didn't make any difference. eXtreme just reported a problem at the first stage: "powering up".
With my distrust of the software rapidly mounting, I took a moment to study the avrdude flags and switch to Linux, where I'm more comfortable anyway. I couldn't make any headway there either.
Then it struck me: there used to be a "click" from the beeper when powering it up via the USBasp or the regular power input. That doesn't happen now.
I didn't have the screen+backlight or buttons attached when powering via the USBasp, but after 5s what I guess was the low input voltage alarm would sound. That doesn't happen now.
I don't think I've done anything dumb here. Before doing anything, I read until my eyes watered. I was wearing an anti-static strap. My adaptor lead makes solid reliable contact, and my Fluke 87 says there's effectively zero resistance or capacitance between the USBasp and the ATMega pins on the charger. I took care that no shorts could arise, especially the charger's regular power input connectors. All my interactions with the chip were reads, not writes.
It worked just fine for 5 minutes, then something broke. With my limited experience, I can think of only two possibilities:
1) powering it via the USBasp rather than the regular power input slowly burned something out
2) eXtreme burner wrote bogus values to the atmega
Can any of you esteemed folks here suggest which is more likely, any other possibilities, or perhaps even if it's salvageable?
Without a good dump of the firmware, my gut feeling tells me this board is destined for either the recycling bin, or maybe Pawel's doorstep for experimentation purposes after the exams. Good luck with them, btw. ;-)
Cheers,
stavs
Without a good dump of the firmware, my gut feeling tells me this board is destined for either the recycling bin, or maybe Pawel's doorstep for experimentation purposes after the exams. Good luck with them, btw. ;-)
switch the usb asp to 5 volt , and then try connecting to the charger.
2 = IF you locked yourself out of the atmega32 -> nothing happens
In this case you will get a message from your programming software telling you that the target is not responding.
In case number 2 ............................ you bricked it , and it will continue as a doorstopper.
If you are skilled enough , out on ebay are many sellers offering the 44 pin atmega32 you need to replace and for and it must be possible to get one for under 5 dollar.But , only if you can desolder the original one without damaging the tracks .
On Friday, 9 August 2013 15:51:25 UTC+1, I wrote:Without a good dump of the firmware, my gut feeling tells me this board is destined for either the recycling bin, or maybe Pawel's doorstep for experimentation purposes after the exams. Good luck with them, btw. ;-)
Of course that should be Stawel's doorstep. Sorry about that. I blame my stupid memory.
I highly encourage You to do the support yourselfwith our help of course,
It seems to me that Your charger is a bigger version of GTPowerA6-10,so it should be not a big problem, maybe even You need only to flash it withcheali-charger-GTPowerA6-10-0.20.hex.
OK, you persuaded me. :-)There is a replacement MCU in the mail, so I shall try my hand at this later in the week.
It seems to me that Your charger is a bigger version of GTPowerA6-10,so it should be not a big problem, maybe even You need only to flash it withcheali-charger-GTPowerA6-10-0.20.hex.I think you're correct. Externally it seems nearly identical to the GTPower A620.Here are some photos of the Mega 400W V2 board:Cheers,stavs
--
You received this message because you are subscribed to the Google Groups "cheali-charger" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cheali-charge...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
can you please make some pictures without the MCU?I can't see all the pcb-tracks
I finally sussed it. After importing and aligning the images, goto "Camera and Lens", click "Reset" and select "Vignetting".
to pins 25,26.I can't see what it is, it's the black "soic-8" chipnearby the 16MHz oscillator.
But I'm pretty sure you can run the GTPowerA6-10 firmware on it,You will probably need to calibrate the internal temperature probe(and maybe other things) inside the source code.
Thanks for the tips. I look forward to trying it later this week.
Hi PawełI installed virtual linux and compiled your source.I create some files and modify maximum Current and power parameters for Turnigy MEGA 400W x2 charger.Today testing the high current my hexfile. GTPOWER hexfile working, but only 10A charge rate.ftp://filex.tv2.hu/7678f6cdde98d59b24cdde621dc6e6bf/ please check new source files, that there is anything wrong.
(hexfiles not tested please carefully. Dont use.)
just a thought.stayed connected batteries for a long time after charging end. after 12 hours charger temperature of 35 ° C and battery cells only 4.12V.It is possible that there is a bug in the balance-off after charge end or mega400W not equivalent GTPOWER?Thank you.Jozsef
ps.The version you are using is out of date,please update it to the 0.31 version.
This Mega400 (x2) firmware good working.-internal Thermo sensor absolutely good working but why are there two calibration? (int/ext?)
I small problem:this charger high current. 20A.if charging started, then delta current too high (0 to 20A 0sec). It would be better to smooth.Many powers supply not good tolerate this high current change. (or gasoline generator with inverter)decrease current of the same problem.original(stock) software approx 3-5A/sec delta current.I would love if possible
Hello,I recently bought a Turnigy MEGA 400Wx2 Battery Charger/Discharger (800W). I quickly discovered that I can´t calibrate it and also the smart fan is not working. I see that you have a firmware where you can calibrate it. Does this firmware also fix the smart fan?
Hi alli think: big power charger is bad hardware design. but:I increase the p0 points and increase the p1 points for better fit the big power:discharger: p0 50mA to 300mA p1: 300mA to 1ASMPS: 50mA to 300mA 1A to 5Amy modded fw, I increased max_calibration_discharger_value up to 255.Pawel, do you think that's okay?
Hi Jozsef
Now we could calibrate it with no problems. Thank you for your help. I really appreciate your efforts in this project. Have you tested all charging and discharging programs? My main coal is to charge and discharge lipos from 2s to 6s.
best regards
Joukko
The Mega 400W V2 is also an obvious derivative of the B6 design. The board is marked "B641C rev A3" and "DL-B641C V3.3".
--
You received this message because you are subscribed to the Google Groups "cheali-charger" group.To unsubscribe from this group and stop receiving emails from it, send an email to cheali-charge...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.