Hoppa till innehåll
Hanterill

Varje utgåva, dokumenterad.

Varje taggat bygge med sina noteringar, senaste först, hämtat från GitHub Releases. Versioner följer SemVer; den fullständiga ändringshistoriken förs per version.

Utgåvenoteringarna är skrivna på engelska.

  1. v0.3.0Senaste#

    All notable changes to Hanterill are documented here. Versioning is SemVer.

    Hanterill 0.3.0

    Released: 2 October 2026

    Hanterill 0.3.0 is one of the largest updates so far.

    This release expands what Hanterill can inspect across the battery, charging system, drive units, infotainment, connectivity, vehicle history and service systems. It also introduces much stricter handling of incomplete or uncertain diagnostic results.

    A major focus of 0.3.0 has been making sure Hanterill tells you what the car actually reported, rather than filling gaps with assumptions.

    Highlights

    Drive-unit history

    A new Drive Units view provides much deeper information about the front and rear electric motors.

    Depending on available data, Hanterill can show:

    • operating time
    • powered time
    • regeneration usage
    • acceleration usage
    • torque availability
    • motor temperatures
    • inverter temperatures
    • coolant temperatures
    • current history
    • torque and speed distributions
    • operating-condition heat maps
    • voltage-spike history The view also makes it easier to compare front and rear drive-unit usage. Where historical band boundaries or physical scales are still being researched, they remain clearly marked as provisional.

    Charge history

    Hanterill can now show lifetime AC and DC charging counts when the related vehicle records agree with each other.

    If the underlying records disagree, Hanterill does not invent a number. The result is left unresolved and the discrepancy is shown.

    Visa hela utgåvans anteckningar

    Historical charge distributions are also visualised as charts.

    Where the exact boundaries of a charge band have not yet been established, Hanterill shows numbered bands rather than pretending they represent known percentages.

    A better reset module

    Resetting a single ECU now says exactly what happened. Hanterill asks for explicit confirmation, reports whether the controller acknowledged the request, and shows outcome unknown when it cannot tell whether the reset finished. Cached readings are cleared afterwards so stale values are not shown as fresh, and the ECU page disables the BECM reset up front instead of letting you start something that would be refused.

    The recorded reset-all procedure runs as a cancellable job with VIN verification and three explicit confirmations. Hanterill separates request delivered from vehicle physically rebooted, a cancelled or interrupted run still returns its partial results, and the confirmation dialog and audit log state what was actually sent.

    Generic broadcast resets and a direct BECM reset remain blocked. See ECU and service functions for the details.

    A better interface

    Owner-facing screens now lead with understandable names such as battery voltage or coolant temperature instead of diagnostic identifiers. Raw codes remain in the expert tools.

    The Battery page has separate full-width sections, so large cell maps no longer overlap neighbouring information. The light and dark themes use cleaner neutral surfaces and one consistent blue accent. Fault-code rows show their description in the list, the Live Data catalogue has All signals, Selected and Favourites views, and a Demo Mode banner appears on every screen. Keyboard and accessibility support have also improved. See User interface for the full list.

    New icons and logo

    Hanterill has a new logo mark, in a colour version and a version for dark backgrounds, and a new browser icon.

    The application icon has been replaced for Windows and macOS, including the sizes Windows uses for tiles and the Store listing.

    Deeper battery diagnostics

    The Battery pages now show per-cell State of Health, capacity and State of Charge, module temperatures from the pack's own sensors, charging history, and contactor and pre-charge history.

    The Battery Health verdict now takes the reported State of Health into account, and a partial cell read is shown as an incomplete measurement instead of being graded as a full inspection.

    More reliable fault codes

    Active, pending and stored codes are now handled the same way on the Fault Codes page, the Overview and the Inspection Report. A module that was not read shows Not read instead of looking clean, and clearing codes no longer claims success without evidence.

    New infotainment diagnostics

    Hanterill now has a dedicated Infotainment page for the car's Android Automotive head unit and audio amplifier.

    Depending on what the vehicle reports, it can show:

    • Android version
    • software build
    • security patch level
    • hardware information
    • part and software numbers
    • storage wear estimate
    • infotainment restart history
    • cloud-service errors
    • connection history
    • software-update history
    • audio amplifier information Software update records are translated into plain descriptions such as installed, failed and retried, or withdrawn before completion. A new Since your last reading section can also highlight new restarts, connection changes, cloud errors and software-update activity since the previous read. The infotainment page is deliberately owner-focused. Technical values that cannot yet be explained reliably are not presented as meaningful vehicle information.

    TCAM connectivity diagnostics

    The TCAM page now includes a new Connectivity section.

    It can inspect information reported by the vehicle about:

    • cloud connectivity
    • service discovery
    • provisioning
    • cellular connectivity
    • mobile network registration
    • connection history
    • failed network registrations
    • modem software
    • emergency-call system software Hanterill does not attempt to interpret unknown network rejection codes or turn them into a good/bad verdict. Potential identifiers found in the returned data are also redacted before being displayed.

    Improved TCAM and GPS information

    The TCAM page has been redesigned to better explain what the module is actually reporting.

    GNSS data is now identified and presented as navigation/positioning information rather than a large block of hexadecimal data.

    Where available, Hanterill can show information such as:

    • fix state
    • satellites
    • signal-quality information
    • TCAM software information
    • module status
    • backup-battery information Coordinates remain on the GPS page behind the existing location consent controls.

    Better TCAM backup-battery diagnostics

    Backup-battery readings are now more transparent.

    If the normal reading is unavailable and Hanterill has to use an alternative method, the app shows what happened instead of simply reporting that no reading was attempted.

    Measured values are also no longer thrown away simply because they fall outside an expected voltage range. An unusual value is shown and flagged rather than hidden behind a decode error.

    This is particularly important when investigating a genuinely failing TCAM backup battery.

    ---

    Battery diagnostics

    Much deeper battery information

    Battery diagnostics have received another major expansion.

    Depending on vehicle and platform support, Hanterill can now show:

    • battery State of Health
    • per-cell State of Health
    • per-cell learned capacity
    • per-cell State of Charge
    • cell voltages
    • cell balance
    • battery-module temperatures
    • hottest and coldest modules
    • temperature spread
    • battery awake time
    • AC and DC charging history
    • time spent in different charge bands
    • contactor behaviour
    • pre-charge history
    • isolation-related information
    • battery identity information
    • additional lifetime statistics The cell views have also been improved with clearer heat maps and better highlighting of the strongest, weakest, hottest and coldest areas of the pack.

    Battery Health now considers actual degradation

    The Battery Health verdict now considers the battery's SoH classification before declaring the pack healthy.

    Previously, good cell balance could potentially result in a positive overall result even when the reported State of Health itself was below the relevant warranty threshold.

    A healthy-looking cell map can no longer override a poor SoH result.

    Partial cell reads are no longer treated as complete

    Cell-balance classifications are now only applied when Hanterill actually obtained enough data to justify them.

    A partial cell sweep is shown as an incomplete measurement, rather than being graded as though the whole battery was inspected.

    The same rule is now used on the Battery page and in exported reports.

    Better explanation when battery data is missing

    When a per-cell SoH, capacity or State of Charge reading is unavailable, Hanterill now records why.

    Instead of simply showing an empty value, the app can distinguish between situations such as:

    • the module did not answer
    • the read failed
    • the returned data could not be decoded
    • the result was outside the expected range
    • the measurement was incomplete This makes it much easier to distinguish a genuine battery issue from a failed diagnostic read.

    Correct battery temperature data

    The battery thermal map now uses the battery pack's actual module temperature sensors.

    This replaces an earlier interpretation that could produce misleading high/low battery-temperature values.

    For supported CMA vehicles, Hanterill can now display the pack's 27 modules with two temperature sensors per module and identify the warmest and coolest areas of the pack.

    Corrected State of Charge readings

    The primary State of Charge readings now come from the BECM's own confirmed values.

    Multiple available sources are compared and the app tells you whether they agree instead of silently choosing one.

    Corrected battery-capacity reference

    Capacity fade calculations now use the reference derived from the vehicle's own battery data rather than the previous topology-based figure.

    This brings the calculated capacity loss much closer to the BECM-reported State of Health.

    ---

    Charging

    More charging information

    The Charging page now includes much more information from the on-board charger.

    During an active charging session, supported vehicles can report:

    • power from the grid
    • power entering the battery
    • charging efficiency
    • voltage per phase
    • current per phase
    • charging limits
    • pilot signal
    • charger status Historical information can also include:
    • AC charge count
    • DC fast-charge count
    • charging distributions
    • time spent in charge bands
    • selected charger statistics Lifetime AC and DC charging counts and the charge-distribution charts are covered under Charge history in the Highlights.

    Corrected charger-health information

    Several charger values previously interpreted as lifetime counters were found not to behave like lifetime statistics.

    Those readings are no longer presented as charge-cycle or restart counts without supporting evidence.

    ---

    Drive units and power

    The new Drive Units view is described under Drive-unit history in the Highlights.

    DC/DC converter diagnostics

    The Power page can now inspect the DC/DC converter that supplies the vehicle's 12 V electrical system.

    Available information can include:

    • operating history
    • 12 V output voltage
    • output current
    • output power
    • available power
    • high-voltage input
    • board temperature
    • historical operating distributions

    Improved 12 V diagnostics

    The 12 V system now uses the vehicle's actual battery-voltage reading rather than a control-module supply voltage that had previously been interpreted as the battery terminal voltage.

    Additional information can include:

    • battery voltage
    • estimated capacity
    • current
    • standby current
    • low-voltage statistics
    • battery age
    • battery temperature history
    • battery-related fault information Hanterill also accounts for known measurement offsets when comparing the 12 V reading reported by different modules. ---

    Driving and vehicle history

    Redesigned Driving page

    The Driving page now focuses on useful information instead of exposing large diagnostic tables first.

    It includes information such as:

    • trip distance
    • driving time
    • average speed
    • average energy use
    • odometer
    • service intervals
    • learned consumption
    • vehicle messages
    • display history
    • driver-assistance information
    • selected vehicle statistics Large secondary data sets are only read when needed, reducing the number of requests sent to the vehicle.

    Learned energy consumption

    Hanterill can now display energy-consumption information learned by the vehicle together with historical usage distributions.

    Where the physical meaning of a historical band has not yet been completely established, the app says so instead of assigning an unsupported scale.

    Automatic capture when connecting

    Connecting to a vehicle can now create a small diagnostic snapshot automatically.

    The snapshot can include selected information such as:

    • charging history
    • 12 V statistics
    • vehicle resets
    • vehicle clocks
    • VIN
    • selected vehicle-state information The next time the same vehicle is connected, Hanterill can compare the captures.

    Since your last visit

    The Sessions page can now highlight meaningful changes since the previous capture.

    Depending on available data, this can include:

    • additional charging cycles
    • new gateway resets
    • newly added keys
    • recently cleared fault codes
    • new charger alarms
    • clock synchronisation changes Captures are matched to the vehicle, so information from different cars is not silently compared. ---

    Vehicle page

    Better odometer verification

    The Vehicle page now leads with the result of its odometer cross-check.

    If the available controllers agree, Hanterill says so directly.

    If they disagree, the conflicting readings are promoted to the top and Hanterill can flag the discrepancy for review.

    Large controller lists remain available but are collapsed by default when they add little information.

    Better controller-time comparison

    Vehicle clocks and controller uptime information are also presented as a consensus where possible.

    If everything agrees, you get one clear result.

    If controllers disagree, Hanterill highlights the modules that differ.

    Keys and locking

    The Vehicle page can now show information such as:

    • number of registered keys
    • whether more keys appear to exist than expected
    • starts associated with keys
    • lock events
    • unlock events
    • key-button activity
    • odometer values associated with recorded events

    Tyre-pressure sensors

    Hanterill can inspect whether tyre-pressure sensors appear to be learned by the vehicle.

    Where the available data cannot distinguish between missing sensors and a vehicle designed to operate without them, the interface says so instead of guessing.

    More vehicle information

    Additional vehicle information now includes selected data for:

    • standard OBD information
    • vehicle configuration
    • grille and spoiler shutters
    • car mode
    • ride-height information
    • immobiliser/transponder information Values whose meaning has not been established remain raw or explicitly unverified. ---

    Fault codes

    More accurate fault classification

    Fault handling has received extensive corrections.

    Active, pending and stored codes are now handled consistently throughout the Fault Codes page, Overview and Inspection Report.

    This fixes situations where:

    • a currently failing code appeared only as stored
    • one fault appeared more than once
    • active and pending totals double-counted the same code
    • the report and Fault Codes page disagreed
    • exported fault state disagreed with the screen

    A module that was not scanned no longer appears healthy

    A missing result is no longer interpreted as an empty fault list.

    If Hanterill did not actually read a module, it now says Not read.

    Only a module that was successfully read and returned no codes receives a clean result.

    DTC descriptions visible directly in the list

    Fault-code rows now show the longer description directly beneath the title when one is available.

    You no longer have to open every code individually just to see its description.

    Recently cleared fault information

    Supported vehicles can expose information such as:

    • driving cycles since codes were cleared
    • time with a fault
    • limited-operation history
    • selected controller-reset information This helps when inspecting a used vehicle or chasing an intermittent issue.

    Offline fault-code decoding

    Captured fault-code data can now be pasted into Hanterill and decoded without being connected to the vehicle.

    Safer DTC clearing

    Fault-code clearing has been extensively tightened.

    Hanterill now keeps track of which modules were actually cleared, which failed, which could not be verified and why an operation stopped.

    If a controller still reports a fault after clearing, Hanterill performs a follow-up check and reports the codes that remain.

    Cancelling a clear operation also keeps any partial results already returned instead of simply discarding the information.

    The clear dialog no longer carries potentially risky choices forward from the previous operation.

    Fault clearing does not claim success without evidence

    An unanswered or incomplete erase is no longer treated as proof that the codes were cleared.

    Unresolved operations are reported as unresolved or inconclusive.

    Some modules, including operations that would require unsupported high-voltage preparation, remain blocked.

    ---

    ECU and service functions

    ECU reset

    Individual supported ECUs can be reset from their ECU detail page.

    The process uses explicit confirmation and reports whether the controller acknowledged the request.

    If Hanterill cannot determine whether the reset actually completed, it reports the outcome as unknown rather than claiming success.

    Cached readings are cleared after a reset so stale values are not presented as fresh vehicle data.

    Vehicle-wide reset remains heavily restricted

    Generic broadcast reset operations and direct BECM reset remain blocked where the required high-voltage preparation cannot be verified.

    A separate recorded reset-all procedure exists for the specific observed vehicle procedure. It uses additional vehicle checks, VIN verification and multiple confirmations.

    Even there, Hanterill distinguishes between request delivered and vehicle physically rebooted. A transmitted reset is not presented as physical confirmation of a reboot.

    Experimental parking-brake procedures

    Experimental electronic parking-brake procedures are available for supported BCM/VDDM configurations.

    These include:

    • release
    • apply
    • enter service position
    • leave service position The procedures require explicit confirmation and perform additional checks before commands are sent. These functions remain experimental. Controller acknowledgement is not the same as confirming that the brake physically moved, and Hanterill does not claim physical validation where that validation has not been performed. Unsupported controller combinations remain blocked.

    Service authentication

    Selected ECU detail pages now support locally confirmed service-level authentication.

    This can unlock access required by certain advanced service operations.

    The process includes safeguards for invalid responses, lockouts and unsuccessful authentication attempts.

    Sensitive authentication information is not included in normal diagnostic output.

    Service authentication does not automatically authorise every other service routine, and physical-vehicle validation is still required for supported write operations.

    Clearer Service Routines page

    The Service Routines page now makes the consequences of write operations much clearer.

    Improvements include:

    • visible read-only/write availability
    • risk labels on medium- and high-risk functions
    • clearer prerequisites
    • stronger confirmation for higher-risk operations
    • better navigation between routine categories
    • clearer explanations when an operation is unavailable Write operations should now look and behave noticeably differently from ordinary diagnostic reads. ---

    Overview

    More useful conclusions

    The Overview page now uses the vehicle information already collected to provide actual diagnostic findings instead of only showing raw numbers.

    Potential findings include:

    • odometer disagreement
    • State of Charge disagreement
    • poor battery SoH
    • cell imbalance
    • incomplete cell measurement
    • low 12 V voltage
    • overdue service
    • incomplete diagnostic coverage
    • active fault codes

    Charging and TCAM added to system status

    The systems overview now includes charging information and the TCAM backup battery.

    The battery row also focuses on the battery-health verdict rather than repeating the same headline number shown elsewhere.

    Missing information is shown explicitly

    Instead of simply saying that some measurements are missing, the Overview now identifies which important readings were unavailable.

    The capture time is also displayed clearly so you can see how old the information is.

    ---

    Reports

    One consistent Inspection Report

    The on-screen report and exported reports now use the same underlying vehicle findings.

    This addresses cases where one view could previously classify something differently from another.

    Missing data is no longer presented as a pass

    If a diagnostic section was not read or was excluded, the report says so.

    For example, leaving out the fault-code scan no longer produces a green result that looks like the vehicle was scanned and found clean.

    Better fault reporting

    The Inspection Report now includes faults that are failing or pending even if they have not yet reached a fully confirmed stored state.

    Stored-only codes remain available separately.

    The report, PDF certificate and Fault Codes page therefore describe the same vehicle condition.

    Improved battery reporting

    Battery reports now use the same SoH, cell-balance and completeness rules as the main Battery page.

    A partial battery read can no longer become a confident balance verdict simply because it was exported to PDF.

    Optional location

    Location remains excluded from Inspection Reports by default.

    It can be explicitly included when needed.

    Better buyer-oriented information

    Reports can include useful inspection information such as:

    • registered keys
    • evidence of recently cleared fault codes
    • limited-operation history
    • tyre-pressure sensor status
    • charging history
    • drive-unit usage
    • battery condition
    • odometer agreement

    Improved report layout

    The report layout has been improved across desktop, narrow windows and print/PDF views.

    Long findings and report controls should no longer squeeze headings or collapse into unreadable layouts.

    Dates and timestamps also follow the selected locale more consistently.

    ---

    Live data

    Improved signal selection

    The Live Data signal catalogue now offers:

    • All signals
    • Selected
    • Favourites You can browse the available signals even before connecting to a vehicle. Changing the catalogue filters while recording also no longer changes which signals are already being captured.

    Live recordings no longer stop after 45 seconds

    A bug could incorrectly classify an active recording as stalled after approximately 45 seconds.

    Valid incoming sample batches now keep the recording alive as expected.

    A genuinely silent connection can still trigger the normal timeout protection.

    ---

    Connection and reliability

    Safer reconnect behaviour

    Hanterill no longer blindly resends potentially state-changing commands after a connection interruption.

    Read operations can safely be retried, but a command that may already have triggered an actuator or routine is not automatically sent a second time.

    This avoids the possibility of performing the same physical action twice after an uncertain timeout.

    Better recovery after cancelled operations

    Cancelling during connection recovery no longer leaves the diagnostic session permanently stuck in a recovering state.

    Better Windows connection errors

    Windows should now more accurately distinguish a host that actively refuses the diagnostic port from a normal connection timeout.

    Better handling of saved data

    Several edge cases that could cause saved sessions or settings to fail have been fixed.

    This includes:

    • extremely fast consecutive saves
    • reconnects that generated duplicate identifiers
    • temporary file locks from antivirus software
    • malformed settings data

    Failed operations no longer spin forever

    If Hanterill receives a result that it cannot decode, the operation now ends with an error instead of leaving the screen permanently showing that it is still running.

    Better handling of fast operations

    Very quick operations can no longer complete before the desktop application has started listening for their result.

    ---

    Firmware

    Firmware audit no longer guesses the latest version

    The Firmware Audit previously contained placeholder comparison data that could result in a module being labelled Up to date or Behind without an authoritative source for the latest manufacturer firmware.

    Those claims have been removed.

    Hanterill can still:

    • show the software installed in the vehicle
    • compare software between two captures of the same vehicle
    • identify modules that could not be read But it will not claim that a vehicle has the manufacturer's newest firmware unless there is a reliable source for that comparison. ---

    Performance

    Faster diagnostic reads

    Where supported, Hanterill can request several readings from a module in the same exchange instead of issuing one request for every value.

    This substantially reduces communication overhead on larger diagnostic pages.

    If a controller does not accept larger grouped requests, Hanterill automatically falls back to smaller ones.

    Less unnecessary vehicle traffic

    Several screens now read only the information they actually need.

    For example:

    • detailed Driving data loads only when requested
    • combustion-engine data is not automatically read on an EV
    • previously retrieved information can be reused during the same session This should make larger diagnostic views faster while placing less load on the vehicle.

    Smaller production build

    Development-only simulated vehicle data is no longer bundled into normal production releases.

    ---

    User interface

    Technical identifiers moved out of the way

    Most owner-facing screens now lead with understandable names such as battery voltage, backup-battery state or coolant temperature rather than diagnostic identifiers.

    Raw diagnostic codes remain available in expert tools where they are actually useful.

    Improved Battery page layout

    The Battery page's main health, per-cell and State of Charge areas are now separate full-width sections.

    Large cell maps should no longer overlap neighbouring information, and they remain usable on smaller displays.

    Improved 12 V views

    Unverified 12 V values no longer receive invented physical units.

    Unknown data is shown as undecoded until its meaning is established.

    Demo mode is clearly labelled everywhere

    Simulated vehicle data now produces a global Demo Mode banner.

    You should no longer be able to navigate to another screen and mistake demo readings for data measured from a real car.

    Better keyboard and accessibility support

    0.3.0 includes several accessibility improvements:

    • sortable tables can be operated with the keyboard
    • focus moves correctly when navigating between pages
    • form errors are associated with their controls
    • keyboard focus is more visible
    • interactive rows provide pressed-state feedback
    • colour contrast has been improved
    • narrow-screen layouts have been improved

    Refreshed visual design

    The default light and dark themes have been updated with cleaner neutral surfaces and a more consistent blue accent.

    Typography, page headers, status labels and spacing have also been made more consistent across the application.

    ---

    Languages

    Much more of Hanterill is translated

    Large parts of the application that previously contained hardcoded English are now included in the translation system.

    This includes areas such as:

    • reports and PDF exports
    • service functions
    • ECU actions
    • connection screens
    • DID Explorer
    • GPS
    • climate
    • retrofit checks
    • export dialogs
    • appearance settings
    • infotainment
    • TCAM connectivity All nine supported languages now contain the new strings. The newly added non-English infotainment and TCAM connectivity translations are machine-generated and still need native-language review.

    More natural interface wording

    English interface text has also received a general cleanup.

    Technical or developer-oriented wording has been replaced with shorter, more natural descriptions, and headings/buttons now use more consistent sentence casing.

    ---

    Updates

    Optional update checking is back

    Hanterill can once again check whether a newer release has been published.

    From Settings → About → Updates you can:

    • check manually
    • optionally enable a daily check when Hanterill starts Automatic checking is disabled by default. The update check only looks for a newer published version. Hanterill does not automatically download or install anything, and vehicle information is not included in the request. ---

    Security and privacy

    Safer network targets

    The desktop application now restricts which network addresses its diagnostic connection can target.

    Vehicle link-local addresses remain supported because they are required for direct DoIP connections.

    Better local credential storage

    Settings, profiles and local service credentials are now stored in the operating system's per-user application-data location instead of whichever directory Hanterill happened to be started from.

    Improved log redaction

    VINs, network addresses and other identifiers are now redacted in more log formats.

    Location remains opt-in

    GPS information is excluded from reports by default and must be explicitly enabled when wanted.

    ---

    Important accuracy corrections

    0.3.0 corrects several earlier interpretations after additional vehicle captures and validation.

    These include corrections to:

    • battery-module temperatures
    • battery isolation information
    • 12 V battery voltage
    • charger-history values
    • battery State of Charge
    • battery capacity reference
    • drive-unit history
    • charge-history distributions
    • VIN-based Polestar model detection
    • cell numbering
    • fault-state classification
    • firmware-version reporting Where Hanterill does not yet have enough evidence to assign a physical meaning, scale or verdict, the value is now increasingly shown as Experimental, Raw, Not established or Not read rather than being presented as confirmed fact. ---

    Experimental features and known limitations

    Some parts of Hanterill remain research-oriented and in beta.

    In particular:

    Installationsfiler · 7 filer · 195.0 MB
  2. v0.2.2Massive update focused on stability, vehicle support, diagnostics, localization and making the information Hanterill presents easier to understand.Anteckningar#

    Massive update focused on stability, vehicle support, diagnostics, localization and making the information Hanterill presents easier to understand.

    Hanterill is still in beta. Vehicle support continues to expand and some features, readings and service functions are still experimental or require additional validation on real vehicles. Just because it's there doesn't mean it works, alot of the service items are placeholders and full implementation has not been released

    Version 0.2.2 is one of the largest Hanterill updates so far.

    This release adds significantly improved diagnostic support for Volvo SPA1 vehicles such as the XC60, XC90, V60 and S60, together with new connection methods for Polestar 4 and other SEA-platform vehicles.

    A lot of work has also gone into reliability. Hanterill is now much better at distinguishing between a vehicle that did not respond, a communication problem, unsupported data and a value that could not be decoded. Incomplete scans can be resumed, failed ECUs can be retried individually, and existing captures can be re-analysed as Hanterill's diagnostic database improves.

    The interface has also received a major redesign based more closely on Microsoft's Fluent 2 design language. Pages now focus on understandable findings and vehicle information first, while raw diagnostic identifiers remain available in the advanced tools.

    Localization has received a substantial update as well. Dutch and Chinese have been added as new languages, while the existing translations have been reviewed and improved across the application.

    Highlights

    • Improved Volvo SPA1 support
    • New Polestar 4 / SEA connection fallback
    • More reliable DID scanning and scan recovery
    • Better battery diagnostics and history
    • Clearer explanations when vehicle data cannot be read
    • Improved DTC scanning and comparison
    • New vehicle configuration reports
    • Improved service-routine safety information
    • Major Fluent 2 interface refresh
    • Dutch language support
    • Chinese language support
    • Improved translations across existing languages

    Added

    • Dutch language support. Hanterill is now available in Dutch across the desktop application, including the main navigation, vehicle pages, diagnostics, settings and newer features.
    • Chinese language support. Chinese has been added as a new application language, covering the main interface, diagnostic pages, settings, reports and other user-facing areas.
    • Clearer battery diagnostics. When a battery value such as State of Health, State of Charge or learned capacity cannot be read, Hanterill now explains what happened instead of simply showing an empty value. It can distinguish between a module that did not answer, an invalid response, a decoding problem and a reading that is not supported.
    • State of Charge cross-checking. Hanterill can compare State of Charge readings reported by different vehicle systems and show whether they agree. If one of the expected sources is unavailable, the missing source is identified.
    • Battery history and CSV export. Saved sessions can now be used to follow State of Health, State of Charge and battery-cell variation over time. History can also be exported to CSV for use in Excel or other analysis tools.
    • Per-vehicle battery history. Battery trends are now kept separate for each vehicle, preventing readings from different cars from accidentally being compared.
    • More reliable DID scans. The DID Scanner now shows how much of the planned scan was actually completed. If communication is lost halfway through a scan, it will no longer appear as though the entire scan completed successfully.
    • Resume incomplete scans. Interrupted DID scans can now be continued without starting again. Previously verified results are preserved and Hanterill shows what remains to be checked.
    • Retry failed ECUs only. Communication failures with individual modules can now be retried without repeating the entire discovery process.
    • Re-analyse existing captures. Previously recorded scans can be analysed again using the latest Hanterill diagnostic database. This means improvements in newer versions may reveal additional information from captures you already have.
    • Improved Volvo SPA1 support. Diagnostic coverage has been expanded for SPA1 vehicles including the Volvo XC60, XC90, V60, S60 and related models.
    • Additional SPA battery information. Early support now includes State of Charge, State of Health, pack voltage and battery-cell information. Data that still requires additional real-vehicle validation is clearly marked.
    • Polestar 4 / Geely SEA connection fallback. Some SEA vehicles do not respond to the normal discovery process. Hanterill can now attempt a direct connection using known SEA gateway addresses when standard discovery does not receive a response.
    • SEA discovery diagnostics. Hanterill can identify cases where a vehicle is visible on the diagnostic network but is not accepting a diagnostic connection.
    • DHCP-based diagnostic Ethernet support. Hanterill can now recognise situations where the vehicle expects the computer to obtain an Ethernet address through DHCP and explain this instead of simply reporting a failed connection.
    • ECU reset controls. Supported ECUs can now be reset from their ECU page. Vehicle-wide reset options are also available from Service Routines where supported.
    • Immobilizer and transponder information. Available key and transponder information can now be displayed on supported vehicles.
    • Registered key count. Hanterill can now read the number of registered keys where the vehicle exposes this information.
    • Offline DTC decoding. Captured fault-code data can be pasted into Hanterill and decoded without connecting to a vehicle.
    • Fault-scan comparison. A new fault-code scan can be compared with the previous saved scan for the same vehicle, making it easier to identify new, cleared or recurring faults.
    • Session evidence export. Diagnostic evidence collected during a session can now be exported as JSON.
    • Connection wire log. The Connection page can display the diagnostic requests and responses exchanged with the vehicle, including response times and negative responses.
    • Vehicle configuration reports. Hanterill can generate printable configuration reports containing information such as VIN, mileage and decoded vehicle options.
    • Configurable report privacy. Report contents, units and privacy options can be configured from Settings. Location information remains disabled by default and is only included when explicitly enabled.

    Improved

    • Improved translations across the application. Existing languages have been reviewed and updated, particularly on newer pages and features. Missing strings, inconsistent terminology and untranslated interface elements have been corrected across diagnostics, reports, settings and vehicle information.
    • Better localization of dates, times and reports. Dates and timestamps now follow the selected language and locale more consistently, including normal local date formats and 24-hour time where appropriate.
    • A much cleaner interface. The desktop application has been redesigned around Microsoft's Fluent 2 design language, with better spacing, typography, navigation and responsive behaviour.
    • More understandable vehicle information. Normal pages now prioritise names such as "Battery State of Health", "Backup-battery voltage" and "Software version" instead of leading with diagnostic identifiers.
    • Technical information is still available. DID codes, ECU addresses and raw diagnostic information remain available in the DID Explorer, Scanner, ECU pages and other advanced diagnostic tools.
    • Overview now focuses on findings instead of raw numbers. Battery condition, odometer consistency, State of Charge agreement, diagnostic coverage and other checks are presented as understandable findings.
    • Better handling of missing information. Instead of simply displaying "Unavailable", Hanterill increasingly explains which module or reading could not be obtained and why.
    • Improved connection diagnostics. Connection errors now distinguish between situations such as no vehicle being detected, a request not being sent, an ECU not answering, an unsupported response, a closed diagnostic port and a timeout.
    • Safer Service Routines. Procedures now show their verification level, prerequisites and risk more clearly before they are executed.
    • More reliable communication with slower ECUs. Diagnostic timing has been improved and Hanterill now respects ECU-provided timing information where available.
    • Better session switching. If an ECU requires another diagnostic session, Hanterill can switch session and retry rather than immediately treating the request as unsupported.
    • Improved software and part-number decoding. More formats used by Volvo, Polestar and related vehicle platforms can now be recognised.
    • More consistent desktop and CLI results. Major diagnostic results now use the same underlying information across the desktop application and command-line interface.

    Localization

    Visa hela utgåvans anteckningar

    Hanterill continues to become more accessible to users outside the original English interface.

    New in 0.2.2:

    • Dutch has been added as a supported language.
    • Chinese has been added as a supported language.
    • Existing language translations have been reviewed and expanded.
    • Newer diagnostic pages now have significantly better translation coverage.
    • Terminology has been made more consistent between pages.
    • Reports, dates, timestamps and settings better respect the selected locale.
    • Previously untranslated or partially translated interface elements have been corrected. Localization is still an ongoing effort. If you find an incorrect translation, terminology that sounds unnatural, or a string that is still shown in English, please report it so it can be improved in a future release.
    Installationsfiler · 6 filer · 85.9 MB
  3. v0.2.1This release adds more than 20,000 manufacturer-reference entries covering over 100 vehicle modules, expands diagnostics for combustion and plug-in hybrid…Anteckningar#

    This release adds more than 20,000 manufacturer-reference entries covering over 100 vehicle modules, expands diagnostics for combustion and plug-in hybrid vehicles, and improves scan recovery and reporting. Hanterill now distinguishes more clearly between values reported by the vehicle, manufacturer-reference data, unverified information, and unavailable data.

    Added

    • Added more than 20,000 documented manufacturer-reference entries across over 100 vehicle modules. Selected entries can be checked against a connected vehicle.
    • Added a Capabilities view for supported systems, modules, service information, and vehicle capabilities.
    • Added an Engine view for supported combustion and plug-in hybrid vehicles, backed by hundreds of additional engine-related reference definitions. Unverified values remain marked until they are confirmed against a matching vehicle.
    • Added live readings for engine coolant temperature, engine oil level and temperature, fuel level, fuel-pump status, diesel particulate filter data, gearbox oil temperature, gearbox adaptation mileage, and 48V battery charge.
    • Added scan previews that show the expected support and approximate scope of an advanced scan before it begins.
    • Added collection of fault-related operating conditions and counters when the module provides them.
    • Added raw diagnostic responses to session history so module replies remain available after the vehicle disconnects.
    • Added vehicle-wide ECU reset with state checks. Functions that have not been verified on vehicles remain unavailable.
    • Added an optional update check in Settings. It is disabled by default, never downloads or installs an update, and sends no vehicle information.

    Changed

    • Fault clearing now targets modules with detected faults by default, with a separate option for clearing the whole vehicle. Progress identifies the module currently being cleared, verified, or reset, and preserves the before and after results for comparison.
    • Compatible reads from the same module now share a diagnostic session, reducing repeated vehicle communication during larger scans.
    • A non-responsive module no longer blocks the rest of a scan. Hanterill reports the missing response and continues with the remaining modules.
    • Fault-code scans can recover from temporary connection loss. Before combining results, Hanterill checks that the same vehicle has reconnected.
    • Platform-specific scans now account for module addressing and omit combustion-only modules when scanning an electric vehicle.
    • Battery diagnostics show more health information, record connection and disconnection activity, and sort module readings more clearly.
    • Temperature channels that remain static or otherwise look unreliable are identified instead of being presented as confirmed measurements.
    • Modules for equipment that was never fitted can be marked as expected absent, with the related option or system shown when known.
    • Reports and snapshots show the full VIN by default. VIN masking remains available when preparing data for sharing.
    • Measurements use appropriate precision, conflicting service values are easier to identify, and each service value names its source module.
    • Compatible diagnostic requests can be grouped, and long recordings are written progressively to reduce memory use.
    • Large visual components load only when needed.
    • Keyboard navigation now covers battery cells, module views, and ECU lists more consistently. Buttons and overlays respond sooner, and live charts retain their zoom level.
    • Revised all eight translations, including broader rewrites of the Danish and Norwegian text and shorter interface labels where needed.

    Fixed

    • Corrected TCAM backup-battery response handling on CMA vehicles. The change was verified on a connected Polestar 2.
    • Battery certificates no longer pass when required measurements are missing. Cell comparisons appear only when the required cell data was collected, and missing measurements use consistent labels.
    • Reaching a configured scan limit no longer appears as a cable or vehicle communication failure.
    • Fixed vehicle-wide requests occasionally missing very fast module responses.
    • A failed first recovery step no longer closes a diagnostic session that can still recover.
    • Restored missing battery, fault-code, ECU inventory, and parasitic-drain data in exports, and fixed imports of affected saved sessions.
    • Fixed modules that could not be selected in scan-scope controls.
    • Fixed software-capability checks that could stop before contacting the vehicle.
    • Empty module responses are now reported as unavailable instead of being decoded as current measurements.
    • Corrected radar and module mappings, incomplete-reply handling, stored scan results, cancellation during long operations, connection recovery, and service-status reporting.

    Reliability and safety

    • Operations that can change vehicle state remain protected by safety checks.
    • Functions without enough verification on real vehicles remain disabled or carry an explicit unverified status.
    • Missing and unsupported values remain unavailable instead of being replaced with assumed results.
    Installationsfiler · 6 filer · 83.6 MB
  4. v0.2.0This is a beta. Handle it with care. Fault code clearing and service modes are active. That doesn't mean the app will work on your vehicle or model, or that…Anteckningar#

    Release v0.2.0

    This is a beta. Handle it with care. Fault code clearing and service modes are active. That doesn't mean the app will work on your vehicle or model, or that you should run these functions. Handle with care, There will be bugs.

    [0.2.0] - 2026-09-13

    Version 0.2.0 is a major update to Hanterill.

    This release adds live-vehicle verification, improved battery diagnostics, broader vehicle-platform support, engine and service information, improved live telemetry, faster ECU discovery, offline session analysis, new export options, eight-language support, and numerous reliability and architecture improvements.

    It also simplifies how Hanterill is built and released.

    Highlights

    • First full live-vehicle verification campaign completed.
    • Broader battery diagnostics across CMA, SPA, SEA1, and SPA2.
    • New engine live-data screen.
    • New vehicle capabilities and vehicle-profile information.
    • New service-status diagnostics.
    • Large vendor diagnostic reference catalogue added.
    • Faster ECU discovery.
    • Improved quiet-module discovery.
    • Live telemetry recording and playback.
    • Better session export to JSON, CSV, ZIP, and PDF.
    • Factory equipment and option-package detection.
    • Eight supported languages.
    • Release versioning is now fully synchronized.
    • Large internal cleanup to make diagnostics safer and more consistent. ---

    Vehicle diagnostics

    New vehicle capabilities view

    Hanterill can now show more information about what a connected vehicle supports.

    The new Capabilities view combines live vehicle information with Hanterill's diagnostic knowledge to show:

    • supported vehicle features
    • available diagnostic areas
    • service-related capabilities
    • known vehicle configuration information
    • software compatibility information
    • diagnostic reference information Where Hanterill cannot determine something reliably, it now shows the result as unknown instead of guessing. ---

    Vehicle profile

    The Vehicle screen now includes a more detailed vehicle profile.

    Visa hela utgåvans anteckningar

    Depending on what the vehicle exposes, this can include information such as:

    • vehicle configuration
    • equipment information
    • platform details
    • software-related information
    • factory configuration data Missing information is shown as unavailable instead of being filled with assumptions. ---

    Service status

    A new Service Status area has been added.

    It provides read-only diagnostic information for systems including:

    • driver assistance
    • cameras and radar
    • steering
    • braking
    • climate control
    • safety systems
    • body systems
    • service-related functions Some reference values are shown as raw diagnostic data when their meaning cannot yet be decoded safely. Hanterill prefers a raw value over a guessed interpretation. ---

    Engine live data

    A new Engine screen provides live information for combustion and plug-in hybrid vehicles.

    Available information can include:

    • coolant temperature
    • oil temperature
    • oil level
    • fuel level
    • fuel-pump status
    • fuel-pump activity
    • particulate-filter information
    • regeneration status
    • transmission temperature
    • transmission adaptation information
    • 48V battery state of charge Values with a known and trusted interpretation are decoded automatically. Values that are not yet understood remain visible as raw data instead of being guessed. This is based on data from the V90 T6 and XC40 T5. It might not fit your car. ---

    ICE and plug-in hybrid support

    Hanterill now includes a dedicated reference layer for combustion and plug-in hybrid vehicles.

    This brings more diagnostic knowledge into the application without mixing unverified information into the trusted diagnostic catalogue.

    The new reference information covers areas such as:

    • engine
    • transmission
    • emissions systems
    • fuel system
    • hybrid systems
    • temperature monitoring
    • vehicle status information This reference data comes from the V90 T6 and XC40 T5 and stays separated from verified vehicle data until it's confirmed on a matching vehicle. This means Hanterill can expand support while still clearly distinguishing between:
    • verified diagnostics
    • experimental diagnostics
    • reference-only information
    • unsupported information ---

    Vendor diagnostic reference catalogue

    Hanterill now includes a much larger DTC reference catalogue. It contains information for more than:

    • 100 vehicle modules
    • 120 diagnostic address groups
    • 20,000 diagnostic identifiers This information powers several new features throughout the application, including:
    • engine live data
    • vehicle capabilities
    • service status
    • vehicle profile
    • diagnostic browsing
    • software compatibility checks The catalogue is sanitized before it becomes part of Hanterill. Sensitive or inappropriate source information is excluded. ---

    Battery diagnostics

    Expanded multi-platform support

    Battery diagnostics now understand multiple vehicle architectures instead of assuming one battery design.

    Supported or partially supported platforms now include:

    • CMA
    • SPA
    • SEA1
    • SPA2 Hanterill can adapt its battery interpretation depending on the vehicle platform and battery layout. ---

    More battery layouts

    Hanterill now understands several different battery layouts used across Volvo, Polestar, and related platforms.

    This includes:

    • long-range EV packs
    • standard-range EV packs
    • plug-in hybrid battery packs
    • alternative cell and module layouts
    • different physical module locations The UI no longer assumes that every vehicle uses the same number of cells or the same battery shape. ---

    Better battery health handling

    Battery State of Health can now be interpreted correctly across more vehicle platforms.

    Different platforms expose battery health differently, so Hanterill now uses the correct decoding method for the detected architecture instead of applying one format everywhere.

    ---

    Battery thermal exposure

    The Battery screen now includes lifetime thermal exposure information when supported by the vehicle.

    It can show:

    • time spent in different temperature ranges
    • total recorded operating time
    • how much time the battery has spent in a preferred temperature range
    • an overall thermal-stress indication This gives a better long-term picture of how the battery has been treated. ---

    Cell voltage comparison

    Battery cell snapshots can now be compared offline.

    Two captures can be loaded and compared without reconnecting to the vehicle.

    The comparison highlights:

    • voltage changes per cell
    • changes in total cell spread
    • cells that are drifting away from the rest of the pack This is useful for identifying changes over time. ---

    Retry missing battery modules

    A battery-cell scan no longer has to be restarted completely when only a few modules fail.

    A new retry option reads only the modules that were missing or timed out, while preserving the successful results.

    ---

    Better battery consistency checks

    Hanterill now performs additional checks between pack-level and cell-level data.

    These include comparisons of:

    • individual cell health
    • overall pack health
    • cell state-of-charge consistency
    • cell capacity consistency This helps surface suspicious or inconsistent readings. ---

    Better battery-pack visualization

    The cell detail view now understands the physical location of cells and modules across different battery layouts.

    Instead of simply showing a cell number, Hanterill can provide more useful context about where that cell sits within the physical pack.

    ---

    Live telemetry

    Periodic live data

    Hanterill can now request live data as a continuous stream instead of reading every value individually.

    This enables smoother live telemetry and more efficient recording.

    Several sampling speeds are supported depending on the diagnostic function and vehicle.

    ---

    Live telemetry recording

    Live telemetry sessions can now be recorded directly in Hanterill.

    Recorded sessions can later be opened and replayed without a vehicle connected.

    ---

    Playback controls

    The Live screen now includes playback controls for recordings.

    You can:

    • play
    • pause
    • scrub through the timeline
    • change playback speed
    • select which channels to display
    • export the recording Playback speeds include:
    • normal speed
    • 2×
    • 5× ---

    External recording import

    External Hanterill recording files can now be loaded into the Live screen.

    This makes it possible to share, archive, and inspect diagnostic recordings offline.

    ---

    Improved live workspace

    The recordings drawer now includes both:

    • previously saved recordings
    • recordings created during the current session This fixes the previous disconnect between the live workspace and stored session data. ---

    ECU discovery

    Faster module discovery

    Initial ECU discovery is now much faster.

    Instead of contacting every module one by one, Hanterill can discover multiple responding modules using a single request.

    During live testing, more than 20 modules were discovered in well under one second. This reduces connection and inventory time.

    ---

    Quiet-module discovery

    Some vehicle modules do not respond during normal discovery.

    Hanterill now includes a deeper multi-stage discovery process for these modules.

    It can check:

    • whether the module exists
    • whether it allows an extended diagnostic session
    • whether identification information is available
    • whether diagnostic faults can be queried
    • how accessible the module is Each module is then classified. For example:
    • not fitted or silent
    • present but limited
    • fully accessible for diagnostics The process includes cancellation and per-module progress. ---

    New park-assist camera identified

    Live vehicle testing identified an additional park-assist camera controller that was not previously part of Hanterill's known CMA module list.

    Hanterill can now recognize it and read information such as:

    • hardware information
    • diagnostic part information
    • software information
    • serial information
    • fault information The CMA module catalogue has been expanded to include it. ---

    Factory equipment and configuration

    Equipment detection

    Hanterill can now combine factory configuration information with the ECUs actually found on the vehicle.

    This makes it possible to infer whether certain equipment packages are fitted.

    Current examples include:

    • Pilot-related packages
    • Plus Pack
    • Performance Pack
    • powered tailgate
    • wireless phone charging
    • phone-as-key Where the result cannot be determined reliably, Hanterill asks for manual verification instead of guessing. ---

    Vehicle DNA improvements

    Vehicle DNA now provides more readable factory information.

    Paint and upholstery codes can be shown alongside their human-readable names where known.

    ---

    Retrofit compatibility

    The Configuration screen now includes retrofit compatibility analysis.

    It compares the vehicle configuration with the modules that are actually present and helps identify whether a retrofit appears compatible with the current vehicle setup.

    ---

    Multi-platform support

    Clear platform support levels

    Hanterill now shows how well the detected platform is supported.

    The current levels are:

    • CMA: Full Support
    • SPA: Decoder Support
    • SEA1: Research Preview
    • SPA2: Detection Only The application also explains what each level means. ---

    Platform-aware diagnostics

    Diagnostic modules are no longer tied to hardcoded CMA-specific controller addresses.

    Hanterill now resolves the appropriate controller for the detected vehicle platform.

    This improves compatibility with vehicles where the same subsystem appears at a different diagnostic location.

    ---

    Fewer CMA-specific assumptions

    Several areas previously assumed:

    • one specific battery controller
    • one battery size
    • one cell count
    • one platform layout Those assumptions have now been removed from areas including:
    • battery diagnostics
    • power telemetry
    • vehicle summaries
    • live telemetry
    • session comparison
    • reports
    • command palette actions ---

    Desktop application

    Vehicle context bar

    A new persistent vehicle context bar makes the active diagnostic session easier to understand.

    It can show:

    • connected vehicle
    • session duration
    • connection state
    • diagnostic state
    • whether write operations are enabled Typical states include:
    • Connected
    • Connecting
    • Discovering
    • Needs Attention
    • Disconnected ---

    Improved Settings

    Settings are now grouped into clearer sections:

    • All Settings
    • Appearance
    • Connection & Runtime
    • Privacy & Storage
    • Developer
    • About The Developer section also includes:
    • anonymized support bundle export
    • temporary verbose diagnostic logging ---

    Desktop diagnostic tools

    The desktop application now exposes much more of Hanterill's diagnostic functionality directly through the UI.

    Discovery

    The Discovery screen now includes the deeper quiet-module discovery process with progress and module information.

    Firmware

    Firmware snapshots can now be compared offline.

    Configuration

    Retrofit compatibility can be checked directly from the Configuration screen.

    DID Explorer

    The DID Explorer includes additional tools for inspecting scaling and data interpretation.

    Live Data

    The Live screen includes tools for periodic diagnostic data.

    Service

    Service-related diagnostic results can be queried without triggering the associated service action.

    DTCs

    The DTC screen includes additional diagnostic queries for:

    • fault counts
    • status information
    • stored snapshot information ---

    Sessions and exports

    Modular session export

    Diagnostic sessions can now be exported as separate structured files.

    Available export areas include:

    • vehicle
    • battery
    • battery cells
    • thermals
    • faults
    • ECUs
    • firmware
    • live telemetry
    • parasitic drain
    • service data Exports can be generated as:
    • JSON
    • CSV
    • ZIP archives ---

    VIN masking

    Exported sessions can optionally hide or mask the vehicle identification number.

    This makes it easier to share diagnostic captures while reducing unnecessary personal vehicle information.

    ---

    CSV export

    CSV export is now available throughout more of the application and CLI.

    CSV output is also protected against spreadsheet formula injection.

    ---

    Command-line export

    The CLI can now unpack stored Hanterill sessions into modular JSON or CSV files.

    ---

    Command-line replay

    Live telemetry recordings can also be replayed directly from the CLI.

    ---

    Diagnostic knowledge import

    Stored DID scans can now be folded back into Hanterill's learned diagnostic knowledge base.

    Results are categorized based on whether the identifier was:

    • confirmed
    • unsupported
    • refused
    • timed out
    • malformed
    • not yet verified ---

    PDF reports

    Desktop PDF export has been improved.

    The new export flow includes:

    • live preview
    • optional VIN masking
    • improved print styling
    • translated output
    • a more reliable summary page Additional safeguards were added for platform-specific PDF rendering issues. ---

    Internationalization

    Hanterill now supports eight languages:

    • English
    • Swedish
    • Norwegian Bokmål
    • Danish
    • Finnish
    • Icelandic
    • German
    • Simplified Chinese German and Simplified Chinese are new in this release. Both are community-translated, so quality may vary. Hanterill can automatically detect the preferred language from the operating system. ---

    Diagnostic architecture improvements

    A large internal cleanup was completed in 0.2.0.

    The goal was to make diagnostics more predictable, easier to maintain, and safer when new vehicle platforms are added.

    Shared diagnostic request handling

    Vehicle requests now pass through a more consistent central diagnostic layer.

    This centralizes areas such as:

    • request authorization
    • diagnostic session handling
    • timeout handling
    • read/write safety
    • architecture checks
    • response classification This reduces the number of places where diagnostic behaviour can accidentally differ. ---

    Shared diagnostic session handling

    Operations that temporarily change the diagnostic session now use a shared session guard.

    This ensures that Hanterill restores the vehicle to the correct state after:

    • successful operations
    • failures
    • cancellations
    • early exits ---

    Shared multi-module scanning

    Several features that scan many controllers now use the same sweep logic.

    This includes areas such as:

    • ECU inventory
    • DTC scans
    • firmware inspection
    • mileage
    • uptime
    • DTC clearing The common logic provides consistent:
    • ordering
    • cancellation
    • unavailable-module handling
    • progress reporting ---

    Better vehicle identity protection

    Long-running scans now re-check the vehicle identity when reconnecting or resuming.

    If a different vehicle is connected during the operation, Hanterill refuses to merge results from the two vehicles.

    ---

    Shared vehicle summary

    Vehicle summary information is now gathered through one common layer.

    This covers information such as:

    • vehicle identity
    • factory configuration
    • mileage
    • service information
    • uptime
    • keys
    • battery
    • battery cells
    • parasitic drain This reduces differences between CLI and desktop output. ---

    Shared battery capture

    Battery diagnostics that need the same vehicle information can now share one capture instead of repeatedly reading identical values.

    This reduces unnecessary diagnostic traffic.

    ---

    Shared diagnostic knowledge handling

    Scan results are now added to the learned knowledge base using one consistent policy.

    This improves consistency between desktop and CLI scanning.

    ---

    Reliability fixes

    Fixed vendor-reference reads on real vehicles

    A major issue was discovered where some of the new reference-based reads could work in tests but be rejected on a real connected vehicle.

    The diagnostic authorization logic has been updated so approved reference reads now work correctly while unrelated requests remain blocked.

    Regression tests were added to prevent this from returning.

    ---

    Correct diagnostic-session handling

    Reference diagnostics that require an extended diagnostic session now enter and leave that session correctly.

    ---

    Corrected reference-data labels

    Some reference data was previously presented as if it had been observed directly on a vehicle.

    It is now correctly marked as experimental or reference-based information.

    ---

    Corrected diagnostic identifier formatting

    A formatting issue could cause some identifiers to be shown with a duplicated prefix.

    This has been fixed.

    ---

    Better unsupported-data handling

    Unsupported battery temperature information is now reported as unavailable instead of incorrectly appearing as malformed diagnostic data.

    ---

    Better floating-point handling

    Very small floating-point rounding errors can no longer produce impossible negative temperature-spread values.

    ---

    DTC clear-state cleanup

    The DTC screen now uses one shared clear-operation state.

    This prevents the summary, error message, and audit information from disagreeing with each other.

    ---

    Improved UI safety

    Several frontend edge cases were fixed, including:

    • battery views with no selected cell
    • conditional report content
    • missing export constants
    • responsive battery layouts
    • dark-mode contrast
    • blueprint rendering ---

    Live vehicle verification

    Version 0.2.0 includes Hanterill's first large hardware-in-the-loop verification campaign.

    Testing was performed against a production 2022 Polestar 2 Long Range Dual Motor, V90 T6, and XC40 T5. Results from the V90 T6 and XC40 T5 might not fit your car.

    Installationsfiler · 6 filer · 69.1 MB
  5. v0.1.1Released: September 11, 2026Anteckningar#

    Release 0.1.1

    Released: September 11, 2026

    This is a large update focused on broader vehicle support, faster diagnostics, better battery analysis, improved reliability, and a more complete desktop experience.

    Highlights

    • Early support for Volvo SPA1 vehicles, including selected hybrids and EVs
    • Early support for SEA-based vehicles, including Volvo EX30, Polestar 4 and selected Zeekr models
    • New Pre-Purchase Inspection scoring and reporting
    • Faster vehicle discovery and ECU scanning
    • Expanded battery, charging, climate and power diagnostics
    • Major reliability improvements
    • Improved privacy when exporting reports and support data > Important: SPA1 and SEA support is currently experimental. Only selected diagnostic functions are available and many vehicles, ECUs and data points are not yet supported. CMA vehicles such as the Polestar 2 remain the most complete platform in Hanterill.

    New Vehicle Support

    Volvo SPA1

    Initial support has been added for Volvo SPA1 vehicles, including selected hybrid and electric models.

    Depending on the vehicle, Hanterill can now begin identifying and reading information such as:

    • Battery State of Health
    • Battery State of Charge
    • Battery voltage
    • Battery temperatures
    • Cell voltage information
    • High-voltage system status
    • Charging information
    • Battery power limits Support varies significantly between models and model years.

    SEA

    Initial support has also been added for vehicles based on the Sustainable Experience Architecture, including:

    • Volvo EX30
    • Polestar 4
    • Zeekr 001
    • Zeekr X
    • Zeekr 009 SEA support is still at an early stage. Vehicle detection, ECU discovery and selected diagnostic readings are being introduced first, with broader support planned as more vehicles are tested.

    Battery Diagnostics

    Battery diagnostics have been expanded to better support different battery layouts across CMA, SPA and SEA vehicles.

    Visa hela utgåvans anteckningar

    Hanterill can now adapt its battery analysis to different pack configurations instead of assuming every vehicle uses the same cell layout.

    Battery-related improvements include:

    • Improved cell voltage analysis
    • Battery temperature visualization
    • Better pack balance calculations
    • Battery degradation assessment
    • Support for additional battery layouts
    • Improved handling of incomplete or unsupported battery data The Battery Health experience now avoids presenting uncertain data as confirmed values.

    Pre-Purchase Inspection

    A new Pre-Purchase Inspection (PPI) system has been added.

    Hanterill can evaluate multiple areas of the vehicle and produce an overall condition assessment based on available diagnostic data.

    The inspection can include:

    • Battery health
    • Battery degradation
    • Cell voltage balance
    • Mileage consistency
    • Service information
    • Battery temperature consistency
    • Electrical system health Historical inspection reports can also be recalculated using newer inspection rules as Hanterill improves.

    Faster Vehicle Scanning

    Vehicle discovery and ECU scanning have been significantly improved.

    Hanterill can now query multiple modules more efficiently instead of waiting for every ECU individually.

    This results in:

    • Faster ECU discovery
    • Faster full vehicle scans
    • Shorter waits for modules that are not installed
    • Better handling of unavailable ECUs
    • Improved reconnect behavior
    • Better reuse of information learned from previous scans of the same vehicle Previously detected vehicle information can now help later sessions complete faster.

    Smarter Diagnostic Reads

    Hanterill has become more conservative about interpreting diagnostic data.

    If a vehicle returns unexpected or incomplete information, Hanterill will now prefer to show the value as unsupported or uncertain rather than guessing.

    It can also remember which readings are supported by a particular ECU, reducing unnecessary requests during future sessions.

    This should result in:

    • Fewer incorrect values
    • Fewer unnecessary diagnostic requests
    • Faster repeated scans
    • Clearer unsupported-data states
    • Better compatibility between different vehicle variants ---

    Platform Status

    | Platform | Current status | |---|---| | CMA / Polestar 2 | Most complete support | | Volvo SPA1 | Experimental / partial support | | SEA1 | Experimental / early support | | Other platforms | Not currently supported or under development |

    Vehicle support can vary by model, model year, installed equipment and software version.

    If Hanterill does not recognize a value or ECU, it will increasingly report it as unsupported instead of attempting to infer a result.

    Installationsfiler · 5 filer · 120.4 MB
  6. v0.1.0Initial beta releaseAnteckningar#

    Release 0.1.0

    Initial beta release

    Installationsfiler · 3 filer · 29.4 MB

Hämtat från GitHub Releases vid byggtillfället. Senaste är v0.3.0.