Thats why I've kept it.. TC just isn't working for me. I also think the eleaf FW is a bit smoother.
My first priority after installing the firmware was to get the devices firing exactly the same as with stock firmware. As far as I can tell that's accomplished. What the software is doing for me right now is helping me learn how i vape. i use an "old fashioned" rda with temp control. After redripping the watts spike to my max setting of 30 but temp is usuallly 100 degrees below my 400 F setting. When the wick is dryer the device hits the 400 degree max immediately but the typical watts is about 5. (The lower temperature liquid feels warmer because it's more dense.) This is all predictable but it's useful to see the actual numbers. I seem to do a lot of vaping when the coil is on the dryer side which reduces juice consumption, extends battery endurance, and is probably healthier. This software gives my pico puffs time and number of clicks and it's resetable with the buttons. That information plus recharging with a USB meter that lets me know how many mAh was consumed in a day, and eventually mAh per ml, which at the moment is appearing to be about 500 mAh per ml I'm interested in this stuff because i'd like to be in charge of vaping instead of vaping being in charge of me. I'd rather be vaping 3.5-4 ml per day instead of 7.
I think stock FW just not show actual T with so fast frequency. If you not change "PI-reg" values it should works as original firmware.
Eventually I'd like to play with the TC power curves, the PI values. i hesitate because i don't know the default values used in the stock firmware. Do you know what those are? I also hesitate to use the battery presets because the firmware doesn't say what those settings are.
I can't tell if the PI settings do anything on the Pico so far..... could be I have just not found the right build for TC yet..... or the right settings.
You could use MyEvic firmware Readme myevic/README.md at master · ClockSelect/myevic · GitHub
Thanks for the feedback. I put a post on the developer's forum with a suggestion and he responded. I suggested it might be worthwhile to have a setting where temperature monitoring worked in power mode. That means there is a report of max temperature but no temp control. I believe this would help with understanding differences between power and tc mode. At the moment the developer is concerned that this might confuse users. I made a suggestsion about how he might address that. So we'll see what happens. Also i wrote to pbursardo and suggested he do a youtube review of Arctic Fox. That might be helpful.
In DNA as I know it could be aesier: there is still ThermoControl mode, but it has not limit... But...
I'd like to be able to see temp in VW mode when using Device Monitor. .... be nice displayed on the mod too.
)) if you use TC, until TC limit it's just VW - because TC is VW with some rules.
You have pointed out the solution and I have suggested this to others in the past so i should have figured this out myself. If I set the temperature limit to the maximum allowed I'm vaping in power mode for practical purposes and i should still be able to see the max temperature reached. There's no reason to add the feature too power mode since it can be created in temp mode.
This assumes you are already getting a good vape in TC.... what if you are getting a good vape in VW using a self created curve...... and you find that those settings don't translate to TC. At least as far as you have found.....
I don't want "consistancy". I want control. I run only temp control at 30 max watts and 400 degrees and never change those settings except to dry burn a coil for rewicking. When I want a more dense puff I saturate the coil. But I spend a lot of the time vaping on a dryer coil because it's enough. That lets me take a lot of puffs without using so much power and liquid. A freshly saturated coil spikes the 30 watts but temperature stops at 300 degrees. With a drier coil the temp spikes to 400 but watts stay around 5. The 300 degree puff feels warmer than the 400 degree puff because the vapor is more dense. I use an 'old fashioned' rda so i can vary the liquid saturation easily. When I build a coil I want a tiny separation between the loops then take care that the wicking goes in without pulling the loops togther. This seems to make my single coil stainless tc builds better behaved.
Man, TC works so (without prehit):
I think it's commertial. I've read when some developer of same firmware wrote about his firmware on official forum, he was banned permanent immideatly.
My be, if developer want)
Just Leningrad band clip, they are cool)
Right now I'm using a USB testing device to measure how many mAh are needed to recharge my LG HG2 from empty. I've learned, after a year in service that one has 2500 mAh of capacity. I would be nice to have that on the mod if all that's requied is a software tweak. From limited observation it appears I use 500 mAh to vaporize 1 ml of liquid. if there is a consistant, reliable relationship i want to learn what it is.
As I know, "capacity" finded by 4.2 to 2.5v discharge.
I don't think that's possible. The actual capacity used will depend on the current drawn and other factors. When you're measuring the mAh under charge it's the capacity at that particular charge current. What you actually get out of the battery under discharge varies. The mod would have to do very precise monitoring of the batteries and calculations if you want reliable data. I don't think it's as easy as "mAh per ml", unless perhaps for only that specific set of batteries under those specific conditions. I.e., your mAh per ml for Samsung 25r A at 30w will not be applicable to LG hg2 C at 50w. It's very possible that I could be wrong though.
