I received an ISDT N16 a while ago from a giveaway. I thought that it might be finishing early while charging NiMH cells so I have started testing it.
Firmware: 2.2.0.1
Battery Type: Eneloop
Task: Charge
Current: 0.5A
Battery: eneloop AAA NiMH 800mAh
| Measurement | CH1 |
|---|---|
| Start Voltage | 1.343 |
| Finish Voltage | 1.420 |
| Capacity (mAh) | 429 |
| IR (mOhm) | 370 |
| Time (hh:mm:ss) | 00:53:14 |
It looks good. 
I’ll try a < 0.5A charge current next.
Firmware: 2.2.0.1
Battery Type: Eneloop
Task: Charge
Current: 0.2A
Battery: eneloop AAA NiMH 800mAh
| Measurement | CH1 |
|---|---|
| Start Voltage | 1.175 |
| Finish Voltage | 1.442 |
| Capacity (mAh) | 902 |
| IR (mOhm) | 380 |
| Time (hh:mm:ss) | 04:40:07 |
It didn’t go over 1.6V when charged at 0.2A.
Firmware: 2.2.0.1
Battery Type: Eneloop
Task: Discharge
Current: -0.5A
Battery: eneloop AAA NiMH 800mAh
| Measurement | CH1 |
|---|---|
| Start Voltage | 1.416 |
| Finish Voltage | 1.169 |
| Capacity (mAh) | 802 |
| Time (hh:mm:ss) | 01:41:32 |
I tried 0.2A and it terminated a bit early.
Firmware: 2.0.0.2
Battery Type: NiMH
Task: Charge
Current: 0.2A
-ΔV: 5mV
Battery: LADDA AA NiMH 2450mAh
| Measurement | CH1 |
|---|---|
| Start Voltage | 1.182 |
| Finish Voltage | 1.387 |
| Capacity (mAh) | 1210 |
| IR (mOhm) | 152 |
| Time (hh:mm:ss) | 06:34:27 |
Well, I don’t know if it was a bit early, probably much too early, it only reached 1.4V. You could have started with a discharged battery, then we would have known how many mAh should be charged.
I see that current is even lower than selected. Thanks for tests!
Discharged to 0V? The Charge test started around 1.1V and the Discharge test started around 1.4V
Yeah, it’s a bit low. I’m running a 0.4A Charge test now.
Charging terminated normally when 0.4A was selected.
Firmware: 2.0.0.2
Battery Type: NiMH
Task: Charge
Current: 0.4A
-ΔV: 5mV
Battery: LADDA AA NiMH 2450mAh
| Measurement | CH1 |
|---|---|
| Start Voltage | 1.142 |
| Finish Voltage | 1.494 |
| Capacity (mAh) | 2515 |
| IR (mOhm) | 153 |
| Time (hh:mm:ss) | 06:46:10 |
The charge current was around 0.3A despite selecting 0.4A on the ISDT C4 EVO.
The lower charge current might be due to the shunt that I’m using. That said, the same shunt was used for the ISDT N16 and the charge current was pretty close to 0.48A when I selected 0.5A, and 0.19A when I selected 0.2A.
I wish they gave us the option to completely remove this dumbass option from the menu… I don’t want to accidentally misclick and fry a perfectly fine battery.
No, to 0.9V. Or turn on Activate charging in settings which discharge battery before charging.
I think I discharged to 0.9V using the C4 EVO, left it for 30-60min and then the voltage was back up to 1.1V
Oh, well, it only charged half the capacity. So we still need to avoid charging below 400 mA.
Me too, observed the same behavior. Anyhow, it’s an improvement since before the update, early termination occurs when charging below 700ma.
But I still prefer charging at 100-200ma as I need to pack more energy for the next month Tamiya Mini-4WD race.
I also hope they implement some sort of voltage set limit where it will trickle charge the battery to maintain a specific voltage. There are certain tracks that requires 1.4v and speedy tracks where having 1.5 - 1.6v is a plus (albeit at the cost of battery life/longevity).
I know I’m asking a lot for such a compact device but one has to dream 
Sky RC 2500 Pro has such ability but it’s too pricey
I’m testing 2.0.0.2 and so far it’s terrible.
Why? I’ve charged NiMH a few times and it seemed fine. Although it always finished charging all 4 at almost the same time, which is a bit odd.
FW 2.0.0.2
Li-Ion in vert, Discharge to 2.5V with 300mA.
F15 = -931mAh 3h29m (should be appr 1044.99 mAh)
F12 = -807mAh 3h01m (should be appr 905 mAh)
Li-IOn in vert, charge to 4.2V with 300mA.
F15 = 1499mAh 5h40m
F12 = 1260mAh 4h48m
Li-Ion in horiz, discharge to 2.5V with 300mA.
F15 = -1400mAh 5h12m (better, but still not correct, should be 1605 mAh)
F12 = -1210mAh 4h30 (should be 1350 mAh)
Li-Ion in horiz, charge to 4.2V with 300mA.
F15 = 1400mAh, 5h13m
F12 = 1238mAh, 4h39m
Causes NIMh overcharging and overheating (1h and above and not being able to stop charging)
Overall I had much more issues with NuMh than with 2.0.0.1. I highly advise never leave this charger without supervision. Also recommend never use “Auto” for NiMh. I’m kinda considering giving up on this charger, TBH. All the efforts, time, messages to developers and very little results, no feedback, not even information what they “fixed”.
Thanks for the detailed evaluation!
Yes, it seems that the latest firmware releases are not really fixing (all) known issues.
I haven’t used my C4 Evo for some time now, apart from updating the firmware.
I use other chargers now for most of my requirements, particularly the Littokala Lii-600 and the Vapcell BL4.
C4 Evo the charger that can’t charge.
So i think i’ve had terrible C4 before, then terrible C4 Evo in 2021 (returned), and now that they brag about NIMH finally working directly on the Amazon pictures, I bought the Limeta version for 43€. Which is a nice price for an analytical charger. Could 4 years of changes mean it can do the basic job: charging? Let’s try v2.0.0.2 with NIMH batteries and fire extinguisher nearby.
Basically all I wanted is to stop defining every little parameter before each charge. Talking about MC3000 of course (MC5000 didn’t change that, they just removed temperature sensors and added similarly slow GUI with crappy joystick). But it looks like the only such charger in my portfolio will be Xtar VC8S for a while. At least some progress, Xtar now can “charge” (VC8,VC8+ could NOT). Bingo! What about ISDT?
Well, it still does undercharges (ERROR #3 mentioned above) like it used to (e.g. finished at 1.35V then top up in MC3000 another 900mAh). It still overcharges NIMH (ERROR #2 like, e.g. drive AAA into 50ºC and even showing the flat curve unapologically). But so far in less frequency. I didn’t try xmass batteries yet, the cold temperature completely fooled this charger before.
As I point the thermal gun on the batteries, one of them is 50ºC and C4Evo is of course showing 38ºC for each. So instead of 6 sensors they brag about there’s maybe 1 system sensor? Congrats MC5000, you have a colleague not caring about temperature. Which saved me couple of times from thermal runaway.
I’ve seen it restart relentlessly (ERROR #1 like) on a start of charge when the input was over 10W. Have to figure this out, chargers themself love to reset the connection.
The main reason why this charger just can’t be easy to operate (insert batteries and forget), is that automatic mode is bad. Unless resistance is is hundreds of milliohms, it will insist on 1.5A for NIMH in any mode. I don’t know anyone who like this default for AA or even AAA batteries. How difficult can be this to change, or add as an option?
Otherwise I do appreciate the very nice GUI, the fantastic screen with insane angles (178º), the compactness, and proper PD input (which still is not present on MC5000). I even like the weird battery placement. It limits the battery compatibility, but it’s smart. It holds batteries strongly, I can move the charger around. Whereas on MC3000, I need to reinsert AAAs many times, and can’t move it a bit, it’s connected via AC cable like it was 1995.
Summary:
Advantages:
- crisp 320x240 IPS display with incredible viewing angle 178º – that definitely helps on a desk (hello MC3000, hello Triton scales, hello tons of other devices)
- very easy GUI which shows all details or charts, while alternating
- very compact device for the functionality
- pretty smart design of battery insertion, tho it’s got some limitations
- using modern QC, PD input is so correct
- quiet fan, mostly not used
- easy firmware update of both ISDT and Limeta “brand” via PC app (yes Limeta too)
- fully automatic mode, and also some automatic options for manual mode, this is where SkyRC MC3000 annoys, taking convenience away
- 1.5V Lion support, unlike SkyRC MC3000
Disadvantages:
- once settings are pressed, can not cancel, and see the results, they’re gone. Also can’t reach global settings when any battery is inserted
- the battery slots can’t accomodate very short batteries, and long batteries inserted horizontally block vertical slots, reducing capacity to 2 pieces (yet they brag about “charging 6 at once”)
- no Eneloop mode
- automatic mode supports only Charge or Destroy function
automatic current is very agressive on AA and especially AAA batteries. Unless the resistance is giant, it will insist on 1.5A which is ironically maximum per vertical slot
- auto start of 5 seconds can’t be customized like on ISDT C4
- resets happen
- temperature sensors don’t work (values are the same, and hot battery doesn’t show up)
- no Bluetooth connection or PC app
Let’s wait another decade for MC7000!
Yeah, modern smart chargers are not for fainthearted. They are like first cars of 19th century, you have to be professional driver and mechanic at least to approach, and then kinda daredevil to drive.
I am nonstop loading batteries, meanwhile manufacturer responded to me downplaying undercharge, saying I can choose my current instead of auto value (how helpful), and also described the sensors are between contacts and plastic housing (and i believe they don’t sense anything, and only system sensor works).
I wanted to keep it, hoping we’re close to leaving beta status, but i’m more and more annoyed:
Time to return this dud and forget this brand for good.
That 8 slot XTAR also has some not healthy issues , according tp serious reviews.
not really, no issues, actually even more reliable than SkyRC. I watched both closely:
VC8 
→ VC8+ → VC8S 
C4 → C4Evo → C4Evo v2
