cheali-charger: version 1.00 (stable)

[Paweł Si]

Hi All,

to the best of my knowledge,

we didn't burn any charger for some time now,

so it's probably a good time to rename the unstable version 0.99 to stable 1.00.

I've uploaded cheali-charger v. 1.00 firmware to:
https://github.com/stawel/cheali-charger/tree/master/hex

This also means that I will do only bug fixes for this version,

and any new features will go into a new 1.10 unstable version.

what changed compared to v0.33:

1. NiMH/NiCd/Pb battery cycling (njoszef)

2. arm: nuvoton M0517 CPU support (arm_draft)

3. arm: second UART (sasam)

4. charge/discharge time limit (njoszef)

5. some nice animations (njoszef) 

6. additional screens (njoszef) 

7. min. output current setting (njoszef)

8. LiXX overcharge setting

9. LiXX overdischarge setting

10. eeprom CRC check

11. disable LogView logging 3min. after end of charge

12. output power limit in real time 
13. calibration safety check
14. ADC noise for atmega32
15. readme.md  (incomplete)
16. Voltage cutoff setting for NiMH, NiCd
17. "fan on" setting

Best Regards,

Paweł

[Samuel Lang]

Congratulations for the excellent work!!! :-)

The one in front fits better to this awesome project!

If I may post a comment, I would like to vote for ENABLE_DYNAMIC_MAX_POWER to walk into standard, because its a cool feature, it works stable and did I say that its cool ;-)

Dont know how many other are using it so far, but for myself I can confirm probably 100+ successfull charges with tremendeous faster chargings _without_ any issues.

Probably if you free the eeprom from "forced bal" you could make that as an option...

My 2c

keep on!

--
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.

[Igon]

note: Dynamic power is not suitable for -dV

can cause false -dV complete

[Paweł Si]

2015-03-12 8:14 GMT+01:00 Samuel Lang <ma...@lang-sam.de>:

Congratulations for the excellent work!!! :-)

The one in front fits better to this awesome project!

;)

 

If I may post a comment, I would like to vote for ENABLE_DYNAMIC_MAX_POWER to walk into standard, because its a cool feature, it works stable and did I say that its cool ;-)

Yes, I can only agree, It's really cool! :)

 

Dont know how many other are using it so far, but for myself I can confirm probably 100+ successfull charges with tremendeous faster chargings _without_ any issues.

Probably if you free the eeprom from "forced bal" you could make that as an option...

But unfortunately I wont add it to the "standard" build,

reason for that is that for each burned charger a get a gray hair on my head,

and this option may increase the grayness ;)
even if it works on your charge, it may not work on others.

But it would be nice if we would have better documentation for it: what it does and how to turn it on.

Maybe You would like to add some documentation?

Best Regards,

Paweł

[Alexandr Karat]

Hello. All day long studied the topic flashing. Decided to try and get the following. Very sad ((( .

 Maybe I missed something?

Thank you for your attention.

[sasam]

Did you try to halt CPU manually?
In telnet/putty window type:

halt
source M0517_unlock.tcl
ReadConf
EraseChip
WriteConf

Could you send screenshots (OpenOCD console & telnet/putty) after ReadConf command.

When I last time tray to unlock (first lock with Bu-link) then unlock with https://github.com/sasam/M0517_flash_tools
everything was as expected. Try to press enter on both windows (OpenOCD console, and telnet/putty).
I didn't connect RST, only 4 wire.

Best Regards,
Saša

[Alexandr Karat]

Thank you very much! We had to disable the RST. Go for a deal with the settings)

Good luck and thanks again !!!)))))))

 Nice work !!


пятница, 13 марта 2015 г., 1:17:17 UTC+2 пользователь sasam написал:

[Стас Глушко]

Thank you for your firmware! It is made from a Chinese copy of real charging. :)

I tried lipo, liio, NiCa (from the screwdriver cyclic restoration), and is now trying to charge the starting battery pb 55ah.

[Сергей Лавреюк]

Привет Павел, Саша и все члены группы. Вчера у меня промелькнула мой Nuvoton M0517 CPU дешевый китайский STM32 ST-LINK v2 для 3,3 $ вашей последней версии 1.00. И у меня есть вопрос о настройке UART. Подскажите пожалуйста, где можно подробно рассмотреть этот параметр. Спасибо вам большое за производителем work.The не применяется так хорошо их программно-аппаратные you.It это большая работа сделано вами.

