iLLNESS
-
Posts
18 -
Joined
-
Last visited
-
Days Won
2
Content Type
Profiles
Forums
Downloads
Posts posted by iLLNESS
-
-
20 hours ago, Asdfghjkl said:
Still no word on an actual fix from evolv?
Outside of them asking users to test a beta firmware I don't think they've acknowledged the issue.
I get the impression the beta firmware was a bandaid and it's actually a hardware issue that for some reason they are trying to ignore.
I'd love for someone at Evolve to say otherwise but considering the most popular thread around the forums is about an issue and they've made no official statement about it tells me they can't fix it and are just trying to ignore it.
-
2 minutes ago, joeblowma said:
Well, to update... going by the puff counter it took 729 puffs before I hit a "throttling" message, at 886 now with no recurrence. Keep in mind I had gone over all the soldering as a first attempt to find a solution, with this version of the theme (I customized gauges to have some different default fields and to re-link the info icon on the main screen to the graph screen) I'm using now I was getting as many as 4 in 10 puffs interrupted with rare longer gap of 20-30 puffs with no issue. Because of that 1 puff I can't say it's 100% fixed, but for me at least it's far far better.
I agree that it is better, but it's certainly not fixed.
-
Trying it out now. So far after a half hour with gauges I've got no throttles.
Time will tell.
UPDATE: Didn't last much longer after my post. Few more minutes and it started throttling.
-
12 hours ago, joeblowma said:
This one is an improvement (though it leaves some modes a little broken), inline with some of the other themes I've tried. It took a good while before I started getting them with this one, but they did come back just not at the frequency it was occurring - about inline with other themes I've tried. I tried whittling through the differences between yours and the regular one and wasn't successful at pinpointing anything specific - just removing one condition (the middle number on the fire screen has conditions for both 'replay' and 'fire and replay' that do the same, I removed 'fire and replay') was a marginal improvement anything more was back where I started.
The changes were to the two items on the left below the graphs. That's where a majority of the conditions lie.
And to update, after about 6 hours of vaping the throttling came back. I'm lost for ideas. Likely the first and only DNA device I'll buy. I'm getting rather sick of this considering the DNA board was always touted as being the best for TC. IMO the 250C is the worst. My RX200s TC is far more stable than this crap. Pretty disappointed to say the least.
-
1
-
-
36 minutes ago, SirTimmyTimbit said:
Thanks for trying that. A little disappointed that wasn't the problem, cause it would've been the easiest to fix lol.
Try replacing the profile/status field on the main screen with just a static status field. That's the only other thing I can think of that might cause this.
I attached a version with a static status field to this post. Keep in mind you have to go to the atomizer profile screen if you want to change your profile.
After more testing I can confirm this version still throttles.
If anyone is interested, they can try my version of gauges 2.2.0 with the coil and power conditions removed. The profile/status condition remains.
Main screen has power in the middle bar (can be modified) and temperature above the status.
It does not suffer from a throttling issue for me, but I cannot guarantee the same results for others.
If it does throttle for you, try resetting your mod to defaults, adjusting your settings then loading the theme.
-
1
-
-
Just now, Pete1burn said:
Are you guys still seeing if it's the theme causing the issue?
I flashed back to stock with no theme long ago and this problem keeps happening.
One additional piece of info is that this seems to happen most often right after removing the tank from the mod to refill it.
I believe it can be caused by a few things:
- miscalibrated case thermals (case analyzer should help with this, but it can also make it worse if you don't do it properly)
- bad mod resistance (under mod/electrical) (this can be calculated using the atomizer analyzer with a copper plug or a known resistance)
- wrong or bad wire profiles
- themes
I'm sure there is more, but the temp control on the mod is calculated with the first 3 items (and maybe more) and if you have those first 3 items wrong it will cause the temperature control to act up. Why it would throttle instead of just run too hot or cold I don't know. I'm leaning towards it being a bug in the code or just inefficient coding that is made worse depending on what's going on with the theme.
If you're getting throttling on the stock theme try resetting your mod to default and punch in your settings again. After lots of fiddling around my mod was throttling a lot even after going back to stock theme. A reset fixed me up until I went back to gauges.
-
6 minutes ago, SirTimmyTimbit said:
Thanks for trying that. A little disappointed that wasn't the problem, cause it would've been the easiest to fix lol.
Try replacing the profile/status field on the main screen with just a static status field. That's the only other thing I can think of that might cause this.
I attached a version with a static status field to this post. Keep in mind you have to go to the atomizer profile screen if you want to change your profile.
Thanks, I'll give this one a go too.
I've done some changes to the stock gauges theme and removed most all the conditions on the main screen and so far that has showed some promise. I don't want to jump the gun and say that's what it is, but so far i'm leaning towards the theme being too 'busy' as a problem. So your change of the profile/status field being static is in line with my findings so far (although that's actually a condition I left alone).
Assuming this is the solution, I'm guessing it's causing the problem because the conditions are likely in the main loop of the software which may be slowing things down to the point where the coil ohm reading is being affected and the device throttles.
-
1
-
-
16 hours ago, SirTimmyTimbit said:
Thanks man, I really appreciate !
So I've been switching between the 3 profiles (gauges, the test version and clean colors) and there doesn't appear to be a noticeable difference between gauges and test gauges. It still throttles for me often, but cool colors is still not having the throttle issue. So it doesn't appear to be an off board memory issue so I suppose that's good!
I have some ideas I'll play around with today to see if I can nail down what is causing it and report back.
-
1
-
-
9 hours ago, SirTimmyTimbit said:
@iLLNESS try this one. Using only 68.2% off board and 60.2% onboard memory on 75c. Less onboard on 250c.
I just removed the battery indicator on the lock screen.
Thanks. I'll do some testing and report back with my findings.
-
1
-
-
Aside from the gauges theme, does anyone know of another theme that uses a high amount of the 'off board memory'? Gauges currently uses 99.9% of the off board memory on a 75C and 250C compared to the default of around 30%. Suspecting this to potentially be an issue, I found a theme similar to gauges in how many screens/features/data it has called Clean Colors. This theme uses 72% of the off board memory and so far does not suffer from the throttling issue. The throttling can be reproduced 100% of the time on my mod simply loading the gauges theme and the only thing out of the ordinary I can see is that gauges uses the max amount of off board memory. Perhaps there is a miscalculation with how EScribe determines the available off board memory and the data in gauges is messing with or overwriting the code of the DNA under certain conditions causing a miscalculation leading to the throttle.
Just a hunch, but there is clearly a reason why gauges is suffering from this issue more than other themes.
On 6/19/2018 at 4:44 AM, SirTimmyTimbit said:Sorry I didn't know the chip was able to show two different messages for those two conditions. I thought like most chips it would all fall under "throttling" or "temp protect". I'll change it back to Temp Protect in the next update.
@Pete1burn I was going to suggest removing the custom status from the language tab to see if it helps. If anything you would see the default message that the chip sends. But if it's cutting out your power when it shouldn't it's out of my league. I assume the max puff time is well over the puffs you were taking?
When the theme had a flicker (and a half second lag) prior to v2.0 this problem made more sense. I cut down on the number of fields that updates while firing as well.
SirTimmyTimbit, any chance you could whip up a test version of gauges with some things removed to drop down the off board memory usage? I'd do it myself but I honestly don't understand what affects the off board memory usage as I'm not quite skilled in the theme designer.
-
1
-
1
-
-
On 8/2/2018 at 4:48 PM, stanere said:
So Evolve support replied to my ticket:
Nothing much, seems like the board itself is fine and the device is faulty.
This seems like bullshit. There is a 3 page thread covering this and the throttling becomes worse depending on what theme you're using. Your 510 doesn't give a crap about what theme is being used and yet there are all those users dealing with that very problem.
-
Quote
Firstly, do the triple battery mods like Triade or Rebel 3x18650 give me any advantages besides battery life and a max 300W output?
Not functionally no. Personally I find 3 battery mods to have a much better form factor though as they just fit perfectly in your hand.
Can't comment on the paranormal as I do not own one.
-
21 minutes ago, dwcraig1 said:
I always figured room temp as being "room inside mod" as there is no sensor outside the mod.
Ambient temp is calculated over time based off the board temp and the results from the case analyzer.
-
20 minutes ago, halford said:
70/80/90s? This is in Fahrenheit?
10C of waste heat measured at source seems OK, no?
Yes those were in F.
10C difference would be okay, but like I said, others are having their board temps in the 70s(F) after sitting in ambient temps almost identical to mine.
if you have multiple devices sitting in the exact same temperature and one is saying the board is 10C hotter than the other as soon as it’s plugged in something is not OK.
-
33 minutes ago, halford said:
Why do you consider this high? A passively cooled semiconductor running in the lower-thirties seems great to me. Is there something I'm missing as my device reports similar and I was impressed at how low it was.
I consider this high because from all the other users I’ve seen run the case analyzer they are getting board temps in the 70s/low 80s around the same ambient temperature as me, where as I’m getting in the 90s.
My board temp shouldn’t be 10C higher than ambient after plugging the device in to run case analyzer. Something ain’t right, and it shows comparing to other users board temps at the same ambient temp.
-
Having this issue as well with my 250C (Lost Vape Triade). It's normally been a minor thing but we just got a nice heat wave today and I've been getting it every 2 or 3 puffs when outside while the ambient was 32C. If I move into the AC the issue seems to resolve itself. This is well below the upper limit that is set in escribe.
I took a look at the board temp while it was throttling and it was reporting in mid 30s. Perhaps users with bad throttling issues could try tossing it in the freezer for a bit to see if it helps limit the throttling. I have a sneaky suspicion it's a bug in the code that's throttling the device because it's calculating the board temp to be too high, or the board temp is being misreported on screen.
One thing to note is this particular devices board temp was causing me issue during case analyzer. After a night of sitting at 22C (verified with a digital thermometer) as soon as I plug it in it sits in the 30s (or 90F+) which compared to what I've seen others report is far too high for an idle board temp in that temperature).
In the mean time I've bumped the max ambient temp up to 55C to 43C to see if that helps.
-
So I just got my Triade 250C and after initial setup/tinkering I'm noticing the board temperature is quite high. With the mod sitting for a few hours while unplugged and with the batteries out, when I plug it in and run the case analyzer the board temperature sits around 33C when the ambient temp is 22C. Has anyone seen this before? Is there anything I can do?
"Throttling"
in General Discussion
Posted
No doubt the beta improved the throttling issue, but it's still there. For a board as high end as a DNA you'd expect it not to have phantom throttling issues which it clearly does.