joeblowma

Does it have SP38 early release firmware on it? As far as I know they haven't pushed this into the main recommended package yet, that one comes with firmware SP35. https://forum.evolvapor.com/topic/66731-early-firmware-and-escribe-suite/?do=findComment&comment=929633 This cured about 98% of the (false) throttling issues for me. Still does it from time to time, but very rare now. Interestingly, I can still induce throttling in wattage profiles by manually setting the resistance to double what it actually is.

@Lanzarotechris it's supposed to adjust the power to remain at a set temp to protect from dry hits. The problem is, when these mods flash "temp protected" on the screen it's doing no such thing - it's just cutting power to the coil entirely, more often than not before it's even heated up (aka: spurious/random/not appropriately.) Other mods usually show 'temp protect' on screen or similar whenever it's throttling the wattage and a different error if there was a fault that caused it to stop firing entirely, for whatever reason Evolv decided to be different. If you read back in the thread I was able to always get a 'temp protected' error if I manually set the coil resistance a bunch higher than it actually was. Again though, the problem is (mostly) solved in the early firmware pack on the thread I linked to.

SP38 firmware update fixed most of my Temp Protect cutoffs ( Fixed spurious Temperature Protected errors that could crop up in certain high-CPU themes with Replay off. ), still happens very rarely for me but not nearly as bad as it used to be no matter what theme. As to the operating system, I think the theme engine was a little more ambitious than the microcontroller was meant for - plus as far as I know 75C and 250C design was finalized back in 2016 and with PMTA looming (they are a US manufacturer after all) no idea if we'll ever get to see anything better. In my opinion they still did very well with what they have, though I've always wished for more from my computers too!

It's in no way as involved as a laptop screen, those things need to be built for rigidity (and I've seen more than one fail because they weren't or worse the hinges were badly thought out.) Worst case there is some double sided tape holding the screen to the frame but IIRC it's just some tape strips down the two side and once you lift those and the screen/glass itself you might even have access to the connector and not even need to get the supporting frame out. I'd have to open it up again myself to be 100% certain as when I've gone in it wasn't to get access to the board at all, but every build I've seen around these screens has been more or less "tape it to a frame" or "put something behind it to hold it into a frame" and in paranormal 250c's case it's definitely resting on top of the frame.

Not much further, the screen is sitting in a tray and you'd probably have to figure out how to get that tray out to get at the connector.

For what it's worth I think if there are any design issues we can blame the US FDA for that - evolv had to finalize and sell the final design before the deeming deadline barring further changes without PMTA approval (which is unlikely except with more closed systems) which I'm guessing was met by copious crunch time... it's also why the US firmware doesn't have some features found in the INT firmware. I can say the betas did correct most of my issues with SS though, still get the occasional 'temp protect' where it doesn't belong and any time I've run into pulsing TC it's been down to my build (ie: coil resting on the block where the grub is rather than just held by the grub, inconsistent coil spacing, things of that nature).

I got that message in watts mode when the saved cold resistance was a fair bit higher than the actual resistance of the coil (for example a 0.32 ohm coil will give throttling message instantly if the saved value in the watt mode profile I have is 0.524 or higher), usually after rejecting a new coil message.

I think he added a bit of info on that beta test firmware post at some point after, noticed late last night... I'm a bit dubious about the 'high cpu theme', as I pretty much castrated the gauges theme to do nothing on the main screen and it was still an issue. Either way, 2398 puffs later I've had it occur 3 times, 729/924/981. Yes, I checked and wrote it down each time it happened because it's happening so rarely now. So... much better than it was.

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.

So far so good! I reverted to a version of the theme that was giving me problems more often than not, disabled replay recording in the TC profile (which was my working workaround to avoid the problem as much as possible) and have yet to run into a halted fire/temp protect event in the last couple hours. At least replay works. They may care slowly, but they do care.

