MacVap

Here are two graphs from device monitor, one when cold (was working until seconds ago, just refilled e-juice), and one after I "persuaded" it to work by raising the temp to 230 C. Both graphs are at 170 C, didn't include the temp set and many other parameters for clarity. Interestingly, I can't see the temperature on the graph, not sure what is happening here, I think I saw it earlier. Maybe it really doesn't detect the coil as temp sensing? Just in case, I am also attaching the profile settings. Mod resistance is 0,0065 ohms. Cold.csv Warm.csv As a side note, not connected (only) to this case, I notice that the room temperature as reported by all my DNA devices is always around 6 to 8 degrees Celsius higher than actual. I have performed thermal calibration on all of them and after that they work better in temperature mode, so that tells me that I am not doing something terribly wrong.

I haven't tried to revert to the old firmware. I will try it now. No puffs shorter than 1 second. In fact, when this started to happen, I tried taking very long puffs (of air) in hope to cool the coil and to force it to start working normally. Very rarely it succeeds, but it is very slow (gives low temperature of vapor and then I have to increase the temperature anyway). Another thing I noticed, when I change material, it always asks me if it's a new coil (it detects the difference). This time the difference is bigger, as opposed to when I "measure resistance" in Escribe. This coil (double coil in fact, in parallel) is 0,36 ohms and then it asks me if this is 0,44 ohms. Heated after some puffs, of course. When I measure resistance in Escribe it goes up to around 0,39 ohms. Edit: With the old firmware it reverted to the old behavior, it doesn't have this gap in temperature to start, but everything is too hot, even at 100 deg Celsius. This started soon before I upgraded, in fact, that's why I looked in the forum if anyone noticed that behavior and I saw there is a new firmware. With the new firmware, now I noticed (and it happenned before, but I couldn't read the small letters) it says "Temperature protect" when I start (after a refill) at low-ish temperature (around 140 Celsius), but when I increase it to say around 230 C it starts working. This "Temperature protect" message goes away at any temperature after two or three tries, but it doesn't start heating regardless. And of course, when it starts working at 230 C it's very hot, that's the behavior I mentioned in my previous post. Most probably there is something wrong with my atomizer, I will dismantle it when I have backup atomizer up and running. Looking for shorts, wash it and make a fresh coil. But this behavior is consistent. In the meantime, I re-downloaded the material (SS 317L) from Steam Engine and the numbers in the CSV are differrent, maybe they updated it, but the behavior in my setup hasn't changed. The wire is from a reputable vendor (zivipf.de) and I think that isn't a problem.

I think this firmware (1_1_SP55_1_INT.sw-service) broke "Temp Sensing Detect" for me, previously was working fine. Device: DNA 400 Color, Hammer Of God. Now, when I refill the atomizer with liquid (I guess it cools it down), it doesn't start heating at the set temperature, at which was working fine up to that moment. I need to raise temperature for around 30 deg. C or more for the device to start heating. Then after few puffs the vapor becomes too hot and I need to return to the original temperature. Nothing was changed except for the firmware upgrade, the atomizer was never removed from the device and even it has the same coil (sometimes dry burned and changed cotton, of course). The material is 317L Haywire from steam-engine.org, which I repeat, was working fine before. Preheat on or off, it doesn't matter. On the graph the first few puffs look like normal, like the temperature is rising and maintaning, but in reality the coil isn't heated and I draw only cool air. If I don't raise the temperature, I never get any vapor, no matter how hard I draw. To my amateur untrained eye it looks like it doesn't update the coil resistance. But on the other hand, when I click on "measure ohms", although there is a difference of 0,03 ohms or more, that doesn't change the behavior. Neither locking ohms does. I am sure the device is set up properly, Mod Resistance was measured with a copper tool, also Case Analyzer was done, but most importantly, it was working fine before the firmware upgrade. I upgraded it just recently, around ten days ago. Edit: Yes, the coil is tight. In fact, when it started acting up, that was the first thing I thought of, so I tightened the coil with a longer screwdriver, nearly to the point of breaking the threads, but it changed nothing.

If for some reason you can't change profiles or you don't have any non-TC profiles: 1. Lock the device (press the fire button 5 times) 2. Then hold the + and - buttons for 5 seconds <- this will allow you to change temperature 3. While adjusting temperature, scroll up until the screen displays OFF

Unlock Ohms. No need for that.

First I'd check the battery, maybe it's worn out or of not the best quality. But other reasons are not excluded.

I use the tightening tool mentioned: https://www.fasttech.com/product/7462700 I have another one from there. Both work the same as the brass rod I threaded myself (they all show the same resistance).

I think DNA75 uses third-party charging board, or something like that, and doesn't know the charge current.

No, it was above TOP DOWNLOADS or higher. It was a big green button. I had seen it many times before. Now it isn't there. I don't have the yellow area since I am not an admin. OK, maybe it isn't so important. Edit: It wasn't START NEW TOPIC

No, it was in the forum list, above or below "Welcome to the new forum".

Since there is no subforum about the forum, I'm posting this here. I accidentaly clicked on the green button on the right. I have seen it before and I decided I don't want it, but because it is always present, it was inevitable for me to misclick it. Now I can't find it anywhere in the forum settings. I assume it will arrive in my mail, which I don't want to. I checked immediately, nothing has arrived yet, but I don't want to see unsolicited mail later. So where is the UNSUBSCRIBE button?

Thank you for your answers. Yes, I know how Replay works. Why was I believing there would be a temp limit? Maybe because of the requirement for a temp-sensing wire.

I still don't have a DNA C. I've watched many videos and read everything I could, but nowhere did I find the temperature limit of Replay mode; or, quite possiby, I got something wrong. If I'm not mistaken, Replay can be recorded and played even in Watts mode (furthermore, I think Replay in temp mode would be pointless - you'd be better off continuing to use temp mode; does it even exist in temp mode?), so what would be limit of maximum temperature reached, if any? I know Evolv pays great attention to safe temperatures in vaping, so I doubt it would be something irresponsible, but what is the actual number?

