Popular Content

Showing content with the highest reputation since 05/05/2020 in Posts

  1. 2 points
    Using either setup both will have the same mAh. Series configuration you're getting a full 16.8V in, 10V output, 400 watts on tap, easier on all your batteries, and a working balance charger Para series max 8.4V in, max 8.4V output, 200 watts tops
  2. 2 points
    Evolv's Data sheet shows 4 cell wiring and pinout for 400 Watt DNA250C.... https://downloads.evolvapor.com/dna250color.pdf To me the 4-cell wiring gives 16.8 volts input between battery + and battery - on the board. Connections G,1,2,3,4 are for cell voltage monitoring. At least that's my understanding. Looks like the data sheet shows the MAX input current is 30A with Peak at 32A. The data sheet also says: The DNA 250C runs on two, three, or four series voltage from lithium polymer or lithium ion batteries, and features battery monitoring and an integrated 2A charger.
  3. 2 points
    There are many themes available for download on this site authored by some pretty sharp folks,
  4. 2 points
    I almost mentioned about not playing well with USB 3.0
  5. 2 points
    Perhaps try a different USB port, preferably one on the back of computer. (If desktop)
  6. 1 point
    Hi, it's going back for replacement as only 2 days old
  7. 1 point
    По моим наблюдениям при нагреве платы более 120С, появляется сообщение "Too hot"
  8. 1 point
    The charger will see each pair of parallel cells as one battery each. No matter how many amps the supply is the board will never draw more than 30/35 amps. (And therefore never output more than 65/70 amps)
  9. 1 point
    Well you have been very helpful. You allowed me to maintain my sanity during this. So for the rest of the story... I recently received two Haku Xeta's. Both are anodized titanium. One is blue and the other is gunmetal. The blue one is the one that I was having trouble with. So I built the gunmetal one. Before doing so, I sanded off the anodizing on the clamps with an emory board, based on your comments about making sure that the connections were clean. I also disassembled the center pin which holds the positive clamp assembly and made sure the threads were clean. I then installed the coil that I had used in my first attempt with the blue Xeta. It is now working just fine with temp control. I also have a raw titanium version and that one never had a problem. I suspect it was the anodizing on the clamps. Rather than drain the boro tank and rebuild the blue one I am going to use it in Power mode until I empty the tank then I'll give it the same treatment. The Xeta is a relatively new atty for the Billet Box boro so this may come up again as it gets more popular. I don't often come across Billet Box users that use temp control so perhaps not. It's a shame because the DNA60 is such a great little chip for temp control. Thanks again for your help. For now I think this one may be solved.
  10. 1 point
    Para-series - 2 sets of 2 batteries, each set wired in parallel, then each parallel pair wired serially. So you're effectively only presenting 2 batteries to the board. Just wondering why you'd wanna do that? Why cripple the board with 2S limitations? You should use the 2S diagram.
  11. 1 point
    When you start escribe, can you post a snipping of the current profile also.
  12. 1 point
    Did you buy it directly from the Philippines? VA only services the ones they sell. If bought from a vape shop you have to go through them. You need to pursue Evolv, it's the best way.
  13. 1 point
    I have always wanted to see how VA wired it. I tried to remove the cover over the board but gave up. The cover is just press fitted in the case. I fashioned a tool from an o-ring pick and got the hooked end inside the little opening and pulled, the cover came right out. Note the black wire, it goes from B- to a spot on the case right under the board. How they attached it I'm not sure, that's copper to aluminum so maybe they glued it.(?) The 3 screws holding the board into the case are able to provide the necessary ground for both the board and 510 socket. All 3 screws on mine were a little on the loose side. I would guess that your problem is with the ground and not the positive.
  14. 1 point
    It's by design. Just use the 18650 option. Also a 2 cell device defaults to 200 watts by design. These are not problems. This may help.... https://downloads.evolvapor.com/dna250color.pdf
  15. 1 point
    Welcome. Since it was a one time thing I would't worry about it too much but would certainly keep an eye on it
  16. 1 point
    u were right! its the port looks like it wont work on usb 3.0 thank you bro!
  17. 1 point
    Data sheet: https://downloads.evolvapor.com/dna75.pdf Did you measure continuity from each ground (mounting holes) to B-? Did you measure continuity from B- to the the atty ground connection at the atty? Did you measure from the negative atty pad at the board to the negative connection at the atty? Did the board work prior to you drilling the holes bigger?
  18. 1 point
    Have you tried using a different USB cable?
  19. 1 point
    Have been experiencing some oddities with reading resistance on a DNA75 (in a JAC Vapour Series B DNA75). Note that I'm thrilled with this device generally speaking, and have been quite pleased with the Evolv boards given my experience with other mods, but have encountered some issues with my TC which I'm trying to resolve. Being highly specific: for MTL purposes, I made a coil from Lightning Vapes SS316L Clapton wire (28/36); 6 wraps, 2.5mm. Steam Engine suggests this should be around 0.7ohm (give or take, leg length and all that), and indeed when built and installed in a Kayfun Prime, tested on my Coilmaster tab it reads at 0.71ohm...so far so good. When I put this on my Therion 166 (I realize this is a DNA250-based board), it seems to correctly read it at 0.71 ohm and seems to work pretty flawlessly for TC with wattage set to 25W (which again is as I would expect given my experience with the wire---drops to around 13-15W once at temp) so seems like all is well. When I put the same tank on the Series-B, it reads it at 0.77ohm and the TC gets odd which is to be expected I guess since the chip thinks the cold resistance is 0.06ohm higher than it actually is---with the same 25W it never thinks it hits 220C so I'm basically just using the coil fired at 25W mode (and temperature is likely higher than 220 once it gets going I'd assume based on what's going on when it's on the Therion). I've done a lot of reading about this sort of thing now and realize I should ensure a few things are set up properly, and am in the process of doing just that. From the mod settings in EScribe, I can see that there isn't really any manufacturer set-up going on here as the case resistance is set to 0...all values appear to be stock default (the Therion came with case resistance set to 0.004). The atomizer analyzer isn't showing any drift in the resistance while it's sitting there (other than minuscule fluctuations as it quick-fires the SS coil), and I did a case analyzer run as the room temperature display was whacked anyway and I've allowed EScribe to set that up for me for what that's worth so will see if that helps at all. Am working on doing the "short" test to see what the case resistance actually is and will set it accordingly once I have the numbers---am waiting for a friend with some solder to come by so I can do the soldered-510-atomizer approach. My concern is that given that case resistances tend to be below 0.01, this isn't likely to be effecting the resistance reading sufficiently to account for the 0.06 difference I'm experiencing with this coil (although is likely having a more dramatic effect on the 0.15 Ni200 stock coils I use in their S22 tank so definitely worth doing regardless). I'm asking then what the next step should be should the above not correct this issue. My current plan is next to open the device up, ensuring connections/threads are clean and verifying that all the screws are making good contact with the board/510/etc. Just seeing if there is additional input as I continue to work on this issue as given my inexperience, this is proving to be very time consuming as it is Thanks ~DMcC
  20. 1 point
    I found that the power boost, and warmth setting that is factory set when you purchase the Orion is too much for the tiny coil, and small amount of cotton, which cause them to burn up fast. So I went into the Escribe program and reset the power boost settings to 0 across the board, and turned the warmth setting to 1. I even lowered the wattage for both MTL and DL a little and ever since I changed the settings I have gotten WAY better life outta my pods, both the .25ohm, and the .5ohm pods. Just a little tip to pass along, it really made a world of difference and saves a bit of money as well.. Hopefully this helps and you get the same results. Obviously it has allot to do with the juice your using and how much you vape. But I vape with my Orion allot and I found a big difference.
  21. 1 point
    Ah, well I appreciate the file regardless. I compared it to the case analysis that I had run yesterday and most of the thermal properties were within "wiggle room" of about the same so I just used the ones in the provided file. And good to know it was a physically jammed pin you're referring to - that definitely isn't the case here. The pin is still moving just fine and at least at this point isn't giving any sticking issues with the Berserker or otherwise but I'll keep it in mind for future reference. I did wonder if it was a DNA75 chipset thing, as this is the only DNA75-based product I own and I can't rule that out yet either. I still feel like just having a once over with the internals to ensure good contacts and tight screws isn't amiss. I've seen so many other reports of misread resistance being related to a slightly loose ground screw and the like to not check that. The one I grabbed is the black one (22mm) for reference. I just adore the finish on it and am a big fan of 22mm tanks anyway so it was the perfect choice (although I am tempted to grab a sandstone one as well which would let me use my Siren 2 more easily...maybe another one for my wife as well... yeah, it's a sickness but I'm just thrilled with that device, what can I say). Interesting to hear JAC is maybe going to do a DNA75C mod though. Last I heard it wasn't clear there was demand for it, but should a "Series-C" (or whatever it should be called) appear with the DNA75C, I'll be ordering the same day, foreign exchange and overseas shipping be-damned. To have something so compact, Evolv-based, and then with "replay" functionality on top of that... good lord that would be christmas. Thanks again for the feedback and we'll see how this goes. Cheers o/ ~DMcC
  22. 1 point
    I have seen one other device reading high, and when we got it back, it looked like there was an issue with the connector, it was sticking slightly and the user had been using the Beserker tank on it, which is right at the limit of the spring in the 510, over time it started to cause the connector to stick a bit, sometimes it would jam in, and cause odd readings. I am sure people will have more insights here, but if you continue to have issues, and can't get it sorted, we can replace the device for you if it is a fault in the device. The case resistance is 0.003, and I have a file for setup which was produced by one of our testers if you want that setup to see if it helps. I've attached it. It was done for using a 25R Jacsetup.ecig
  23. 1 point
    Thanks for the excellent writeup! This should help a number of people.
  24. 1 point
    There are a few mac usage questions regarding escribe spread around. To consolidate them, here is a starting point.You can run various "guest" operating systems on your mac. You will need to run a guest version of windows in order to use escribe.The simplest way to do this is with a free program called Virtualbox. This allows you to install and run many different operating systems that run virtually on your system. Prior to starting down this path, get accustomed to the lingo: your mac is the "host" and the operating system you run virtually will be called the "guest". Got it? OK.To set this up, download the OSX "host" software from:https://www.virtualbox.org/wiki/DownloadsWhile you are there, download the extension pack listed as for "all supported platforms".When the DMG for OSX has downloaded open it and run the install package as you would for any other program.After it has installed, open your applications folder, and right click virtualbox and select open...you will have to do this the first time as it is a program downloaded from the Internet...for future uses you can open it normally.Once open, use finder and go to your downloads folder and double click the extension pack you just downloaded. Virtualbox will open it and add it to its program.From here you need to install a version of windows that you will use escribe with. If you have a disk for an install, you can follow many of the guides on-line to use your install media to install the operating system. For example:http://www.howtogeek.com/forum/topic/how-to-install-windows-7-in-virtualbox-guide-hatrystIf you want to skip the install (though I recommend it), you can download pre-built virtual box images from Microsoft. These are for testing Internet Explore but work fine for running escribe. http://dev.modern.ie/tools/vms/mac/If you go the download route...they are large files. Once the download is complete, open Virtualbox and go to "File" then select "Import Appliance" (another bit of lingo is that a complete "guest" OS is called an appliance). Navigate to your downloads folder and pick the pre-setup virtualbox image you downloaded.This will bring in the downloaded install of the version of windows you selected. Once it is imported, select it and then choose "start". It will boot your guest appliance in a window. From there you will have a fully functional system that you can use to download escribe. The first thing I like to do is install the VirtualBox drivers for the host OS, for windows, you click "Devices" on the menu tab while in your guest windows OS then "Insert Guest Additions CD Image". This will prompt you to install drivers the MS way and should run its course with little issues. Once installed, you will need to reboot the guest OS.If you install your own guest OS or download it, you will need to authorize it to allow it to access your USB devices. The first step to doing this, with the guest OS off, is plugging in your DNA200 so that your mac recognizes it, then go to Virtualbox, select your new guest operating system and on the right scroll down to "USB" and click it to make changes to the USB configuration of the guest OS. Click the plus icon on the right to add a USB device to this build and then check "Dimension Engineering Evolv DNA 200 USB [0101]" so this device can be accessed by the guest OS.From there you should boot your guest version of windows. Then go to the "Devices" menu item in the virtualbox window running your version of windows and select "Insert Guest Extensions CD Image". This will put a fake CDROM into your guest operating system that has drivers for the hardware that the virtual interface emulates. Allow windows to auto run this CD and install the software, clicking yes to any "trust this developer" questions.Reboot your windows install, plug in your DNA200 and open esribe.I have found that I have to frequently issue commands twice (Connect and Download or Upload may fail the first time, but works the second). This is due to a timeout issue programed into escribe. Later versions of escribe have increased this timeout and this issue is diminished.If you have questions you can post them here and I will try and help. The process sounds more complex than it actually is.You can also use VMFusion from VMWare, parallels from Apple or bootcamp from Apple. I do not use either of those and can not offer assistance on them, but perhaps others will join this thread who can. VMFusion: http://www.vmware.com/products/fusionParallels: http://www.apple.com/shop/product/HGDA2LL/A/parallels-desktop-10-for-macBootcamp: https://www.apple.com/support/bootcamp/
This leaderboard is set to Detroit/GMT-04:00