Tank Monitor Console Multitool 0.59.1

• Windows taskbar: the app now shows its own icon on the taskbar instead of the Python logo when
  run from source, and every window the app opens carries the icon, not just the main one.

---

File: vr_tls_tool.exe (12.45 MB)
SHA-256: 6dca05aa8bf99f1925fc0825518be5d7dba65efbb1bcfbe968a72017534c9985

To check your download, run this in PowerShell and compare:
Get-FileHash .\vr_tls_tool.exe -Algorithm SHA256

Tank Monitor Console Multitool 0.59.0

• Migration: five settings that a real TLS-450PLUS has been measured to refuse or throw away are
  no longer sent. Two answer "unknown code" (the RS-232 receiver flag and label); three are
  acknowledged and then not stored (AccuChart update scheduling, the line leak lockout schedule,
  the RS-232 DTR flag). The report lists each value under its own heading so it can be entered on
  the console, and the completeness list flags AccuChart scheduling and the lockout schedule.
• Restore verify: three in-tank leak test codes (613, 61A, 61B) that a TLS-450PLUS never answers a
  read for are now reported as "cannot be read back on this console, check the screen" instead
  of "no reply, re-run a dump". A 450PLUS backup says the same when its sweep misses them.
• The migration report now says it has been exercised against two real consoles.

---

File: vr_tls_tool.exe (12.42 MB)
SHA-256: 4301d2038f6b2229f4b3ac78158f841dc9ed28388bd4688d93ed1a1f4c41f9b4

To check your download, run this in PowerShell and compare:
Get-FileHash .\vr_tls_tool.exe -Algorithm SHA256

Tank Monitor Console Multitool 0.58.0

• 450PLUS Migration tab: a saved device mapping can now be reopened and corrected. Press Edit
  device addresses and every box comes back as you saved it, so one wrong address is a one-box
  fix instead of re-entering the whole worksheet. Cancel keeps the saved mapping.
• The mapping is tied to the backup file it was entered for. Picking a different backup opens the
  address dialog empty, and Migrate refuses to pair a mapping with a file it was not entered for,
  since the addresses are keyed by that file's tank and sensor numbers.
• Every console IP box is checked before anything is attempted. A mistyped address, such as an
  extra dot, is refused with a message instead of being looked up as a network name. That lookup
  is what left the window disabled for a long time after Set clock with a bad address.
• Set clock and the live status banner can no longer leave the window disabled if something goes
  wrong on their connection; the result always comes back, as a message.
• TLS-450PLUS Program tab: 27 more fields are now marked verified on real hardware, after a second
  full migration was read back from the console and matched: products, pumps, lines, sensors,
  relays, external inputs, probe labels, port settings, the water alarm filter and the HRM limit.
• Migration report: an obsolete pipe type (White or Yellow Enviroflex, 1.5"/2.5" Enviroflex) is not
  stored by a TLS-450PLUS as the report used to say. The console accepts the write and silently
  puts its own default pipe in its place, which tests the line against a different pipe. The
  report now says so and tells you to choose the type on the console.
• The Program tab now says what the loaded file is, next to the Console type box. A file migrated
  for a TLS-450PLUS is shown on the TLS-350 field table on purpose, because its settings are the
  TLS-350 codes both consoles share, and the tab now says so rather than just reading 350.

---

File: vr_tls_tool.exe (12.42 MB)
SHA-256: 764b655605e6e6d8d523bdace61b119a9731285de9c40e5f037e8dbf59452dce

To check your download, run this in PowerShell and compare:
Get-FileHash .\vr_tls_tool.exe -Algorithm SHA256

Tank Monitor Console Multitool 0.57.0

• Backups, migrated files and Program tab saves now record which version of the tool wrote them,
  and the oldest version allowed to use them. A file that needs a newer version than you are
  running is refused, with a note to update. Older versions of the tool cannot do this check, so
  it only applies to files written from this version on.
• Every file the tool writes is now stamped so it can tell if the file has been altered since.
  Restore, migrate and reuse-an-existing-rollback all refuse a file that no longer matches its
  stamp, before anything is read or written. That covers the header as well as the settings: the
  header is what says which console a file is for and whether the backup finished.
• Backups taken with earlier versions carry no stamp. They still work, with a note saying the
  check could not run.
• The stamp is there to catch an edited or corrupted file, not to keep anyone out. The tool has
  to write these files offline on site, so it carries what it needs to stamp them.
• New Roll back button on the Restore tab. It finds the rollback file the last restore took for
  that console, shows a preview first, then writes it back. A fresh rollback of the console as it
  is now is taken before it writes, so the undo can be undone.
• Fixed: a rollback file taken during a TLS-450PLUS restore was refused by the tool that wrote it,
  and the message told you to convert it, which was wrong for that file. Rollback files now record
  which console they came off. Files written by earlier versions do not, and cannot be used to roll
  back a 450PLUS; the tool now says so plainly instead of sending you the wrong way.
• New Check file button, and a Check a backup file menu option. It answers "will this restore
  work" with no console attached: whether the file would be refused, what would actually be
  written, what the file is missing. Useful before driving to site.
