VapingBad
-
Posts
2,710 -
Joined
-
Last visited
-
Days Won
30
Content Type
Profiles
Forums
Downloads
Posts posted by VapingBad
-
-
The results look good, I wonder why you used that profile, if I recall correctly it was just for some untypical stainless steel in the early days and most wire is better with the stock profile.
-
It is probably the battery or a connection issue between the battery and board, I seem to remember on some of these there was a screw near the battery cap that came loose and caused issues there is a thread on here somewhere about that, sorry don't have the device or time to search right now.
-
It should be fine at those resistances, I would check you are not getting too much voltage drop on the battery or ground connections - IE good solid and tight connections, hard to be more specific online.
-
1
-
-
Replay does override the max temp setting, but I think the case that has not been mentioned is using a temp limited puff as your seed puff. This is a bit of an edge case and most of the time if you have temp control working well I would stick with that, but adding replay can help with set ups with less stable resistance.
-
Using all SS316 would probably be best, any temp sensing wire, but not mixing metals will give you the best results.
-
I had it with fixed battery when connecting the screen after connecting the battery, disconnecting the battery and reconnecting solved it.
-
1
-
-
15 minutes ago, amirdna250 said:
hey so how do start an RMA because the same thing is happing to mine with my vapor shark evolv dan 250 is saying warranty service
To start an RMA https://helpdesk.evolvapor.com/index.php?a=add&category=1
-
You will need the international version, enable manufacture UI setting in EScribe then you will be able to access the max power setting.
-
No, the soft cell cut off is per cell not for all the cells together. It is hitting the limit because it is a 2 cell mod, there is nothing you can do in Escribe it is the max output voltage limit for 2 cells comping into effect.
-
I have not seen any tutorials, looking at themes that have the feature you want is probably the best option.
The status field is for system messages and text you put in the status fields for a field and then it is shown when in focus, I don't think you can change the *. You could have a condition like when charging and display board temp when true and status when false, you need a condition for fields to occupy the same area.
-
Yas try turning the warmth down on the profile, but it me it sounds like a connection issue somewhere, I havn't tried locking ohms with replay but it may help with your set up.
-
6 hours ago, Pur3impulse said:
@James I don't know how to go back to old versions. And I'm running international windows. I doubt its software, or I wouldn't b the only one, that's what's so confusing, it ACTS time software, cause scribe used to work AND my cable and connection currently work. But if its not hardware, y am I the only one with the issue?
Just installing the previous versions of EScribe should do it.
-
Ni80 is the problem, it is not a temp sensing material, if it is a 250C you could try change this setting to dubious as it allows some coils that don't behave as expected to work, but it is a small margin so I doubt it would help you.
-
I just pull cold air through by taking a couple of puffs not firing after changing the battery, that brings the coil close to room temp.
-
Working great for me with duel triple twisted ss on the 75C and dual stapled ss claptons on the 250C, 400 W preheat really brings those big coils to life.
-
This is ss in replay with temp protection turned off, but I did record the puff with temp protec on.
-
You have watts selected as the material type, so disabling temp fields, but you should be able to see it is not level power regulation and yes it should give dry hit protection.
-
There is are 3 fields to do with Replay:
Atomizer - Replay : replays the last puff, like a record and playback button
Atomizer - Can Replay : enables replay for the profile
Atomizer - Can Replay Now : tells you if the last vape had enough resistance to record and replay
You can use these to build conditions.
-
You need temp sensing wire like stainless steel, Ni, Ti or NiFe for replay to work, Nichrome (Ni80) and Kanthal are not going to work.
-
It recreates the temp profile of the vape you record, vape while connected to device monitor and you will see it. You can use replay and temp protection together, only really a benefit if you have coils/atties that have unstable resistant. The benefit of replay is you get most of the benefits of temp protection without having to set that up.
-
Yes only the C variants AFAIK
-
Just load the previous config fiel you saved before you did that and upload to device, if you never saved there may be an original Paranormal config posted here, you would lose profile changes you made though.
-
It is how much extra power you let the board provide when the coil is cold. You may want it higher if you recorded a puff at the end of a series when the coil and atty were warm to start with or you may want it lower if you recorded a puff from cold.
-
2
-
-
9 hours ago, Farhan said:
Thanks for the help. I did try that and the screen disconnect was showing around 0.30+. So I am guessing the screen is busted?If i had dropped it or something it would be understandable. That is very strange though for such an expensive Mod. Now I am stuck with it as I am in the middle east and there is no way that I could get that fixed. What a bummer.
0.30, surly that is 30 it should be a whole number, it just counts the number of times the board can't communicate with the screen. It is most likely an assemble fault that the screen cable was not kept away from the fire button or it could be the cable has come loose or the connection got dirty, but these 2 are far rarer. You should be able to get it fixed under the mod manufactures warranty.
EScribe no longer working on Mac
in EScribe, Software and Firmware
Posted
Hello Scott B, sounds like mac update changed or blocked something, rolling back the update if you can would probably work, but is a bad solution. I would give it a few days and if no update are forthcoming raise a support ticket to ensure it gets in the queue. Thanks for teaching me the basics