Llama

Yup the .RUN file is what I call the snap package. But I'm OK now, as I did a fresh Arch install for another reason, and it works fine now.

Hi, and first of all, huge kudos for working on a Linux version of Escribe ! But I couldn't get it to work on Arch yet, both with the snap or the aur package, here's what I'm getting: → escribe-suite Initializing UNIX (GTK)... Benchmark: Settings took 22.258 ms. Benchmark: Register took 15.7947 ms. then nothing, the process is still running but nothing happens, I have to ctrl+c out. Tried this as root and a regular user, with the same result.

I don't use pre-heat so maybe I'm wrong, but at least I noticed that when you set a TC material, and select "Off" for the temperature in escribe, it still shows the preheat settings, while it disapears when selecting a non-TC material.

Now we have two ways to use VW mode: setting the temperature to OFF, or using a non TC material. I am usually doing the former, as it shows watts on the main screen, and I noticed so far is that it's possible to use a pre-heat with the "temperature OFF" method, but not with the material one. I was wondering if there was any other difference between thoses two ways.

Well it's just that I wasn't aware of this way of operating. Prior to the DNA200 I grabbed around the date I registered to this forum, my experience with resistance lock from another company's firmware was that it was ment for atomizers having resistance varying due to other factors than temperature. For example a 510 pin not doing contact very well with the mod, or not so good build quality. And when the resistance was unlocked, it was keeping reading the temperature to get a more acurate (I reckon average) value, to output more acurate results. I had been doing a profile per atomizer since the update allowing to change materials, but never ever locked the resistance, just using one of my workaround if I needed to recalibrate. In the end, I was just using any preset, adjusting on the fly, as I usually do pretty much all the time the same builds. Now with a better understanding of how this works it's not going to be the same. BTW, is the refining ment to do several resistance tests to do an average too ? Also is there a manual, wiki, or anything like that explaining all this ? Yes, but it's typically something that needs some playing around with values, and with its 3 parameters it could be in a menu on the mod.

I never said anything was not working as intended, I said it would be convenient to be able to quickly recalibrate. Even the fact it doesn't always detects an atomizer change is probably because the difference in resistance seemed enough for the firmware devs to assume it was the same coil, so it's like this by design. At first I didn't get what dwcraig1 ment, but after playing a bit more with profiles I understand, and I didn't know it kept locked resistance values tied to a preset (now that I think of it, I should have guessed, with the checkbox for locked resistance in profile pages in escribe) . This isn't even a workaround, but apparently a proper way to deal with the situation I described, making profiles much more usefull. Thanks for these informations. But I still think it would be nice to be able to just recalibrate quickly ^^ (and also change the preheat without using escribe, but that will be for another thread) EDIT: I rejoiced too fast, are the locked ohm values erased when the device enters in standby mode ? my 0.39? build is seen as 0.41? on all my profiles now.

Just as a follow up to this thread, I bought an Hotcig DX75, never got zapped so far after one week, and the mod doesn't go into weak battery error when it's not pushed to its limits. I'm very happy with it. Thanks for the informations !

If you set it idle long enough for it to turn itself off, then it will recalibrate when restarting (if you see the boot logos), is it what you mean by refinement ? EDIT: ha my bad, apparently it recalibrates when set idle, without entering in standby mode. I didn't know that, thanks for the tip Still, not vaping is not really what I'd call a good solution to this calibration problem, being able to force it would be much better, imo.

First of all, just noticed I posted in the DNA200 section, while I'm doing my tests on a DNA75, did the test with my 0.39? & 0.41? on my DNA200 and it asked me if it was a new coil (but I already had similar issues with closer resistance values). The example I'm using for this thread might happen because of the optimization made for low TCR materials like SS they got in the DNA75 firmware. Anyway it might be better to move this to the DNA75 section, even if I think that being able to force calibration would benefit to both chipsets. Isn't resistance not tied to a specific profile ? Or do you use resistance lock to set a resistance to a given profile ? I think it wouldn't read the right resistance when calibrating to a very different build between the close ones, if it were what you described. I tried to make refinement happen, and vaped for like 15 minutes my 0.41? with 0.40? displayed (previously calibrated to the 0.39? a bit before it was completely at room temperature). Refinement never happened. The problem seems to be that the difference is small enough for the mod to think it's the same coil, and refinement is a poor way to deal with such situation, if it means having a non satisfying vape, even temporarly.

Do you mean if I use the wrongly calibrated atomizer for a bit ? It probably would, but as far as I remember that means vaping too hot or too cool for a few minutes, which is not really a good option. I'm using SS wire, small calibration differences cause big temperature changes.

Yes, and just tried again to be sure, this time by swapping my 0.41? device back after the 0.39?, it stays on 0.39?.

I often do similar builds on my atomizers, that come out with differences in the order of 0.01?, but when I swap between two similar atomizers it often doesn't detect that the atomizer is different, and stays on the previous resistance. For example right now I was vaping on a 0.41? coil, switched to a 0.39? one, and the mod remained stuck on 0.41?. This causes an unreliable TC vape experience. There's a few workarounds for that, like mounting an atomizer with a big resistance difference between the two similar ones, or removing the batteries so it forgets its setting, but they're workarounds, and I do think there should be an easy way to do that from the mod.

Just to clarify, I own none of these mods, I had the Hotcig on pre-order, but currently cancelling it after seeing this review. What you say makes sense, especially since the reviewer doesn't seem to have properly configured the mods using escribe, and probably pre-heats at 75W. But the battery weak message and cut-off seem to happen after the pre-heat time.

The irony is that I bought a cheap 26650 mod before, to test a bit battery life on 26650 before investing more in a dna75, but it doesn't have any of these problems. So I guess it's bad components used in thoses mods.

I was looking for a 26650 DNA75 and settled on pre-ordering a DX75 from Hotcig, but apparently there's some problems with the DX75, and the VT75 from HCigar. At least on the mods that have been sent to this reviewer (skip to 20 minutes, you will see the problems) https://youtu.be/5_3TrVg0bTk Basically, the mod enter into weak battery error while the battery is fully charged, and some problem with ground turning the personnal vaporizer into a personal electrical stun stick. For the ground issue I guess it can be coming from the manufacturers, even though it's surprising that the two have done the same mistake, but the weak battery issue rather looks like a chipset issue. What's weird is that I haven't seen it mentioned in the few reviews available, anyone have seen these issues mentionned elsewhere ?