blueridgedog

I think that is the XP device monitor display issue that has been addressed to my knowledge.

I think any connection to the vehicle, especially one that will draw up to 23A, should be fused. This is not to protect the mod, but the rest of the car.

Sounds like a bad cell. I would return it prior to the hassle of building a mod around it.

You can easily use anything from 900 up to...well as big as you want to carry. The C rating required goes down as you get higher in mAh or Ah.

Any C rating over 20 for a 2200 pack would be fine. A 10 C rating on a 5000 pack would give you 50 amps, so more than enough. Most packs you find in the upper mAh ratings will be well outside of the rating.

Sounds like screen pinch...worth looking at to verify.

I think he is vaping off a larger capacity "setup" pack until the back is finished.

The chip requires a maximum input of 23amps. A 1000 mAh or 1Ah pack would then need to be rated at 23c to achieve this, but have no margin of error. C is for capacity and the rating is the multiple of the the capacity that it can be discharged at. So a 1000mAh pack rated at 10c would be able to sustain 10 amps (1000mAh = 1Ah, 1Ah * 10 = 10Amps). So, as the capacity of your pack goes down, you will need a higher C rating to cross the 23amp minimum. A 2000mAh pack can be solved with 2Ah * X = 23A or 11.5 C. For a smaller pack, say 850mAh the math is .85Ah * X = 23A or .85 * X = 23 so X=27.06. In each case I would go for a 20% margin of error (increase in C rating of the pack). A fast way to do this is to simply know that your pack in Ah ratings (1000mAh is 1Ah) should be greater than 28 (23 plus a 20% margin) when multiplied by its C rating. So a 1300mAh pack with a 20 C rating gives you 1.3 * 20 = 26 sustained amps and would be rejected (below the margin), but a 40 C pack of the same capacity would give you plenty of amps. If you post the mAh rating you are considering, a minimum C rating for that pack can be suggested.

It sounds like you have a resistance issue in your atomizer or in your atomizer wiring. A few things I would do to get more information: -use a piece of straight copper wire to create a near zero resistance bridge on your atomizer and then run atomizer analyzer to see what the rest of your atomizer looks like from a resistance perspective. It could be a week 510 spring or a atomizer with an internal sprint that is part of the circuit. I have one of the new GTS2 atomizers that I can't use on my 200 as it has a center pin that is not making contact with the metal in the atomizer unless it is firmly pressed. It is firmly pressed in the reference designed 510 and works (a friend of mine has the reference mod) but on other available 510's it fails due to varying resistance. -try another atomizer and compare results -evaluate your coil build...is it a good TC coil? Firm connection to the atomizer, no contact areas that would create hotspots and no way for the resistance to dramatically change under load.

Excellent that you discovered that the mod was locked and that the chip itself is fine. As to the screen and cable, yes I too tend to beat them up when testing out a new enclosure design. Most modders or case designers I know of have eaten at least one. I have defaulted to using a dead screen for such purposes for that very reason. A few rough installs is frequently enough to bust them. I have also started testing enclosures without the ribbon connected initially (for the DNA200, not for the 40 and others as I now have dead boards and screens for each of those that I can test with). They are cheap to replace: http://modcrate.myshopify.com/products/dna-200d-replacement-screen-oem Additionally, Evolv may stary carrying them on their website, that that is just a suggestion at this point.

Have you configured your battery on the mod tab to let it now the watt hours you are using? A hard reboot is not a bad idea to get more information. I would do it when the mod is cold and unused to see if the chip temp is correct.

Shouldn't Hana Modz be loading out a correct setup of the chip, specifically as it relates to battery? I am confused...are folks saying the chip is coming without having been configured for the battery that they installed?

Which raises the question: What torque is recommended? I only use plastic cases, so the plastic will strip prior to damaging the chip, but for those using metal, can we give them a rating?

I have that pack and it gives me 1.5 days of vaping at a frequent rate on a .23 coil with big vapor and I undercharge it.

Statistically if the cable came with a cell phone charger...it has a good chance of not having the data wires...just to save money.

Would a 2S lipo work?[/QUOTE] Yes

In the STL files they are holes in the solid...ie there is no closure to the face...they are not tubes but simply holes. There are also gaps around the edge of the atomizer milling area. The entire STL comes across as full of open faces.

There are some near ideal hammond builds in this thread: /topic/65689-topic/

I think you have to commit to a lipo size based on your vaping style. I get buy on a 1,000mAh pack. If you think you can do the same, then look at the hammond build in the thread on this forum about builds.

What lipo are you contemplating?

And there are those who can't believe in this day and age that there are people still using IE. The list of reasons to avoid it are long and significant. Personally I recommend Chrome for fast safe browsing.

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/Downloads While 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-hatryst If 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/fusion Parallels: http://www.apple.com/shop/product/HGDA2LL/A/parallels-desktop-10-for-mac Bootcamp: https://www.apple.com/support/bootcamp/

Have you tried making a profile for a non-TC wire and using that? I believe based on discussion here that the chip will determine TC availability by looking at the resistance response of the coil.

They have yet to start to git repository for the project. Unless I have missed it. If you know where the community entry point is to this project, let me know. As is, I have only had to assume that they have not started it.

I have laid out three squonkers. Currently testing this one: https://www.shapeways.com/product/R52DK7LSJ/dna200-squonker-v2-7?li=shop-results&optionId=57414597 How big is too big?