среда, 11 марта 2015 г., 15:31:33 UTC+2 пользователь cheali-charger написал:

Привет Всем,

в меру моих знаний,

мы не сжечь неисправные зарядные устройства в течение некоторого времени,

так что это, вероятно, хорошее время, чтобы переименовать нестабильную версию 0,99 стабильной 1.00.

Я загрузил cheali-зарядное устройство V 1.00 прошивки:. https://github.com/stawel/ cheali зарядное устройство / дерево / мастер / HEX

Это также означает, что я буду делать только исправления ошибок для этой версии,

и любые новые функции будут идти в новый 1,10 нестабильной версии.

что изменилось по сравнению с v0.33:

1. NiMH / NiCd / Pb батареи на велосипеде (njoszef)

2. рука: Nuvoton поддержка M0517 CPU (arm_draft)

3. рука: второй UART (sasam)

4. заряда / разряда срок (njoszef)

5. Некоторые красивую анимацию (njoszef) 

6. Дополнительные экраны (njoszef) 

7. мин. Текущая настройка вывода (njoszef)

8. Гладкая установка завышенную

9. Гладкая установка избыточной разрядки

10. EEPROM CRC проверка

11. отключения ведения журнала LogView 3 мин. после окончания заряда

12. Выход Максимальная мощность в режиме реального времени 
13.  проверка безопасности калибровка
14. ADC шума для atmega32
15. readme.md  (неполный)
16. Запирающего напряжения настройки для NiMH, NiCd
17. "Вентилятор на" настройки

С Уважением,

Пол

[Maksym Siryk]

понедельник, 16 марта 2015 г., 11:28:52 UTC+2 пользователь Сергей Лавреюк написал:

Привет Павел, Саша и все члены группы. Вчера у меня промелькнула мой Nuvoton M0517 CPU дешевый китайский STM32 ST-LINK v2 для 3,3 $ вашей последней версии 1.00. И у меня есть вопрос о настройке UART. Подскажите пожалуйста, где можно подробно рассмотреть этот параметр. Спасибо вам большое за производителем work.The не применяется так хорошо их программно-аппаратные you.It это большая работа сделано вами.

Что за поток сознания??? 

[Nagy Jozsef]

Hi Pawel.

I have The small problem on 400Wx2 (V1) chargers.

Flashed the new 1.00 fw, eeprom resetting, calibrating with 6S battery (set Voltages (6cell + input voltage), charge curretnts and discharge currents.) (int/ext temperature senor not.)

adjust first slot the 5S, 32.00Ah  lipo battery setting. (I work th 4pcs. 8000mAh 5S batteries).

After start, displaying the info screen second line   41.0V  20.9V.

Charging start not avaible.

return calibration menu, press voltage, and press IN voltage twice (save)

now info screen second line is good  20.9V  20.9V.

Thanks.

Jozsef

[Andrew Frewer]

Hi Pawel. Are your compiled files in Intel or Motorola hex format? I need to convert them to bin to use with CoFlash.

Thanks!

[sasam]

Try conversion with objcopy
conversion hex => bin
arm-none-eabi-objcopy.exe -I ihex -O cheali-charger-imaxB6-clone_1.00-20150504_nuvoton-M0517.hex cheali-charger-imaxB6-clone_1.00-20150504_nuvoton-M0517.hex

Best Regards,
Saša

[sasam]

Wrong extension in last post .hex insted .bin

arm-none-eabi-objcopy.exe -I ihex -O cheali-charger-imaxB6-clone_1.00-20150504_nuvoton-M0517.hex cheali-charger-imaxB6-clone_1.00-20150504_nuvoton-M0517.bin

[Andrew Frewer]

Thank you. Unfortunately my colinkex won't work, so I'm stuck waiting for an st-link.

[Paweł Si]

Hi Jozsef, it's nice to hear from you,

I have to admit that I don't have enough time to check this issue,

but a possible explanation would be that you battery main leads

were not well connected, This would charge the output capacitor

and the charger would use the capacitor voltage (which slowly falls) to calibrate the output.

OR (of course) we have a bug :(

Best Regards,

Paweł