E-1 error

Status
Not open for further replies.

Envithyx

Super Member
ECF Veteran
Verified Member
Feb 25, 2012
525
996
NorCal
When you say you lowered the ohms, did you mean voltage?

E1 either means a short or you're pushing too many amps (high volts on a low ohm coil).

Either try another carto, or lower the volts to 2.9 and work your way up and find the limit. Not sure if you have a v1 or a v2, but if it's a v2 then more than likely it's the carto. If it is the carto, with all the protection that Provari has built in, it may just be protecting you where as the kGo doesn't care. The carto may not be 100% damaged but heading towards failure.
 

kidbeaster

Super Member
ECF Veteran
Verified Member
Jan 8, 2012
374
140
61
New Auburn, WI
Sorry it took so long to get back. I was up pretty late last night gaming with some friends on Xbox live. I've used the tank on my KGO last night and all went well. After getting back to my post and reading the responses I put the tank back on my V2 (1 week old) provari. Now its working without any problems. I have it set at 4 volts.

Now I'm baffled as to why I would get an E-1 error when I first tried using the tank carto yesterday and now it works fine. What gives?
 

Envithyx

Super Member
ECF Veteran
Verified Member
Feb 25, 2012
525
996
NorCal
Wanted to add that your carto could be getting shorted after being screwed on to the Provari, and not shorting on the kGo. Try screwing the carto on less tight and see if it makes a difference. Could be that the pin on the Provari is overly engaging the contact point of your carto and causing it to short out (damaging the insulation).

It would also be wise to test the resistance of your carto with the Provari and see what it registers. If it's showing a really low #, then try another carto.

EDIT: I added this post before your post posted to my screen. Interesting it works now. Perhaps it just didn't make good contact the first time around.
 

Slurp812

Super Member
ECF Veteran
Jun 18, 2011
431
122
63
Northwest Ohio
Sorry it took so long to get back. I was up pretty late last night gaming with some friends on Xbox live. I've used the tank on my KGO last night and all went well. After getting back to my post and reading the responses I put the tank back on my V2 (1 week old) provari. Now its working without any problems. I have it set at 4 volts.

Now I'm baffled as to why I would get an E-1 error when I first tried using the tank carto yesterday and now it works fine. What gives?

How is the spring? Mine was a bit pushed down, and would sometimes act a bit flaky. Anyway I streched it out a bit, and now it touched the battery before I get the cap threadded on....
 

kidbeaster

Super Member
ECF Veteran
Verified Member
Jan 8, 2012
374
140
61
New Auburn, WI
When I switched over to the provari with my tank this morning it started working. This afternoon I started to get a dry slight hint of a burnt taste to it. And then a couple of puffs later I got the E-1. I checked the atomizer setting and it read 1.3...wtf? I did a bunch of non firing hits to juice up the carto. Then it vaped fine. I did another atomizer check and it read 1.6. Any thoughts?
 

AmnNate

Super Member
ECF Veteran
Verified Member
Sep 2, 2010
495
714
Charleston, SC
I'd say use a new carto. At $1-2, they're not worth messing anything up over it. It sounds like the Provari is protecting itself from a messed up carto. I'd just toss it and not worry too much about it. You may have just got a dud. If it does this with another carto from the same batch, then you may have to investigate further. Then again, I've heard tales of people getting 3 duds in a pack of 5. Just sayin.
 

donnah

Vaping Master
ECF Veteran
Verified Member
Aug 22, 2010
4,470
4,463
Albemarle, North Carolina
I noticed something like this once. I let a carto get too dry and got an error. I would imagine what's happening is the ohms drop when the carto starts to burn dry and the provari is just protecting itself like its supposed to. This is why we paid the big bucks!

At 4v on a 1.5 atty you're hitting the amp ceiling already.
 
Status
Not open for further replies.

Users who are viewing this thread