Magigamix

Yes, it works on Debian 12 bookworm. (It doesn't work / is not installable on Trixie (testing) as some packages are missing (gtk-sharp2 and others), it can be installed after getting the missing packages from bookworm, which is not ideal).

No, I've not tested the suite in Linux Mint 🙁, I use Ubuntu 22.04 and it works fine, it should work in Mint without problems as it is a derivative distro of Ubuntu.

In order to Escribe to recognize a theme (either by opening with "Escribe -> Theme -> Load Theme..." or with the Theme Designer) the xml file (ECigTheme.xml) should be zip compressed and with the .ecigtheme extensión:

I think there is not such combination of buttons on the "C" boards, as all the functionality should be accessible through the installed theme. The theme developer decides what options are available.

I think the download links are broken:

Hi @James, Thanks for the update, unfortunately neither of the two Service Packs (1.1 SP55 INT and 1.1 SP46 INT) included with the new SP44 for Escribe fix the "Temp Sensing Detect" issue: Once the "Temp Sensing Detect" value is set (on or off), it will never reset until the battery gets removed or the config is uploaded to the device. On 1.1 SP33.2 INT, TSD works good: the TSD value gets reset by removing the atomizer, by switching between Profiles or Materials assigned to the Profile. -Ariel

Update: - With the latest Firmware Version: 1.1 SP45.2 INT: TSD doesn't work as expected. - With the previous available Firmware Version: 1.1 SP33.2 INT: TSD works as expected (the value gets reset after switching between Profiles, or Materials, or by just removing the atomizer. The only problem is that this Firmare verson doesn't implements the "Highlighted fields now time out after a while", which is a nice feature. More info in the following post:

Yes, that is the difference ! (I was writing the post and accidentally pressed Ctrl+Enter, I posted it before finishing writing it, I just edited the post with the complete information).

Hi @BillW50, My device (DNA 75C) is running the latest available firmware: ------------------------------------------- Firmware Version: 1.1 SP45.2 INT Firmware Date: 2021-12-22 Escribe version: 2.0 SP31 Date: 2021-12-22 ------------------------------------------- Tried with the previous available firmware: Firmware Version: 1.1 SP33.2 INT Firmware Date: 2018-04-17 And it works, the TSD value is reset after switching between profiles or by switching the Material for the Profile. I also can confirm that the TSD value is reset if the atomizer is removed from the device (no need to switch between Profiles or Materials). The only problem with this firmware version is that it doesn't implement the "Highlighted fields now time out after a while. This is nice for themes with very visible selection colors." feature, which is nice to have. So, it looks something about the TSD changed on the latest firmware (1.1 SP45.2 INT). Resuming: The TSD behavior in firmware version 1.1 SP33.2 INT works as expected but it doesn't implement the "Highlighted fields now time out after a while". The TSD behavior in the latest firmware version 1.1 SP45.2 INT doesn't work as expected, but the "Highlighted fields now time out after a while" works fine.

Hi Hubert (@Mr.Bottomfeeder) , thank you for your answer. Do you mean the "Device Monitor" Reset Action? (it was the only option I found on "Theme Designer" related to "Reset Device". I tried it and it doesn't work, I think it resets the selected options of the "Device Monitor" on Escribe, unfortunately doesn't changes the set value of TSD. TSD keeps if saved value (after the first fire on a TC Profile) until the mod is reset, by removing the battery, for example (I have tried by switching between Profiles, Temperature-Sensing Materials assigned to the Profile, or after a "New Coil" is detected), I added a field to show the status of TSD, it keeps its saved value (never runs again the validation). My theme has a lot of complex conditions based on the TSD value, so this affects it a lot 😕. Meanwhile I removed the TSD on the conditions, so my theme is not "Smart" anymore. -Ariel.

Thank you for the answer. I already submitted a Support Ticket. I have tested it, unfortunately by switching to another Profile (or material assigned to the Profile) doesn't unset the saved value for the "Temp Sensing Detect", it keeps its value until the device is restarted: I added a filed on my Theme that shows the status of the "Temp Sensing Detect" to check if it changes after switching to another Profile and it doesn't, even if a New Coil is detected and / or firing the Mod for the first time after switching to another TC Profile with a proper TC Coil installed. The impact of this depends on how the Theme reacts to the "Temp Sensing Detect" value (what it shows, what enables or disables), on my Theme, when a no TC coils is used on a TC Profile, it switches to Watts mode, disables the TC features and shows a message on the Main Screen letting the user know that he is using a no TC coil on a TC Profile. But there is no way to revert back, as the "Temp Sensing Detect" was already set, and the "routine" doesn't run again. Excuse if I'm being redundant with trying to explain, English is not my native language, so sometimes is difficult to express myself. -Ariel

Hi, I would like to report an issue: The function that sets the "Temp Sensing Detect" value only runs the first time the board is fired when in a "Temperature Control" Profile, once the value for "Temp Sensing Detect" is set, there is no way to re-run the function, so the "Temp Sensing Detect" value will still unmodified until the board is restarted. My theme uses a lot the "Temp Sensing Detect" value to decide what to show / hide, and to enable / disable some features, for example: If the board is configured with a "Temperature Control" Profile* , and it detects** a no temperature control coil is fired, it switches to Watts mode, on the Main Screen shows the corresponding information to that mode (hides anything related to Temperature Control and its different features) and disables some features for that Profile. The thing is that there is not any way to re-run the function to check and set the "Temp Sensing Detect" value, that is, if a proper TC coil is installed, the board never checks again, so the "Temp Sensing Detect" value will stay as false, until the board is restarted (by removing the battery, for example). The value of "Temp Sensing Detect" will not change after the "New Coil" detection. Desired operation: maybe the "Temp Sensing Detect" routine should reset its value to "True" every time a "New Coil" is detected and the board is using a Temperature Control Profile, it should run the first time the board is fired and Temperature Control is enabled for that Profile. The value of "Temp Sensing Detect" should be reset every time the users switches between TC Profiles. There is a discussion thread about this, but we haven't find a solution: --------------------------------------------- Serial Number: MOVE OVGK AWSH Firmware Version: 1.1 SP45.2 INT Firmware Date: 2021-12-22 Revision Code: 311104598 USB Vendor ID: 268B USB Product ID: 0418 USB Product Version: 1.1 --------------------------------------------- * A Profile with a "Temperature-Sensing" material assigned to it, and "Temperature Control" enabled. ** Based on the "Temp Sensing Detect" function / value). Thanks in advance. -Ariel.

After some testing, I discovered the "Function" that sets the "Temp Sensing Detect" flag, only runs the first time a TC Profile is fired, for example: Insert the battery. Select a TC capable profile, let's say Titanium Profile with Titanium Wire assigned and defined as a Temp-sensing material. Install an atomizer with a Titanium wire, and fire the mod. It will ask if it is a New Coil, select Yes. Everything should work as expected, TC Mode. Then without changing the Profile, install an atomizer with a no TC material, Kanthal, for example, it will ask if is a New Atomizer, select "Yes". The Board will still working as if it was a TC capable coil, of course, it will not be able to control the temperature, but it will never switch to Watts mode. TSD Function never runs again, which in my opinion is wrong. ---------- Another funny thing: By doing the same experiment but installing a no TC capable coil (Kanthal, for example) on a TC Profile after firing the first time, it will run the TSD Function and it will set the value to "False", if you remove the atomizer and install an atomizer with a TC Coil (following the above example, with a Titanium wire), the TSD will still set to false, but if "Temperature Control" is enabled, it will control the Temperature just normally. The problem is that, my theme shows different information according to the TSD status, but the TSD function never runs again.

Hi @Mr.Bottomfeeder, I know it is an old thread, did you find a solution for the "Temp Sensing Detect" issue? I understand exactly what you described, I just discovered my theme has the same problem, when a TC Profile is used (a Profile with a Temperature-Sensing material assigned) and Temperature Control is enabled, it checks the "Temp Sensing Detect", so, if for example, the user installs a coil which doesn't support TC, it switches to watts mode and disables some features for that Profile, as Temperature Control, Replay, and shows a message that a coil which doesn't support TC is used in a TC Profile. The problem is (as you described), there is no way to re-check or reset the "Temp Sensing Detect" value / feature, even if you install a proper coil (a TC control capable coil), the "New Atomizer" is detected, or switching between Profiles or Materials assigned to the Profile. The only way is, again, as you described, reloading the config to the board, or removing and reinserting the battery. Weird thing is, I remember that, when I was designing and testing my Theme, I noticed that, by switching between profiles it reset the "Temp Sensing Detect", I guess it was due the firmware version, but I don't remember which one was it, as I updated to the latest version, as it implements the "Highlighted fields now time out after a while". It is like the Function that does the Temp Sensing Detect never runs again. I created a support ticket about this, I hope to get some answer from Evolv. Greetings !