retird

The LED setting are for the DNA75. If I recall you have a DNA200...

Wismec's web site shows that the new version Reuleaux RX200 is not a DNA200 but a different chip as is the Reuleaux RX200S. Their web site shows a device named the Reuleaux DNA200 which is a DNA200. Wismec web site (Products page): http://www.wismec.com/product/

Not a bug in my opinion... just an OCD thing as some would say.... LOL....

Well the Materials are there to use in any rate... wonder if telling the device to alphabetically organize them would increase processor activity or it could be done in EScribe? Out of my zone of knowledge tho...

Good... ya got it fixed to your liking....

Try setting them to settings I posted and adding yellow as your "Normal" and see what you get. Set all to 1.00

If you change name Nfe 48 to Nfe48 and etc will they group... it looks like the numerical order of all wires is being sorted....

Can you post a screenshot of your settings as I did???

There is a learning curve with any APV.... all my APV's, including DNA's work "right out of the box"....( APV... Advanced Personal Vaporizer ) Here is a few videos and a tutorial (some need updating) but may help.... TUTORIAL : https://downloads.evolvapor.com/escribe/guide/story.html https://www.youtube.com/watch?v=9oxb5rNAqPU https://www.youtube.com/watch?v=6KQGxsYfG9U https://www.youtube.com/watch?v=Bywx-twQMM8 https://www.youtube.com/watch?v=csOQTYEht5I https://www.youtube.com/watch?v=D3vNJRT0uh4

Fire... blue Charging... red Charged.... green Normal.... (not set) Those are the setting on my DNA75.... (not a SMY device) When not plugged in to charge I get no led color until firing... Upon firing I get blue. When plugged into charge and I fire I get momentary purple (millseconds) as it turns blue. Charge and charged colors are as set... only time I get purple is when plugged to charge... You get purple for several seconds??? My settings: Red and blue make purple...

You might try other Atty's also.... Maybe atty, coil build, poor grounding in the device, or connectivity issue....??

Yes I love the new software and firmware as they made my vape experience even better than it was with SS on the 200's and added the 60's, 167, and 250's to the mix....

Normal..... Li-Po for 18650

In checking Mod Resistance with a tool the setting should always be tested with a 0 reading to start. When you test is it set to 0 before testing?

Why would EScribe allow this if it would void the warranty and even allow you to share your custom themes?

Where did you hear that? You can design custom screen and install in EScribe....

That's exactly what I noticed with the latest update "Early Release" firmware for the DNA200 with SS316. Smooth temp graph and Temp message sometimes displays but Device Monitor shows almost straight line temp variance at temp... Heck, I can't see my display while vaping anyway. Very satisfied that the 75 and 200 both work great with SS316... Note highlighted in blue:

LOL.... with retirement comes old age and aches, pains, grandkids, and a fixed income, etc, etc... but I love it..... you will get there...

Noticed this on file properties....

KTMRider.... I tried to install service pack on my non-VS device using 1.2 and got same error message.... noticed while extracting the Zip file it didn't give the normal Evolv logo icon on the desktop file...

@mactavish.... James just up a possible resolution of your issue... Could you test it as yours is still not charging right? THX /topic/65665-topic/?do=findComment&comment=888330

Yep...." Early" releases can have glitches that weren't caught already I guess and the Early release is not stated as "Recommended " versions. Most folks know that as this has been the process for a while now. My thoughts are that those with VS200's may or may not have an issue, may or may not decide to load the early version, and if there is an issue they can revert back as some have already done. As far as I know only some VS200 are showing this. Granted a quick resolution would be good.

Saw where you already posted this 2 days ago and Evolv is working on it... doesn't effect ALL VS200's as I understand... Here is your previous post: /topic/65665-topic/?do=findComment&comment=888277

I think your issue is different than the one being discussed now... yours is that your VS arrived DOA...

You probably saw the pinout in the datasheet for the DNA60: dna60.pdf