Jump to content

timbomfg

Members
  • Posts

    28
  • Joined

  • Last visited

    Never

Everything posted by timbomfg

  1. Ah... Kinda regretting getting shot of my VT200 now...
  2. Unless i'm misinformed, shouldn't it be doing its voltage/amperage calculations based off cold ohms though, and regulating using the hot-ohm calculation? 0.4ohm at 6v is still 90w and it never even reaches that. I can now confirm it plays ball fine on 3 different Joyetechs, the XCube2, the Sig150TC (in power only mode), and even my old ratty BT65
  3. I can keep on firing without vaping through it, and it never reaches 235degC or uses 100w Seems to stay in TC though, just not reaching limits even if i don't actually breath it in!?
  4. blueridgedog: Touché, none, however, my preheat profile is set to 75w, preheat of 0.5sec and a punch of "5" - Also setting my device to 0 preheat has the same result But it ALSO has this issue in power mode. That's what i consider the big issue further than the TC aspect. I'll grab a screenshot once i get in tonight as sadly my work take a dim view of me blowing clouds in the office.
  5. I don't think its the coil/vendor to blame. The unit works fine on 2 different Joyetech TC devices with the tcr set to the same value in TC mode, and also works fine in power mode. It's something to do with how the DNA200 board reads/works with tungsten i think.
  6. Even though i'm only firing at 75w?
  7. Ah, occurs out of temp mode too, straight power mode get the same result, OHMS climb to 0.60 ish, and then the mod reports "ohms too high"
  8. Search function left me wanting, so here's a post! This morning i recieved my Horizontech Krixus tank which uses a Tungsten coil embedded in cermaic. Pulled the CSV from SteamEngine and got the mod loaded up. 225degC @ 75w base, on a 0.37ohm coil Fires fine, but after a few minutes it starts saying "ohms too high" and shows the ohms have reached into the 0.60 ish territory Found a couple other vapers on FB experiencing similar issues. Using EScribe 1.042 with firmware 2016-02-23 on my VT133 Edit: Tried and got the same result both with the resistance locked and unlocked Thoughts/advice?
  9. Been another week, i'm happy with how the mod vapes. Largely in line with how my VT200 used to vape, and that was my only prior benchmark with this sorta mod. Can't say i've experienced a lack of punch compared to any other mod i own
  10. Update: Been running 0.005 for the last week or so with good results. Need to play with the case analytics further i think tho, as tc wavers a little more than my VT200 did when i step outside.
  11. Right, done that again, set mod resistance to 0, upload back to device, back into atomizer analyzer, and once i crank it down, its wavering between 0.004 and 0.005 tho the blank is night and tight. Split the difference and call it 0.0045?
  12. As far as the documentation seems to imply, cold ohms IS raw ohms. It's the base ohm of the item in question. It fluctuated whilst the tool was still loose, but the moment it got to the point of being "tight" it held 0.004
  13. I'm afraid that's going to be your answer mostly i think. I managed to find one for the LG HG2s which are close, but tbh i plan on running the analyser to get a more solid value. What do you have set for your Wh and soft cutoff?
  14. Zero'd the mod by doing a hard-reset of the mod yeah
  15. I did, apologies i should of thought to share: http://signaturetips.com/calibration-tool-for-dna200-devices.html
  16. Update: expecting a 99.9% copper calibration tool within the next couple of days with any luck!
  17. As mentioned, i have no mod resistance set yet as i haven't bought/built a tool to test it. I'm running a fresh married pair of LG HG2s
  18. First few hours since running this, i'm getting a far more consistent vape, albeit at a lower temp than i would expect
  19. Right... Sat my VT133 in my server room for a few hours. Room is kept at 18degC using a fairly decent A/C unit, and the multiple readings around the room confirm the room temp. Unit left to run through its process over the 4 or so hours it takes, results are as follows:
  20. IIRC weren't there two different 510 connections over the course of the VT200s production run? Maybe that'd account for it? I have to say, based on what i'm seeing between a few other mods i own, my VT133 could be around 0.01 out. I need to either build a 510 blank to test, or see if the gent on here who makes the copper slugs with the M7x0.5 thread would ship the the United Kingdom of Tea and Scones.
  21. Checking my config for my old VT200, yeah i had 0.022 too Currently running the case analyser as it appears to be about 10degC out, causing all tc modes to run a bit rough!
×
×
  • Create New...