labo

I measured mod resistance shorting 510 thread with a huge copper wire, it results 0.004/0.005 ohm, i set 0.045 ohm in mod resistance, according to previous posts it should be fine. It should be safe due to the fact atomizer resistance isn't considered here and it will always be over 0,001 ohm. However I finally ran case analyzer and battery analyzer and these are Hcigar VT200 results, do you think are they fine? I attached battery profile, just rename it from .txt to .csv Moreover, I see that using very low resistance coils like I did will take in troubles in TC mode. I used 29AWG nickel200 because it's really hard to make a proper coil and insert the cotton with 30 or 32AWG Then yesterday I made a ribbon wire with 32AWG nickel and 29AWG kanthal DNA200 reads 2 parallel 7/8 wraps coil as 0.151ohm I calculated the right temperature curve using steam engine Like so I have no trouble with TC I really hope I helped somebodyLabo_Hcigar_VT200_Battery.txt

it's not set... I really don't know how it tends to be on my mod

Goliath v2 on a VT200 Dual Ni200 coil 29 AWG 2.5mm diameter 8 Wraps It should be 0.061 Ohm (from wire wizard) Atomizer analyzer: Clean Profile, 210°C, 60W, preheating 200w Cold Ohm reading: ? Fire button rapidly pushed, cold Ohm: 0.076 I vape 3 second, cold ohm value rises I vape 3 more seconds, cold ohm value rises, Cotton is burned, cold Ohm 0.236 Ohm locked profile (0.076 Ohm), 210°C, preheating 200w 1sec Too hot Ohm locked profile (0.061 Ohm), 210°C, preheating 200w 1sec Everything good For comparison Eleaf iStick TC40W Cold Ohm reading: 0.06 Without locking anything that value is stored for the following puffs Everything good

I know that but there's something wrong anyway The board shouldn't store room temp at the very first vape, in my opinion it should to do it when device is not used since x minutes as a background task, updating previous reading

@James & @EVOLV Team I think there's a bug in room temperature reading, see my post here.

I'll try when the battery will be a quarter to half full. I have to discharge it. However I think that's not the problem... Room temperature reading it's too high compared to real one, even with the device fully charged with no usb current flowing. And there's the other bug that it stops reading room temperature after the first vape. EDIT: I think the board saves room temperature as board temperature after a reset and after the first vape, but after a reset the board can be hotter than room temperature or colder, I really don't know where the next reading is scheduled, if there's one. We really need a delta correction, or the possibility to control room temp without escribe or to force a new reading whenever we want

Hi, I have a Vt200, I noticed that room temperature reading is always wrong. Right now room temperature is 62,6 °F, I'm sure the box has the same temperature, it's been 2 hours that I'm not using it. When I attach it to Escribe to monitor the Temp I can see that the board temp is fluctuating (it raises when I hold it in my hand), the room temp instead is always the same (73,88 °F) So there must be a problem and ohm analyzer can't correct ohm reading @ 70°F the right way. Any help? EDIT: After a Hard Reboot from Escribe the Room temp started fluctuating, but it's always too high 78,73 °F vs 62,6 °F, could you add a programmable delta correction? EDIT2: After the first vape after the hard reboot room temperature stops fluctuationg and remains the same, maybe a firmware bug? I'm on latest firmware with Escribe 1.034 EDIT3: The only way to make it work is to do a Hard reboot, soft one doesn't help. BTW Delta correction will be helpfull.

That was the problem, thanks man, however it's not explained very well in the software

Hi everybody, I have a VT200, I updated it with the latest firmware 30/09/2015 Left info (ohm, volt, temperature) doesn't change when I put it under charge with USB cable. If I change default fields in non charging mode every field works as expected but they don't change, regardless it is USB connected or not. The problem was still present with older firmwares. I tried different USB cables and wall chargers.