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 itself 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 configuration 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, for instance, 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 single bay. The manual is explicit that the original station should be fully configured before it's copied, since the copy inherits whatever state the original was in at the time.
Getting results off the instrument
The FEV350 saves all its test data to internal memory as you work, and transfers it to the TruTest desktop application over a Bluetooth connection. Pairing is done from the instrument's own TruTest Software menu, which walks through the connection on-screen; once paired, TruTest pulls the saved project, station and connection point data across for report generation.
The FEV500 works differently at this step, using a wired USB-C connection to a PC rather than Bluetooth, reflecting the larger dataset and file transfer needs of a DC fast-charging test session (SLAC results, RISO and RLO readings, IMD test outcomes, and load test data all captured per connection point). The FEV500's USB-C port sits in a protected compartment and doubles for both PC data transfer and firmware updates via a USB-C flash drive, so it's worth keeping that port and its cover in good condition on a field unit that sees regular outdoor use.
What actually happens in TruTest once data lands
Once a project's results are in TruTest on the PC, the software's job is to turn what was, on the instrument's small industrial LCD, a series of individual pass/fail screens and saved event tables into a single, properly formatted, professional test report, one that preserves 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, and so on, depending on the instrument and test scope). This is the document that actually gets handed to a building owner, an MCST, or an auditor as evidence a charging point was tested and what the results were, not a screenshot of the instrument's own display.
Firmware updates: a straightforward but specific procedure
Both instruments' firmware is updated through the same general mechanism, and the FEV500's manual documents the steps precisely: download the latest firmware file from Fluke's software downloads page, place that file in a folder named exactly FEV500 on a USB-C flash drive formatted as FAT32 or exFAT, insert the flash 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 present on the drive, which may be newer, the same as, or older than the version currently installed, and applies it, restarting several times during the process. Because the update can involve multiple restarts and takes the instrument temporarily offline, it's worth treating it the way you would any firmware update on field test equipment: schedule it outside a planned test session, don't interrupt power to the unit mid-update, and confirm the new firmware version shows correctly in the instrument's Product Info screen afterward before returning it to service.
Exporting service data for support
If Fluke's own support team can't resolve a problem remotely, the FEV500 has a documented Service Data export, accessed through the Settings menu, that requires a removable USB flash drive with at least 2 GB of free memory and takes several minutes to copy. This exists specifically so Fluke's engineers can evaluate the underlying data and diagnose the root cause of a hardware or firmware issue that isn't resolvable through standard troubleshooting, which is a useful thing to have ready before calling support on a persistent, unexplained fault rather than starting the conversation from scratch.
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, the practical workflow looks like this: create one project on the FEV350, enter the 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 whatever genuinely differs between them (such as connection point numbering). Each bay is then tested individually under its own station entry, with results saved locally. At the end of the session, one Bluetooth transfer to TruTest on a laptop pulls all eight stations' results into the single project, and TruTest compiles them into one combined report covering the whole car park deck, with the shared client and site codes already carried through from the project level, rather than eight separate disconnected reports that then need to be manually stitched together.
Free demo, Lite, and Advanced: the licensing structure worth knowing before you buy
TruTest itself is not a single, flat product. Fluke offers a free 60-day demo version so a technician or a facilities team can evaluate the actual reporting workflow before committing to anything, with a software key purchased separately to unlock either the Lite or Advanced version once the demo period ends or once you decide the reporting workflow genuinely fits how your team works. This tiered structure matters for the same reason we cover in more depth in our guide to renting versus buying an EV charging analyzer: an organisation buying an FEV350 or FEV500 outright, but only ever using the demo period or the base Lite tier, may find itself missing report customisation, template, or data-management features that only the Advanced tier unlocks, precisely the kind of software-tier cost that's easy to overlook when the conversation is all about the instrument's own purchase price. Before committing to a tier, it's worth trialling the free demo against the actual report format your clients or your own compliance records genuinely require, rather than assuming the base tier will be sufficient and discovering otherwise midway through a reporting backlog.
Bluetooth versus USB-C: why Fluke didn't use the same connection method for both instruments
It's a fair question why the FEV350 pairs wirelessly while the FEV500 requires a physical USB-C cable, and the answer comes down to the nature of what each instrument is moving. The FEV350's dataset, per-connection-point pass/fail results, saved control pilot events, and configuration data, is comparatively small and well suited to a Bluetooth link, and wireless pairing is a genuine convenience advantage when a technician is moving between several AC charging bays in a car park and wants to sync data without repeatedly plugging in a cable. The FEV500's DC fast-charging test sessions capture a larger and more detailed dataset, SLAC signal characterisation data, RISO and RLO readings across multiple test points, IMD no-trip and trip results, and load test voltage/current traces over the duration of an energy transfer, and a wired USB-C connection gives a faster, more reliable transfer for that heavier payload, with the same physical port doing double duty for firmware updates via flash drive. In practice, this means a technician running a mixed AC/DC site visit should expect two different data-retrieval habits, not one, and should budget cable-based transfer time into an FEV500-heavy day differently than a Bluetooth-based FEV350 day.
What TruTest is not
Worth stating plainly, because it's easy to assume otherwise: 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 and not 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 and specified 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.