It was still Nada, same exact figures as you've got there :/
On a lighter note it does produce a vapable hit at 580°F+.
On a lighter note it does produce a vapable hit at 580°F+.
Hmm, I've raised my ohms reading to .39 now and it has much improved, still not 100% but at 450°F I'm getting a decent enough hit. I have a feeling there is something wrong with either the 510 or the amount of power it gives out.
I'm still going to reinstall the software using the old tool, something isn't working somewhere.
What I have noticed with the beta tool is that the third time's the charm. I did it three times and on the third time, the upgrade "took" and showed 1.092.Tonight I finally upgraded my Smok to 1.092. Not going great so far.
First of all I used the new Upgrade Tool. Which is a hell of a lot nicer than the old one, given that the old one was simply the developer tool provided by the chip manufacturer. Terrible end-user experience. The new one is incredibly basic but if it works it will be fine.
Unfortunately, it didn't work. It downloaded the new firmware OK, then went through all the motions of upgrading - three steps, followed by PASS. Turning on my Smok, I found that it had been reset to factory settings, but was still on FW 1.08. Repeated the process, same result.
I had to go back to the original tool - and it's lucky I still had it installed and knew how to use it, because they appear to have removed all mention of it from their site.
So I've got 1.092 on now. Unfortunately, I can't use TC yet - because I can't login to the Android app to enable the "Upgradation". Once again Smok demonstrates the utter stupidity of locking the use of essential features to an external app. Every time I try and login to the app, I just get "Unknown Error, please contact administrator." Which is nice.
If anyone has their phone/tablet and Dumb Bec to hand, could you see if you can login OK? So I know if it's just me or a global problem. It's definitely not a network issue on my Android install, as all other network stuff is working fine.
On the upside, I was pleased to see in the release notes for 1.092 mention of fixing underheating. Though it said it was for Ni200 mode. Have they fixed underheating for Ni200 but not Titanium? The mind boggles. But maybe Titanium was already fixed in an earlier update? I didn't look at the notes for 1.09 or 1.091.
The saga continues. Sooner or later this could be a really nice, capable mod..
What I have noticed with the beta tool is that the third time's the charm. I did it three times and on the third time, the upgrade "took" and showed 1.092.
Really? Wow, it's so bad it's almost.. no, it's just bad. I only tried twice for the 1.092 update. I'll try harder next time
Did you first go to Download under Settings on your mod? That was suggested earlier as a difference. Though to be honest I am doubtful that that's doing anything different.
Anyway hopefully there will be another FW update soon to try again on SS so I'll try the new tool three times and if that still doesn't work I'll then try first going to Download on the mod.
Ok, I'll add some more wierdness to this situation with my latest experiences. Bought some 26 gauge ti1 wire yesterday and couldn't get it to do squat initially. Then I talked to my friend that works at a local vape shop who has had NO, I repeat NO problems whatsoever with the XCube 2. We put our heads together and figured that my issue must be my lack of having done the proper upgrade for Ti and Stainless through the bluetooth app. It wouldn't enable the profiles at all. That said, while I only have Ni in my firmware listings (Ti and Stainless won't show up at all), Ti vapes respectably on the Ni coefficient, and for me... fine tuning meant increasing the initial resistance by about half an ohm.
This is getting strange.
Did you make sure you held down the firing bar once you clicked on the "Check version" button in the update tool? You can't let that thing go until you're done once you get past that point.
Vaping Titanium on the Ni200 profile without temperature adjustment will certainly give a good vape, but it won't be temperature controlled. You will get burnt hits. If you've got the mod set to 230°C the actual achieved temperature - at least on a normal mod, obviously the Smok is less predictable - will be near 400°C. This does serve to prevent the Titanium coil being destroyed by taking it above 600°C, but doesn't prevent dry hits or really count as TC.
Titanium can be vaped on a normal Ni200 profile no problem - I have a number of Ni200-only mods on which I vape Titanium. You need a temperature offset of 90-100°C. So instead of 230°C, set 130-140°C. On the Smok, perhaps up to 150°C.
Or if you were to adjust the TCR down, say to the minimum 0.004, the offset would be much smaller.
Though with the Smok I feel compelled to caveat that this is all theory and what works on other mods. Who knows what the Smok might do!
The Check Version thing doesn't communicate with the mod so far as I can see - it checks the Smok site and downloads the latest FW version, if not already present. You can do it any time, with no mod connected.
After doing Check Version to get the FW downloaded, I then removed my batteries, plugged the mod in via USB, held fire down and kept it held down while clicking Connect, then Upgrade, then Disconnect. Then released fire.
I've got some pre-made Nickel heads that have been gathering dust since I just coil myself with 30AWG in my Kayfun/ Squape/ Lemo etc. Just for giggles and a bit of a test, I popped a new one in a subtank, primed it, tried it first on Sig 75W, worked well. Waited for it to cool, then put it on the xcube 2, yes to new coil, set at 420F- bang!!!! The coil literally fried!!! I can see in the gap between the base of the 'square bit' and the bottom of the head where the coil has melted like a fuse! It's a bit worrying!!
You make no mention of firmware version, or whether you set it on the XCube 2 to single or dual coils, or even whether or not you've done the upgrades through the bluetooth app, so that leaves a whole host of things that could have gone wrong. If you tried running it on the dual coil setting with a single coil, I'd imagine you'd get that result. It's not quite so simple as "plug and play" yet, with this device. Please be more careful in the future.
Well it's 1.091, SC, upgraded through the old tool that i've uploaded several pages back, i dont think you can just say "oh, user error".... I've been vaping a fair few years now and have never had a coil literally explode before!!! If it's happening to me and i'm doing it under controlled conditions, then just imagine how dangerous it could be if it was someone's first 'big mod', just saying really how flaky this thing is...
I think I understand what you're saying about the TC, Bloke. I've got the temp set at 410 though, and it displays up to about 380 till the atty starts getting dry, where it spikes to 410 and gives me the "temp protected" message and won't fire steadily until I refil it. I truly don't get dry hits and don't understand what's happening.
For the upgrade, I apologize, I should have been more detailed. First, set the download to ON in the options, then remove your batteries. THEN plug in the cables. Check version, then hold down the fire button and proceed with the upgrade and don't release the button until you're done. Any order other than that has given me a negative result. Again, I apologize for not being more clear. Hope this helps.
I don't have the xcube, but there's no way the mod should fire a dual coil differently to a single coil.You skipped the part about running a single coil in dual coil mode, actually you don't mention the TC setup menu at all and this is the part where I was referring to a "host of things that can go wrong".
Also, I repeat, you give the impression that you just put the coil that functioned on another device which used an entirely different firmware, onto the XCube 2 and expected everything to autodetect. Not a good idea with this device... yet.
Finally, I never said user error. It should be clear by now that there is plenty to be debugged in this device, and just tossing stuff onto the device to see what happens is unwise at best, user error or not. With all the variances in the misbehavior of this device, the only thing that is going to keep you safe is slow, careful testing... and even that comes with no guarantees. If you had started at a much lower temp and slowly increased, you'd likely have found a sweet spot, or at least learned something other than how to blow up a coil. One thing everyone here can agree on is that the TCR's aren't functioning as they should on this device. As I said in closing my last post to you... please be careful.
Edit: And yes, while I absolutely adore VW mode on the XCube 2, the TC mode is very squirrely at the moment, and that's probably putting it a bit too lightly.
I don't have the xcube, but there's no way the mod should fire a dual coil differently to a single coil.
Sent from my C6903 using Tapatalk
You skipped the part about running a single coil in dual coil mode, actually you don't mention the TC setup menu at all and this is the part where I was referring to a "host of things that can go wrong".
Also, I repeat, you give the impression that you just put the coil that functioned on another device which used an entirely different firmware, onto the XCube 2 and expected everything to autodetect. Not a good idea with this device... yet.
Finally, I never said user error. It should be clear by now that there is plenty to be debugged in this device, and just tossing stuff onto the device to see what happens is unwise at best, user error or not. With all the variances in the misbehavior of this device, the only thing that is going to keep you safe is slow, careful testing... and even that comes with no guarantees. If you had started at a much lower temp and slowly increased, you'd likely have found a sweet spot, or at least learned something other than how to blow up a coil. One thing everyone here can agree on is that the TCR's aren't functioning as they should on this device. As I said in closing my last post to you... please be careful.
Edit: And yes, while I absolutely adore VW mode on the XCube 2, the TC mode is very squirrely at the moment, and that's probably putting it a bit too lightly.
My mistake, sorry, I meant 1.092, it's hard to keep track of their firmware numbering scheme!!- I was just running a little test with a Ni200 coil at a known resistance to see if any improvement had been made to their TC implementation for Nickel... If anything I think they've turned the dial the other way, that's certainly how it feels now compared to the ipv d2 and sig 75, haven't done a cotton burn test to check for charring/ smoke though yet.
Do we think the sc and dc mode differentiation is actually doing anything? Can't recall if DSLabs chap did a test on that?...
Was just a little alarmed that it should literally 'pop' a coil at what many would consider to be 'average' temperature, and just posted as a bit of a cautionary tale![]()