Spector NS5 RD

not interested in turning yer mod into a light show, like the x cube 2, dwcraig1?

just putting this out there, the max output when in 2s mode is 6 volts. 100w @ .29 ohms comes to around 5.39v. what you have your mod resistance will come into play as well. in device monitor, with the atty voltage checked, what is the voltage when firing your .29 build at 100w? is it close to the 6v limit? also, here's a thread that might offer some help. /topic/67084-topic/

in escribe you hit "restore default settings". all your settings from escribe will be defaulted to evolv's. dunno if that's what you're asking.......

i'm sure volcano ecigs is going treat you right. i recently RMA'd my new Vaporshark DNA 200. they paid shipping both ways. got my device back in 5 days with a new board installed. you'll be fine.

there is also a "set charge estimate" in device monitor. if you know your battery pack's total watt hour and you know it is fully charged, you can manually type in the charge percentage in wh's. for ex. a fully charged 900 mah 3s lipo = 10 wh's. that number would be entered in the estimate field if the battery is fully charged. or 5 wh's if at half charge and so on.

worth a shot......try rebooting your comp and only start up escribe. that works for me when my comp won't recognize my dna boards.

my 'auto locking' issue has seemed to clear up, i hope. i just now set my VS 200 back to 3x click to lock and unlock. we'll see if it behaves. i pretty much did what dwcraig1 mentioned in his post. i gave the fire button about 20-30 hard pushes. not crazy hard, but pretty forceful. my thinking is by pressing the button harder a bunch of times it might force the contacts to make better connection, by reshaping the wafer thin metal dome contacts inside the switch or clearing any debris. since my device still is under warranty, i was not too concerned if the fire button broke or got worse. if the button starts acting up again, i'll just send it back for a second time. i'm not saying do what i did. i'm not even sure it's remedied. will report back

if i can add one thing.........with big clapton coils like the ones you're using, they often ohm out very low. that can be tricky to tc when you go under the .1 range. also coil mass will come into play. if you're using 316 for all the wires then you have the right tcr. you might want to go into escribe, in device monitor and check the cold and live ohms, temp, wattage. and post a screen shot of you taking a vape. atty analyzer will also tell you if your connections are janky. as bobw50 said, spaced is the way to go for ss tc. more stable. take a wrap out if needed for them to fit.

definitely send it in to VS and let them fix it. you have the warranty so that's good. is there any stray metal shavings/strands that you can see inside of the 510 threading of the mod? can you get a light and shine it down into the connector to make sure there's nothing metallic shorting your 510? also make sure your center pin is free moving (up and down).

send me a couple lace. i'll try and solder one to the board and see if it's better than the one that's in my VS 200.

unfortunately this is happening to my recently repaired Vaporshark dna 200. i had it set to 3 clicks but out of necessity i had to change it back to 5x. still auto locks now and then. i'm debating whether or not to send it back for a second time....... my guess is, when i sent my mod into vaporshark for a new board, they replaced my bad board with a new board that had a fire button that was made on a monday or friday. my luck.

pm sent

i just got these in the mail today. i got two of em for $16 and change shipped. my Vaporshark Dna 200 stays pegged at 1.99 amps while charging with these cables. they are charge only tho, no data path. i'm really happy with these. http://www.ebay.com/itm/PortaPow-Specialised-3-3ft-20AWG-Charge-Only-Micro-USB-Cable-2-Pack/301913480090?_trksid=p2141725.c100337.m3725&_trkparms=aid%3D777000%26algo%3DABA.MBE%26ao%3D1%26asc%3D20141212152338%26meid%3Da24f5f600c864bf68f4a9749a000ce4a%26pid%3D100337%26rk%3D1%26rkt%3D1%26mehot%3Dlo%26sd%3D381293739821

so while the device is plugged into a usb charger and you hit the fire button, it displays this message? i'm trying to figure exactly when you get the message. or is just random? it'll just flash check battery while charging? what's going in device monitor while you're getting the CB message? more specifically individual cell voltages and pack. also usb current and voltage? with them all checked, anything out of the ordinary? really high or low volatge on the pack, taps, or usb? have you disconnected the battery mains and taps and reconnected to see if that clears it up? first time hearing this problem.

even tho it says it's not connected, sometimes a firmware redo does work, and sometimes not. under tools - update firmware - keep hitting ok see if works.......if it keeps saying device not found then that means it's RMA time. not worth the trouble of trying to bring it back from the dead. i have heard of evolv taking in entire devices and replacing/repairing the board. just don't be surprised if asked to only send in the board. just to be clear, you have had escribe working with this mod before? as in, you remember what usb cable also has data and charge capabilities? make sure you're using a known escribe compatible usb cable.

you're positive the board is dead and you've forced a firmware update? and still no go........ if you're handy with a soldering iron you can open a help ticket with evolv and send the board in for a replacement. most likely an RMA situation.

i'm not saying that isn't juice in two of the three vent holes in OP's pic, but if you have ever noticed what is left behind after a component self destructs such as a mosfet or a hefty diode, it pretty much looks like that. black shiny enamel crust. i have seen many a circuit board that resembled OP's relo's innards. just my two cents, shillings, and pence. either way it sux.

what type of mod @Havensal? i'm curious.

i know yer handy with stuff but before you drill, just take a look at 'DJLSB VAPES' on youtube. he dismantles the updated sdna 200 and reassembles it. maybe you can bend up the negative part of the 510 connection to get a wrench or pliers on that brass nut. just putting it out there. hope you get it fixed mike.

try a pcb safe solvent and give the usb a good cleaning. there's probably ejuice in places where your eyes cannot see. @dwcraig1 could give you some pointers on cleaning the usb area. he had a similar problem. board should be fine once ejuice is removed completely.

it could take a few days but they will reply to your ticket. just don't send them more than one email. they said it will take longer for a response if you start blowing up their inbox.

only if you want your battery bar/meter to be accurate. but is it a necessity? no.

EDIT........i received my repaired VS dna 200 in the mail today. here's the repair ticket VS included with my repaired unit. however, i would like hear some intelligent thoughts/answers as to what kind of USB fault would draw over 25 amps blowing the fuse. the outer part of the USB socket is grounded, as is the aluminum VS body. so what would cause a hard short? shoddy soldering on VS part? maybe the balance tap or main wires were soldered with excess solder or a stray wire finding it's way to the USB area? even with a blown fuse the device should connect to escribe. i would understand if the USB is severely shorted, then escribe would not be able to make a connection. like i said, if anybody has some in depth, intelligent thoughts, i'd like to hear them.

i'm outta ideas. if anyone else has some theories as to why this is happening, feel free. i'd say if whole watt increments cure the pauses, when selected in escribe, just role with that. or open a help ticket from evolv's website.

what version of escribe are you running? i'm trying to recreate on my vt200 what you're describing and cannot. maybe you're just not holding down the + or - button hard enough (your press is intermittent at times rather than a steady press?). is it only happening when scrolling up or down in watts? or both?