• New Files tab listing every backup and rollback file on the computer, with what each one is and
  when it was read. It calls out any that must not be used to restore a console: a backup whose
  sweep did not finish, one with no records in it, a read-only reference sweep, and any file whose
  contents no longer match the stamp this tool wrote.
• A restore that is cut off part way through can now be finished. Every write is recorded as it
  lands, so Resume interrupted restore sends only what did not go. Anything the console refused,
  or that was sent with no reply, is sent again. All the usual checks and confirmations run again.
• New How well proven button on the Program tab for TLS-450PLUS. It lists what is worth testing on
  a real console and in what order, so time at a console can be spent on the settings that are
  least proven.
• The text menu gained the same three offline actions for anyone running without the app.
• The 450PLUS Migration tab now asks for one confirmation instead of four. Everything the job is
  about to do is listed in a single block, and you confirm it once by typing the console IP. That
  one answer covers the load, the skipped backup if you chose it, and the automatic events in
  step 5. Nothing you are told has been removed; there is just one thing to type.
• Typing the console IP stays the confirmation, rather than a word. It is the one answer that
  also confirms which console you are about to write to.
• New Skip the pre-restore backup box on the Migration tab, unticked. Use it only when the
  450PLUS's own DB Backup has already been taken to USB, which is a more complete image than this
  tool can read over the serial port. Ticking it adds a line saying so to the confirmation.
• The Restore tab and the command line are unchanged and still ask for their separate
  confirmations.

---

File: vr_tls_tool.exe (12.41 MB)
SHA-256: 9cc155657ad0dbe3d0791c803c1db025409106cdf010959695fd4dcb1abb52a5

To check your download, run this in PowerShell and compare:
Get-FileHash .\vr_tls_tool.exe -Algorithm SHA256

Tank Monitor Console Multitool 0.54.0

• The Program tab can now build a TLS-450PLUS configuration, not just a TLS-350 one. Pick the
  console type at the top of the tab. The 450PLUS form covers the things a TLS-350 does not
  have at all: VR-BUS device addresses, probes, products, pumps, lines, line pressure sensors,
  relays and external inputs, and the serial port settings.
• Every 450PLUS field says how well proven it is -- written and confirmed on a real console,
  written and acknowledged, only ever read, or from the manual alone. Saving a 450PLUS config
  lists the ones that are not proven so you can read them back on the console.
• Loading a backup switches the form to the right console type by itself.
• A saved configuration now always records which console it is for. Built from scratch it used
  to record nothing, and a file with no console type is one the Restore tab cannot refuse for
  either console.
• Restoring a native TLS-450PLUS backup no longer tries to replay five settings whose read
  format is not the format the console accepts for writing (device addresses, the line-to-pump
  mapping, tank-to-product, and the automatic event trigger and task). They were being sent
  malformed. Configurations built by the Program tab and by a migration are unaffected and
  still write normally.

---

File: vr_tls_tool.exe (12.36 MB)
SHA-256: 41d08a6907e1559d08d9b1d6df71400dfc088181312271d3221a5036a1acb9c3

To check your download, run this in PowerShell and compare:
Get-FileHash .\vr_tls_tool.exe -Algorithm SHA256

Tank Monitor Console Multitool 0.53.0

• The tool is now developed and published by Verbose Software. The About tab, the licence and
  the download page carry that name and its copyright, and the program's file properties in
  Windows name Verbose Software as the publisher.
• The download is signed under a new publisher certificate. If a laptop was set up to trust the
  old one, import the new vr_tls_tool_codesign.cer so Windows keeps recognising the publisher;
  until then it will say the publisher is unknown the first time each version runs.
• Migration: two tanks can no longer be pointed at the same probe. A probe sits in one tank,
  and answering the wiring question that way used to go through silently: one of the tanks was
  left with no probe address and no probe configure, the console accepted its tank enable and
  ignored it, and that tank never came on. It is now refused where you enter it, and again
  before the migration writes a file.
• Migration report: the tank/probe worksheet shows each probe's VR-BUS address beside its
  number, so it can be checked against the panel.
• Migration: reading the wiring off the console no longer gives two tanks the same probe number
  if the console reports one twice. It falls back to bus order and tells you to confirm both.
• Migration: the step that creates the automatic events (line disable, relay alarm tasks) no
  longer skips in silence. If step 1's TLS-350 backup box is empty, or holds a migrated file
  instead of the backup, it now says so and tells you what to do -- those assignments only
  exist in the original backup, so without it no events are created and the lines will not
  shut down on a tank alarm.
• Loading a one-file migration now says, every time, that it cannot contain the automatic
  events (Device Tasks). The console creates those and assigns their IDs, so they can never
  be in a saved file. It tells you to run commission-events against the original TLS-350
  backup. This shows up wherever the file is loaded from, including the Restore tab.
• Migration report: the shift schedule note counted every shift slot the backup asked for,
  not the shifts actually programmed -- a site with one shift was told it had sixteen, and
  to set Max Shifts/Day to sixteen. It now counts and names the real ones.

---

File: vr_tls_tool.exe (12.34 MB)
SHA-256: baeed70d55d73c29e722644cc80485a549211e52794d9d348098a9bcacb3e755

To check your download, run this in PowerShell and compare:
Get-FileHash .\vr_tls_tool.exe -Algorithm SHA256