DNA 200 Watt

[Tpat591]

ok, lets say i get the hub that splits into 4 usb's. the question becomes, if i split the single micro usb port on this tablet, can i send voltage (a charging voltage, current) back through the tablets usb port? all the while having a dna 200 or any device that requires the usb 5 volts charge, operate. simplified, can a single micro usb port send and receive voltage? (voltage out for a device and voltage in to charge the tablet, all at the same time.) as for soldering on a second micro or full size usb on the mother board i guess it would be possible. theres no extra room on the board for a second so i would have to piggy back it off of the original. but if i do that, i would in effect bypass escribe's commands for both analyzers. im sure you know when running batt analyzer you have to turn the charging current to zero in device monitor so the mods battery doesn't charge in between firings. and case analyzer intermittently turns the charge on and off and also sets specific current limits at certain points in the test. believe me, i've racked my brain or this and i think ive got a decent solution. just gonna hot glue one of the micro usb charging boards(5, 1 amp boards for $3 from ebay #TP4056) to the bottom of this tablet or if im feeling frisky, find room inside the tablet casing, install it internally and make it look nice.

edit.....to sum it up, the charge needs to come from the tablet, through escribe, when running any of the two analyzers. can't come from usb hub.

That can't be right.

Escribe setting charging current to zero tells the dna200 not to accept power from the USB from the Laptop. It does not tell the laptop to stop delivering power. At least I think that's the case.

Right?

 

[AtmizrOpin]

i asked myself that when i started this project, i dont know, is my answer, lol. i took yer suggestions and ordered these just now.......
http://www.amazon.com/Friday-4-Outp...=UTF8&qid=1448853619&sr=8-40&keywords=usb+hub

http://www.amazon.com/Male-Female-P...&qid=1448855260&sr=8-11&keywords=usb+splitter

we'll find out together buddy. would be great if i could use on of these.

edit..... the more i dissect your statement about the onboard charger in the dna controlling the current limit and on and off state via commands from escribe make more sense than escribe controlling the computer's usb. thanks for the Help @Tpat591 .

 

[Tpat591]

I think escribe is sending commands to the dna board only through a command line interface, not the computer.

The first usb hub may or may not work to charge your tablet, but will still come in handy even if it doesn't. Think that Y cable will be your ticket for doing what you are trying to do. Just remember that one of those female sockets is for power only and the other is power + data. I would definitely mark which is which by painting the power one red.

 

[AtmizrOpin]

even if i have to cut and solder different connectors on etc, i'll figure out sumpin. i also think that y cable will be my best bet for what im doing. we'll see. i'll post back with what options worked best for me and my application. it's nice to have people on here who take the time to help a brother out. thanks again, @Tpat591 .

 

[Tpat591]

My pleasure, just wish I knew more about which splitter/hub was best.

 

[Vlad1]

Interesting comments.

Now you imply that Evolv folks like Brandon, James, John, and others will not give correct or honest answers. It is starting to become very clear to me now what your motive and intent is by flaming DNA's in every DNA thread and also a topic frequently visited in your beloved thread which shall not be named as this is a DNA thread here. I really think a large part of your hate for the DNA is because you try to compare it's innovative technology to a different technology which you adore. If one likes a certain technology and it gives you what you want then that is all that matters even though it doesn't function the same as a DNA. Why not spend your time on the technology you love? If you do not like the DNA why not just move on? If you want to like the DNA then why not be a part of the solution by addressing what you feel are bugs directly with those who can address them (Evolv)? You already spend time reading there.

I spend a bit of time researching new technology and should something become available that tops the DNA200 you can bet I'll have one. I'm trying to gather info on one I want to research further now but not much info available yet. It would be so nice if all new technology could come with a dedicated manufacturers forum, specific video tutorials, an opportunity to get responses from those engineers, software guys, and business owners, but at the moment Evolv is the only one that offers such customer service that I'm aware of. I hope others companies will follow as the community would benefit I think.

As I've stated previously I have no motive or intent and I'm not flaming DNA's in every thread as you suggest, but you can believe whatever you like. Most of my comparisons reflect the intended design and functionality of the board by the maker, other comments are generally personal experiences. I am an owner of the tech and I can share my experiences with others in hopes of making them a more informed consumer. Many of these forum posters love to get into their little cuddle puddle, join the gang and promote a product even if it's not that good or they themselves have had many problems or RMA's etc.. So, sorry you don't like opinions that oppose yours. I don't hate any technology but blindly ignoring bug's or blaming them on everything else when they are pointed out or trying to deflect from them with attacks like this is one thing that I do "Hate".

I'm unbiased IMO when attempting to compare products and will state bugs or potential problems I may see. And yes I compare equipment to what I have else I'd have nothing as comparison. I'm sure you recall the Bug I identified and reported in that other unnamed thread of another manufacturer with Eco Mode, the one where you attempted to take several of my posts out of context by ignoring the natural progression and re-posting them. There was quite a different reception in that thread with reports of problems where we collaborated and identified the problem, duplicated the problem, developed a work around and ultimately got a fix from the manufacturer. This thread seems to be more about how to divert from problems or blame them on the makers, user, 510 anything other than the boards and when that fails attack the poster. And for about the fourth time the bugs or problems I've posted have been posted on the Evolv Forum, rest assured they can read them if they like. Other items are by design and I'm sure they are aware of those as well.

So unless you have something to contribute to the bug I've pointed out or the questions I've posed I'll wish you a good day and ignore any further posts you or your cuddle puddle club may have that are irrelevant to those topics. I've already stated I wasn't interested in following down that path but was somehow lured back.

 

[RainZG]

^^
troll level = high

 

[retird]

Vlad1,

Yep, one can identify a possible bug and work with the manufacturer to get it fixed. You did it with a device (but not this one). We do it with the DNA. So just take your bug report to the manufacturer. Just because one calls it a bug doesn't mean it is. You would be surprised how many possible bugs (and new feature requests) were reported and corrected that were fixed even before the dna was launched (bugs in the firmware and in Escribe)(new features also added). They were submitted to the maker (both in their forums and by e-mail), not in a social forum. Those true bugs were addressed and those false bugs were laid dormant. It still works that way. I still believe that a lot of the confusion is because different technology operates differently and when one is familiar with one technology he/she compares another technology to it and expects it to work the same. One device may have a feature which identifies a non-TL coil and switches to non-temp mode where a different device doesn't. Is that a bug..... one can say it is....pretty simple to properly set the device and it won't drop into non-temp... I think one can take any latest technology device and make it work improperly...

I really think it boils down to what we see in social media all the time..... some may want to accuse, try to convince, and then convict using social media and to sway public perception while others just identify what they think is a bug and report to the manufacturer and it get addressed, either fixed, or laid to bed. I choose the later.....my approach would be to identify what I THINK is a bug, post it here, and just say I have reported it to Evolv. (I'm old but I learned months and months ago [thanks to you and others here in ECF beating it into my head ] that it is not productive nor necessary to defend any technology against another [ the technology speaks for itself ] thus you don't see me playing the X vs, Y game.) ...nuff said.... we really need to get back on track here... at least that is my opinion...

 

[BlueridgeDog]

Coming from the software side of things, users will use the term "bug" to cover a full range of things. This typically involves something like in condition A I expect output 1, but get something else. Only the designer of the product can take in an issue and call it a "bug". It is within their domain only to state that the observed condition is either intended, unintended (potentially a bug) or that there are co-conditions to condition A that are actually causing the output. Evolv has gone to great lengths to create a public forum where users of their product can state these issues (when I do this, that happens) and publicly sort out what may be a bug and what may be caused by collateral issues or miss-aligned user expectations. In the end, their judgement wins and if a given issue you have is not labeled a defect that needs addressing you have two choices: 1) give them more information so they can reconsider or 2) respect the decision made.

