JoeBingo

In the Linux Mint distro world (and many others) under a similar software release philosophy, they call it a BETA release. Been that way for well, always. Available to anyone who would like to have it for testing and evaluation before posting a finalized update release to their servers. Beta / Early ... same difference I guess. I'm just becoming familiar with "your" terminology and semantics. Thanks

... I had overlooked those pinned posts because they are labeled as "Early ..." and thought they maybe had no current relavence . D'OH

Thanks !!! ChatGPT can rest easy

Okay, so no one has chimed in with thoughts and I have not been in contact with Evolv. So with that said, I will try to answer my own questions with my best guess. 1) Any idea what the differences are between U.S. and INT service packs with the same numerical release? Historically, some firmware or SP releases included features or options that were only in the International edition, either because the feature set wasn’t compliant with certain regulatory restrictions in the U.S., or Evolv wanted to test new or experimental features internationally before wider adoption. For example, older SPs sometimes enabled Boost or other features only in the International Edition of the firmware or EScribe build. However, overall the numerical version itself (like 1.1 SPXX) refers to the same core service pack release. The U.S. and INT builds typically differ only in regional compliance bits or included features rather than major functional divergence. 2) Given they are numerically the same, which should I use, the latest INT or latest U.S. version ... or whichever one is recommended? If your device was sold in the U.S. and you want to stay within U.S. compliance, then using the U.S. SP makes sense. The International SP will generally work fine too (they are not usually restricted), but could include options or behavior that were originally intended for markets outside U.S. regulatory constraints. EScribe’s built‑in Update/Check for Service Pack feature sometimes auto‑recommends the INT version even for U.S. users. This behavior seems driven more by the latest unified build being marked as recommended in Evolv’s servers, not necessarily because the INT is “better” for U.S. users. Why EScribe might suggest INT first: EScribe’s update service likely pulls a default recommended build that is not region‑specific. Evolv’s backend does not always segregate recommendations by U.S. vs Int based on your computer locale. Thus even on a U.S. EScribe install, the INT build may show as the recommended update. 3) When update service packs are released, is there any documentation as to what was changed from the previous service pack? Official Evolv documentation does not publish detailed change logs for every Service Pack. Evolv’s website and support pages do not provide a comprehensive public changelog for SP releases. Final thoughts about the practical reality of all this as pertains to my DNA 60C: Functionally and operationally, both U.S. and INT service packs which are numerically identical are also effectively identical. The firmware code controlling power, boost, screen, menus, and safety checks is the same. There are no extra features in the INT build that affect how the board works day-to-day. The only differences, if any, are “region tags” or regulatory compliance markers that Evolv embeds in the build. For example, Evolv might flag the U.S. SP as meeting FCC/UL requirements. The INT SP is flagged for non-U.S. markets and might include “experimental” options in some larger boards (but DNA 60C doesn’t have those). Bottom line: For a DNA 60C, you can safely assume that the U.S. and INT SPs with the same number are essentially identical. The difference is mostly for Evolv’s internal labeling and compliance bookkeeping, not for anything you’ll notice while using the device. ... am I wrong? 🤷‍♂️

OH ... Just to add ... The EScribe version I downloaded and installed is the US Version for Windows. So that isn't an influence as to why maybe the recommendation is to upgrade with an INT service pack. In fact, the recommendation seems counter intuitive when there is a US service pack available with the same version number. That's why I asked the questions in the OP, to try and wrap my head around it. Thanks !!!

When device is attached to EScribe and a Service Pack update is recommended, it seems to always be the INT version. When I go to the install service pack tool, I sometimes find the same numerically numbered SP but with a U.S. designation. I'm in the U.S. so it would seem the U.S. SP would be preferred, but in the install menu, the INT version is still listed as "Recommended" in parenthesis. Questions: 1) Any idea what the differences are between U.S. and INT service packs with the same numerical release? 2) Given they are numerically the same, which should I use, the latest INT or latest U.S. version ... or whichever one is recommended? Also I don't know if the information is even available publicly, but ... 3) When update service packs are released, is there any documentation as to what was changed from the previous service pack? Thanks !!!

Oh how I was wrong LoL. The Evolv DNA 60C is awesome and Evolv, with a keen eye on safety, performance and reliability, has allowed for ALL vaping persuasions. Sometimes devices don't arrive perfectly configured from a manufacturer or vendor, but that isn't Evolv's fault. The possibilities are there for the choosing in EScribe. With invaluable help here, I've gone through the bonding phase and have my device dialed in perfectly. I apologize for my earlier naive, newbie observation. D'OH

Thank you for the patience, consideration, suggestions and support @Wayneo ... continues to Evolv

Now if I can only figure out how to set something so that the DNA 60C circuitry queries the atomizer routinely for resistance rather than only during firing. In other words, when I attach an atomizer, the display should automatically show the current coil resistance rather than all zeros ... until I fire.

Is there maybe a downloadable theme here that I might be able to temporarily upload to my device just to see / copy how they did it? EDIT: @Wayneo ... nevermind. Actually your pointing me to the Power Options Settings in themes allows me to do EXACTLY what I need to do for my theme. Thank you sir

Thanks @dwcraig1 and @Wayneo for sorting me out on this. Greatly appreciate it !!!

@dwcraig1 ... thank you for all your patience and help. I'll have to fiddle with everything a bit more, but I've learned I can dial in a virtually perfect vape for me. I'm real close now. Just need to sort behavior of Evolv software and hardware. Couldn't have done it without EScribe or without your help. Thanks !!! I'm done for tonight. It's late and I'm old HA

One other thing of note @dwcraig1 ... If while in that profile I've set to 6.5W, I happen to manually change the wattage on the device with the +/- buttons ... the device will not go back to the 6.5W. It will fire at the whole number for which I've manually selected. Consequently I will need to configure a profile for any partial watt value and remember not to manually adjust the wattage on the device ... change the profile on the device instead. If that makes sense.

Good call @dwcraig1 and you nailed it. When set to 6.5W in the EScribe profile, the vape device I'm using and Evolv hardware displays 7W. But when I check Device Monitor in EScribe and take a pull, Current Puff Power is ~6.5W So for device display, the actual power setting is rounded to a whole number but the device is still powered IAW profile setting as proven by Device Monitor. Good call. Thank you for following up on this.

@dwcraig1 ... What I just now tried in EScribe ... By default as the device arrived, my Watts profile is profile 2 in EScribe. In the Settings > Power field of that profile, I changed the value to 6.5W Then I uploaded settings to device ... The DNA 60C display on my Cthulhu Sentinel immediately showed 7W ... the Evolv software rounded up a half watt. Hmmm ... thinking out loud, but maybe there's a setting somewhere in EScribe about how it handles decimal places or something ... dunno 🤷‍♂️