Mine is Y08040.
eVic-VT mini?
- Thread starter Daisychainvaper
- Start date
- th_trl_thread_readers 0
- Status
Mine is Y08040.
Seriously just shut it if you can't help,and can't accept the fact that people are having issues
Sent from my AMOI N820 using Tapatalk
I also have mine set at 530 on a 0.37 Ti build. Nice warm vape. With Ni200 anything over 480 was too hot.
You must have your magnet in backwards because mine points away from the south.
Mine is J08020, I sent an email to Joyetech support I haven't filled out the forms they sent me.
Sent from my SAMSUNG-SM-N920A using Tapatalk
Sent from my SAMSUNG-SM-N920A using Tapatalk
yup same thing but mine is .12 @45 watts,
weird..
really weird..
ni mode,have not tried yet,
just ti mode,since i do ti builds.
Maybe I missed a few posts but didn't you guys figure out a few pages back that this ni200 problem occurred only with builds below 0.19 ohm and anything above that didn't have the problem. Not being contrary, just trying to understand as I have only used the vtc w/ stock coils.
I have the same problem with the factory Ti heads so, at least for me, the problem isn't specific to nickel. Additionally, the specs state the mod should work with TC resistances as low as 0.05.
But it is good with builds above 0.19ohm in both modes? What did Joyetech say when you told them about it? Stock coils still going strong but CLR heads & TiT1 are slowly making their way from china so I be trying my hand at building them soon.
cant say yet,
since i mostly do dual coils.
its hard to fit in right now.will try a bit later and see on a thinner wire
Just trying to understand the quirks of this mod with this issue so I can tailor the resistance of my builds to work within the range of the mods current capabilities while you guys fight the good fight with Joyetech to fix the quirks that are present.
It sounds like the whole problem occurs when the mod enters a soft sleep mode since it works fine when atty is first attached. Correct?
They say the IStick 40w TC has the same issue.
It sounds like the whole problem occurs when the mod enters a soft sleep mode since it works fine when atty is first attached. Correct?
They say the IStick 40w TC has the same issue.
Hey @CaliVaper how it the Spider Silk holding up?Got my Spider Silk (26g) in the mail the other day. Here's my first Ti build & first ever TC build period. Luckily I haven't had any of the issues some of you guys have mentioned. In the picture you will see the VTC set @ 440°F. I bumped it down to 380°F and that seems to be ideal for this RTA/juice. I take relatively short mouth to lung hits ~2s and don't often "activate" TC with how its set now. I find that if I lower it to 350°F I start activating the TC, and so far it has been working just as it should. I'm running the factory installed firmware v1.02. I was going to upgrade, and I probably will sooner rather than later, but part of me still feels like "if it aint broke, don't fix it". One odd thing is, I've yet to see the screen that asks me if I have a new atty, no matter what I do... lock/unlock, unlock then remove atty and fire, etc.
This 26g spider silk is super easy to work with. I was able to almost perfectly straighten the length of wire I cut just by running it through my fingers a few times. Also, after wrapping the coil, there was virtually zero recoil/unwinding.
Have you encountered any problems with the TC on the mini since you have been using it and are you still using Firmware 1.02?
will upodate you if i get a good build running above 0.20
once i get thinner wires.
hard to make a decent above 0.15 ohms on a 0.50mm wire,titanium
For those who have done a FW upgrade.
When you plug the mini in to your computer the software will give you its hardware version as well as the firmware version. I am just wondering if the hardware version number is the same for all of us. I'll post mine later when I get home.
When you plug the mini in to your computer the software will give you its hardware version as well as the firmware version. I am just wondering if the hardware version number is the same for all of us. I'll post mine later when I get home.
Anyone using RDAs experiencing the same problem? Very weird indeed. But this is probably the reason behind upgradable firmware so that when this kind of stuff happens they can fix it. This is the first release after all.
I'm really bummed that so many of you are having this problem now, with this mod. A little surprised too, since it got such glowing reviews from the first few that got them. Could they have changed something in their manufacturing process or something to cause these problems? Maybe they switched to a different chip supplier? Seems to be a new problem happening with the later batches, so maybe something to bring up with Joyetech. I'd bring it up to them myself, but I don't have one to complain about yet. 
- Status
Similar threads
