Just out of curiosity, 1, is there any way you might have confused your wire? 2. have you cross checked the resistance on a meter? 3.have you tried a different atty on your mod, and your atty on a different TC mod? 4 Does the mod still work on either nickle OR Ti? 5 is the firmware upgradable (I'm not familiar with your mod) and if so, do you have the most current version?Not trying to be an ahole, sometimes I get stumped, and the problem is staring me in the face.
In any case those should nail down whether its the mod or not
1 It's spools
2 Pretty much impossible when dealing with wire that has a resistance that's near what the internal resistance of the multi-meter is. It calculates right with Steam Engine and is confirmed on other TC mods.
3 Yes, stated above. Also multiple attys, decks and working builds from other mods.
4 It's a Ni only mod. By work do you mean fire? Yes it starts fires very well. What it doesn't do is control the temperature of the wire to avoid starting fires

It works better with Ti than with Ni, but it still builds heat above the setting the longer it's hit.
5 I hope so but because I want a Ti mode. I don't think this is a firmware problem or there would be more reports of it. I think it's a bad chip, extra/cold solder, bad connection or mailman field goal practice (the box for the VTC in the same bad was smashed but no damage to the Sig box).
The way it's acting I'd think it was another fake TC like the Smok M80, except I've seen video of it not burning cotton and dropping to 0v with dry cotton.
Not wanting to beat a dead horse - but you did lock it in by pressing the fire button and the down button at the same time (I'm sure you did, but just wanted to be absolutely sure, since it's such a common problem!)
If so, sounds like it's time for a warranty exchange. I had an Istick 40 tc that changed resistance even after locking and ended up being useless in tc mode.
Yep, the above picture was after using it with a TI, it was locked at .36Ω I had to relock it with the Ni to get it to .06Ω. I would think I was hitting fire a split second before down but the IPV4 agrees with all the coil lock ins I've tried on it.
It's also not acting consistent. For the picture was lit solid. It was just very slight red solid, dropping to .71v and pretty much staying. Now it's back to glowing and pulsating. The not pulsing has started since I've been "resetting" to see the firmware revision.
I guess that could be a 510 connection issue, reads right but changes when it fires. I'd think that would act the opposite though. Spring feels heavy enough. Wish they made it easier to see the wire connections.