Ak89

My method noted above could work for you. If your resistor is the correct value, soldering to the location I used for green will do what you want in the end. Having the led light during firing requires using escribe to program the behavior, however having only a single color will limit the extent of what you can achieve.

@Gilbertrican90 I have no idea. My understanding is that Linux beta is a type of emulator, and because it is still considered to be in "beta" stage, it is not fully functional. Emulators are quirky things and it is hard to predict how they will function. I am not familiar with the implementation of Linux beta on the chromebook,but I know that Linux emulators on windows are terrible for anything more than simple bash commands. They don't have a full Linux kernel so dependencies usually get screwed up. I wish I could assist more, but documentation is scarce, and that Google docs statement that usb devices are not yet supported is a big problem that may not be fixable.

@Gilbertrican90 Escribe is meant to connect to evolv dna boards, typically through USB. Therefore, a mod would be a usb device....

@Gilbertrican90 You may be fighting a losing battle. Linux beta on chrome book may not support usb devices. See: https://support.google.com/chromebook/answer/9145439?hl=en @Podunk Steam Linux MX has a desktop environment so terminal may not be needed at all. Right click the escribe file. Look for a permissions tab, and check for a box (or something) referring to making it executable. My earlier post about chmod requires "+x" not "-x", I mistyped and didn't catch it until I posted. It was edited immediately, but you may not have been notified... The notes you are seeing are due to permissions on the file. If it was downloaded with a su account it requires root permissions. Download the file in your standard user account to give yourself permissions to the file, and make it executable in whatever way you find easiest. (permissions can be changed as it is but it would be tricky to type everything required on my phone)

As long as the file does have executable permission it should work to run it. If you are in the directory that the file was downloaded to, try "./SetupEScribe2_SP19_INT.run" (If that is what it is called: Linux is case-sensitive with everything. Not sure if your disto supports it, but tab-complete usually helps avoid simple typing mistakes) If that doesn't work, log out of the super user account. I know early on with the Linux releases there were issues and the script will error if it has superuser (or sudo) rights. As an alternative, if you are running a desktop environment, navigate to the folder (with dolphin or whatever file manager exists) and simply double click the "SetupEScribe2_SP19_INT.run" file. If executable permissions are set, it should start a gui of some form.

It has been a while since I used escribe on Linux, but if I remember right the *.run file is a script to install. You wont use apt. (Unless something has massively changed) It can be used for any missing dependencies, but not for the actual install. Try using "chmod +x" on the file then running it as an executable. Edit: I used minus x instead of plus x.

@bluegray Hmmm. You have me curious now... If this Behavior existed intentionally, I'd be interested to know the reasoning behind removing it. I know my 250c doesn't do it so I would assume there isn't an issue with yours. Please post what you manage to learn from evolv. I'm sure there would be others equally curious as well.

@bluegray The 250c does a lot of math when calculating resistance and TCR. I assume in order to get replay to function. When resistance is set on a profile, the board also saves ambient temp readings from a built on sensor. The board then calculates "expected" resistance changes based on changing ambient Temps and Coil material saved in the profile. As far as I know, the older boards lacked the ambient (room) temp sensor. Meaning that they were making calculations based on live ohm changes instead of any form of baseline, which the resistance lock may have made up for. So, on the 250c, say I am running a profile with ss316l and tc, coils measuring 0.2ohms at 75F degrees. If I am outside in the cold for a while the temp lowers, and so does the Coil resistance. If I vape, the Coil resistance rises but ambient temp does not. But based on the TCR of ss316l, the 250c recognizes the change as being normal. However, if I remove and reinstall my rta while the coils are warm, the detected changes in resistance (from nothing to, say, 0.24ohms) would be outside of the TCR possibilities and the board asks if they are new coils. Had I locked the resistance (ohms) the board would seemingly ignore the above mentioned wild swing and simply assume the coils are the same regardless of their current state or measured resistance. Another possible use of the "ohms lock" would be setting profiles for multiple Atomizers, each with differing builds. Assume that Mod and Atomizers were the same temp when profiles were set up, but the mod stays in a pocket all day while the additional Atomizers may be sitting near an air conditioning vent. Temps between the two can be very different. Having the resistance already locked in the profile can allow the 250c to utilize the coils on a newly swapped atomizer accurately without any effect from differing temps/resistance or waiting for the temperatures to stabilize between the two. A third use could be for atomizers/coils that aren't very stable, having shifting resistance for unknown reasons. It would effectively prevent random "new coil" prompts.

