Separate names with a comma.
Discussion in 'Suggestions' started by maelstrom2001, Feb 24, 2020.
Come on, I just saved $30?!
yep, works perfect!
found a bug. when charging finishes (current drops to 1ma and battery voltage started to fall from "full" 4.18 to 4.17...4.16...4.15...slowly), mod still shows that it charging - screen on, battery blinks, batt 100%.
Thank you, seems logical: in the OEM firmware case "stop charging" looks like BatteryVoltage >= 4,25V or "logical 1" from external charger IC. The second condition is not critical as turned out, so it seems that we have to lower BatteryVoltage value.
can you control charger ic voltage/current/curves in firmware?! or just monitor it? asking because 4.25 seems much better than 4.18. it still in range for most lipo/liion but capacity usage should be better. oem firmware charges to 4.25?
I can send you one
Unfortunately no, just monitoring is available.
Attempt to fix charge end case: 200417
Thank you, I think we'll solve all problems faster than the postal services will deliver it
I don't know about stm32 boxes (have only rim c on this platform), but on nuvoton devices (tested on invoke and gen3 dual) I found that it actually can be controlled via battery profile + bvo Standard USR batt profile capped to 4.1, but if raise it to 4.2, it really charges to 4.2, not to 4.1. Also found that sometimes there is significant difference in balancer calibration between batteries (I don't know if there is calibration at all, maybe it just in hardware, too lazy to disassemble), but on my devices (2 x invoke + 2 x gen3 dual) I got +\- 0.01 to 0.07 diff from actual voltage. BVO + batt profile with precise voltmeter appears very useful. I am happy, thank you man! )
Testing 200417, waiting for cutoff, will let you know soon.
...still not goes to sleep
...found that my device also has wrong voltmeter calibration (+0.02), adjusted BVO and user batt profile to 4.20 (was 4.12). and...... now it works ) finally goes to sleep! but battery profile has no effect on charging voltage here, I think BVO was the point.
Thank you very much for testing and help
All about chargers zoo:
Welcome, always ready to help if needed, and thanks for charger matrix, looks like I was right about invoke/gen3.
I see swag there, have plans to support it?! I got one... )
Swag (TPCBAT hardware only) is supported: https://nfeteam.org/forum/threads/vaporesso-swag-1st-gen.2289/#post-11794
Wow, sorry, didn't know.. Will try it today, thanks!
I just made an account to say thanks so much for working on the Eleaf iStick Rim C Artic Fox Firmware!! I purchased this mod like 6~ months ago but absolutely hated the default navigation built into the firmware so I never really used it. After flashing Artic Fox 200417 I haven't found any issues so far, though this is the first and only mod I have that is compatible with Artic Fox so I don't have a good comparison. Let me know if you need any testing done, I have many different atomizers I can test out.
Hi! First off, thanks for all of your hard work.
I have an Eleaf Rim C with AF installed. However, when in TC/NI mode and auto fire, it will reach temp for about 10 secs and then it will say "Atomizer Not Found" and immediately stops heating.
0.48ohm / 33w / 360°F
Even if I hold the fire button manually to fire in TC, it will get up to temp for about 10secs and gives me the same error. Is there something I can do about that?
Auto fire TC/NI works absolutely fine with my Wismec TC Presa 75w however.
I echo the sentiments about your hard work! Also I'm having similar troubles with the current build on my rim c. Both with my sai and my dtv4. It will get up to heat stay there for a bit and then cut. The monitor indicates a wild temperature spike, sometimes I will see the error mentioned. The rim c is also my only arctic fox capable mod and I've only just got into box mods in the last few months.
Guys... Instead of thousand words post screenshots of profile, then open Device Monitor, make a puff and post screenshot and recorded CSV data.
Not sure what you want screenshot of, please forgive my ignorance. I have made the recordings and attached.
Read about "deep protection" state:
My apologies as well. I hope this is what you are asking for. Thanks again for all of your time and consideraton.