AllenH

Hi guys! Well, it certainly could be the atty here. My dual coil ni200 28 ga wire builds are coming out around 0.08 ohms initially. They often creep up to around 0.13 ohms (when things got crazy hot). When I think I got my bad hit, it was showing 0.3 ohms. I'd like to mention that I've also seen the ohms change even when locked. So, even if my atty is at fault here, the ohms shouldn't creep up in that condition. My last build on my RDA was tight, no screw slipping, even after vaping the night before. After refinement in the evening with charging, that 0.08 had went up to 0.13, and was just not vapable in a non-locked ohm condition. This is on the beta mod box. I was getting burning tastes, which means the 230C the device was claiming was just not correct. The RDA was heating very fast in that condition. So, I retired the RDA for today's vaping. Decided to use my subtank mini today with lower wattage, and it's been acting fine since I changed the RTA this morning (0.15 build on the RBA deck, single coil). So, my RDA does appear to be worse at this than my RTA, but I haven't used my subtank before today, so we'll see if it experiences the same thing as my RDA. Thanks for everyone's thoughts here. I definitely understand this whole thing is a system, and that the chip can't control everything. I do question the 230C issue... should it really be hitting so high and still claiming 230 on the board? All coils are tight etc., and was cold from the overnight charge and overnight refinement.

Hi Vaporlips! I don't think the intended result is that it kills temp protection... I suspect it only removes refinement. So, once read, the ohms are kept/locked, and then future changes to resistance are used to calculate the temp. However, since temp protection works by way of the change of resistance with heat, I'm now wondering if there's a problem with the temp calculation with the ohms locked. Going to send you a note about your experiences here in pm - I'm experiencing a few more things that have got to be bugs- wondering if you have also. -A

Hi James, Ok, I've complicated things un-necessarily here, I apologize. I was attempting to give as much information as possible. I wanted to lock ohms because I was getting that standard creep with refinement seen in DNA40. At this time I think it may also be related to a bad hit I've had in the past (hence wanting to stop it) - but for now I can't say that it is. However, here are the issues that I see currently (at least one of them is similar to vaporlips): 1) With ohms locked, temp protection kicks in immediately after the first vape. Can practically not get a single vape after that initial temp protection. 2) related to (1) I sometimes see the locked ohms changing, even though they are locked. (hard to reproduce and catch) 3) related to (1) I sometimes see temp in temp-protection mode with ohms locked jump up to 600 F etc. (certainly not real temps) (also hard to reproduce and catch) 4) (I think I saw the same thing on vaporlips screen, but can't be sure) - in Atomizer Analyzer, if my ohms are locked previously, I can get no cold-ohms reading showing up- only a "?" appears in the "cold ohms" designated spot in the Atomizer Analyzer. Other things that have happened that likely need a different thread: 5) An insanely hot and dry vape that practically exploded in my mouth with a vape - however, I have been unable to reproduce this at this time. I recently updated the firmware to the latest firmware as of 7/13/15, and I have noticed that with Ohms *Unlocked* temp protection is working well, and I can vape through a good portion of remaining e-liquid on the cotton. This is what makes for an enjoyable device! However, this is definitely not the experience with Ohms Locked! (see the above, as well as vaporlips video)

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.

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.

I want to briefly confirm what MadModder also saw- I too saw ohms change even with the lock on. I wasn't sure if it was reading real-time or what at the time. I believe that may have been a precursor to a bad hit for me, but again, I can't be sure of that experience (other than the bad hit) - I often vape and drive. so, I can't pay too much attention to the mod at that time.

Hi John! It does appear that I get almost immediate temp protect on my RDA if I'm low enough in the temp control. When set at 230C (sorry for C- I think better in C for experiments = 446 F) I do get almost immediate temp protection if I've vaped to temp protection recently. So much so that I can't "work through" the absorbed e-liquid on the cotton in my coil (something I was doing with the DNA40 to eek out the last of the eliquid). I get a bit more flexibility if I up the temp protection to 235C (455 F) and can vape through the eliquid on the cotton a bit better than earlier. [Of course volume of the vape goes way down, but often it's just enough for me with strong tasting eliquids.] So, at least initially (didn't see any jumps to 600 temp here- this appears to be normal operation), it appears both firmware are operating the same. This thread likely should be combined with the other thread where vaporlips was having a similar problem.

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.

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.

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.

Hi Ryan! You mention that you have connectivity issues... I don't seem to be seeing that at all in Parallels. I seem to be able to stay connected and connect easily in Parallels, and now have it set to hit the windows side immediately by passing the option to connect to the mac side with the dna200 via usb. Seems to be working quite well. But- I thought it might be important to mention the setup- perhaps only mac users are experiencing problems- time will tell.

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.

Hi John, It looks like my version of escribe came with a 2015-06-26.sw-update and I think the latest release was the 2015-06-30.sw-update. Is that correct? (shows date modified of 7/1/15 on the last one). I have them in the application folder, and it does indeed allow me to select them. If those are correct, I'll run the other tests first, then revert the firmware, and see if things are solved with my latest experiences. Thanks for all your help this Sat. night! (you're obviously seriously devoted to this forum and the questions arising here! thank you for that!!) -A

Hey John, I appreciate it- thanks so much for your replies tonight. I was a bit bummed and even moved back to my DNA40 when I was having some trouble here. So, if I can solve this, that's excellent. (I'm already in love with this new device!) Let me load this up in a clean browser (where I don't block tracking and ads of various sorts)... yup, even in my clean firefox instance, I can't seem to find the firmware links. I apologize if they're there and I can't find them. [Or if there is a method to download them via escribe I'm not seeing... it all seemed automatic last time when the new firmware was available.] Thanks so much for your help with this!

Hi John, sorry for being such a newbie here... I don't see any firmware download links in the forum here. I also don't see a way to push an alternative firmware file within escribe to the device (only update firmware is in the menu system).

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!!

Hi John- thanks for the weekend reply! Is it easy to revert? Is the firmware available to download at different release points? Thanks!! It may be something I'm doing wrong. Will check the resistance as you suggest!

I also think I've experienced this with a nickel coil, no ohms locked. [Previously was ohms locked until I said it was a new coil.] Resistance was jumping up from a 0.08 dual coil build up to 0.31/32 during firing. I had a horrible burnt hit- even in temp protection (never kicked in). Latest firmware as of 7/11/15. Couple that with the locked ohms problem and temp protection kicking in immediately, I think something might be up with this firmware.

I'm also using Windows 10 Preview running on Parallels Desktop on OsX 10.10.4. [Another die-hard mac user... I leverage the unix subsystem for my research work.]

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