Jump to content

Jiyce

VT Member
  • Posts

    1
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Jiyce reacted to Earthling789 in iStick 20W can't settle on resistance   
    I've had an iStick since before Christmas, and it's worked beautifully with every tank or RTA I've put on it... with the exception of over-tightening a KPT3-mini on the adapter, causing a short (my fault, I know).

    Now, my newest iStick is starting to do weird things, in that I can attach any tank, and it will show the resistance (usually very accurately), and after I take a hit or two, I get a burnt taste... look down at the read-out, and suddenly the resistance is reading some rediculious Ohm reading... like 4.9 or 3.5.

    Once it reads the resistance incorrectly, huge voltage is applied to reach the Wattage I have set, which means I'm burning wicks (and my juice). I've had to re-wick my RTA twice in one day, and so far I've toasted a couple of Kanger and an Aspire coil... Fortunately, I've not toasted any juice (yet).

    If I set it down and wait a minute or two, press the button, and the resistance is correct again... WTH?

    I have re-seated attys, and even if they are fully seated, this occurs randomly. I've tapped the fire-button and watched the resistance change in the window (wild fluctuations).... wait a moment, tap again, and it will read correctly...

    I have tweaked/lifted the center pin, and it still occurs randomly, even right after adjusting the pin, installing a tank, and not touching anything.... a couple dozen hits are fine, then boom... excessive Voltage applied because it reads the resistance incorrectly (always too high)...

    I've tried using VV mode, and that has stopped the over-voltage issue, but it still reads the attty incorrectly at random times... and if it reads the atty at max Ohms, the Wattage will be below the threshold, causing it to not fire at all... so that's not helping much either... although it has stopped the burning of wicks

    Do I have a defective iStick, or what? Does anyone else notice this issue?
×
×
  • Create New...

Important Information

Terms of Use Privacy Policy Guidelines