@bluegray No "auto-correction". It would be counter-productive because of the multi-profile design of the board. (ie You can set a profile for each atomizer. Helpful if one rotates tanks regularly.) As for ohms lock, I find that it is helpful if I remove my rta/rda while the coils are warm. The DNA board will detect the absence, and when I screw it back on it assumes that I have provided "new" coils of a different resistance. A "new coil?" prompt can be annoying when it happens a lot. (I clean dust and stuff from my mod often. Hazards of work.) FYI, Ohms lock is per profile. Setting it does not change non-active profiles...

I personally haven't had this issue. I do know that the larger pads dissipate heat more and may be contributing to your problems, however, I assume that your main problem is an absence of flux. Don't rely on the flux within the core of the solder to be sufficient, unless you melt tons of it directly onto a hot pad. (Which could cause board delamination and pads that peel off from the excessive temps---NOT recommended) Instead source standalone flux (Rosin, not the acid stuff for plumbing), preferably no-clean or alcohol cleanable. (Avoid "water" clean, for obvious reasons) To make things simple, source a "flux pen", a nifty little dispensing pen with a felt tip. However, a bottle of liquid or jar of paste can be used rather simply too.... As a side note, a soldering iron that is "too hot" can cause problems too. Dull joints are a sign of too much heat, or not enough flux. The solder oxidizes, forming a crystaline structure that cracks easily and adds excessive resistance. "Good" joints are round and shiny. Not sure if these are your issues, but something to look at. (Edit): Also, take note that DNA boards, like most all circuit boards these days, are made with lead-free solder, which has a MUCH higher melting point than standard 60/40 leaded stuff. (Something like 100-200°F more) And mixing lead-free with lead is tricky because of the temp differential between them. If your iron isn't "Lead-free" capable, meaning adjustable, and able to achieve the higher temps, then this, too, can result in your difficulties.

@engmia I vape almost exclusively in TC, although I do play around with replay one in a while. My go-to is a Vandy Vape Pyro at the moment. Dual coils of quad-twist 28g SS316L, 7 wraps, resistance of .175 ohm. Settings currently are TC, 460F, power set at 110W, preheat at 120W, and punch at 8. Even at those wattages I can easily vape all day with ~30% battery remaining when I plug it in at night to charge. I don't disagree that 20700/21700s are superior to 18650s for capacity and amperage ability, however, my experience is that they don't tolerate high drain very well. Internal resistance comes into play.... My preferred vape works MUCH better with a Li-Po. Higher wattage abilities without voltage sag or parasitic loss due to excess battery heating.

@DJT All possibilities. I have had a couple chargers that acted strange. Not Nitecore though. One (Efest, I think) seemed to stop charging almost randomly, sometimes going beyond 4.2v. Another that routinely stopped at 4.15v. Coughed up for an Opus BT-C3100 and never looked back: it consistently charged to a perfect 4.2v. I don't use 18650s in my mod anymore, but I still use my Opus to charge flashlight and other batteries. (As well as capacity and health testing...) If you have a multimeter, check voltage of the cells once the charger says they are full. That should give you a good idea of where it is stopping.

@DJT On a whim, try using the DNA to charge your batteries vs. the external charger.... Maybe the charger is stopping prematurely? Just another idea to try out.

@DJT It appears from your screenshot that your batteries aren't balancing. If those cells truly are fully charged, "fresh off an external charger", then they are not matched very well. The voltages vary too much. The DNA board will show 100% once ALL batteries balance. Out of curiosity, what batteries are you using? I have found that "cheap" (Usually more expensive) re-wrapped cells sold at local vape shops tend to have quite a bit of variance. The quality control just doesn't seem to be as high as quality branded batteries. (ie. LG, Sony, Samsung) In fact, many re-wrapped batteries are actually cast-offs from such branded companies; cells that did not perform to specifications and quality requirements demanded by the company.

If the battery is new, I'd say return it. With the voltage on cell 3, it would not be safe to try to force a charge. It is permanently damaged. Be safe with LiPos. Chemical fires are scary...