TFR bug in the Wire Wizard (fixed)

When combining different materials in parallel, the Wire Wizard sometimes failed to fetch the temperature data for the materials of the individual strands correctly, resulting in an inaccurate TCR/TFR output.

To be more precise, some temperature factors were matched to the wrong temperature points. This affected the slope of the temperature curve.

Current status

I have fixed the issue in the code and uploaded a new version. It should hopefully become visible in a matter of minutes from now, but YMMV depending on browser caching and that sort of thing.

Do the users of the Wire Wizard need to do something?

If you’re using a multi-wire coil comprising of different materials, and you have entered temperature (TFR or TCR) data from Steam Engine into your mod, you may want to re-do the calculations and configure your mod again.

DNA users who have made profiles for multi-wire coils made up of different materials may also want to create new CSV files.

How to check if you have the fix

  • Open the Wire Wizard and make a parallel coil.
  • Select SS 304 for one strand. Leave the other one alone. Don’t change anything else.
  • In the Temperature control window, click Table.

If the TFR at 300 °C is 1.17463 then all is good, and you are on the new version. If not, try waiting a while and reloading the page.

Sorry for any inconvenience or bad vaping experience that may have been caused by this bug. Many thanks to Christian for pointing the bug out to me, and for providing the data I needed in order to know where to start looking.

2 thoughts on “TFR bug in the Wire Wizard (fixed)

  1. Brandon

    I used the Wire Wizard (today) to profile the all-Kanthol 24g/36g fused clapton wire I’m making. Naturally, temperature control isn’t applicable with this wire. Selecting this wire in the Coil Wrapping tool seems to work fine, but using it in the Wire Wizard throws the following error to the console: “t.toFixed is not a function”. Apparently there’s some data missing, I’m guessing whatever t is in the minified Javascript is actually null. Not sure if this relates to the bug you’ve fixed or if it’s a new one; also couldn’t find a link to report this in a tracker somewhere – are you guys using Github?

    Thanks for all your hard work – these tools are a lifesaver!

    Reply
    1. Dampmaskin Post author

      Hi. I found one instance of toFixed in my code, it was in a display routine (of course), and I have now made it null-safe. Try deleting appcache, reloading js, and see if it works better now.

      I guess I should use a tracker but I haven’t gotten around to it. Anyway, thanks for the helpful report.

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.