Here: You don't link to the page containing the image, but to the image itself and put it in [img ] tags. Edit: The forum editor is doing something or it doesn't allow external linking through https or Imgur doesn't allow that.

Hi, My Reuleaux DNA200 was sitting unused for two years. Now I started using it daily and it has frozen twice on me. I want to know the reason and whether I can prevent it or is it a sign of a dying board. I have done the "ribbon tuck" a long time ago and Screen Disconnects is always 0. It froze when connected to a PC, either for charging or for doing the Case Analyzer. It seems (I am not sure) it happenned when it was in deep sleep mode. It wouldn't react to the buttons, but firing still worked, and the screen was at around 5% brigthness (barely could see there is something on it) and wouldnt turn on. Escribe also froze after the end of the Case Analyzer (when I hit the Upload button) and I would have lost the data if I hadn't made a screenshot. During the analysis, it was working fine. Soft reset fixed it, it seems. But I had to disconnect and reconnect it. I also noticed that, during the Case Analyzer, the current when cooling wasn't zero, but a very low value (something like 0,00x Amps) and changing rapidly, only the last number. I don't know if it is just an imprecise reading or it is really leaking. Any thoughts are appreciated. Thank you.

Something must be done, it's too annoying.

Options > Units > Metric But there are still remaining in some places.

Not possible on this planet, at least without some serious equipment. What you're seeing is normal, it's just that DNA chip updates the display rapidly (very often), others don't tell you that but still do it. You could try the "Preheat with kanthal" trick (a topic somewhere on this forum) and/or lowering resistance within reason, but you'll never achieve a square wave.

@James, Why not include the driver in the early release versions of Escribe, so that they can be standalone? This way the earlier version has to be downloaded for the driver only. Also, I think using the term "Service Pack" for everything - both as a version number and as a description of a beta/service release - is kinda confusing for less technically inclined persons. The situation with the downloads currently is clear because there is no prerelease, but it was more complicated before. I hope it is a sign it will stay that way.

Not a big deal, just something I noticed (I don't plug this mod often because it's on Power mode for tootle puffin'). As you can see, at the beginning it always overshoots (the green line). I'm not ready to tear it down and build lower resistance/higher Wattage setup yet, I am just curious is it normal.

@James The firewall is silent now. Thank you.

Thank you very much James, but maybe you shouldn't have if it might create other problems/problems for others. Mine is a fringe case anyway, and it would be enough for me to open the firewall for Escribe to localhost. I just didn't investigate further to which address it connected to, I thought it was a compiler or .Net framework bug (or telemetry).

It's Look'N'Stop firewall, yeah, quite old and uncommon, but that's why I like it, because potential rogue programs wouldn't expect it. Win7 x64 btw. The thing is, Escribe didn't do this until this last version and there were no problems with it.

Why does Escribe 2.0 SP4.2 need access to the Internet for every little thing? The firewall alerts me it wants access with most of the operations (Device Monitor, Upload settings... I haven't tried many more, but these are some of the most important ones). If I block it with firewall, I get this screen: "Continue" salvages the program and it still works, but (for example) it still doesn't enter Device Monitor. If I unblock it with the firewall it works as it nothing happened. The blocking/unblocking acts as a toggle - it immediately cripples or heals the program, even in the same instance (if it is still running).\ I hope this is just a compiler bug or maybe something on my side, but I don't see what could it be. I have installed most of the early versions and none did this.

I've been burned by VW devices in the past (my fault, inconsistent connection) enough times that I'd want to have at least 1 (out of 10, for example) VV device.