iSDT C4 EVO Firmware V2.0.0.2 Now Available

I understand firmware version 2.0.0.2 is now available for the C4 EVO.

Anyone know what changes have been made?

It seems that NiMh charging is finally working properly. I recently used this charger with firmware 1.0.0.4x and Kyosho, and it terminated charging too early. I’ve now switched back to it, and so far it seems to be working fine.

2 Thanks

Thanks for your comment.

If there are any further or resolved issues, please let us know.

Thanks for the heads-up! I replied on another thread about the termination issues and based on my investigation, the issue only happens if I charge my batts below 600mah. I’ve recently updated to v2.0.0.1 and it seems they somehow addressed that issue as I’m able to charge now @ 500mah without early termination.

Hopefully this v2.0.0.2 allows charging @ 100-200mah as I need to pack more energy to power up my cars, for the upcoming Brickyard Tamiya Mini-4wd Leg 5 Race this weekend.

Update:

My bad, the latest firmware can be downloaded and installed via the ISD Go app for windows. :grin:

I bought the charger mainly because of the ability to charge 1.5V Li-Ion batteries. Right after unpacking, I updated the firmware to the latest version 2.0.0.2 to enable this option, which happened and the “1.5V LiIon” option appeared in the menu.

However, after inserting these batteries, the temperature increased disproportionately to almost 60 degrees Celsius (measured with a non-contact thermometer, because the charger completely incorrectly measures the temperature). Based on this, I measured the input voltage that the charger gives to the batteries, and I measured 6.21V, which is too much!!!. There should be a maximum of 5V. I tried to measure the value of the XTAR VX4 charger, and it is 4.85V and the batteries almost do not heat up. This is wrong and I can’t imagine what would happen if I left the batteries in the charger longer.

  1. Can someone please check if the measured charging values ​​are the same as mine, i.e. 6.21V? (1.5V Li-Ion AA)

  2. Does anyone have an older firmware 2.0.0.1 or 1.0.0.49 saved? I would like to test if they have this error as well.

thank you