bingbling
-
Posts
42 -
Joined
-
Last visited
Never
Content Type
Profiles
Forums
Downloads
Posts posted by bingbling
-
-
Fasttech carry this:
https://www.fasttech.com/products/0/10023554/5088900-authentic-hcigar-vt200-replacement-1300mah-li-po
Looks like the real thing. However, since I know that battery sux I'm not sure I want to buy that. I might look in to a new device instead, after x-mas when I am not broke haha. Not sure what one though. -
ChunkyButt200 said:
honestly, everything looks in order. 3.41 for cutoff is a sliver high but nothing major. i set it to 3v for all my lipo dna mods. not any lower, as lipo's lose there muscle after the 3 volt mark and become very unbalanced the lower you take the cells. 3.41v will extend the life of your lipo but you do sacrifice some capacity, a trade off. what might be conflicting with the battery meter is you have 9.8 as the WH capacity but battery analyzer came up with 9.473. try putting that value back into the capacity field. also,with over 50k puffs the lipo could be on it's way out. maybe starting to get weak and unable to provide the current the board needs. you would be able to see this while firing the device and watching device monitor, looking for a drastic voltage sag under load. you'll get the weak battery warning when you're reaching your cell soft cutoff value.
as for the res reading off, try cleaning the 510 threads, pin etc. other than that you can re-test you mod's internal resistance with one of those copper threaded plugs. that's what i use.
http://smokefreemods.webs.com/apps/webstore/products/show/6619269
Yeah it's set at 3.41 because the battery sux, and it's getting unbalanced below that. Could very well be a dying battery. I am gonna change the Wh capacity and see what happens. I'll check the device moniter during a puff, what voltage drop would be acceptable, and what vdrop is a dying battery? If I can't get this sorted I guess I will get another device.
Edit.
I took your advice and changed the Wh. The weird thing is, now it says it has 1% charge, it had like 75% before I uploaded the settings?
Here's a screenshot
Edit no2. After letting the device charge for about an hour it jumped from 9% charge to 100%. Now I am gonna see if the meter stays "normal" and not fluctuate 20%. -
ChunkyButt200 said:
post a screenshot of your battery settings in EScribe. you might have an incorrect number or something input.
weak battery is also tied into your lipo. post a screenshot of Device Monitor with pack and cells 1-3 ticked
wrong read resistances can be a case of "mod internal resistance" set incorrectly. what is the value input in EScribe?
Well, the thing is I have been running the exact same settings for a year, and its been spot on. Until now that is. I haven´t changed a single thing. And about the incorrect resistance reading, it doesnt affect all my attys or builds. And yeah I know ur thinking its probably the build/connections that are loose or something. And I thought so too, but I have confirmed the actual correct reading on both a 2nd device (vaporshark dna40) and with my USA Ohm meter, and it always reads the same resistance, its weird rly. If the connections were loose there should be some variance on those two units as well. But its just the DNA200 device that gets the reading wrong sometimes. And its not like its just a tad off, its off by alot. The build that is currently giving me headache is a .17ohm, and that one reads between .17-.22.
Anyhow on to the rest. Here's the screenshots u asked for:
-
Hey.
I've been having weird issues with my device for a while. Three things mainly. Firstly the battery meter is acting weird. What's happening is I set it to charge lets say at 0% and charge it to 30% for instance. Then I unplug and vape for a bit and let it rest. Then after a while, like a few minutes when I fire it up again, the battery meter suddenly says I have 50% battery instead of the 30% I had when I unplugged it. And its always off by 20%-ish.
Secondly since this started happening the device rarely signals "Weak battery", the vape just gets very weak/no existant so I know the battery is down, but no weak battery signal.
And lastly, the device sometimes fails to read the correct resistance when switching attys/builds. And I have confirmed a numerous times that the connections are tight, and my other ohm meters reads the resistance correctly.
What gives? Is there anything I can do? Should I do a soft/hard reboot? -
DannyK9 said:
I dont see the need for an OS-X version to be honest, yes it would be nice but it does work in Parellels running Win 10 and also bootcamp running Win 10.
Agreed you might loose 25-30GB of HDD doing it this way but it does work.
P.S Did I mention you dont need Keys for Win 10 - JUst download the X64 ISO from Microsoft and skip the part where it asks for Key, it will prompt again when finilising installation but skip it, you will end up with Win 10 not activated but from what i can see fully functional for zero cost.
Well, for ease of use its "needed". Not everyone wants to go through the hassle of setting up a VM or a secondary OS just for escribe. Personally, I have both a PC for gaming etc and a Macbook Pro for couch-surfing. So I am not really in "need" of a Mac version. However I would still like one for the moments when my PC is inaccessible, and for convenience. -
Lemi_O2 said:
Any news from Evolv, regarding native OS X version?
Don't quote me on this, but I am almost certain I read in one of the threads somewhere here that there are plans for a Mac version, but not in the immediate future. Possibly in 2016. -
LarryLenz said:
Scoopy,
For the wire loops, are you using Kanthal or NI200? I'm assuming Kanthal but I want to be sure.
Thanks
Kanthal -
blueridgedog said:
[QUOTE=bingbling]*bump*
So I tried opening the file on my work computer, same thing
Can't open - "Unsupported file format". Could some knowledgeable person please help me? This is looking more and more like a bug in the software, maybe due to some localization? I work in IT but I am not a programmer so I can't debug this. Maybe someone from the escribe software developer team could assist?
You do not want to open the file as it is indeed of a type that has no association. You want to go into escribe and select File and Open to open the file.[/QUOTE]
Well, no entirely true. Both my work computer and home computer has the *.ecig file associated with escribe, and doubleckling it opens it. So both methods work. However this has been solved. I will quote myself from a few posts above.bingbling said:*bump* The mystery has been solved. Me and Ari have been discussing this quite a bit today. And after some experimentation we found what was causing the issue. The problem was the date/time format. I am in sweden and I run an english OS Win8.1Pro with swedish keyboard layout and swedish date/time format. And the calibration file from Ari contains timestamps in US format which couldnt be properly handled by escribe when I was in swedish date/format in the OS.
So what I did was switch to US date/time format - started escribe - loaded the calib file - uploaded it to the device - disconnected - switched back to Swedish date/time format - started escribe and downloaded the settings and then resaved the file. Now it loads just fine for me in swedish date/time format.
-
Azzitude said:
[QUOTE=bingbling][QUOTE=dc601][QUOTE=bingbling][QUOTE=Stevelee]Can I have the file also ? I am using vt200 also Million thanks Email : stevelee8217918@gmail.com
I spoke to Ari, the author of the file about sharing it, and he felt it was better you get it directly from the source so he can provide support and updates for future escribe versions. I will respect his wishes and not share it here. You are welcome to join the Facebook group "Dna200 modders", there you will easily find the posts from Ari containing the settings file and support for it.[/QUOTE]
Why not contact Hcigar and get their file after all they made the device. Ari's file was modified by Ari thus different than Hcigar's file. Go to the source, or at least that is my take on it. Good luck.[/QUOTE]
That would of course be the ideal solution, if HCigar had bothered with calibrating the device from the start, which they have not. They ship it with evolv defaults.[/QUOTE]
that is all well and good except not all vt200's are the same, each battery for instance is not identical and the import you get may not be ideal for your battery .....using evolv defaults you get the experience tuning your own device using the analyzer's in escribe and building your own profile ..... a lot quicker than waiting on someone else to do it[/QUOTE]
Yes, your are correct, not all VT200 are 100% identical and the battery will have minor differences. I did run the battery analyzer myself, and I measured the mod resistance. I have my own wire profiles setup etc etc. So I have gone through the process of setting things up. I wasn't looking for a "quick and easy" way to setup the VT200.
This whole thing started out with me wanting to inspect and try Ari's settings out, and see what difference it would make. Ari has made some valid arguments in the comment section of the dna200 modders group on facebook, as to why he made the settings file. I am not going to get into the technical stuff why he did it, he is a lot better at explaining that than me. Anyone interested is welcome to join dna200 modders group and read the comments or ask him. -
dc601 said:
[QUOTE=bingbling][QUOTE=Stevelee]Can I have the file also ? I am using vt200 also Million thanks Email : stevelee8217918@gmail.com
I spoke to Ari, the author of the file about sharing it, and he felt it was better you get it directly from the source so he can provide support and updates for future escribe versions. I will respect his wishes and not share it here. You are welcome to join the Facebook group "Dna200 modders", there you will easily find the posts from Ari containing the settings file and support for it.[/QUOTE]
Why not contact Hcigar and get their file after all they made the device. Ari's file was modified by Ari thus different than Hcigar's file. Go to the source, or at least that is my take on it. Good luck.[/QUOTE]
That would of course be the ideal solution, if HCigar had bothered with calibrating the device from the start, which they have not. They ship it with evolv defaults. -
Stevelee said:
Can I have the file also ? I am using vt200 also Million thanks Email : stevelee8217918@gmail.com
I spoke to Ari, the author of the file about sharing it, and he felt it was better you get it directly from the source so he can provide support and updates for future escribe versions. I will respect his wishes and not share it here. You are welcome to join the Facebook group "Dna200 modders", there you will easily find the posts from Ari containing the settings file and support for it. -
rbeamj said:
ok.
So I have been doing some additional testing as the vendor I purchased this from is not answering me.
With ultra-low ohm, Nickel coils (premade from Aspire directly and advertised as 0.15) the vape is not as consistent as with my DNA 40 device. Actually, running the same settings on the VT200 results in very little vapor production. (40 watts @ 470 degrees). To get similar results on the VT200, I have to run 530 degrees and 30 watts. As the atomizer heats up (I chain vape) the vapor production gets less and less on the VT200.
I got an .ecig file from someone on here, with a VT200, that included settings for 316L. Using the 316L in TC mode, I get constant vape production even when chain vaping. Those settings are 450 degrees @ 50 Watts. Even when the atty heats up the vape production is constant! I actually had to drop the temp to 420 degrees as I do not like it that warm. This is on 0.3 ohm coils directly from Aspire.
So it appears my mod has an issue with the ultra-low ohm coils..
I have the Mod Resistance set to 0 for both tests as I do not have the means to test the Mod resistance. Inputting settings from other VT200's (Mod resistance at 0.0045 or 0.01) resulted in much poorer performance from the NI200 coils.
Maybe one of the DNA peeps can chime in here and help out.
That settings (ecig) file was from me. And the 316L wire profile is for stainless steel, not Nickel. So you should not use that one with nickel coils, it will be way off. Actually all the wire profiles preprogrammed in that file is exclusively for Sweetspot Vapors wires, and should not be used without those particular wires. Its better you use steamengines wire wizard for generating csv-files for each of your non-nickel wires. All the other settings in the ecig-file is valid though. However I changed the mod resistance from 0.01 to 0.0045. -
Dampmaskin said:
My day job is time management/planning software development, and if I can make a suggestion to Evolv's dev team:
Use the ISO 8601 format for dates whenever a date needs to be exported, stored or transfered as a string.
This format is unambiguous, human readable, alphabetically sortable, easily parsable, all sorts of good stuff. ISO 8601 makes date format pains go away.
+1
Would have saved me some headache
-
*bump* The mystery has been solved. Me and Ari have been discussing this quite a bit today. And after some experimentation we found what was causing the issue. The problem was the date/time format. I am in sweden and I run an english OS Win8.1Pro with swedish keyboard lauout and swedish date/time format. And the calibration file from Ari contains timestamps in US format which couldnt be properly handled by escribe when I was in swedish date/format in the OS.
So what I did was switch to US date/time format - started escribe - loaded the calib file - uploaded it to the device - disconnected - switched back to Swedish date/time format - started escribe and downloaded the settings and then resaved the file. Now it loads just fine for me in swedish date/time format. -
*bump* The mystery has been solved. Me and Ari have been discussing this quite a bit today. And after some experimentation we found what was causing the issue. The problem was the date/time format. I am in sweden and I run an english OS Win8.1Pro with swedish keyboard lauout and swedish date/time format. And the calibration file from Ari contains timestamps in US format which couldnt be properly handled by escribe when I was in swedish date/format in the OS.
So what I did was switch to US date/time format - started escribe - loaded the calib file - uploaded it to the device - disconnected - switched back to Swedish date/time format - started escribe and downloaded the settings and then resaved the file. Now it loads just fine for me in swedish date/time format. -
File is OK, not corrupted etc. It has been confirmed by a number of people, both mine and Ari's copy of the file(s). I am going to try a few different possible solution later at home. It might have something to do with localizations within the OS. I will report back later.
-
Please see this thread for details:
https://forum.evolvapor.com/topic/67314-topic/?do=findComment&comment=905855 -
*bump*
So I tried opening the file on my work computer, same thing Can't open - "Unsupported file format". Could some knowledgeable person please help me? This is looking more and more like a bug in the software, maybe due to some localization? I work in IT but I am not a programmer so I can't debug this. Maybe someone from the escribe software developer team could assist? -
rbeamj said:
Ok. It took me a bit but got the file to load To do it open escribe. Click on file in the upper left corner then scroll down to open. Navigate to where your file is located and you may not see it but in the lower right corner of the dialog box is a file type drop down Menu. Change this to all files and your file will now appear. Click on it and click on open. You cannot just double click on the file in windows explorer or use any of the load buttons within escribe. You have to use the file menu at the very very top of the window
Yeah I know how to open the file haha I've been around computers and such for the last 20 years or so, I work in IT tech/support business reapairing/building computers. So I am fairly tech savvy
The issue isnt "how" to open but to get it to open without the error. When I try opening the file, no matter which way, doubleclick or open it via the File menu, it throws the error "Cant open - Unsupported file format". Thats what baffles me since I know the file is OK, and my escribe works in any other way. But the file simply wont open. Its an enigma, and its driving me nuts! I am going to try it at work tomorrow morning.
-
dc601 said:
[QUOTE=bingbling]Is there any way to debug why I can't load the ecig settings file? Perhaps a way to log whats happening in the background to see why and what makes it fail? It seems I am the only one who can't open the file. Its really weird.
Have you tried from a different computer?
Send the file to me in a message and I will try it, if you want to let me have a go at it?
[/QUOTE]
No I have not tried it in a different computer yet. I only have access to one PC and one Macbook at home. And its too much of a hazzle to get escribe running on a Mac. I will however try the file at my work computer monday morning.
I can send the file to you if you want, even tough I know for certain there is nothing wrong with the file. James the admin here has confirmed it working, and so has countless other people from the closed facebook group I got it from.
The file throwing "Unsupported file format" error for me simply makes ZERO sense. We all have the exact same version of escribe and the exakt same version of the ecig file. I can't for my life figure out what is wrong. And even if I were daft beyond belief there simply is not much that could possibly go wrong opening the file
I alos tried uninstalling and reinstalling escribe, same problem. I ran it as admin and normal user, no difference. I am on a Windows 8.1 Pro x64 machine, eng version with swedish keyboard layout if that could possibly be a factor.
I saved my own custom escribe settings file earlier, just to try it out. And that one loads just fine, not that it does me any good though lol
-
Is there any way to debug why I can't load the ecig settings file? Perhaps a way to log whats happening in the background to see why and what makes it fail? It seems I am the only one who can't open the file. Its really weird.
-
James said:
Could you give a link to this calibration file?
If it is a .CSV file, go to Material and choose Custom, then click Load CSV on the Material Profile.
If it is a .ecigprofile file, click Load Profile on one of your profiles.
Actually it's none of the above. It's a *.ecig file, the filetype escribe defaults to when trying to open it with FILE-OPEN. I was under the impression thats the way to import the settings. I have tried to open it with file-open and load profile. It's supposed to contain a complete calibration of all settings, including battery analysis/battery discharge/cell soft cutoff/mod resistance/case analysis/wire profiles etc etc.
I got the file from a closed facebook group, and I am not sure whether Ari agrees to making it public. I will send it to you in a PM James. -
Ari from sweetspot vapours has been kind and created a proper calibration file for the HCigar VT200. But I can't get it to load. I am getting "Unsupported file format" when trying to open it. Others have reported it working, and the response to people who have had the problem has been given the advice to install the latest version of escribe, but I already have the latest. What am I doing wrong? I am trying to open it with FILE-OPEN.
Edit. Not entirely sure but it looks like the reference by Ari for "the latest" escribe is actually the second to latest escribe. -
bmclaurin said:
I haven't had a chance to run the analyzer yet, but I'm curious about when the analyzer terminates the test. Does it simply cut the test at a preset voltage (as measured under the load of the test)? If so, what is that voltage? If it's using voltage under load to terminate the test, I presume it would be best to run the test with a load that is representative of your typical atty.
EDIT: Also, are the SOC curves based on voltage at rest or voltage under load? I presume it's the latter, since the data would be gathered by the battery analyzer while the cells were under load (unless it periodically unloads the cells, allows them to recover, and samples their resting voltage). If that's the case, I'm also curious about how the battery meter works (since the resting voltage of the battery will be higher than its voltage under load). Is the battery meter basing its estimate of SOC on the voltage of the battery when it was last under load (i.e., during the last puff), or is it basing it on the resting voltage at that moment? If it's the latter, then it seems to me that it would always be overestimating SOC (assuming the analyzer doesn't periodically sample resting voltage throughout the test).
If I recall correctly, my observation during the test was, the test terminated when the voltage dropped below the Cell Soft Cutoff under load. Mine is set to default 3.09V, and I am almost 100% certain I saw the graph dipping to 3.08V and then terminate.
My DNA 200 (HCigar VT200) is going bonkers
in General Discussion
Posted
I see. Might give it a go then, and its not a fortune lost either if it sux