Being a big time fan of DNA chips myself for their accuracy and having over 50 DNA mods. I think we might be missing something. As just the other day I had taken one of my Atlantis EVO tanks with a Triton Ni200 0.15Ω coil off of one of my Odin DNA250C mods and threw it on one of my Aegis X mods and I was shocked! Far more vapor and flavor. Even while chain vaping, the tank even stayed much cooler. So was the vapor as it was cooler than the DNA, both set to 440°F.
We already know some juices has complex flavors to them. We also know that most of these flavors peek at different temperatures. And the way we capture the majority of them is by controlling the ramp up time. Say for example:
- Flavor 1 peeks at 400°F
- Flavor 2 peeks at 410°F
- Flavor 3 peeks at 420°F
- Flavor 4 peeks at 430°F
- Flavor 5 peeks at 440°F
Thus we want our DNA mod to start at 400°F from the start of the vape and ramp through to 440°F at the end of the vape. At least that is how I set it up to do.
John Bellinger explained this in one of Daniel's DJLsb Vapes videos a few years back. Daniel unfortunately didn't seem to grasp the concept of capturing different flavor notes at different temperatures. Or at least didn't seem to care. At least Daniel did record it for the rest of us.
While I haven't scoped any of my Aegis X (v1.08 firmware) yet. It vapes like instead of going for a nice steady temperature like the DNA, Geek Vape went more with temperature control sweeping (I just made up that term TCS). That would explain the wide range of flavor notes I am experiencing from my Yeti Vape Haze Cap e-juice. It would so explain why the tank is staying much cooler. Some e-juices only has one flavor note and that is it and you won't notice anything special. For those you might as well just hit that temperature and just stay there.
I tried tweaking the ramp time on the DNA trying to duplicate the flavor I was experiencing on the Aegis X. I could get it somewhat like the flavors I was experiencing from the X, but the X was still doing it better. Maybe someone should contact John and Nick to have them investigate this. Maybe it might be incorporated into a later firmware update if John believes it is a good idea.