Yup, I saw - plus you changed the temp output location to the big number display which doesn't work so great with wattage modes. I was pulling conditions off those one or two at a time, hoping it was just one thing that made a notable difference but none of them reached the effectiveness of yours. Have you tried the workaround I've been using... enable 'can replay' in the profile, but just don't use replay to save at all? I'm not sure the changes are just to the theme when that is enabled, it could be the entire TC method is switched over to something else in the process. As these boards alone go for around $95CAD, and all of my $65CAD or less TC capable full mods can get through a TC puff (though to be fair a few of them needed ArcticFox to do so, OEM didn't cut it)... I too am disappointed. R.I.P. "At least Replay worked."

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.

I gave mine a factory reset, uploaded a save of my settings, then uploaded the theme (the version I edited to allow temp change while replay is enabled in the profile) with the lock screen battery icon replaced with the default tiny one (75c:71.6%/60% 250c:71.6/50.8 off/on board) and as expected the problem went away for the first while but came back. I even let it sit for a couple hours just to make sure it wasn't a "works great until it gets warmed up" situation which would point to a component issue, but coming back to it and it picked up where I left off with the bad puffs. Turned back on replay option (but still have never bothered to lock a puff) in the profile and... no more problems. Yay for random things working!

First, take out your batteries. Take out 2 phillips screws by battery door hinge at the bottom front of the mod (marked as 1), remove the battery door. Under the battery door is 1 screw, then 2 more between the batteries (marked as 2, though one of them is under the battery door). Once these 3 screws are out with some gentle pressure the bottom of the mod just pops off directly down. Take out the 3 screws around the 510 connector, and the 2 screws on either side of the frame on the opposite end of the two for the battery door (marked as 3). Once the bottom is off and those other 5 screws are out, you can grab that front panel part down below the usb port (marked as 4) and pop it forward and up. This gives you access to the buttons and piece I was taking photos of previously.

So far the only way I've gotten it increase in frequency (as much as 4 in 10 puffs when it's being ornery) is using gauges or other themes that are 'busy', simpler themes like carbon or the one that came on my paranormal do it much less but still do it (maybe 1 in 20 or 30 puffs.) Sometimes it happens early in the puff (0.6s), and almost makes you feel you haven't gotten anything at all right from the start and other times it gives you a part puff before it occurs (1.1/1.8/2.4s my 'typical' puff seems to be somewhere around 2.5-3s) so watching the screen is necessary, as unfortunately this event is not logged along with the recordings. That the theme affects it at all is basically all the evidence I need to think it's a software issue rather than a mfg/qc issue and not something that we can correct ourselves, which will likely crop up relatively randomly in themes.

You will, eventually. Maybe not as often, but I'd rather not at all. So far enabling replay recording (but not playback) seems to be mitigating the issue for me, whether that is because while replay is recording it's "smoothing" the results and filtering the readings that are causing the protection to trip, or because doing so impacts timing in an update loop, or... who knows, I'm not privy to the code. What I can say though, is either finding a reliable workaround or better a way to cause the problem every time (in this cause gauges increases the occurrence which is better than nothing and in my mind at least shows there is definitely something wrong in the software somewhere) is the best info to give a developer. Barring feedback from the dev and seeing a lack of updates for some time now, as I said previously, for the time being I'm going to just assume the firmware is essentially abandonware on this point and what I thought was an investment in a great product which was known for it's excellent TC ability along with excellent after sale service is an overwhelming fail on my part (except in the instance the board itself proves to need warranty service, maybe... I didn't exactly wait patiently for retailers to stock this box in Canada which has only been relatively recently occurring.)

A little over a week using it daily in TC mode only, with the 'replay' toggled in the gauges onscreen profile editor but never having locked in a puff at somewhere over 1k puffs... I've had one temp protect occur towards the end of a ~3s puff just after changing the target temp. Disabled replay via the profile toggle and it behaved for a little while, maybe 15 or 20 puffs and then started throwing temp protect again fairly often. @iLLNESS I spent a little time trying to see if what you say is replicated here. Sitting idle for a good while my mod seems to read at 28-30C directly from idle, my room being somewhere around 22-23C. I chain vaped it for a 30 or 40 puffs (with the replay switched off, after vaping a tank dry and pausing to refill it) the board temp reached 37C, but interestingly I never had a temp protect occur while it was hooked into mod monitor though those did start up again shortly after I shut down the PC. It's all just intermittent enough, and possibly going under the radar on the forum going by the quiet from evolv (I think they haven't even pushed the 'mod won't turn on fix' past beta), that I don't have much hope of seeing it fixed. Maybe they'll prove me wrong though, now that the new pod board is getting out there.

Well this seems interesting, keeping in mind I've had protect events in multiple other themes as well as in wattage mode when the profile's stored resistance was about double what the current coil was... with gauges 2.1.0 it was getting really annoying today so I went into the profile editor via the little i icon in the bottom right and turned on replay (and never locked a puff in) and haven't had it happen once since, it seems to be performing consistent with the uninterrupted puffs I had before I turned it on without locking a puff as well. I edited the conditions on the gauges main screen so I can still adjust temperature there (which I did a little out of wack because I can still edit the temp when replay is locked in) without having to toggle replay off, and so far... real good. Again I still don't think it's the theme, or the others wouldn't be hitting protect. Hopefully the devs see this workaround and it at least gives a direction to look for possible bugs.

{Bump} Well I'm willing to point fingers. It's not the theme. Been having this problem with my paranormal 250c since day 1. My small pile of facts (accumulated with ss316L): happens most often at about 0.66s, but can happen after that seemingly at near 0.66s intervals, it suddenly stops firing and gives a "temp protected" error (which tbh seems suspiciously tied to a likely periodic event?) downloaded recordings have no sample event of the fail sample, but do note a higher then should be expected "peak temp" in the recording data (anywhere from 10F to 30F or more over the set value) cleaning/soldering the 510, swapping in various coils and atomizers... does not improve the situation changing to a lightweight theme reduces the frequency of occurrence, but it still happens and is even more jarring when it does so less often replay does not show any similar spikes in resistance to what you'd expect for a "peak temp" that far out of range during the recordings which strongly suggests this is a software issue even the forum randomly "half" signs me out while typing further suggesting software isn't a strong point here...? Ran into something fun in wattage mode too, I had a wattage profile set with a 0.5ohm coil and changed tanks to one with a 0.24ohm coil and declined the coil question, and when I went to fire it... "temp protect". Is "temp protect" just a go-to "we won't let you fire for reasons undisclosed" message? Or does "temp" actually mean "temporary" like "temporary placeholder for a real error message which we may never include"? (Yes, a joke! Because laughter is what I have left after spending DNA sized moneys!) Considering TC is what Evolv boards were known for, and I waited so patiently for a 250c... this is a little depressing really. My much cheaper ~$30 mods all manage to get through an entire puff... and arguably those builds aren't near as good as DNA should be. Anyway, still loving my paranormal even though I haven't found TC to be up to snuff on it... though it's epitaph really shouldn't be "at least replay worked."

@DJT my nitecore sc4 was charging to 4.21V when I first got it, now 6+ months later it seems to like to stop at 4.18V. I tried new VTC6 batteries too a couple months back thinking maybe my batteries were just aging, and nope still 4.18V on the nose. I really wish nitecore had gotten back to me sooner, I would have returned it to the store I got it from if I had known that if I set all 4 slots to 1A, it effectively charges them in the same time as 1 or 2 batteries set to 0.5A because it switches between pairs instead of just charging all 4 in parallel. Ah well, it works well enough for now and I'm almost to the point I can ignore that awful noise it makes when it's not charging.

Simple answer... it draws a vertical line at 1s increments. Try a 3s, 4s, 5s etc puff and see... sometimes the intervals don't look quite equal but I assume that is down to averaging and having to shift a pixel left or right due to the screen resolution.

Sure, I marked the diffuser with a pinkish box and the ribbon the bleed is coming from with a red box. I had to remove the diffuser and shorten it a little so it wasn't making physical contact with the ribbon, then put something between the ribbon that is bleeding light and it.

The TFR profiles are built into AF so it's whatever the developers chose them to be, typically if I use TCR I'd use 120 (0.00120), so that the temperature settings are consistent between my mods as that seems to be around where most of them set their SS profiles. As I don't have a temperature gauge (or environment to get such readings properly) I'm willing to replace accuracy for consistency - that said I'm fully aware it's never going to be an accurate thermostat as long as I'm using essentially random wire and don't have the ability to calibrate it, just that coming from such mods v4 has provided me the closest experience.