r4nd0m

check this post /topic/66731-topic/ the first one holds the latest escribe which includes the latest firmware

Hi there, I was wondering if the 8 profiles is a hard limit (eg memory in flash) or if this could be extended? I do struggle with the amount of attis and taks I have to just have 8 profiles - would be convenient if more profiles could be made available ... cheers r4n

Well mine is a 9/30/2015 so I assume even newer ... Well I'll go ahead and do some more testing but I can replicate with my vortice easily - dual could build 7 wraps totalling at 0.27ohm ... Firing it at 50watts @410F it goes into TC, do I set it to 210C it just fires in wattage mode ...

I see this on my vaporshark dna200 - when using Celsius - when setting it to F it seems to work just fine ... might be worth a try as I can see you are using Celsius as well ..

well I use 2015-10-21 EScribe 1.0.35.2 and firmware 2015-09-30 - which I believe is the latest available and I can observe this "glitch" on my device ...

what I have found on my Vaporshark DNA 200 with the above SS wire profiles - it never enters TC mode if I use Celsius in my profile - took me a while to figure that out - not sure what the reason is - I then calculated my desired temp C into F and it always ramps up in TC mode ... not sure if this is a bug or intended - as the CSV is based on F

Lance - did you try locking the Ohm at 0.41 and see what it does when you come back afterwards?

Yes please re-upload mate would be interested myself to test those curves - thanks in advance - just realised the links haven't expired yet

I can see where this is going but I would actually prefer a battery warning - especially for lipos you don't want to run them down any lower than 20% to maintain longevity of the pack itself - have been doing that for years in rc so wouldn't do that on a mod either as I know the impact this can have on a cell - so I'd prefer a low percentage warning or even battery cutoff option so it doesn't fire but gives you a warning message ...

That's not the idea just saying there will always be two camps but as a manufacturer you should be able to clearly state how the device or software you produce should be used and possibly even give some detail with it - helps for sure

Well, from what I see there are two camps here - I would suggest a TC best practices threat to explain how to do it "properly" or "intended" with this device. I have been playing a lot lately and reading this thread explained many things I was experiencing but still keeps questions unanswered which means the instructions aren't clear enough - I don't mind being blamed for being lazy but when searching the web you'll find both camps all the time spaced vs contact coils for NI, Ti, SS or watts vs temperature ... would be nice if the developers would tell people how the device and software has been designed to work best or at least how they intend people to use it with an explanation why ... I can see some points in this thread but again I think a clear explanation would help so people use it how it has been designed and it woods as expected ... This surely would open up the conversation for comments and hopefully will be helpful for all of us. Just a friendly comment ... with regards to scrum do it, we do it for quite some time and it has improved the ability to introduce new features much quicker - agile development is anyhow better especially if you are able to release feature builds vs full builds that require full QA ...

hello mate, just reconnect your device and flash again - might give you an error during the first attempt but then will apply the update - so far I haven't managed to brick the chip while trying to ... partial firmware uploads etc etc good luck r4n