lordmage
-
Posts
35 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Downloads
Posts posted by lordmage
-
-
On 8/15/2019 at 5:21 PM, Wayneo said:
sorry its been awhile but no not completely it did slow them down for a time. i had to revert to full default theme for a bit and they still came back unless i downgraded version so i can only assume it maybe due to the battery wiring issue i read about with another member in the UK and i dont have spares to send this one in to be checked so im sitting a version down without them,
i tried both TC and non TC coils with default and without a default theme using the menu hack if needed and it seems the only clue to the issue has been possibly that with the higher version the tolerance for input power is a bit higher and that a poorly wired board may not sustain this level and it throws the error and resets.
-
Let me amend my earlier comments publicly so far on sp38 i have not had an issue after wayneo sent me some info... if you have this issue please check your theme screen settings use this thread as a suggeted fix https://forum.evolvapor.com/topic/70342-dna250c-error-press-up/?tab=comments#comment-932290
so far so good no error at all for me...
-
1
-
-
@Wayneo @nibo i am personally curious about what in sp38 makes it more sensitive to the "battery connect" "error up message vs SP 33. you would think a poor power connection would be a universal issue regardless of the software other than possible tolerance issues in the programing .. aka test point at pass at 1v fail at .95 v just an example god i dont know the ins and out of the programming.
-
On 7/22/2019 at 3:33 PM, Wayneo said:
What's not to like @nibo The soldering to their board needs repairing, and being in the EU, you've been given an EU authorized repair shop. Probably cheaper shipping for you, less customs and duties issues? No?
so does @nibopost above mean i should send my device in for repair if sp38 gives me the press up error paranormal 250C i have to sat on sp33 as noted above to not experience it
-
20 minutes ago, Wayneo said:
@nibo Did you ever try the default evolv theme with SP38? Earlier you said SP33 was working fine.
What SP are you running right now, where this is occurring?
For me sp38 default theme had it. Sp 33 does not
-
the dna device uses your local pc time when you upload a change at least it does for me. theme designer can change what and how things are displayed
-
Ваша информация верна при использовании ecribe и если у вас есть проблемы с морозостойкостью по умолчанию.
устройство установит базовую линию, когда вы ответите «да», если вы хотите установить ручное сопротивление, тогда просто загрузите новые числа без блокировки его ... использование режима блокировки - это когда RDa или бак делают катушку нестабильной, и вы хотите переопределить его на установленное количество
your information is correct when using ecribe and if you have issues with the default cold resistance.
the device will set the baseline when you answer yes if you wish to set a manual resistance then simply upload the new numbers with out locking it in... using the locking mode is when the RDa or tank makes the coil unstable and you want to override it to your set amount
блокировка омов - это бандаид для ошибочного или не идеального соединения. Единственная причина, по которой он находится в программном обеспечении, заключается в том, что конкуренция предлагает это, и многие просили об этом, и это выполнимо, поэтому evolv сделал это, но в идеале вам никогда не придется блокировать Омы. если вы часто получаете новую катушку с такими же сообщениями катушки, то, возможно, было бы лучше просто измерить сопротивление вашего мода, а затем добавить сопротивление к смещению, как описано, если ваше сопротивление прыгает вокруг достаточно, чтобы вам пришлось использовать блокировку сопротивления, тогда Существует проблема, которая должна быть исправлена.
locking the ohms is a bandaid for an erratic or less than ideal connection. only reason it's in the software is because the competition offers this and many have requested it and it is doable, so evolv did it, but ideally you shouldn't ever have to lock the ohms. if you get frequent new coil same coil msgs then it might be a better idea to just measure the resistance of your mod then add the resistance to the offset in escribe, if your resistance is jumping around enough that you need to use the resistance lock then there is a problem that should be corrected.
-
2
-
-
you may need to restore the default theme as well ... the theme could have been setup with a different menu
-
4 minutes ago, zark said:
Well, I give up, you are a genius, vape god. Just try to manually change the room temperature on an unlocked resistance. Goodbye I'm not interested with you.
Locking function is not locking the resistance. when the device asks "is this a new coil?" that is what you do with all coils the locking mode is a diagnostic tool used with escribe that others use to correct issues. Функция блокировки не блокирует сопротивление. когда устройство спрашивает "это новая катушка?" это то, что вы делаете со всеми катушками режим блокировки - это преимущество диагностики, используемое с ecribe, которое другие используют для устранения проблем.Funktsiya blokirovki ne blokiruyet soprotivleniye. kogda ustroystvo sprashivayet "eto novaya katushka?" eto to, chto vy delayete so vsemi katushkami rezhim blokirovki - eto preimushchestvo diagnostiki, ispol'zuyemoye s ecribe, kotoroye drugiye ispol'zuyut dlya ustraneniya problem.-
1
-
-
there is some term confusing going on...
if you are placing a room temp rda and coil onto a dna device the mod will ask if "is it a new coil?" yes,no,recheck depending on theme.
This is referred to others as locking or setting a base line...
Locking the ohms Function is only if the above is not working and confirmed in escribe
-
locking ohms is meant for unstable builds but normally i only lock ohms when i am sure it is a Certain cold ohm and the mod argues with me but in truth i have not locked an ohm in a long time. back then it was the RDA Post that was breaking and causing the ohms to jump. once i replaced the RDA no locking since.
-
1
-
-
15 minutes ago, Adam_Aves said:
Thanks @lordmage
That makes sense.
Why do you choose material watt for your ss coils? Do you not like to use SS as material with TC for those?
Ive noticed even with my ti coil that using: material watt and then replay works very well.
i find some SS coils work better under watts. with Ni and Ti since they are known to be temperamental i would rather have Full TC with replay vs no Tc and Replay with watts
-
12 hours ago, Adam_Aves said:
Hi @lordmage, I'm a little confused with replay but almost there
I'm using a triple titanium coil with a resistance that doesn't float. Its .35
If if I use my first profile which is replay, and leave the material on Watt, adjust to a good known wattage (in this case 35 watt) get a good puff and save it. Then replay that puff, is it doing some sort of temp control (utilizing replay)? or do I NEED to change the material to TI in this replay profile for any kind of temp control?
thanks
in your case as i under stand replay i would setup a separate TC profile for your TI coil and have it be replay mode on set your Temp and TC as desired and when you find a vape you like save it and replay will attempt to make it happen again. Replay will work with a Temp setting Replay is designed to give you that yummy vape again hence replay.
To answer your question it is merely taking the data of your vape and replaying it as best as it can. i mainly use Replay for SS coils in Watts material mode. if i use NI or TI then i setup my TC as we all know and turn replay on. find a vape i like and save it.
-
42 minutes ago, dwcraig1 said:
I thought that SP38 solved that problem.
Edit : this is the most stable for me in terms of the error code have yet to see it
Firmware Version: 1.1 SP33.2 INT -
i had the same issue then i went looking into mooch battery results https://www.facebook.com/batterymooch/posts/ive-received-a-few-inquiries-regarding-hohmtechs-use-of-my-test-results-for-thei/1829482420674669/ in short i lowered my overall mah total in escribe and adjusted the battery curve a bit to match his comments and testing results and i find it much closer
-
1
-
-
first confirm your coils are tight...
second confirm your goon has a solid connection to the mod.
third be sure to set a cold resistance before you start to dial in a replay
forth are you getting a new coil message when under replay when it will not work...
if yes it suggest your coil resistance is all over the place and may need adjusted somewhere... try above again...
if no will this work under 316L TC material vs replay.... if yes it suggest your coil should accept replay as is...
have you tried it under TC and seeing how your temp curves look. that could tell you where the issue is.
-
i had to revert to core sp 35 i think to not see the message on my 250c
-
i can also confirm the Error press up happening with SP38
mod is the lost vape 250c
for me i have seen it happen more with inactivity and a few when sending profile updates my device was from september going back to Core it has yet to happen. the device was first updated then used until the error was frequent between uses . after reverting it has yet to happen with the same use pattern and all.
-
update sp3 loaded and running the only comment i can say is that while using device monitor to change a setting say temapture in this case i still have to click ok rather then enter. but i do love the indepente use
-
http://www.steam-engine.org/#wirewizard and load the dna version im afraid besides from some battery profiles and dna200 groups on fb and what not is all down to each user to set.
-
-
Jaquith said:
[QUOTE=PLANETGETLOW]Im about to move from TI to SS....getting 28g and 24G in. I would appreciate it if the V4 csv can be uploaded so i can use it
Here's the ensemble of all the UD SS316L Profiles - http://www.filedropper.com/udss316ltcprofiles
As the Version goes up, so do the temperatures; I generally use V3 or V3.5 myself.[/QUOTE]
would you sir please be so kind to reupload the cast once again filedropper links dont last to long. -
so far big plus on the temp dominate choice, material storage , the added battery specs makes it all the more better in my book. took a bit but so far i like it.
there was one error i came across while uploading materials. it might have to deal with csv file names with numbers. like 1.csv for exampleSee the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************
System.ArgumentOutOfRangeException: Index and length must refer to a location within the string.
Parameter name: length
at System.String.Substring(Int32 startIndex, Int32 length)
at A.Fe.hh(String )
at A.Fe.M(String , String& )
at x.DT.yq()
at x.DT.yb(Object )
at x.qF.ak.w(Object , EventArgs )
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
DEScribe
Assembly Version: 0.0.0.0
Win32 Version: 0.0.0.0
CodeBase: file:///C:/Users/lordmage/AppData/Roaming/Evolv/EScribe/EScribe.exe
----------------------------------------
DimensionEngineering.Common.Windows
Assembly Version: 0.0.0.0
Win32 Version: 0.0.0.0
CodeBase: file:///C:/Users/lordmage/AppData/Roaming/Evolv/EScribe/DimensionEngineering.Common.Windows.DLL
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34250 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34262 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34239 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
DimensionEngineering.Common
Assembly Version: 0.0.0.0
Win32 Version: 0.0.0.0
CodeBase: file:///C:/Users/lordmage/AppData/Roaming/Evolv/EScribe/DimensionEngineering.Common.DLL
----------------------------------------
DEScribe.Core
Assembly Version: 0.0.0.0
Win32 Version: 0.0.0.0
CodeBase: file:///C:/Users/lordmage/AppData/Roaming/Evolv/EScribe/DEScribe.Core.DLL
----------------------------------------
DEScribe.Branding
Assembly Version: 0.0.0.0
Win32 Version: 0.0.0.0
CodeBase: file:///C:/Users/lordmage/AppData/Roaming/Evolv/EScribe/DEScribe.Branding.DLL
----------------------------------------
DimensionEngineering
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/lordmage/AppData/Roaming/Evolv/EScribe/DimensionEngineering.DLL
----------------------------------------
System.Xml.Linq
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
IllusoryStudios.OpenSsl
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/lordmage/AppData/Roaming/Evolv/EScribe/IllusoryStudios.OpenSsl.DLL
----------------------------------------
DEScribe.PluginApi
Assembly Version: 1.4.0.0
Win32 Version: 1.4.0.0
CodeBase: file:///C:/Users/lordmage/AppData/Roaming/Evolv/EScribe/DEScribe.PluginApi.DLL
----------------------------------------
DimensionEngineering.PluginApi
Assembly Version: 0.0.0.0
Win32 Version: 0.0.0.0
CodeBase: file:///C:/Users/lordmage/AppData/Roaming/Evolv/EScribe/DimensionEngineering.PluginApi.DLL
----------------------------------------
System.Security
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34248 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Security/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Security.dll
----------------------------------------
SecondLanguage
Assembly Version: 1.0.3.0
Win32 Version: 1.0.3.0
CodeBase: file:///C:/Users/lordmage/AppData/Roaming/Evolv/EScribe/SecondLanguage.DLL
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
NBit
Assembly Version: 1.2.1.0
Win32 Version: 1.2.1.0
CodeBase: file:///C:/Users/lordmage/AppData/Roaming/Evolv/EScribe/NBit.DLL
----------------------------------------
ICSharpCode.SharpZipLib
Assembly Version: 0.86.0.518
Win32 Version: 0.86.0.518
CodeBase: file:///C:/Users/lordmage/AppData/Roaming/Evolv/EScribe/ICSharpCode.SharpZipLib.DLL
----------------------------------------
IllusoryStudios.Math
Assembly Version: 1.1.0.0
Win32 Version: 1.1.0.0
CodeBase: file:///C:/Users/lordmage/AppData/Roaming/Evolv/EScribe/IllusoryStudios.Math.DLL
----------------------------------------
EquationParser
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/lordmage/AppData/Roaming/Evolv/EScribe/EquationParser.DLL
----------------------------------------
HidSharp
Assembly Version: 1.9.0.0
Win32 Version: 1.9.0.0
CodeBase: file:///C:/Users/lordmage/AppData/Roaming/Evolv/EScribe/HidSharp.DLL
----------------------------------------
SaberUpload
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/lordmage/AppData/Roaming/Evolv/EScribe/SaberUpload.DLL
----------------------------------------
Mono.Addins
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/lordmage/AppData/Roaming/Evolv/EScribe/Mono.Addins.DLL
----------------------------------------************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
-
Perhaps the forum guru's could help me nail down a good tcr and build for this wire.
according to the packaging it has a tcr of.00223/f_.004c.
i wrapped a couple single coils in the mutation v4 for tested. each one seemed a bit anemic using the tcr in ecribe under special. there is vaper but it is hit and miss. i have 31awg at 3.266 ohms/ft and some 28awg at 1.630ohms/ft.
should i be aiming for a specific cold resistance or should i simply try matched duals at this point.
each test coil was 3mm using a coil master the first came out to .607 and the second came in at .810
Can't Login to the forum
in General Discussion
Posted
just wanted to public say thanks to webmaster for correcting my issue which presented with a red box that simply said try again in my case i tried 3 different browser two neve came here before so no cookie issue... it seems my profile needed reset... so a ticket to evolve fixed it for me.