bluegray

#!/bin/bash export UBUNTU_MENUPROXY= mono /home/user/.local/opt/evolv/escribe-suite/main/EScribe.exe --launch DeviceMonitor & I use this to launch Device Monitor directly.

Yes! Updated SP19 is working fine again, thanks @James

Yeah, it takes much longer to start up, and it's as if any click actions take a few seconds to complete. Would it be possible to try the new SP with the old compiler please?

Thanks for the update @James, just tried it out. Curiously, this update and SP18 is very unresponsive - I've had to revert to SP17, and that works flawlessly. Did anything change recently that might help me debug?

Thanks @Ak89 , I can't speak for older boards, but on my DNA60 both the board and room temp sensors are present. This is going to be a little long-winded - but hopefully it clarifies better what I'm trying to convey On my DNA60, cold resistance is defined as the resistance of the coil at 70°F. While firing, the coil is heated and the live resistance change is measured by the device and then used to extrapolate the temperature of the coil based on the TFR curve (or TCR value) and the cold ohms value set. This is all well understood and functions the same on most TC mods. Assuming the TFR curve accurately describes the resistance change of the coil with change in temperature, the cold ohms is therefore setting a baseline value to figure out the temperature of the coil from it's resistance. So for most TC board, unless you connect a new coil at ambient temperature 70°F, there is no way for the board to know the true ohms at 70°F, unless you specifically set it to a previously measured value. But by using the ambient temperature reported by the room temp sensor, and assuming the coil will also be at that temperature, the resistance at 70°F can be guessed by the board. Because there are a few factors that can influence the reported temperature readings, this is not always accurate, and there can still be a difference between the true temperature of the coil, and the temperature reported by the temp sensors. What makes the DNA boards more accurate, for the DNA60 at least, was that while idle, the temperature values and coil resistance values were periodically measured. When the board finds that both are reasonable stable, ie. not changing much over time, the cold ohms value was updated from the measured resistance and temperature. Obviously, there are a few factors that can still mess with these recalculations. Room temperature is not always stable, and temperature measurements are notoriously inaccurate, since they are located inside the mod, next to batteries and coils with little airflow. Coil material and atomiser connections can also influence resistance measurements. And this is where locking the cold ohms value comes in. I can tell the board, that I'm satisfied with the current cold ohms value, and that it does not need to refine it further if it detects changes in temperature or resistance when idle. Normally this is not needed, as refinement is usually pretty accurate, but there are circumstances where it is useful to override the automatic refinement of the board. And indeed, as far as I can tell evolv only recommended locking ohms when experiencing instability issues. Now, on the DNA250C the notion of "cold ohms" is somewhat different. The temperature can be specified/saved with the resistance at that temperature. Although we don't have to specify cold ohms at 70°F anymore, it is effectively still the same thing, a specific resistance value for the coil at a specific temperature, from where the temperature of the coil can be extrapolated with the TFR curve. All the previous issues with finding accurate cold ohms values from inaccurate temperature sensors inside the mod still applies in the same way as before. The only difference is cold ohms is not necessarily defined at 70°F anymore. This is all fine and good, but the one feature that set the DNA boards apart in my opinion, was the ability to refine the cold ohms value when idle. So far I haven't seen this happening on my DNA250C at all. The cold ohms resistance and temperature is effectively locked and no refinement takes place at all. Since there is very little documentation available, I'm basing this on my experience with the boards I have used for a while now. What I would like a definitive answer on, is whether the above is indeed the case and the intended behaviour. Based on @Wayneo 's answer above this seems to be the case. What is confusing to me, is that there is still a setting to "lock cold ohms" in EScribe. Either the idle refinement of cold ohms feature was removed, therefore making the lock setting obsolete (since it is now effectively always locked), or there is something wrong with my mod/board/coil, or indeed my understanding of TC on the DNA board for the last year To further the confusion, if automatic refinement was removed, I don't understand why evolve would remove the one feature that made their boards more accurate to calculate cold ohms. Sure you can set the temp for cold ohms now, but the recommendation was always to not lock cold ohms unless you have a problematic atomiser setup that made automatic refinement inaccurate. That recommendation is contradicted by them effectively always locking cold ohms now. I don't really care either way, as I can manually measure cold ohms quite easily, remembering that it should be done only when the mod has cooled down for a while and temp sensors are stable. But I would like to know if there is something wrong with my setup that prevents me from benefiting from automatic refinement if it is indeed still present on the DNA250C boards. As it really was the most useful feature that set DNA boards apart form other chipsets.

I don't think I quite understand what you mean by auto correction being counter productive as ohms lock can be set for each profile separately as well. Auto correcting cold ohms has been a standard feature in all non color DNA boards afaik, and they all have ohms lock as a per profile setting. It seems to me that the ohms lock function on the color boards is not doing anything at all. Cold ohms is effectively always locked as far as I can tell. I contacted evolv support as well to get a definitive answer. So far I only got a handful of unrelated copy/paste replies that does nothing to explain cold ohms locking behaviour for the new color boards. So it seems not even evolv knows what the lock setting actually does...

So no automatic correction for cold ohms over time like the older boards used to do? If so, then what is the ohms lock for?

I just got my new DNA250C mod and I'm still getting used to it, as there are some differences from the DNA60 I'm used to and have been using for quite a while. For one, I have never seen cold ohms to be corrected after letting it sit for a while. Cold ohms is not locked as far as I can tell. I've tried deliberately remeasure cold ohms with a warmish coil, so I know it will need to be adjusted, which it normally does on my DNA60. But it seems that this behaviour has changed on the DNA250C. The only way to correct it, is to wait for the coil to stabilise and manually remeasure. Is this the expected behaviour? I'm on the latest SP38 firmware. Another slight niggle is the fact that you cannot change temp/watts directly with the up/down buttons. You have to select the field first and then edit. This is probably to allow for more theme customisability, but I do miss that I cannot easily change as I would on the DNA60.

@Coyote, do you know how the min/max values for a gauge works? There does not seem to be any way to customise that. Eg. I'm trying to add a gauge for live ohms, but it's not very useful since it always just show the gauge as almost empty because the ohms value is always low. Ideally I want to specify that the gauge should be full at ~ 1ohm.

I have been using GeekVape SS430 for a while now with a custom material profile (TCR 0.00185). This works fine for the most part, but recently I noticed that if I leave my mod to cool for a while, the cold resistance fluctuates quite a bit. Between 0.69-0.71 ohm for my current 10 wrap spaced single coil. Which means I constantly have to check and lower temp to not get burnt hits. My mod is a EPetite with a DNA60 board. As far as I could gather, cold resistance is fine tuned by using a combination of material profile and case thermal settings, with the latter not applicable to the DNA60 because the USB charging happens off board? For reference, I got the TCR 0.00185 value from this post, and also verified that with a dry burn test and some experimentation.

I use 0.011 Ω for my EPetite and it works fine most of the time. I do have a slight issue with cold resistance changing over time, not sure if it relates to the internal resistance setting. Also see discussion here: