Evolv DNA Forum
Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment   Page 1 of 3      1   2   3   Next
vaporlips

Member
Registered:
Posts: 48
Reply with quote  #1 

While within the atomizer analyzer, I clicked "override ohms" and a window pops up and asks' me to input the ohms.  I input the ohms, exactly what atomizer analyzer was reading.  (For some reason the device was reading .12 and I knew the coil was .09, which is what escribe said it was whilst in atomizer analyzer.)

After overriding the ohms, my device first displays a 0.00 resistance with the lock next to it, and then shortly after the device will display whatever resistance it's reading from the coil.  The issue is, when I do this I can't vape at all.  The temperature protection is kicking in instantly.   Usually if the displayed resistance is off a little, you can still get a little bit of a vape before it hits temp protect, but with whatever this override ohms does it makes the device think it's hitting the set temperature instantaneously.   I can not get any vape whatsoever because it's just so instant to hit temp limit.  

After disconnecting my device, and exiting escribe, the problem continued.  I could not vape whatsoever.  I tried unlocking the ohms on the device, as well as locking them again but nothing helped.  What solved the issue was putting a kanthal build atty on the device, it then fired as usual.  Put the original nickel coil atty back on, and now everything is working beautifully again.  

Just to confirm as well, I can see the display on the device is set to 440F.  This atty has always been just fine for me.  Atomizer analyzer also confirms that the resistance is steady.

 I have the latest updates for Escribe, as well as dna200 firmware.  I have an 11.1 volt 1000 maH 30C LiPo battery.    


__________________
VaporLips Custom Box Mods
AllenH

Member
Registered:
Posts: 43
Reply with quote  #2 
I'm glad someone else brought this up.  In my situation I can fire the initial fire, but then I almost immediately get over temp protection warnings... this is particularly bad in situations of short puffs and frequent puffs.  I have a hard time believing we're getting up very high temp- I thought I read some instances of 500-600F even though almost no firing was occurring.

Another thing I've noticed is a consistently increasing resistance... a coil that was reading 0.08 was jumping up to 0.31 during firing.  I find that hard to believe.

Thank you for mentioning this VaporLips- I've been experiencing similar issues.  The refinement problem I'm experiencing is different, and I haven't played with it today recently.  I'll try to create a new thread on the refinement problem.  But the locked ohms and instant temp increase I'm also seeing it appears.

My build is dual coils, total resistance reading around 0.08 ohms.  The analyzer is saying "?" for cold ohms for some reason.  I'm running around 60 watts (also experienced at 115- but got a horrible dry hit from it earlier today, so had to turn it down) - temp protection was set at 450F (now I set it at 230C)  Ohms locked at 0.08.  When the ohms wasn't locked, resistance was hitting above 0.30 ohms from 0.08.  [resistance was stable in analyzer earlier] - that caused the horrible dry hit for me earlier.  So, something with this new firmware is going wonky.

Hope we can get to the bottom of this somehow.

RDA = CiGreen Arrows RDA
Coil = dual vertical coil, 28ga Ni200, 10 turns on approx. 0.3mm, 0.081 resistance in analyzer
Mod = Evolv Beta Mod,  latest firmware as of 07/11/15
eliquid = Adirondack Vapor Delta, Max VG
System= Mac OsX 10.10.4 running Parallels desktop 10.2, Windows 10 pre-release
John

Avatar / Picture

Administrator
Registered:
Posts: 500
Reply with quote  #3 
If the atomizer analyzer is showing a question mark, it doesn't think that the atomizer is connected. Can you screenshot a graph of power, temperature, cold ohms and live ohms as you fire and post that here?
AllenH

Member
Registered:
Posts: 43
Reply with quote  #4 
That's weird- because it was actively reading the resistance with the analyzer. I'll take a screen cap of that. Also if I can, I'll do a live fire recording and screen cap also. Thanks!!
vaporlips

Member
Registered:
Posts: 48
Reply with quote  #5 

Mine would display the correct resistance on screen as well.  Never saw the question mark.  It's just after I override ohms , the device just thinks it's hitting 600F instantly.  Even though the atomizer analyzer is still showing the correct resistance, which obviously is not changing enough to be in the 600F range....

 

I will also try to get you some screen shots/ screen capture video.


__________________
VaporLips Custom Box Mods
AllenH

Member
Registered:
Posts: 43
Reply with quote  #6 
Hi Vaporlips - yes that's exactly the type of thing I was seeing as well.  I saw it ramp up on screen to 500 then 600 I think!  I was quite shocked, and of course it was only outputting 0.1 Watts at that point and hit temp protect practically immediately.
AllenH

Member
Registered:
Posts: 43
Reply with quote  #7 
Ugh- just tried to reproduce it, and it appears to be operating correctly now. Appears to be intermittent- I'll have to catch it when it's acting up.
vaporlips

Member
Registered:
Posts: 48
Reply with quote  #8 
I just reproduced it, and caught the whole thing on video/screen capture.  Encoding the video, and will be uploading shortly.  The exact same thing happened.  No need to explain anymore, I recorded the computer screen, and also had a live feed camera of my dna200 device as well (on the screen).  Should be clear if I am doing something incorrectly, or what the problem is.
__________________
VaporLips Custom Box Mods
vaporlips

Member
Registered:
Posts: 48
Reply with quote  #9 
Here's a video recording of the whole event. 

I would love to hear if there was anything I am doing incorrectly, or what comes from this. 

Thank you!

__________________
VaporLips Custom Box Mods
AllenH

Member
Registered:
Posts: 43
Reply with quote  #10 
Hi Vaporlips and everyone,

Thanks for that video!  Yes, that's very similar to what I was experiencing.  Interestingly, I think you were having the cold-ohms question mark also- I'll have to go back in and look at the video (before the Kanthal build).  A few notes- it appears you're running on a windows machine, which is good- that confirms it's not the system software.  Second- I experienced this without removal of the atomizer in lock mode.  If I did remove the atomizer and replace it, I always said old coil when asked.  I just can't remember the series of steps to get the harsh hit- it appears you got one, but it might be due to changing the atomizer head without unlocking ohms?  Not sure if the board detects it should change everything... when I say new coil, it certainly unlocks the ohms for me (just couldn't tell if that was going on in the video for you).

I did just experience something that may be proper operation, but reminiscent of this.  Well... I'm fairly sure it's not proper operation... I got good vape for a bit, then hit temp protect (on the DNA40, I'm used to vaping through that to finish up the eliquid and start to dry out the cotton- LOL- only device that can do that!)... Then after the initial temp protection hit, I was immediately hitting the temp again.  So, I couldn't "work through" the temp protect and dry out the cotton more.  It can't possibly be all dry, and there's no way it's staying at 230 C (446 F).  I would expect it to drop at least a little.  I was able to save the graph for that.

Another interesting tidbit- but may be related to my OsX/Parallels/Win10Prev is that the system acknowledged the device when I plugged it in to catch the behavior.. but then the device refused to talk to the system.  I was able to rectify this by using another usb port on the other side of my laptop- so I am chalking that up to the system and not the device.

So, very similar experiences, but I didn't change atomizers, and also running different Os.  Oh- nice to see you using a tank also, I was using dual coal rda, however, at similar ohmage 0.081.

I'm going to try and get the 600+ temps again if possible, then revert to the old firmware to see if I experience the same thing.  [Although all this occurred within a few days of upgrading the firmware for me.]

Yup- just tried to take a vape again after a long time cooling (took a shower) and it still says it's hitting 230... so something's off.
vaporlips

Member
Registered:
Posts: 48
Reply with quote  #11 
Just to clarify - the video is demonstrating only that my device was hitting temp limit extremely fast.  It may appear that I got a burnt hit in the video, but I did not.  The "burnt hits" I got really could be due to a whole list of different causes, and I am not describing that as a symptom of "this bug". 
__________________
VaporLips Custom Box Mods
AllenH

Member
Registered:
Posts: 43
Reply with quote  #12 
Hi Vaporlips!  I agree- I can't add the burnt hits to this list either right now.  I need to reproduce it, and glad to hear that one wasn't one!

So, just like you, I can't get vapor after say the initial temp protection kicks in... even a few moments pause, then re-hit, nothing- hits temp protect immediately.

Thanks for the video!!  I'll be upping a graph of my temp protect hits soon.
AllenH

Member
Registered:
Posts: 43
Reply with quote  #13 
Been trying to use the DNA200 for the last few days here exclusively and this temp-protect thing is killing me.  Making for very frustrated vaping.  I get one puff, then have to wait a few minutes, then another puff... something is wrong with temp sensing with the ohms locked. [frown]
James

Avatar / Picture

Administrator
Registered:
Posts: 304
Reply with quote  #14 

Hmm. I will look into this.

Just out of curiosity though, why are you needing Ohm lock at all for normal vaping?
(Much less Override Ohms, which is for an even more specific case, and really for testing?)

Incidentally, what Atomizer Analyzer shows large the raw Ohms, not the 70 Fahrenheit (cold) ohms.


AllenH

Member
Registered:
Posts: 43
Reply with quote  #15 
Hi James- I should say that this bug has gotten a bit complex since Vaporlips submitted it.  We're both describing an ohms locked temp protection problem (see vaporlips earlier posts), and I also see a cold ohms ? in the atomizer analyzer.  But the temp protection is such a problem that we should probably start a different thread about it.  Also- I'm not using override ohms.  [And all functionality should be working regardless, right?]  I am however using ohm lock, because I've had issues with ohms going crazy and changing the vape.
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.