The forum I reference actually has a thread collection called "report a bug" where any user can make the case for the existence of a design defect. 99% of the items reported end up being classified as "not a bug, but collateral conditions causing the issue". The 1% of issues that are rolled into the development cycle are typically advocated for by bright helpful folks that want to improve a product and put real work into documenting what might be the issue and things they think could be the solution. These same folks move on from their issue if the designer states, no, this is how we intend this to work for ABC reason.

 

[nic_fix]

guys I apologize if this is really stupid but I don't know. why does it not ask new coil each time? hardly ever does.

 

[retird]

guys I apologize if this is really stupid but I don't know. why does it not ask new coil each time? hardly ever does.

Non-technical answer:
It will ask if it is not sure and/or if it thinks it is not a new coil it will not ask. That is why one can remove and refill a tank and replace and it doesn't ask.

 

[jazzvaper]

Non-technical answer:
It will ask if it is not sure and/or if it thinks it is not a new coil it will not ask. That is why one can remove and refill a tank and replace and it doesn't ask.

No, no, no.

It's a new feature called "Mind Reading". It was put there for those who confuse bugs with features. [emoji41]

 

[nic_fix]

okay, I am glad that was not a jab at me. at least I think it was not. I am pretty sure I do know who that was aimed at

 

[jazzvaper]

okay, I am glad that was not a jab at me. at least I think it was not. I am pretty sure I do know who that was aimed at

No, not aimed at you. [emoji106]

 

[dwcraig1]

Some things are better left unsaid.....

 

[AtmizrOpin]

^^^^^^like when you fart in an elevator. it's just better not to say anything. agreed.

edit.....after reading mr. dwcraig's post below this one, since he posted something HE may or may not have actually done, lol. I now realize that made a certain part of my in jest post also look like i may or may not have actually done something i'd never admit! yikes! lol edit, cut, delete!

 

[dwcraig1]

^^^^^ or when you set off the main fire alarm at the quarter billion dollar property where you work with your vape.

 

[dwcraig1]

^^^^^^like when you fart in an elevator. it's just better not to say anything. agreed.

edit.....after reading mr. dwcraig's post below this one, since he posted something HE may or may not have actually done, lol. I now realize that made a certain part of my in jest post also look like i may or may not have actually done something i'd never admit! yikes! lol edit, cut, delete!

I did it, 80 units of wealthy older folks filed out into the cold of night. That's the day I learned about the various types of smoke detectors. The fire alarm system had thousands of dollars in "upgrades" due to that.

 

[retird]

^^^^^ or when you set off the main fire alarm at the quarter billion dollar property where you work with your vape.

I did it, 80 units of wealthy older folks filed out into the cold of night. That's the day I learned about the various types of smoke detectors. The fire alarm system had thousands of dollars in "upgrades" due to that.

Did they ban vaping after that?

 

[dwcraig1]

Did they ban vaping after that?

Nope, they never knew what had happened, thought it was a false alarm.