VapingBad

Evolv have never produced them for anything other than Ni or Kanthal as far as I am aware, they are in the spec sheet. But you can work it out for yourself EG You want to know for SS316L You need to pick a temperature, I will use 450 F as you didn't specify From the spec sheet we have max output voltage 6.2 V and max output current of 30 A (I will ignore the max pulse current of 40 A) For full 75 W: max res is found from R = V*V/P = 0.5125 ohms min res is found from R = P/(I*I) = 0.08333 ohms But you have a temp sensing wire which changes things a little, I will use SteamEngines TCR of 0.000879. res at room temp = 1 then res at 450 F = 1.1866 Then we take the std max res and divide it by this 0.05125 / 1.1866 = 0.0432 ohm for 75 W at 450 F Then we do the same with the min 0.08333 / 1.1866 = 0.0702, but this will be below the std min so will not get to 75 W until hot, so I would suggest just using the standard min. But if you only wanted max 50 W then the std max res would be 0.7688 ohm, and for SS316L @ 450 F it would be 0.648 ohm But if you only wanted max 25 W then the std max res would be 1.5379 ohm, and for SS316L @ 450 F it would be 1.296 ohm Because the temp & max power you want and wire type are all factors it is not easy to make a table. The main bit is what resistance will the coil be at when it reaches temperature and is that below 6.2 V squared divided by your wattage.

The "Check Battery" will be triggered by the lowest cell going below the soft cell cut-off (default is 3.09 V) while the mod is firing. To balance leave it on charge after it seems fully charges, it can take a long time. If you want to see who it is progressing or when it's done temporally put the cell voltages on the device screen in EScribe.

I think there is a little delay in the back end system, try again in a few minutes.

You could solder a couple of bits of single core hook up wire to the holes you would wire the switch to and just touch the ends together to simulate the switch.

I can connect fine, I did read that one of the big root cert authorities had a big fault this week http://www.theregister.co.uk/2016/10/13/globalsigned_off/

If you go to device monitor look to see if one or more cell is very low at rest and while firing.

I think it has been mentioned, but I can't find it right now. Try V1.2SP4 there are some scaling fixes for EScribe, but that is not mentioned explicitly, follow the link in my footer to early fw.

As far as I understand it you should only get that message in relation to stuff set on research tab.

I have never seen that, but would check the research tab in escribe, specifically that the puff, energy and time limits are set to disabled. Here is what the defaults look like.

Check the 510 centre pin in not stuck or come loose inside.

You're welcome

You can create a custom material in EScribe and manually set/edit a TCR, just be aware when you edit it the value is the default and not the current value because it is not stored as a single number TCR.

That looks like a lot less than a second delay in power delivery, I think you mean the the coil take a second to get up to temp, which would just be the coil not the mod. Cold res doesn't matter if temp limiting is disabled. If I were you I would use temp limiting and preheat, it works very well with ss, I even have triple twisted dual coil SS316L builds. Also with less advanced many mods sold as VW only measure the res at the beginning of the puff and set the voltage, so with ss the power goes down as the coil heats just like a mech, DNAs give a flat power output even if the resistance. So the vape will be different between boards with ss and maybe that is why it seem slow to you.

That looks like almost no delay, are you vaping in temp mode as it looks like you have live ohms checked in the 1st one with the cold ohms too high or locked res and no preheat.

0 is fine and much better than too high. At very low resistances or very high wattages you may notice the difference between 0 and the correct value for your mod, but it will still vape well only the watts and temp values may be a little out. I don't know what your value should, all of mine are 0.003 or 0.002 ohms.

It is part of the V1.2 update, you need to go to Options - User Interface and choose Advanced for the basic mod settings or Manufacture for all of them.

In EScribe Options - User Interface choose Manufacture then go to the mod tab and set the mod resistance to 0 and you should be OK.

The resistance needs to be between 0.09 ohm and 0.4 ohm for 200 W https://downloads.evolvapor.com/dna200.pdf

In the spec the pins are numbered GND, 1, 2, 3 with no pin 4, I will use that for consistency. You don't need to bridge to the positive or negative unless you plan to only use a single balance wire from the point between the cells to pin 1, if you did it that way then you would bridge GND to negative and pins 2 & 3 to positive. Otherwise just bridge pins 2&3, it could be done in the plug if you prefer and the rest of the wiring is the same as normal.

No, mine update between 50 & 10%, I'm looking at one now showing about 35%. It maybe the battery has a very flat discharge curve in that range, the metre only goes by voltage on the 75 it's not as sophisticated as the meter on the 200 and 250.

Does is say check atomiser if you press fire with not rta in the 510?

Glad you go it going Car!

I know, but just the fw causing it seems even more unlikely to me, I understand that that is the only thing that has changed and a logical conclusion, but if it were just the fw loads more people would have the same issue. It is also possible there is a hardware issue and with the new fw you get these issue that don't show up with the old fw, still very strange I know. Sorry, wish I had a better answer for you, I would open a ticket with Evolv to see if they can help.

That sounds more like an issue with the 510 or atty, have you connect it to EScribe to get a live resistance reading when it does it? I don't think the atty analyser issue and it saying shorted are connected. I have read about people who have found tiny bits of machine swarf in their 510s causing strange problems, that or damaged insulator or damage wiring are the most likely thing I can think of ATM.

If it is just that the mod res reading is ? and you can get a stable reading with the old fw then I would just use that value with the new fw, I do in fact with no issues. It is only an extra feature and it reading ? will not cause issues with anything other that trying to read the mod res. It is a very different scenario from it tracking the resistance of an atomiser, you would never try and vape a coil that was below 0.01 ohm.