My CD with coating shipped today lol, earlier than the vapecige, I can not believe it...
My CD with coating shipped today lol, earlier than the vapecige, I can not believe it...
If EScribe sees it when attached to computer then more than likely the fuse is blown. If it were mine I'd open a ticket with Evolv and send just the board (with the male batt connector and 510 pin included still attached) to Evolv.FWIW: I received mine on Saturday afternoon. Red/Black, s/n 0833. First impressions:
- Case uses all hex screws, no magnets (personally, I prefer this in this device)
- About 1 mm shorter and 2-3 mm thicker than my Cloupor T8.
- Definitely heavier in the hand than my T8. It feels like a small brick.
- Build quality seems very nice. It feels sturdy. Not a fan of the lettering, but overall, I like the look.
Vaping on it:
- Holy! I now get what this DNA200 chip is all about. Kanthal is 'as usual', but in temp control mode it is a different ballgame. Better than anything else I have (and have tried). Ni200, Ti, mixed builds, I finally get a 'satisfying vape' from temp control.
- Running dual Ni200 claptons @.1 makes battery life pathetic. After 10 minutes, battery dropped 20%. But hey....
- At 200W with kanthal this thing is an absolute beast. Instant power and the vape production rivals my best mechs - copper Manhattan w/Warhead @.09 NiChrome (dual Clapton) and my dual 18650 series box @.3 kanthal.
- Ended up uploading some images through eScribe and playing with various 'normal use' Ni200 tanks and atomizers.
After about 360 puffs on the counter, I called it a day. Had it charging overnight.
Woke up Sunday morning and grabbed my vape: It did not work. While plugged in, it will not read any of my atomizers (check atomizer keeps flashing). Unplugged, it won't even turn on.
Took it apart to make sure the connectors were tight, no wires are pinched, etc. Nothing. It's dead. D-E-D. Dead.
Don't know what the problem is, but IMO it should not happen. I really want to like this box, but it just will not let me.
Did I mention that it feels like a small brick? Now it actually is one.
So, what you're saying is you're screwed?
Sent from my C6903 using Tapatalk
FWIW: I received mine on Saturday afternoon. Red/Black, s/n 0833. First impressions:
- Case uses all hex screws, no magnets (personally, I prefer this in this device)
- About 1 mm shorter and 2-3 mm thicker than my Cloupor T8.
- Definitely heavier in the hand than my T8. It feels like a small brick.
- Build quality seems very nice. It feels sturdy. Not a fan of the lettering, but overall, I like the look.
Vaping on it:
- Holy! I now get what this DNA200 chip is all about. Kanthal is 'as usual', but in temp control mode it is a different ballgame. Better than anything else I have (and have tried). Ni200, Ti, mixed builds, I finally get a 'satisfying vape' from temp control.
- Running dual Ni200 claptons @.1 makes battery life pathetic. After 10 minutes, battery dropped 20%. But hey....
- At 200W with kanthal this thing is an absolute beast. Instant power and the vape production rivals my best mechs - copper Manhattan w/Warhead @.09 NiChrome (dual Clapton) and my dual 18650 series box @.3 kanthal.
- Ended up uploading some images through eScribe and playing with various 'normal use' Ni200 tanks and atomizers.
After about 360 puffs on the counter, I called it a day. Had it charging overnight.
Woke up Sunday morning and grabbed my vape: It did not work. While plugged in, it will not read any of my atomizers (check atomizer keeps flashing). Unplugged, it won't even turn on.
Took it apart to make sure the connectors were tight, no wires are pinched, etc. Nothing. It's dead. D-E-D. Dead.
Don't know what the problem is, but IMO it should not happen. I really want to like this box, but it just will not let me.
Did I mention that it feels like a small brick? Now it actually is one.
If EScribe sees it when attached to computer then more than likely the fuse is blown. If it were mine I'd open a ticket with Evolv and send just the board (with the male batt connector and 510 pin included still attached) to Evolv.
This is where to be posting your concerns: http://evolvapor.forumchitchat.com/latest. Mine should be here in a couple more days.... I hope.Thanks, DWCraig1.. I looked at some videos on how eScribe looks when the fuse is blown, but for what I can tell, I am getting different results. If the issue does not get resolved by the vendor, I will definitely reach out to Evolv directly.
FYI... There have been at least two mod manufacturers, VS and Vapecige thats been reported to have made statements that there are known issues with the charging circuit on some of the DNA 200 board that causes it to die. I posted a pic of VapeCige reporting this the other day earlier in this thread that they had posted on Facebook but has since been removed it appears and @wrice4 has reported VS customer service expressing the same to him on the VS products. They state Evolv is aware of the problem and it will be covered under warranty but I've seen no statements from Evolv about this and the removal of Vapecige post has me wondering if this is being hush hushed.
Given some of the stuff coming out of vapecige, I'd take their statements with a grain of salt
Someone said almost exactly the same thing in the Vaporshark thread.
And I understand since these are only vague reports we don't really know but it seems there are a lot of reports across all device's of them just dying while charging or shortly after charging that adds a bit of credibility to these statements. In my case I've seen the charge circuitry exhibit two problems that oppose what Evolv states so I'm a bit worried about the charging circuitry myself and only charge while I can monitor.
The two problems I'm referencing is:
1. Device will not charge over 500mA if data lines present (notice it's charging at almost 1A with data line connected)
2. Will not charge over 4.2V and will trickle down to prevent overcharge (notice it's at 1A and hasn't trickled down w/ all 3 cells at 4.2V)
![]()
Someone said almost exactly the same thing in the Vaporshark thread.
And I understand since these are only vague reports we don't really know but it seems there are a lot of reports across all device's of them just dying while charging or shortly after charging that adds a bit of credibility to these statements. In my case I've seen the charge circuitry exhibit two problems that oppose what Evolv states so I'm a bit worried about the charging circuitry myself and only charge while I can monitor.
The two problems I'm referencing is:
1. Device will not charge over 500mA if data lines present (notice it's charging at almost 1A with data line connected)
2. Will not charge over 4.2V and will trickle down to prevent overcharge (notice it's at 1A and hasn't trickled down w/ all 3 cells at 4.2V)
![]()
520.00 is Temp Set (My Temp Setting)Vlad1,
What does the 520.00 represent on the right side of the USB voltage chart. (while saying 4.364 volts on the left side)?
520.00 is Temp Set (My Temp Setting)
I don't know enough about the evolv charging circuit to say, but from what I do know, that does not look right or good.
You might consider posting on the evolv forum to see if there's something that explains what your getting there. What device are you using? If it's the VS with its own charging board, it would be expected to behave differently from evolv specification. If it's just the DNA 200, you have something odd there.