TruTest is Fluke's free desktop software for managing EV charging test data: it pulls saved results off an FEV350 or FEV500, compiles them into professional test reports, and handles firmware updates for the instrument itself. The FEV350 transfers to TruTest over Bluetooth; the FEV500 transfers over a USB-C connection. Neither instrument is a standalone report generator on its own, the on-device screen shows pass/fail results and saved event data, but the actual client-facing document, with station configuration, test dates and full sub-test results laid out properly, is produced on the PC side, in TruTest.
The data structure you're actually building, before software enters the picture
Getting a clean report out of TruTest starts with how test data is organised on the instrument itself, and both the FEV350 and FEV500 use the same basic logic: a project contains one or more stations, and each station contains one or more connection points, with individual test results recorded per connection point. On the FEV350 specifically, a project can hold client and site codes entered once at project level so every station and connection point under it inherits that context automatically, and a project can contain up to 20 stations, with the device supporting up to 10 projects at a time before older ones need to be cleared or archived. One feature worth building your commissioning workflow around: the FEV350's Copy a Station function duplicates a fully configured station, including all its settings, as a new station with the next sequential number. For a site with several electrically identical charging bays, a condominium installing eight matching Type 2 AC wallboxes, this means configuring the station parameters correctly once, then copying that configuration seven more times rather than re-entering mains voltage, RCD type, fuse rating and cable current capacity by hand for every bay, provided the original station is fully configured before it's copied, since the copy inherits whatever state the original was in.
Getting results off the instrument and into TruTest
The FEV350 saves all its test data to internal memory as you work, and transfers it to TruTest over a Bluetooth connection paired from the instrument's own TruTest Software menu; once paired, TruTest pulls the saved project, station and connection point data across for report generation. The FEV500 works differently, using a wired USB-C connection to a PC, reflecting the larger dataset of a DC fast-charging test session (SLAC results, RISO and RLO readings, IMD test outcomes, and load test data per connection point); its USB-C port doubles for both PC data transfer and firmware updates via flash drive. Once a project's results are in TruTest, the software turns what was, on the instrument's small industrial LCD, a series of individual pass/fail screens into a single, properly formatted, professional test report preserving the full detail needed for a compliance record: which connection point was tested, under what station configuration, on what date, and the result of every sub-test run (PE Pre-Test, control pilot, RCD/RDC-DD trip time and current, SLAC, RISO, IMD No Trip/Trip, Load Test, depending on scope). This is the document handed to a building owner, an MCST, or an auditor as evidence a charging point was tested, not a screenshot of the instrument's own display.
Firmware Updates and Service Data Export
Both instruments' firmware is updated through the same general mechanism, documented precisely in the FEV500's manual: download the latest firmware file from Fluke's software downloads page, place it in a folder named exactly FEV500 on a USB-C flash drive formatted as FAT32 or exFAT, insert the drive into the instrument's USB-C port, then go to Settings, Firmware, and select Scan for Available Firmware. The instrument identifies the firmware version on the drive and applies it, restarting several times during the process; schedule the update outside a planned test session, don't interrupt power mid-update, and confirm the new firmware version in Product Info afterward. If Fluke's support team can't resolve a problem remotely, the FEV500 has a documented Service Data export, accessed through the Settings menu, requiring a removable USB flash drive with at least 2 GB of free memory and taking several minutes to copy, so Fluke's engineers can evaluate the underlying data for a hardware or firmware issue not resolvable through standard troubleshooting.
A worked commissioning scenario
Consider a technician commissioning eight identical Type 2 AC charging bays across a new condominium car park deck. Rather than treating each bay as a fresh setup: create one project on the FEV350, enter client and site codes once at project level, fully configure the first station (mains system, voltage, RCD type and rating, fuse type and rating, maximum cable current), then use Copy a Station seven times to replicate that configuration across the remaining bays, adjusting only what genuinely differs between them. Each bay is tested individually under its own station entry, with results saved locally, and at the end of the session one Bluetooth transfer to TruTest pulls all eight stations' results into the single project, compiling them into one combined report covering the whole deck, rather than eight separate disconnected reports needing to be manually stitched together.
Licensing Tiers and Bluetooth versus USB-C
TruTest is not a single, flat product. Fluke offers a free 60-day demo so a technician or facilities team can evaluate the reporting workflow before committing, with a software key purchased separately unlocking either the Lite or Advanced version. This tiered structure matters for the same reason we cover in our guide to renting versus buying an EV charging analyzer: an organisation buying an FEV350 or FEV500 outright but only using the demo or base Lite tier may find itself missing report customisation, template, or data-management features that only Advanced unlocks, a software-tier cost easy to overlook when the conversation is all about the instrument's purchase price. Trial the free demo against the actual report format your clients or compliance records genuinely require before assuming the base tier will be sufficient.
It's a fair question why the FEV350 pairs wirelessly while the FEV500 requires a physical USB-C cable: the FEV350's dataset is comparatively small and well suited to Bluetooth, a genuine convenience when moving between several AC bays in a car park. The FEV500's DC fast-charging sessions capture a larger dataset, SLAC signal characterisation, RISO and RLO readings, IMD results, and load test traces, and a wired USB-C connection gives a faster, more reliable transfer, with the same port doing double duty for firmware updates. A technician running a mixed AC/DC site visit should expect two different data-retrieval habits, not one.
What TruTest Is Not
Based on Fluke's own published documentation, TruTest is a desktop application for data transfer, report generation and firmware management, not a cloud-hosted platform or a live remote-monitoring service watching charging stations in real time. If a facility genuinely needs continuous remote monitoring of charging point health between periodic test visits, that is a separate capability layered on top of, not provided by, the FEV350/FEV500/TruTest workflow described here, and should be scoped as its own requirement rather than assumed to come bundled in.
For what the individual sub-tests captured in a TruTest report actually mean when something fails, see our guide to reading FEV350 and FEV500 test results and fault indications. For how to schedule the physical maintenance of the test instruments themselves so they keep producing reliable data for TruTest to compile, see our guide to preventive maintenance for EV charger test equipment.