Jump to content

Sternenwolf

Members
  • Posts

    7
  • Joined

  • Last visited

Everything posted by Sternenwolf

  1. My Finder is working fine now for nearly two weeks … ☺️
  2. My black Finder was ok - it was my red one, which did not want to wake up. My four Paranormal were ok, too. I got my fix for testing in the German Colour DNA Group on Facebook. You should ask "admin" here, if he would be so kind to provide it here for download … 😉 All tests in Germany showed the bug fixed, as far as I know … My red Finder started fine after eight hours. I now let it rest 12 hours over night.
  3. Please be patient - there will be a firmware update to fix very soon. Some users are beta-testing … ☺️ P.S. Downgrade to "33" did not work for me …
  4. @Photo Pete I just tested an OBS Engine II on two Paranormals … same settings - same vape But the settings do not work the same on my Eleaf INVOKE with ArcticFox and 316L-TFR-curve… there same vape at 40°C less On my Wismec Presa with ArcticFox and 316L-DNA-Curve 40°C higher gives the same vape. This ist because no mod has a probe in the atomizer's chimney If you have 10 Mods and only 1 Atomizer, you can trim the 316L-settings on each mod - but if you have 10 different atomizers??? You have only 8 Profiles - and it is a lot of work. Just give it a few more clicks - and temperature is fine. My Ijoy Captains are for my 30mm atomizers - my Therions and Paranormals are for my Kylins and Aromamizer Supreme - my Finders are for my Triple RTAs - my Triades are for some other atomizers - as my old Reuleaux and other older mods. The DNA250C-mods are the best I have ever vaped with - very exact measuring of resistance … and very fine mods. But you can have a very fine vape with non-DNA-mods, too …
  5. @Photo Pete Hi … if I understand your "problem" the right way: There is no sensor for temperature in any mod … and not in any atomizer. Temperature Control only concearns the heating wire. If you are using five different atomizers, you will have five different vapes at the same chosen "temperature". If you open or close the airflow, this will change the temperature of the vape … for example ... I am using ArcticFox-Firmware, too … but AF does not make the sensors for resistance or 510 connection in a mod any better - it uses them in a better way to calculate differences of resistence better … and this is called "temperature control" I have a dozen DNA mods and three dozen atomizers - six mods with ArcticFox - and 10 with normal firmware. The vapes are all different if I use a single atomizer at 240 ° C alternately in turns at all mods.
  6. So sorry Guys and Girls nothing so far is really solving the problem … and I am not sure, that a real "Deep Sleep function" really exists My way by disable the "lock function" (which I missunderstood as "Deep Sleep" in cause of my small English) only "worked" for one and a half day - and the "not waking up" came back after next following night. The box always wakes up when USB is plugged in … It does not matter how much the batteries are charged ... I do not think either, that there is a fault in the battery compartment The mod keeps working fine al long as I keep using it at least every 30 minutes Meanwhile I think, the fault can not get fixed by a new firmware update … and the box needs a new DNA-board instead. So I informed my Vendor (3Fvape). I sent a video, how the mod does not start with two sets of fully charged batteries, then start once - and does not start again with the other set. Then the box started with the first set - and no start with the set, that worked a minute before …
  7. I just got two Finder DNA250C - a red and a black one. Only the RED one shows the "I do not want to wake up"-fault. red: Version 1.1 SP33.2 INT - produced May 4, 2018 black: - Version 1.1 SP33 INT - produced March 23, 2018 First of all I disabled "deep sleep" in escribe and loaded to device … did not solve the problem ... Loaded default theme of my Paranormals, which do not show this fault … did not solve the problem enabled and disabled "deep sleep" in escribe again and loaded to device - took battery off and put it back - let device start … Fault of "not waking up from deep sleep" did not show up again … fine 😁
×
×
  • Create New...