.thumb.jpg.a21e2bc6a6a2439a8c97330238778481.jpg.881b063a7329fe27fadeaeacdd147081.jpg)
retird
-
Posts
2,610 -
Joined
-
Last visited
-
Days Won
135
Content Type
Profiles
Forums
Downloads
Posts posted by retird
-
-
John posted this back in June:
https://forum.evolvapor.com/topic/66331-topic/?do=findComment&comment=896275 -
Good to know that's an Evolv error message.
-
It may be a "custom screen" put in the Littup44 by whoever built it. Maybe ya need to contact the vendor and get an explanation.
-
techbearus said:
[QUOTE=lamonjullo]Check out this video regarding the VTBox200 by Vape Cige. It was just uploaded today and is what I know to be one of the first videos giving a first-look at this particular mod. Watch the whole thing, it just keeps getting worse the more he touches the thing.
Wow! I'm floored.
One major issue that others noted somewhere else.. at 9:20 in the video when the reviewer shows the Lipo connector, note that the male and female connectors are not installed properly.. Lipo has the exposed leads connector and even in the video there was a high likelihood it would do a dead short on the mod metal body when he was moving the cables around.. yikes..
@Evolv... I don't know what to say, but this kind of puts you also in bad situation, if any user were to get hurt with inferior mods that are built with no proper QC or vetting .. I am at loss for words here ..[/QUOTE]
Vape Cige should tell the mod manufacturer to change the connector leads so the battery has the female connector. Easy fix at that point. If you noticed the batteries Evolv has do not have connectors for the main connection leads and only have a connector for the balancing leads. I really don't see Evolv being in a bad situation as the mod maker configured the connections and built the mod. -
That's a question for John or James I think. Here is a bit of discussion on it.
https://forum.evolvapor.com/topic/66934-topic/?do=findComment&comment=902104 -
It means it is failing a self-check and is out of calibration, so the wattage settings and temperature settings aren't correct anymore.
RMA it. -
Since you built your own device you need to run Case Analyzer in EScribe (found in the Mod tab). It takes 1 to 6 hours to run.
EScribe tutorial: http://www.evolvapor.com/guide/story.html -
Ran across this "Adding Windows 10 to a Mac:
http://www.cnet.com/how-to/how-to-install-windows-10-on-a-mac/ -
Have you ran Atomizer Analyzer? What doers it show when you look at a vape in Device Monitor Live view?
-
Since you are wanting to bypass any China involvement concerning their warranty you might want to talk to Evolv and get a clear understanding of the process. It will be generous of you to carry and stock all the additional parts necessary to replace defective or poorly installed components of the device and assuming the full warranty liability after you replace/repair the device as you are not a warranty repair/replacement facility approved by the China Manufacturer. Making any repair may void the remainder of the China Manufacturer's warranty which you will then assume for your customers.
Just my thoughts.... -
blueridgedog said:
Check one thing at at time...uncheck all other items. You are slowing down the data flow if you ask it to monitor several things. Test one at a time and verify if that works.
Did all that before posting. Repeated again and still doing the same thing. When all items are checked under Current Puff it displays all data immediately in Current Puff section. When all items are unchecked the data may fill in slowly or may only fill in a few items of data and sometimes not fill in any data. When only a few items are checked those items fill with data immediately but uncheck items may or may not fill in slowly. No matter whether items are checked or not the current puff under Statistics updates just fine.
Strange that it just started doing this yesterday on both reference devices that have been used since June 2. Wondering if a Windows 10 update has anything to do with it?
Not a big deal and it doesn't effect vaping but just wanted to let James and John know I've noticed this.
Attached video -
promod2000avenger said:
dc601
Could be a few different things.
1 Could be the USB cable your using. Try a different cable.
2 Your computer Operating system. Try defraging.
3 Files corrupted in escribe. Uninstall & Reinstall current version of Escribe.
4 Hard Reboot device.
Just my 2 cents !
USB cable good but tried a new one also. Both good and transfer data.
Windows 10 x 64 bit recently installed. Defragged. (was only 1% fragmented)
Uninstalled EScribe and reinstalled and firmware. (also tried with 7/29 version of EScribe and 2 earlier firmware versions)
Don't see the need for Hard Reboot but did a soft reboot.
Still doing the same thing.
-
I've been using the EScribe 1.0.30 and 8/7 firmware and just today I noticed this:
In Device Monitor the data under Current Puff doesn't always fill in while vaping as it always has before. Power, Temperature,Current, Voltage, and Live ohms may or may not fill in while vaping. (See below captured screen while vaping) When I tick Power, Temperature,Voltage, Current, and Live Ohms to show in Live View the data fills in under Current Puff every time but when I untick them it goes back to not always showing data. ( If I take an extremely long vape it may fill in the data sometimes) Could this have to do with transfer of data being slowed down for some reason? It happens on both reference devices. Tried 7/29 and 7/27 firmware with same results.
-
Yes, those are the ones. See pdf here for wiring information.
http://www.evolvapor.com/datasheet/dna200.pdf -
No just use the 6 thru-hole solder points.
-
Will be interesting what VS comes with. Maybe with no daughter board this time?
-
OK. Good that you see ohms now.
-
EDIT: posted as you were adding info. Do you have it connected to EScribe? What does Device Monitor show you?
-
Think you may find the VS rdna40 uses standard screen/ribbon.
https://www.youtube.com/watch?v=__0hD-h0ufY -
RE: Not Connected error message. I saw that message 4 times while trying 4 different USB cables. Bought a new quality USB data cable and no more error message. No saying that is your issue but it was mine.
-
Yes, I shorted the center pin to the 510 shell and pushed the fire button and got the error message. No error message until the fire button was pushed.
-
Using Windows 10 - 64 bit Home version with USB 3.0 laptop computer and it sees and talks to the board just fine.
-
Don't know if this will be helpful but I took a reference device and without an atty attached I shorted the center pin to the shell of the 510 connector and got the atty shorted error message. Attached an tank atty and all is well. No blown fuse.
-
The Evolv made device has been in my hands a minimum of 10 hours per day, every day, since June 1 and if it was going to show a "gottcha" it should have done it by now I would think. The custom made 510 connector really impressed me. I've debated whether to take it apart and anodize it but "if it ain't broke, don't fix it" but an Evolv kit, if it becomes available, will my next purchase.
Leakage current from USB killing the fuse?!
in Report a Bug
Posted
hum, I wonder, as I've vaped a reference device since early June and much of the time I vape while it is charging via the computer USB. Each time I press the fire button the charging stops and continues charging again after releasing the fire button. After more than 3 months of doing this daily I've not had a single fuse let go. Just giving my experience vaping while plugged into charging USB. No issues here.