In a couple more days the hcigar boxes should start popping up for sale.
Then again maybe a bit longer.
Then again maybe a bit longer.
No but it can be installed using Boot Camp, VirtualBox and the like.does anyone know if the DNA 200 software is Mac compatible?
i was just about to pull the trigger on a sx mini m class to replace my vapor shark RDNA but now the DNA 200 is out!!! what to do????
Not yet. Use a virtual machine to run windows. I'm having to do it to use escribe on a Linux laptop. Apparently evelv are working on it at some point but its not a priority to them because windows has the largest market share. Virtual machine is the only way to do it without buying a new computerdoes anyone know if the DNA 200 software is Mac compatible?
i was just about to pull the trigger on a sx mini m class to replace my vapor shark RDNA but now the DNA 200 is out!!! what to do????
ok thanks for the info. i'm not buying a computer just to vape? i have a RDNA 40 and it S@cks in temp control that i need to replace!!!! i keep reading about how good the sx mini is and now the dna 200 comes out? i know this is not a witch is better discussion? Cant wait to there is a compression review !!!!
I personally think the hcigar vt200 box is one of the nicest looking production dna200 mods I've seen so far. I would buy one.In a couple more days the Hcigar boxes should start popping up for sale.
Then again maybe a bit longer.
With all the new devices being released or soon to be released that incorporate the DNA 200 board is it at production release at this point or are they still in Beta / Pre-production on the boards?
With all the new devices being released or soon to be released that incorporate the DNA 200 board is it at production release at this point or are they still in Beta / Pre-production on the boards?
I personally think the hcigar vt200 box is one of the nicest looking production dna200 mods I've seen so far. I would buy one.![]()
The production board won't be changed if anything they will just release another firmware update. The board only had the pre beta run just to make sure it was solid before mods started coming out. It is solid tho and most failures were manufacturer errors
As Tom pointed out, the hardware will not change. The firmware is rapidly changing. The rate of "bad chip" or as evole called it "infant mortality" isn't bad, but there are some vendor install methods that seem to be causing issues (Hana pinching the screen ribbon, Opus using metal nuts to hold the board in for example).
Is there a way to identify what the manufacturer date or revision is in the event there are hardware changes?
Under the "General" tab in Escribe for the DNA 200 click on "information" and the date the board was initially programmed is shown.
The current firmware version is shown on the Device Monitor screen at the lower right.
Duane
You can get the date the board was programmed in EScribe.
Thanks, I've played with Escribe a bit but those function are unavailable to me since I have no device to connect yet so it just errors. I should be able to check once I receive the device but that would only tell me when the chip was initially programmed not necessarily what revision or date of manufacture of the board correct? I guess my question is more to do with the hardware revisions not so much about when the firmware was uploaded, but that may not be public knowledge.
I believe that the "initial programming" date equates to the manufacture date. I don't know how one could get a better handle on the date that manufacturing was finished than "initial programming".Thanks, I've played with Escribe a bit but those function are unavailable to me since I have no device to connect yet so it just errors. I should be able to check once I receive the device but that would only tell me when the chip was initially programmed not necessarily what revision or date of manufacture of the board correct? I guess my question is more to do with the hardware revisions not so much about when the firmware was uploaded, but that may not be public knowledge.
I believe that the "initial programming" date equates to the manufacture date. I don't know how one could get a better handle on the date that manufacturing was finished than "initial programming".
Duane