Jump to content

Karsten

Members
  • Posts

    32
  • Joined

  • Last visited

Posts posted by Karsten

  1. I have the same issues with flavors in TC.  I prefer Ti coils over the SS for TC as they seem to provide a better flavor at temp than the SS does.  I've found some juices have a very narrow range of about 5 degrees F before some flavors really shine but push it another 5 degrees and a secondary flavor in the same juice starts tasting burnt (as you mentioned).

    Sometimes the only way to go is wattage with Kanthal though.

    However, I'm still a bit flummoxed by the new Crown III coils - I've done the math and unless I'm missing something big (like a logarithmic increase in resistance above a certain temp) it seems to me that running between 80W-90W (as recommended) puts the temp well into the danger range where eJuice starts to breakdown into nasty chemicals.  Normally I sent my temps all below 500 but this is the first coil where I've pushed it above that in an attempt to determine the difference between TC and watts and the resulting vape.

  2. Correct me if I'm wrong here - but my understanding is the TFR is used by the DNA200 to determine when it's hit the selected temperature by comparing the expected resistance (from the TFR) to the actual resistance being read during the firing. In which case, simply specifying the wire type isn't nearly enough to get an accurate curve...

  3. I'm a bit curious as to why there seems to be a discrepancy between TC and Watts on the Crown III 0.25Ohm Parallel SS316 Coil.  According to UWell the coil is recommended at 80W-90W in non-TC mode.  My TC is set to cap at 600F.  I'm currently using the coil in TC mode w/ an 80W punch @ 2sec set to 535F and while it jumps to 80W pre-heat when firing that immediately falls off to 40W (give or take a couple watts as it pulses) to maintain the 535F temp setting.  The materials curve is for straight SS316 (not 316L).

    If this is correct - then what temp would this thing be running at if I switched it over to Wattage mode and set it to 80W continuous?  Also, why the huge discrepancy?

  4. Happy to report that after going through both the one-step and all-at-once the DNA200 is performing flawlessly. So, it was either two bad boards in a row or one bad board that was just restored and sent back. Either way the guys at Evolv were great. While it would've been nice to have known what the issue was, it's not a requirement and I'm still a happy user.

  5. retird said:

    Understand wanting to not fry a new coil...Ti was too "touchy" for me so I don't use it... 

    It's a Ti Clapton. Best flavor of any material so far. Works great with right curve. Current plan is to bring it up on a basic kanthal and run it for a bit before loading up my Ni200, SS, and Ti's for TC. Debating on whether or not to just blast a full config at it, including screens first go around and basically say 'screw it' and fire up, or take it one step at a time until something either causes it to behave as before or I end up with a good ecig and functional DNA at same time...
  6. retird said:

    Are you going  to fire it and check it out before changing the ecig file?  Let us know how it goes...  I would probably maker sure I had a properly functioning device before making any changes, but that's just me... :)

    I did switch it to a default Ti profile and gave it about 3 or 4 quick presses. The screen stayed on but that's enough to confirm what I needed before creating a new ecig. I want to test it connected to the PC as well. Plus, I don't know what curve is in there for Ti and would rather not fry a good coil
  7. VapingBad said:

    The data capture from device monitor uses three decimal places in the CSV produced (0.001) but it will be higher internally, IDK the limit.  The precision show through EScribe or the mod screen will be far lower than the internal precision. EG: in Escribe you can set material profile data points to in 0.0001 steps, but internally it is 16 bits below the decimal point or increments of 0.0000152587890625. 

    That's insanely precise. Begs the question: just how accurate is it at that precision?
  8. VapingBad said:

    I can't see anything in the config that would explain your issue, I copied the screen settings to a DNA 200 and they work fine, I would decrease the fade in time to 0.25 myself.

    [image]

    I actually had them at .25 & .75 but changed to 1 & 1 as part of the testing
  9. txmonkey214 said:

    Glad it was an improvement. Try this: Go to Screens, and change all the settings for charging and running in both temp and wattage. Reset. Then, set them back where you want them. Reset. Rinse, lather, repeat!



    The "improvement" only lasted a couple hours.  Now the screen won't come on AT ALL whether charging or not, so it's now in the worst shape yet.

    Holy crap this is seriously annoying.

    I went back and re-did the earlier test but this time no effect.

    Also did a "Restore Defaults", upload, soft reset - still no screen.  Reloaded only the minimum necessary settings to fire a NI200 coil to the defaults, re-uploaded, soft reset - no screen.  Reloaded original .ecig, uploaded, soft reset, went back and changed screen settings, re-upload, soft reset - still no screens.
  10. Karsten said:

    Thanks! I'll give it a shot tomorrow morning! I've suspected its related to their implementation/configuration of the DNA200 firmware & eScribe. I included my .ecig file along with the initial Evolv RMA but I don't think they did anything with it. What I got back was either a replacement board that was reprogrammed on the 16th or they just reprogrammed what was in there on the same date. Will post results tomorrow after the test.



    Initial results:

    Doing exactly what you described was able to bring the screen back in all instances EXCEPT for when firing - so a major step forward from no screen except when plugged in, bringing me right back to the no screen when firing.

    At the very least I'll be able to change profiles now!

    Still wondering what's causing it to turn off while firing though.  Maybe when I've got a few hours to kill I'll start from default and change eScribe settings one at a time to see if it makes a difference - although, I've already tried reverting back to defaults and it still goes off when firing (so maybe something in firmware triggered by an eScribe setting that can't be undone w/o reprogramming the board from scratch?)
  11. txmonkey214 said:

    Sounds like a corrupted file. Try this: While plugged into escribe, go to "screen", and set all the light settings to 0%. Upload settings to device, soft reset, then go back to screen, raise all the settings to 100%, upload settings to device, soft reset, and see if that makes a difference. Ypu might have to reset a few times, to get the battery level off 0%. If that doesn't work, try it with hard reset. You have nothing to loose, but time.

    Thanks! I'll give it a shot tomorrow morning! I've suspected its related to their implementation/configuration of the DNA200 firmware & eScribe. I included my .ecig file along with the initial Evolv RMA but I don't think they did anything with it. What I got back was either a replacement board that was reprogrammed on the 16th or they just reprogrammed what was in there on the same date. Will post results tomorrow after the test.
  12. UPDATE:

    It took two weeks but I got my Lavabox back from Evolv last Thursday.

    Took it in to work, connected to eScribe, loaded my .ecig file and uploaded it to the box.

    Screwed on a tank and hit fire.

    Screen went dead.  Same as before.

    Stayed that way for about an hour and then...

    The screen is now OFF all the time EXCEPT for when charging.  If fired during charging (or changes made to temp/watts) the screen blanks again and won't come back on unless it's unplugged and replugged in to the charger or PC.

    When it's unplugged the screen NEVER comes on.

    Have replied multiple times to my original RMA ticket with EVOLV since Friday morning but so far zero response.

    Worried that I'll be without it again for another 2 weeks AND worried that it'll come back after those additional weeks STILL non-functional.

    Does anyone have any pointers as to what may be going on?  I've requested that info from EVOLV but have received nothing.  Nothing came back with the unit describing what was done either.

    VERY FRUSTRATED

  13. m4k3r said:



    No, they just fix them and give them back. My guess is the display ribbon cable. After taking one apart to get an idea of what's going on, the ribbon cable is tucked right behind the fire button. It works for a while but after getting tossed around for a few months it may be shifting positions causing them to cut out. Again, that's just an educated guess.

    Wouldn't that show up as a screen disconnect in escribe though?
×
×
  • Create New...