====2025-10-14 Public FanTestic 5.17.01.25 Hotfix - hotfix for null crash report in fan pressure line refresh - fix error in display of 95% confidence upper value on ASTM EFLA - fix disappearing barometric values on file open =====2025-10-06 Public FanTestic 5.17.01.23 with the changes to FPL/FPC management and refactor, aerobarrier included, show confidence limits for ASTM, output windspeed to excel, SMACNA UI fixes, persist fan locations when do multiple Find Gauges, proper detection of DM32X-30A so max room pressure allowed is correct, fix for recognizing latest DM32X firmware version Standards fixes: - include confidence intervals in ASTM UI and reports (as well as uncertainties). - fix in calculating ASTM uncertainty for slope and intercept - show difference UI in summary when multiple sets are in the same direction ASTME779 - changes to number of decimals displayed for m3h flow, based on request from Retrotec EU. - ensure that wind speed is output to the ISO9972 excel template - fix overlapping sample results and summaries, show non-% value for correlation for EN13829EU - SMACNA fixes for imperial units, minutes to take point not saving in settings, showing, csv output with corrected flow, target pressure and other display of target pressure - fix report template and UI so SMACNA does not show parameter compliance as they are not required - added {s-FanRangeNamex} output tag to word documents for users wanting range name only. - change year for ISO 9972 EU to correct value of 2015 in the choose standard list, and put ‘draft’ in the name EN13829EU (draft ISO9972:2015) to encourage people to use the correct standard for ISO9972 instead of the interim standard put into FT early on as a temporary measure (it IS already in the older standards list). Fan Pressure Line fixes: - handles all cases where users are starting a test with different ranges on the gauges. - fix so changing range line before test started or has data does update any open TestDashboard. - fixed so adds a fan pressure line if there isn't one when find gauge with different range. - ensure that fan pressure lines are not messed up when do a static test after a range change on the second set, and that fan locations are not lost. Test operation fixes: - allow use of DM-2 together with DM32 and DM32X - fixed not sending fan speeds consistently to all connected fans in common control. - ensure the Stop Test button does not appear when using semi-auto and gauges are lost - fixes for not recognizing that gauges have the latest firmware version (DM32X 1.1.5) - ensure multiple fan tests with primary in range, where average is being held because slave fan speeds cannot change anymore, does not stop the test and allows user to continue data collection. - fix for fan locations getting obliterated during Find Gauges - fix so Main Window does not go behind after a gauge refresh is performed Semi-Auto Fixes: - prevent semi-auto data collection with multiple gauges but only one specific one selected - prevent semi-auto gauge refresh if already refreshing. - fix so semi-auto refresh button does full check and updates if gauges have changed. - Fixed so Semi-Auto will get gauge list even when gauges are bad - fix semi-auto Refresh gauges button call so it actually checks for disconnected gauges. - Improved messaging on the Set Speed and data collect, Bugs fixed: - fix for missing alternative ranges (such as Ignore, PrA Only, PrB Only) for tests with Devices brought forward from old tests. Users have to update by opening in Calibration window, OK, and then save re-open file. - cleanup on calibration.xml file that ensures that undated calibrations are removed, commas are replaced with dots, duplicates are removed and 7000 are updated with proper ranges. - fix possible range index bug when do Calculate with no points in test dataset (seen in reported bugs). - prevent users from entering special characters in the Device Serial Number field - prevent fans with no serial from opening calibration window. - ensure that fan locations are not lost when click Find Gauges button multiple times - fix auto-reported crash in Flow Equation Parameters window ========2025-06-11 Public FanTestic 5.16.33.99 - Added the two Aerobarrier fans with their range images - allow floor area entry and report output for ATTMA - fix elusive zero fan speed or pressure bug which happens when there is no PrimaryGaugeReading in common control and a slave is read first. - fix when check test Direction before collection to check for zero pressure and avoid the 'zero pressure detected' error that often happens on test start - fix for fan locations getting lost during FindGauges. - do not re-start fans when hit continue after range change in semi-auto mode if user already hit Stop Fans. - Fix so speeds are not changed once gaugeSet reaches pressure, or the primary is close to pressure, while seeking target. - fix for semi-auto when change range and continue - if had captured to end of test with baseline prior, would set target to zero. - fix missing replacement of some tags in set reports. - fix time in reports so it always shows the time the test was taken and the performed in time zone, no matter where the report is generated. - when using GaugeOnly device, show values in reports and show PrA/PrB in UI - fix range mixup possibility in exml when users change range on the actual gauge before starting second set. - make sure live gauges fan pressure lines are managed if change primary or do other DoorFan changes after a set is collected. - get graphs to show data being collected (after the first flow point is collected). - fix for MainWindow not going behind after a gauge refresh is performed. - fix so customer info, duct installer, duct manufacturer wrap text panels get inner scroll, and witness is limited, in the building info panel. - fix overlapping text in SMACNA and @50 duct tests - fix SMACNA and DW143 UI for specified test pressure depending on duct construction class - needed rounding when converted from Pa to the display value when using InWC. - fix possible smacna test range mismatch on 450, when find gauges from the equipment panel - ensure Refreshing Gauges code is protected and not interrupted during UI updates - get gauge status display working in energy to show the room pressure consistently ====================2025-02-13 Public FanTestic 5.16.31.94 reporting hotfix=============== - fix reporting cue replacement when tag contains s- for replacement ====================2025-02-12 Public FanTestic 5.16.31.92 ================ Retrotec recommends recalculating results for FanTestic tests (performed between October 28, 2024, and January 30, 2025, with software versions 5.16.21.61 to 5.16.25.82) due to a baseline pressure compensation bug. The calculation error depends on the recorded baseline pressures; larger baselines will result in larger errors. - allow entry of floor area in ATTMA tests - show "0" for induced pressure when room and static pressure are the same. - warning when users choose range 2 and 1 on 350 or 450 - easier to read message for gauge discovery with no gauges found. - fix for old files having fan pressure lines set to 'Open' range no matter what the original range was (when re-opened in a new version) - Ancient fan pressure lines being used which are missing basic attributes and needed initializing for backwards compatibility. - fix for bias min and max not checking min negative and max positive for EN13829 (except france which already was, noticed in Belgian standard) - includes fix for energy report templates showing Wind Variability instead of Wind (Beaufort) and some spaces after dashes preventing substitutions. - have calibration table respect decimal separator based on language chosen in FT - fix so only D1 shows up on the equipment and calibration tables in the report for a 7000 fan with factory defaults (was confused about D1 and B1) - speed up report generation - ensure lodgement tags are deleted from word reports if there is no lodgement info - fix for changing lodgement organizations when don't have appropriate test for the standard, so doesn't revert to None. - fix the ATTMA and other organization saving and retrieving of the thermometer and barometer id values, including defaults saved in settings for new files. - write Design Air Permeability to the reports for anything with a lodgement xml element, using the correct organization for output. - hardening around lodgements which are giving a 'network error' when lodging an empty test. - add lodgement ID to the report depending on which lodgement organization they are using (for ATTMA), as well as design permeability and thermometer/barometer ids - improved user experience around first install ever and license expiry (generates a lite license if there is anything wrong) Also note that Retrotec updated its default factory flow equations for a number of fans including 5000 and 6000 series fans in 5.16.25.81 as well, which further improves fan accuracy. Retrotec fans measure within 5% of system flow, the changes to the default flow equations further increased the base accuracy and will result in small changes when compared with tests prior to version 5.16.25.81. Tests completed using fans with serial numbers and the calibration date set will not be affected by the change to the default flow equations. ====================2025-01-30 Public FanTestic 5.16.29.88 with Baseline fix================ Retrotec recommends recalculating results for FanTestic tests (performed between October 28, 2024, and January 30, 2025, with software versions 5.16.21.61 to 5.16.25.82) and Integrity tests (performed between December 16, 2024, and January 30, 2025, with software versions 5.16.23.75 to 5.16.25.81) due to a baseline pressure compensation bug. The calculation error depends on the recorded baseline pressures; larger baselines will result in larger errors. The most updated releases from Jan 30, 2025 are: FanTestic Integrity 5.16.29.87 with Bias fix FanTestic Pro 5.16.29.88 with Baseline fix Also note that Retrotec updated its default factory flow equations for a number of fans including 5000 and 6000 series fans in 5.16.25.81 as well, which further improves fan accuracy. Retrotec fans measure within 5% of system flow, the changes to the default flow equations further increased the base accuracy and will result in small changes when compared with tests prior to version 5.16.25.81. Tests completed using fans with serial numbers and the calibration date set will not be affected by the change to the default flow equations. ===============2025-01-23 Public FanTestic 5.16.25.82 (hot fixes)=============== - fix for energy report templates showing Wind Variability instead of Wind (Beaufort) and some spaces after dashes preventing substitutions. - update of flow equation parameters for 7000, 6000, 5000, 3000SR, 300 series, 400 series fans (D1) - flow equation parameters remain the same (B1) for 200 series, 500, 2000, 1000, Other manufacturer fans ====================2024-12-11 Public FanTestic 5.16.23.71 ================ - ensure the average is done correctly on all barometric pressures - fix the barometric pressure for ATTMA and CIBSE direct entry of before and after to not change other value during entry and to show mbar, - and to save separate values for ATTMA and CIBSE, not all as the average - 3 decimals for NEN3686 standard Qv10kar and other permeabilities when using L/s - fix CIBSE compliance, 2025-01-24 DevFanTestic 5.16.26.83 - includes December update of flow equation parameters - includes fix for energy templates showing Wind Variability instead of Wind (Beaufort) and some spaces after dashes preventing substitutions. #17001 - fix so only D1 shows up on the equipment and calibration tables in the report for a 7000 fan with factory defaults (was confused about D1 and B1) #16982 - warning when users choose range 2 and 1 on 350 or 450 #16996 - fix for bias min and max not checking min negative and max positive for EN13829 (except france which already was) #17007 noticed in Belgian standard - speed up report generation by preventing multiple replacements for the same key tag in reports. - fix for changing lodgement organizations when don't have appropriate test for the standard, so doesn't revert to None. #17006 - fix the ATTMA and other organization saving and retrieving of the thermometer and barometer id values, including defaults saved in settings for new files. #16941 - write DesignAirPermeability to the reports for anything with a lodgement xml element, using the correct organization for output. #16127 - hardening around lodgements which are giving a 'network error' when lodging an empty test. #16691 - add lodgement ID to the report depending on which lodgement organization they are using (for ATTMA), as well as design permeability and thermometer/barometer ids #16127 - fix for null ref during FanTesticSettings.Save when is the first install ever - auto reported. - fixes for license so that FT generates a lite license if there is anything wrong (licensing testing details are in the Dev Wiki) - fix to make crlf show up in dialog message for discover with no gauges found and refresh gauges where none are found. #11171 - prevent multiple replacements for the same key tag in reports to speed up creation. - start of refactoring of string tags into constants for reporting and xml elements and language tags correct statements in UI and report - fix astm3158 to enable barometric entry when Direct Measurement chosen - fix target point deletion asking for whole set deletion. ====================2024-10-29 Public FanTestic 5.16.21.63 hotfix================ - ensure when change fan model and it is non-SR, that the override checkbox goes off - fix for not stopping continuous sampling when cancel the low fan pressure warning - fix for fans tied to license not having fan serial numbers recognized ====================2024-10-28 Public FanTestic 5.16.21.61 with connection UI================ - include menu items for users to send files (in File menu and in Help menu) - support for CGSB 2024 edition (editorial only, no calculation changes) - support for CIBSE standard included - Override for Non-SR fans so room pressure is not subtracted - allow users to choose the type of connection to use and types of gauge to check for - allow search for gauges with known IP - Show the before and after barometric for ATTMA (like CIBSE) - fix for DW143 calculating max allowed leakage and extrapolated value comparison - SemiAuto improvements to allow users to re-acquire a target after sealing an enclosure without stopping fan. - move Technician and report ref number to Header - improve messaging when finding gauges does not go well - included new UI info in the hover for fan pressures to show the minFP based on K2*RP which can cause LowFP. - include target info or gauge info in drop-downs (delete point, gauge chooser) to make it easier for users to choose the item they want. - add warning to L ranges - fix for dutch label flow per envelope - revert labels for NEN dutch standard to use QV10kar instead of the new QV10lea;ref - fix for manual entry of bias pressure having input wiped out. - fix for manual entry of building pressure being wiped out when there is no fan pressure entered. - improve Reporting message when cannot open template file to indicate a problem with OneDrive. - final 7000 and updates to 5000 and 6000 flow equation parameters - Prevent multiple writes of a particular device (fan) into the test or master calibration file. - fix for new install/without calibration.xml file not creating a default calibration.xml. - to allow fan calibration date to properly update, get rid of multiple devices and devices with no calib date from test files and calibration.xml. - ensure the user specified folder for tests, reports, images is persisted - fixes to prevent files from getting corrupted during shutdown - fixes to prevent UI lockup/slowdown as files get bigger ================================== 2024-10-28 DevFanTestic 5.16.20.60 with connection UI and Known IP search but no BT - fix for not starting fan the first time when start semi-auto and set speed. #16944 - fix to remove entered value from UI when already a value in a different range. #16945 2024-10-28 DevFanTestic 5.16.20.58 with connection UI and Known IP search but no BT 2024-10-25 DevFanTestic 5.16.20.56 with BT and connection UI - hardening for changes to gauge serial numbers in DFs, mainly handled already by not firing events. - Show the before and after barometric for ATTMA (like CIBSE) #16941 2024-10-15 DevFanTestic 5.16.20.54 with BT and connection UI - small fix for tcp gauges waiting long enough for launching on the broadcast. - fix so not so many checks of the range id when checking for IsResponding. - more precise logging of connection during connection errors. 2024-10-10 DevFanTestic 5.16.20.52 with BT and connection UI - locking fixes to prevent deadlock, and allow the UI to skip an update if it is already locked doing one. #16927 - prevent events from firing in the Requesting SampleControl (already complete) when do an AddSampleControl. #16905 (more prevention around the changing of ranges in the FPLs). 2024-10-09 DevFanTestic 5.16.20.50 with BT and connection UI - fixes for UI updating properly in the ISO9972 variant Summaries and for CIBSE. ASTM3158, ASTM E779 missing correlation. #16908 - ensure the rc version is removed from DM32X firmware version before checking against latest version. - prevent overridingRampTime when have fewer than three samples, so that gauges have time to respond. #16928 - ensure that the CANCEL command does not clobber an in progress command by locking. - ensure that a command is not canceled when the response contains the opcode (DM32X can respond with multiple opcode responses in one). - clear errors from gauges when RestartGettingContinuousReadings to give another chance 2024-10-07 DevFanTestic 5.16.20.49 with BT and connection UI - OpenAsNew fixes, when TestDashboard open #16905 - fix problem when deleting doorfan not removing Fan Pressure Control line in manual test, causing crash #16924 - make sure fan pressure lines that exist when SetDoorFansIntoControl in FPsC are maintained, at least a single one per doorFan. #16922 2024-10-03 DevFanTestic 5.16.20.47 with BT and connection UI - fix for BT search not always catching the LAUNCHING, so not finding gauge. - more hardening for DM2Panel RangesComboBox_SelectionChanged null ref error. - ensure are able to change to alternative ranges when there is data in the lines (#16921 regression, RangeComboBox changes) 2024-10-01 DevFanTestic 5.16.20.45 with BT and connection UI - add help document for the bluetooth. - Change labels on SemiAuto Set Target (Change target) and Change (Change point) 2024-09-25 DevFanTestic 5.16.20.43 with BT and connection UI - fix for target to collect into choice being overwritten when click Run Fans in Semi-auto. - ensure SetGaugeHadDataError values (and log messages) have fan speed rounded in display. per BW 2024-09-24 DevFanTestic 5.16.20.41 with BT and connection UI - ensure that TestDashboard is set to not waiting once pressure is attained in semi-auto. #16917 - ensure that readings are paused before do a set speed in StartCollectingData. - Fix check for fans having speed and room pressure during TakeDataPoint (was false when speed was 0.1 or 1.0 for DM-2), - fix check for MissingPrimarySameAsDFs in UpdateInstructions in DM2Panel so label is correct, - Fix for ImmediateResponseNeeded calls to SendSerialCommand to allow a retry because the BT gauge was not responding in time.#16918 - fix tabbing to go from room pressure to fan pressure for manual entry need to test with multiple fans 2024-09-17 DevFanTestic 5.16.20.39 with BT and connection UI - fix parsing of target pressure in Semi-Auto, #16915. - Ensure that all checking for empty string also takes into account whitespace strings all over the code. 2024-09-16 DevFanTestic 5.16.20.38 with BT and connection UI - fix for crash on text box validate due to change in digit separator 2024-09-13 DevFanTestic 5.16.20.35 with BT and connection UI - manual data not saving properly need to create the two readings per target point, one for Room Pressure and one for room and fan pressure. - fix for overlapping control in ATTMA building control. - ensure never use . or , for numbergroup separator to avoid confusion. - change wording in known IP and connection UI, - move Technician and report ref number to Header - message for nothing selected when do FindGauges, fix find known IP close message #16914 - revert labels for NEN dutch standard to use QV10kar instead of the new QV10lea;ref - fix for lagging connection to DM32X BT or USB because launching timeout added even when not sending a prompt. #16769 2024-09-11 DevFanTestic 5.16.20.34 with BT and connection UI - fix for manual entry of bias pressure having input wiped out. - fix for manual entry of building pressure being wiped out when there is no fan pressure entered. - changes to App.xaml.cs for rendermode try catch improvements for reported errors around loading controls . - small fix in SampleControl event clearing to clear FanPressureControl events 2024-09-09 DevFanTestic 5.16.20.32 with Bluetooth and UI to select connection type - update EN2686 wording in all language templates to match UI. #16882 - improved logging to label samples during auto test points. - get summary and sample controls using the UIlabel return method, and hiding and showing the correct info in the UI when changing between standards. #16908 - needed to put in text wrap for the ASTM3158 and USACE test pressures compliance statements, too long. - some fixes for finding gauges and resuming when there is a single gauge that went bad and is refreshed from the testDashboard. #16904 - major fixes for Open/New/SaveAs/SaveAsNew and closing FT so it does not raise UI events until all that is done. #16905 -(possible cause of troubles in the exml file fan pressure line numbers). - fix for semi-auto choosing new dropdown target location for UI getting wiped out when click CollectData #16906 - (FTI) fix for datasets with different ranges to output correctly to reports when more in one sample than the other in the pair.#16907 2024-08-23 DevFanTestic 5.16.20.30 merged with FTI branch and with Bluetooth and UI to select connection type - update all project files to always build x86 no matter the configuration. - trying to avoid the errors in bugreports indicating that dlls cannot be loaded. - changes for NEN2686 UI and set up for adjusting of Qv10 flow value based on enclosure volume above 500m3. #16882 - refactored UI label finding into TestXmlManager for EN13829 and ATTMA. need to refactor CGSB and ASTM UI methods to use the new method, and use it also in reporting and check CIBSE labels. #16737 - fix for dutch label flow per envelope - more updates for NEN2686 labels and refactoring EN13829 and ASTM labels and updating ISO9972 method in the Summary section. - fix for null reported during Common.FanTesticSettings.Save(Boolean isSaveRetry) due to default path not being able to be created. -Included message in OnStartup if cannot do this. - fix for bug report to let users know when having trouble accessing the HistoryFile. - updates to UI for semi-auto gauges and points dropdowns, gaugeStatusDisplay gauges dropdown and delete points drop down to make it easier for users to choose the item they want. #16887 - have the Set Target grey out once they enter something for Target or Speed so it is obvious they have to click Run Fans. - Don't grey out Set Target when they click Change for location to put data if Run Fans is disabled). #16887 - ensure correct case on deviceSerial number is used when comparing master and test device info, and that isNewer method finds the date correctly. #16892 - Prevents multiple writes of the device into the test or master calib file. 2024-08-14 DevFanTestic 5.16.18.29 with Bluetooth and UI to select connection type - fix for multiple timeout dialogs being launched #16875 - include removal of datacollection engine timeout error handler one other place. #16875 - disable the knownIP search if only DM-2 selected, hide DM-2 if knownIP search selected, hide selected connection modes if knownIP search selected. - Move Add Test Fan to above the test fans list. - fix to ensure that data entered for barometric pressure directly is persisted - regression bug from adding CIBSE. #16867 - fix some default settings for BarometricBefore and BarometricAfter #16867 - null ref fix for DM-2 not noticing disconnection #15961 - fix to unoverride getting readings when carry on after a timeout or other event so does not stall - fixes for not resuming after timeout. - prevent resume if waiting for gauges (zeroes being returned - tubing error). #16876 - change in CollectData.TakeDataPoint to recognize when there might be a tubing/fan shut off problem going on and provide info to user (close to zero on both channels with fan at speed) - add warning to L ranges (including most translations) #16873. - arrange that warnings for range and fan model are not covered by the popup window #11174. - show calibration window messages on top of fan calibration windows. - fix for settings problem when change number of flow targets to 1, needed to set the target pressures to seek to be equal and small fixes in the adjust targets to ensure that all targets are re-loaded into the UI. #16881. - more logging in the settingsForm so can see what users set. More logging in ProcessCurrentPoint so can see settings in use. - fixes for starting auto tests after clearing data or baseline or target point that was nulling out the GaugeSet and preventing resume.#16884 - ensure reporting clears out FP tables when there is a sample with no data followed by one with data. handle situation where first sample is empty but there is data in the second set. - get reporting replacement tags ready for use, document how the templates work #16737 - fix in App.OnStartup to catch COM and out of memory rendering errors and set the App to SoftwareOnly Rendering as advised in MS Learn. - Hopefully handle all the render-thread-failures seen in the bug reports. - more logging in OnStartup 2024-08-02 DevFanTestic 5.16.18.28 with Bluetooth and UI to select connection type - New UI to specify which connections to search on. - more logging during StartSync during refresh. - fix UI not showing correct barometric entry method when re-open a file. #16867 - fixes to get rid of trying to open the non-operational half of the BT pair. Speeds up the find gauges by 5s per pair. have to see if works with simulator. - fixes for regression bug from override SR feature, computing zero building pressures and flows for some sets because DoorFanControl.Refresh operating the UpdateReadings asynchronously during the load, when the check box is operated for an SR fan. - hardening for null ref during DM2.RangesComboBox_SelectionChanged. - harden up code around removing fan pressure lines to start ensuring it is not done if there is data in the line. - remove load of fpl during Main.Window.LoadTestFile because done elsewhere. - Prevent removing of fpl with data in the DM2Panel.StartSync which happens in the Refresh, so if the gauges don't match the doorFans, fpl are not messed with. - Show the range version/round that is in use in the log. - fixes for ensuring that non-dated calibrations in the calibrations.xml and in the test file are removed upon load. - fix for new install/without calibration.xml file not creating a default calibration.xml. - to allow fan calibration date to properly update, get rid of multiple devices and devices with no calib date from test files and calibration.xml. 2024-07-23 DevFanTestic 5.16.18.27 - fixed startup with FindGauges and needing launching. #16769 - longer waits for launching because were sometimes exceeding the 3s. - fixed StartAutoTest without findGauges - on first search for gauges from the StartAutoTest when find different primary gauge than is specified in the Equip Panel UI - updates Primary DF serial number to the gauge found, including in the EquipmentPanel summary - need to test with having multiple DFs in the list, some with gauges that are found and some without. - and to be sure does not happen when there is flow data in the test. - fix known IP bug not adding gauges to DF collection. and some code hardening for null refs #16855 2024-07-19 DevFanTestic 5.16.18.26 - fix for no gauge display when set semiauto fan speed on specific gauge #16842 - fix startup of semi-auto when have not done find gauges or other start auto test and DM32X needs launching. - fixes for resetting targets when starting an autotest so when clear data after a semi-auto with odd targets, does not try to use those. #16843 2024-07-16 DevFanTestic 5.16.18.25 - alphabetize the list of standards more closely in the Standards chooser list, put previous CGSB into old area. - Fixes for DM3Scanner and GetSerialDM32List for connection problems - null ref and handling wait for the DM32XLaunching during non-startup calls #16769 - fix for semi-auto not starting fans immediately when choose single fan. #16764 2024-07-15 DevFanTestic 5.16.18.24 - support for CGSB 2024 edition (editorial only, no calculation changes) - start bringing in tags for docx replacements (work done in FT6) - fixes for cleaning up calibrations.xml (updating with new values for 7000) #16766 - make OpenFileAsNEW actually work with the locked streams for settings/calibration/history. - output all set results to reports (except tables of pressure/fan pressure) #16837 2024-07-05 DevFanTestic 5.16.18.23 - fix for incorrect base Test files directory - getting set to Retrotec\AppData. #16805 - Included Help button near the file select button in SettingsForm - fix FanPressureControl range being overwritten when do semi-auto after test has data (or when resume test) #16804 - provide update to 7000 flow equation parameters in the calibration.xml for any that are factory B1. #16766 - clients have to update their Excalibur ones themselves. - happens when a file is opened or new file created - include latest copyright in about, eula windows - include fixes in FanTesticSettings for Integrity tests (NFPAED2022) 2024-06-26 DevFanTestic 5.16.18.22 - increased the timeout on DM32X launching wait. #16769 - in the DMGauges.GaugeSet_RefreshSerialDM32 and other places, do not close the port if it is Bluetooth. #16769 -needed fix for when close gauge app during test because the ping is starting the launch. - fixed UI update after find known IP. #16794 - fixed the start test to not do a broadcast again in the case of known IP search. - fix the primary being changed when start test using KnownIP . - fixed DM2Panel.Refresh to respect the searchForKnownIP. - fixed so that correct FPL are created when do FindKnownIP. - UI for all buttons including change units needs disabled during autotests. #16789 - show the Refresh button when cannot resume after range change because waiting for Gauges. - to show the find DM32X and DM32 check box information in the known ip UI - missing ranges in dropdown after FireSample test completes or is stopped if there is no range change before the end. #16791 - Also included new UI info in the hover for fan pressures to show the minFP based on K2*RP which can cause LowFP. - fix for auto-reported null reference on Range selection in TestDashboard. - improve Reporting message when cannot open template file to indicate a problem with OneDrive. - fix SampleControl showing ChangeRange button when test completes. - fix for DW143 calculating max allowed leakage and extrapolated value comparison #16788 - progress bar on scan for known IP #16168 2024-06-07 DevFanTestic 5.16.18.21 - #16748 fans stopping when say continue trying when something goes wrong with attain pressure. - fix for door fans/fan pressure lines disappearing if do a change primary with active gauges - was removing them when did CheckGaugesAndStartTest(). - fix SaveFile to have truly unique filenames by using the seconds, and to know what was the previously open filename to prevent trying to overwrite. - fix double click when FT already open, shows a MessageBox instead of the licenseKey dialog. - manage DoAutoSave so processes dont whack each other. - check the test stream so that if the xml doc has no length that it doesn't get written, and also check that disposing the stream does not flush an empty stream to the file. - Make Settings file and HistoryFile shared as readable when being used by FT. - put the OpenAsNew into the File menu. - fixes for #16758 getting 'unable to open file' dialog when do file SaveAs and try to open - #16764 fix so can run fans individually in semi-auto 2024-05-31 DevFanTestic 5.16.18.20 - #16739 fix date changing bug - ensure changes to UsePolynomial for RangeInfo are updated in the exml if different ones come in from Excalibur. - Set the flow_m3h attribute in the exml based on incoming units from excalibur (which are agreed to be CFM). - fixes for re-checking gauges once they have been lost. #16753 FT - after start test with missing primary, problems with finding gauges from start button even when there. - improved messages. 2024-05-20 DevFanTestic 5.16.18.19 - Bluetooth enabled for finding DM32X - Known IP search enabled - include menu items for users to send files (in File menu and in Help menu) #12824 - ensure the user specified folder for tests, reports, images is persisted . - CIBSE standard included - Override for Non-SR fans so room pressure is not subtracted #16718 - ensure NoFanControl does not show LowFP if the device is not GaugeOnly. #16732 - fix to allow ranges to change when test completes. #16733 - have auto captured values show up in the UI even if they are being ignored in calculations. - ensure that PrA is not subtracted from PrB for readings that are not being used for flow or PrA is being ignored - fix messaging when they need to use Find Gauges first instead of Start Test. (gauges and fans do not match what is in equipment list) #16714 #16692 ============== 2024-05-14 Public release FanTestic 5.15.15.86 =============== - many fixes to ensure that the correct Fan Pressure Lines show up in the UI when creating, re-opening and saving exml files, or when changing range. #16710, #16692, #16521 - fixes to ensure DoorFan and line numbers don't change when users do Make Primary or the primary gauge is lost and the user starts semi-auto. Auto-Test - include option to "Collect Data Anyways" when are having multiple fans and the average room pressure won't settle #16570. - fix for semi-auto or multiple fan tests not having an option for continue with data collection when encounter a timeout failure. #16569 - add option to carry on with semi-auto or continue data collection when some fans are at full or low (stalled) in indiv control #16570 - fix problem of point being skipped when previous point went over DataCollectionTime in order to get extra needed readings. (5s per target test) - needed some locks around the setting of completed indications and resetting of timeout - also skip the timeout dialog when dataCollection is in completed status - fix readings not being saved into test file sometimes #16629 - also ensure that Ignore data readings are properly identified even with alternative ranges. - get TestDashboard to act accordingly for FT becoming unresponsive unless respond right away to dialogs. #16576 - fixes to prevent the timeout happening when users leave dialogs open for a long time. #16576 - need to make sure fan speeds are sent to gauge from master to prevent stopping when non-primary gauges in common control have no room or fan pressure at less than initial ramp time. #16579 - fixes to ensure that messging when starting tests better indicates what problems are occurring - Ensure that TestDirection gets checked when handle random error and collect data anyway in first target point. Semi-Auto - added a calculate when the Semi-Auto window closes so that all new values are included before they save and results do not seem to change when a file is reloaded. #16628 - fix for problem in semi-auto after changing range which was re-setting the target to zero even if not a static collection. - semi-auto fix so can run another target without stopping fans, #16571 - semi-auto option to re-aquire current target so users can seal and then re-run a target. #16588 - semi-auto UI improved so that users get more warnings when settings are not correct in the Semi-auto UI. - fix for fan pressure lines and room pressures not updating during semi-auto capture when have done a range change in a previous set and added a new set #16629. - fix for CollectData in Semi-auto not sending set speed when oscillation does not settle and user chooses the option to continue with semi-auto. #16691 - fix semi-auto so when choose static collection it sets dropdown to next Incomplete point. #16658 - fix for #16660 crash when data in test and start semi-auto after refreshing - fix for semi-auto not allowing set speed after next target #16626 - semi-auto UI enable/disable while seeking or capturing #16518 Finding Gauges - Allow Cancel any find gauges in progress by clicking on any Go button or change auto/manual button. - fix so serial DM32X needing launching will launch and then be found without clicking find gauges again #16362 - fixes also for UI not updating Fan Pressure Lines to the right range when try to start auto test with different gauges than are in the Equipment Panel. - new logging information in case the 30s wait while scanning for gauges continues to occur. - fix refresh in TestDashboard to resume after re-finding gauges as long as they are ok #16419. - fixed the need to click find gauges multiple times. - need to manage losing connection to a non-critical gauge during data collection. #16518 - fixes so that losing a gaugeOnly gauge does not stop the test. #16518 - more logging to get details on extra pop ups and then resuming. #16518 - Include new mode for port checking so Simulator can use dynamic ethernet ports like DM32X does General UI - added a button to FT so can clear just the Baseline points. #6934 - fix for the tabbing in manual which was not leaving the last box of an entry grid. - fix for clicking into an manual entry cell not being respected so it was hard to select last cells in grid, and tabs would go to strange locations. -mostly affected the fan pressure lines, building pressure and static pressure entry in manual entry - minimize showings of the DM-2 obsolete warning #16573 - Fix gauges display to show the absolute value of room pressure in the graph. - show users what fan is the original measured model in the equipment panel and in the fan pressure line (model and range) - when they have chosen an alternative range such as PrBOnly #16589 - prevent adding and deleting doorFans when there is data in a test, even for manually entered ones #16585 - ensure that clicking generate report menu item first calculates. #14651 - Deleting all set data will allow changing of equipment section data #16204 - prevent opening a double clicked file if there was an update done ... the FinishDeploy. - Fix when a forced change to a Lite license happens so that a protocol is allowed (ASTM if nothing loaded in the App.Settings) - change the phrase "your home" to "the building in the ASTM report talking about air quality and leakage. #16490 - fix updating reference permeability pressure labels in SampleControl #16523 Settings - fix for number of targets and static points in tests - where when set to 1, was never allowed to change after that. - Note that putting the same target pressure in both boxes for high and low test target results in FTI/FT adding a difference as specified by the standard. - n> at end of Settings corruption - fixed this possible happening - fix for updating the latest DM32X from web when newer than default in sofware. - Include check for zero length Settings.xml file, corrupted somehow. - SMACNA test with 450 and DM32X-30A putting results into the wrong UI line. #16534 - basic clean up of export to excel. #16520 - Include 7000 fan with correct parameters Waiting for Next Build: - Allowing users to enter Known IP addresses so finding gauges can be done without the broadcast. - Bluetooth discovery for DM32X ===========2024-02-01 Public FanTestic 5.15.13.54 - fix to get the correct range for calculating flows during the live display on auto-testing (previously needed to re-load a test to get correct values). ===========2024-01-31 Public FanTestic 5.15.13.52 - provide dialog for low room pressure after initial ramp time when there is fan pressure, instead of just stopping. - fix for incorrect no pressure on Channel B dialog happening when there is actually no pressure on channel A - include warning for low room pressure with some fan speed, instead of just stopping, so they can choose to change range or abort or cancel. - fixes to ensure there are no extraneous fan speed too high warnings with no room pressure dialogs. - fix second target value not being set properly into target pressure - all standards - fix number of samples in average not reset when use the (reset to default) settings button. - fix for UI fan pressure cell hover text to show min FP and show the actual FP in use based on test direction. - fix to prevent skipping reading if same as previous reading during data collection except for long data captures or for primary DM-2 - Many changes to manage the DM32X regularly returning 0,0 during baseline - include fix so testdashboard provides dialog when lose connection to serial gauges. - remove the DM32X-20A from the Gauge Models dropdown (devices.xml) - fix for entering manual data to correctly set the UIDeviceName and UIRangeName in the readings. - fix for gauge firmware not retrieved properly on serial connected gauges. - added 7000 rough flow equation parameters and range images in preparation for release. - Not available on any gauges yet. need updated values for MF, K2 and the B ranges (polynomial or not) ====================2024-01-17 Public FanTestic 5.15.11.42 - fixes for DM-2 not able to run tests - #16326 DM-2 multiple fan test not starting second fan. - #16387 fixes so speeds are set on all slaves properly, no matter type of gauge or primary. - #16384 fix for fatal error during a logging message at start of auto test when had all three types of gauge in the mix. - #16326 fix adding extra FPC for wrong DM-2 range after FindGauges then Start test. - #16245 fix restart of gotopressure when DM-2 has reached 100% with no room pressure - include individual error queues for each doorfan - allows the individual controlled multiple fans to accurately determine when they have reached pressure. - #16325 make sure IndividualControl is using the new indiv queues to determine are we there yet... - include operational alternative ranges for performing Neutralization tests (needed for ASTM3158) - white digits in UI fan pressure line for ignored FP, not included in flow calc. Usual Neutralizer workflow: -open FT, set to individual control, do Find Gauges, set one to Neutralizer, Start test. - Change range should be ok for the fan that is pressurizing the enclosure. - include ASTM3158 compliance checks. will change the high target setting if not valid when entered into Settings - with report for ASTM E3158 large building testing standard - Included number of static readings count in report - included the CFM/sqft pass level setting in the UI, report and SettingsForm for ASTM3158 (like USACE) - #16388 fix settings UI not updating properly with 3158 pass level setting - #16268 when add a new set: if 3158 or USACE just copy direction, otherwise change the direction but leave the operator location the same. - chances are they are doing an opposite direction test. this will help avoid extra test direction changes that seem to sometimes cause problems. - #16300 add new set in opposite direction to direction of the set the button clicked on. - #16309 NEN2686 needs max of 2 decimal places for results when using L/s flow units (based on the Standard) - #16069 fix annotations on graph for two direction tests, and ensure graphs show when there is data in two directions both in the same direction. - #16222 fix instructions on ask for tech support to include correct email address to send bugs. - improve background processing so FanTestic is not so heavy on resources - fixes for CPU ramping up after losing gauge connection. - #16398 fix for high CPU usage. - put in way to cancel refresh if click start test for use with hung 'Find Gauges' operation - (click the start auto test button when the progress bar is open) - major improvements to gauge connectivity. FanTestic will now let users know if it is having a connection problem and let them decide how to proceed - (check their gauges and resume test....) - fix so seeking and data collection engines recognize loss of connection immediately. - #16187 fixes for all types of gauges disconnecting USB during data collection and during seeking - #16187 fix DM32X usb connection and disconnection - improved slow finding and recovery after loss of DM32X (by reducing timeouts). - improved logging - #16396 fix for error message to properly indicate when average room pressure is too low vs too high - #16405 fix message when fan at 100% speed and have not reached pressure during seek - should pop range change dialog - new warning when zero fan pressure on one or more gauges in indiv control. - fix for display of target = 0 attained on first semi-auto target pressure point if start without doing an auto first. - better message for Negative Fan Pressure reason to include possibility that fan speeds not being sent to DM-2 or slaves. - #16407 fix so in Semi-Auto after a range change, the 'next incomplete' will not overwrite previous target. - fix for possible setting of fan speed to non-zero during static collect. - DM-2 working again on Indiv control. - #16329 fix speeds being set after resume to depend on common or indiv control. - #16237 #16346 fix incorrect target being used when resume and fix fans stopping when resume from first target point. . - #16269 allow range change to alternative after there is data in the line, and recalculate based on the alternative range. - #16274 fix choosing a 450 sending the wrong (noncompatible) range to the gauge and causing the DM32X to crash. - #16244 new files now able to read last test file again (when do New file with a test open) so not ' losing' equipment - #16271 fixes for Settings file loading and saving to prevent crash seen in many bugreport emails - #16273 - allow primary DoorFan to change fan model. - #16270 fix crash on DM-2 during cannot reach pressure dialog. - #16240 fix fatal error when a DoorFan with a connected gauge is set to GaugeOnly in the Equipment Panel. - ensure latest DM32X Gauge App version value is used even if cannot retrieve from online source. - fixes for - null reference on MainWindow.RegurlarCursor() reported in bugreports - fix docX error causing reports not to be written, when using a png logo or if don't have any images in the template - include more logging for saving of settings file and more use of the settings.xml stream lock. - more error catching whe loading range data, during startup and while writing/reading calibration.xml file - fix for picking an image crashing when unable to access the Images directory known issues: - Find Gauges does not always find DM32X on serial (usually only if the Gauge App has not been launched on DM32X) - known issues for new ASTM3158 option are -English only report output -multi-point only option -static information in report for manually entered data is suspect ========== 2023-07-25 Public Release FanTestic 5.14.23.90 - UI implemented for guarded testing options. Can choose Neutralizer, FlowBooster, Gauge Only options in equipment pane. - After the test is done, can also choose to include or exclude PrA and/or PrB from any calculations by using the range drop downs in each fan pressure line. - Implemented user settable tests/images/reports/templates location (done in Advanced Settings, only if the users have a paid for license) - Fix for dates not keeping timezone info when adding new samples to a test. - fix for settings values disappearing after change tabs in Advanced Settings form. - fix not being able to change fan serial number even when delete the data in an auto-test - prevent a negative fan pressure on PrB from triggering a warning unless it is more negative than the current average bias (or zero if the bias is positive) - fix for first time demo users (was an infinite loop asking them to enter a standard) - popup telling users they need a Lite License and to contact retrotec if have an expired demo - prevent users from opening an already open file. - changes to file access so software is not plagued with problems because of file sync (such as OneDrive) ==========2023-06-15 Public FanTestic 5.14.21.81 - provide UI to choose what types of gauge to scan for so users can minimize the time required if they do not have DM32X - fix ASTM and ASTM2019 not having their settings properly saved (separately) - change reporting to include a tag in the reports for {DataSetNumber} and {TimeZone} so users can exclude them if they are not interested in seeing that. - ensure to save the default date and time for test when save and calculate - fix for values entered for reference pressures showing as N/A - fix for problem of being unable to select first cell in the manual entry grid. - warning message when they choose DM-2 that it is an obsolete gauge - ensure that the fan at 100% with no room pressure warning is working (red tube missing mistake or fan speed cable not hooked up) - provide message for negative fan pressures when start an auto-test target (yellow/green tubing mistake). - ensure the DM32X 30A sensor limits are correct (DM32X does not always have the 30A sensor) - Improved message when the primary is missing at Start Auto-test, tells them to use Find Gauges. - fix so 100% speed triggers a range change or continue dialog - ensure flow averages were not being influenced by readings taken during the various error conditions (waiting for gauges, refreshing, data errors) - fixes for gauge failure during data collection taking a long time to be acknowledged - fix for DM-2 taking too long to give the dialog when reaching 100% - fix not being able to start bias/target set with DM-2 even after find gauges. - set type of gauge sensor correctly when gauges are found and based on serial number ========2023-05-02 Public FanTestic 5.14.19.57 - fix for DM32X not understanding Set Pressure with decimal value in non-US regions. - fix typo in french message about connected DoorFans - fix changing to no flow range with live gauges and before any data is taken. - fix to provide proper 100% fan speed pop ups on single gauge. - fix for null or empty paragraphs causing crash during report generation ====2023-04-24 Public FanTestic 5.14.17.53 - improve connectivity particularly for the multiple blank receives often received from the DM32X on busy WiFi - improve the waiting for gauge refresh during data collection - fixes making sure we wait at least the time avg time before checking pressure arrival criteria. - when seeking pressure common control needs to pop out when the primary is within pressure but average is not - and notify user what is happening instead of just (gauges oscillating) - fix for crash when change test direction manually by changing sign of entered room pressure - fix description of time zone being output to reports - Fix for finish time default being set to a date string rather than being empty. - fixes for reporting (ATTMA intercepts) - fix for ATTMA bias calc leaving zeros out of avg positive and negative biases. - include the 30A sensor and fix messaging about 20A and 30A when select gauge. - better hints in the deviceChooserPanel, and better order of fans in deviceChooserPanel - lookup LatestDM32X version online - fix fan calibration date not getting set properly when enter parameters #15982. -default of todays date was messing things up. put in 1984 default. - fix so looking at Advanced Settings during a test does not prevent proper gauge refresh afterwards =============2023-03-14 Public FanTestic 5.14.11.30 with DM32X known issues with DM32X: - in multiple DM32X situations when connectivity is lost, the GaugeApp has to be restarted by the user before it can be found again. Features: - add support for DM32X - updates for EAS (iATS) test data lodgement to new server Changes: - allow resume with data in the test after stopping - make sure 'searching for gauges' progress bar is showing during Find Gauges - prevented running another Find Gauges if one is already running - fix messages for fan at full and no fan pressure.... - change message when have fan at full with 0 room pressure situation. - fix for fan speed at 100 popping problem dialog instead of Speed Too high without reaching pressure dialog. - better Messaging for room pressures in different directions - ensure semi-auto warns if try to take a static point with a value set for pressure (or speed) - fix where semi-auto target point is set to the original cell value when clicking to retry. - fix so semi-auto will run same target again after canceling a range change or other operations - fix for showing wrong pressure achieved when say continue with semi-auto after a problem is displayed - fix semi-auto re-seek same target after abort, - rename continue collection option in semi-auto low FP and range change dialogs to allow users to carry on back to Semi-Auto, - fix for DM32 waiting too long when very low room pressure. - fix primary DM-2 delays in latching on to pressusre when at 1% speed, and low speeds. - fix primary DM-2 not latching on to pressure when takes a long time to reach pressure. - fix DataCollection retry errors when do not get readings from every gauge (connection issues). - fix non-zero speed possibly being set during baseline with indiv control...needed to zero out the fan speed queue when start a baseline point that is not resumed. - skip test direction, oscillating and stalled check until after have some room pressure. - check test direction only when there is room pressure - fix so losing single gauge, or having any off gauges during a static data collect stops test after retries #15815 - fixed the display when a gauge problem is found when start a test so the Instructions are last, and the GaugesExpander will open so they can see the Refresh button. - fix for target collect losing gauges so it properly pauses test 2023-01-24 Public FanTestic 5.12.55.115 hotfix - fix for SaveAs changing fan pressure line ranges to open bug #15849 - fix for building image not showing up when clicked bug #15850 2023-01-17 Public FanTestic 5.12.55.114 Features: - New standard available to choose: ISO9972 Europe 2016 (Germany) (ISO9972DE) - allow “no flow” range on multiple fan pressure lines for the same fan so flow calculation can ignore a fan (used when doing guarded tests) - allow users to change fan serial number even with data in the test - show an “All Gauges” option in gauge display sidebar so the average room pressure and total flow are shown during an semi or auto test. - option to allow user to skip oscillating or stalled flow target pressure points during an auto or semi-auto test - warning when reach 100% speed but no room pressure detected on flow steps (fan not powered on....) - option to “collect data anyways” when primary is running at minimum gauge speed (1% for DM-2, 0.1 for DM32) - New method for lodging tests to the ATTMA backend (to upload the whole test file), including persistence of the success ID number in the test file Auto-Test Fixes: - fix so does not stop test if resuming without data and did a direction change (was causing immediate stop on first point of many tests) - fix Continue Pressure Station after a range change so fan speed is properly set to previous speed when resuming (keeping room pressure same as prior to stopping) - ensured the target point with DM-2 is correct during seek pressure so can set to proper fan speed for collection with DM-2 (keeping room pressure from changing) - changes in seek to pressure operation to fix the DM-2 having trouble attaining pressure, and DM32 attaining pressure when it is oscillating o Note that DM-2 only changes speed in 1 percent increments so at low fan speeds it can take a long time to get within criteria for reaching pressure. o DM32 can also get stuck oscillating or slowly reaching pressure o With fixes for data collection - Setting speeds at beginning of data collect (only primary needs speed set if in common control) - Grabbing the correct fan speed to set o With fixes for reaching pressure: - DM-2 stalling or taking too long to start collecting when on pressure - DM32 primary or DM-2 primary in multiple gauge situation, - DM-2 primary in single gauge with high target pressure and oscillation on start. - DM-2 primary in single gauge with low target pressure and stalled reaching pressure situation. - DM32 primary attaining pressure too soon when volatile with oscillation on first target pressure. - DM32 primary with oscillating fan speeds, . - DM-2 primary in multiple gauge situation - fix operation of the “Abort Point And Proceed” operation to first check if gauges are refreshing before starting next point, and wait for them to finish refreshing. - fix for odd time out error during data collect when gauges are in error or are refreshing in the background - fix for auto test stopping sometimes like there was zero room and fan pressure received when there was not (another cause of stop on first point of many tests) - ensure the wait time is long enough after setting speed before collecting data to allow room pressure to adjust (particularly on the DM-2) - fix for common control operation to only set speeds into the slave gauges when looking at the primary gauge - for individual control ensured that the most recent fan speed is used from gauge queue (target attainment relies on error from the average room pressure of all gauges) Semi-Auto fixes: - fixed semi-auto UI to allow 1 percent speed to be set. - fixed to correctly interpret user input of target values in the semi-auto UI when in a non-US language. - fix range change at start of semi-auto to refresh the main UI if new ranges were added. - fix for first flow point reading sometimes being corrupted with readings indicating it is doing a static collection (line number and df number being 0) - prevent a semi-auto static collection if a fan speed has been set (speed has to be zero) - prevent checking test direction if doing a semi-auto static collection (can only check when is a flow target point collection) Control Calculations - fix problems with bias average calculations in the average of all positive or all negative room pressures. o only do the per reading calc for EN13829_FR and ISO9972, and not for other EN13829 standards or duct. - fix updating of the Room Pressure Variation (displayed in the room pressure hover tooltip information, and as yellow colored room pressure text if >10%) o so USACE with multiple fans shows correct values, o during auto-test the correct room pressure is used for reference for the variation (average room pressure or primary gauge room pressure). o Color room pressure text yellow instead of red for non-USACE tests so users are not so worried, but still get indication that their room pressure is variable Gauge Connection Fixes : - Changes so the gauge can recover on serial when both USB and Network are connected and the Network (TCP) connection drops UI Fixes: - Allow deleting the first flow target point - fix “Show Graphs” button to work even when first or last points don't have flow readings (but some do) - fix so flows are not cleared in UI when an auto test completes - update fan pressure line ranges, equipment panel and clear main gaugeSet when SaveAs - ensure only valid model names are in the list of devices that a gauge model can be set with - Color the room pressure text yellow instead of red for non-USACE (when more than 10% variation in readings), - fix room pressure variation display to show proper sign - fix in ISO9972 which prevented variable room pressures on low targets from showing yellow when they were variable. - fix in graphs for overlapping correlation values on graphs with two directions - fixes for changing fan serial - show the fan serial in the hover tooltip of fan so that we can see it - update the equipment panel summary (in the expander label) when change fan serial - removed nag screen about needing a fan serial on start of auto-test - fix EN13829NL UI being rounded up to 0.400 from 0.392 when recalculated before being output to report in L/s - fix SMACNA UI to update properly - fix building address UI to switch properly when change out of ATTMA or ISO9972 and have “none” as the lodgement organization - fix CGSB UI not showing some uncertainties. - fix defaults for “Build Progress” dropdown in ATTMA - some fixes in German language UI labels Flow Equation Parameters (calibration data) - ensure calibration data is saved and retrieved properly. o when loading range information in the main UI, do not overwrite the fan calibration date. o also need to check for actual custom in the test file . o new method for setting the device model so when creating new files we can update flow equation parameters from last test that was opened. o actually save changes to master calibration file and recalculate when changed - update factory default flow equation parameters with new MF for 5000 fan - when no certificate found in Retrotec online for a fan, prevent a calibration date from being added. Reporting Fixes: - fix output show multiple same direction sets in ASTM - show the performed in and displayed in time zones in the report - France variant energy tests with multiple sets are now output properly (were missing the second set even if it was there) - The base energy template now includes translations in the output tags, rather than needing it in each language base file. This is only in the base template currently for all ISO9972 variants and EN13829EU. - Witness Name and Witness Phone are now available for output to Duct and Energy reports if users put them in. - fixed German language energy template - fix UI being rounded up to 0.400 from 0.392 when recalculated before being output to report in L/s in EN13829NL Settings Fixes: - add UI limits when entering auto-test parameters Test File (exml) Fixes: - lock the xml during save - fixes to turn off AutoSave during all other operations - fixes when create new file, save a file As (duplicate), or save a file as New o create new GUID when do file SaveAs, o use UTC for DateModified and created. o include a flag for WasSavedAsFromGUID which keeps the original GUID. o include a flag for SavedFromVersion which is updated when create new, save or saved As o keep locations and fan serials in the Device element when do a SaveAs o Clear Devices element when create New file, or do a SaveAsNew, so that the Test Door Fans are either empty or can be properly loaded from the last opened file. - needed to increase the number of decimals being stored in the exml file - fix in Duplicate to ensure correct TargetPressures are based on original sample rather than app.settings defaults. - force a file save if the flow equation params are changed - fix update to set all fan serial numbers in calibration master file to lowercase and remove any duplicates, happens when open a file. Programming Fixes: - Fix a crash when users use non-gregorian calendars such as UmAlQuraCalendar which have different MinValue and MaxValue for dates. o Affects all time related conversions, UI and values in xml files. - Set build parameters to avoid auto-reported System.InvalidProgramException bug (probably related to users with Win11) - fix some crashing in text entry boxes - App now has build flag for use whole file for ATTMA lodgement - new certificate and time stamp server used - some fixes to reduce in-memory footprint when opening and closing tests (out of memory error) - when getting flow equation parameters from online, fix for model name check and added logging - provided more logging when saving flow equation parameters.