When PUMA reflash tools are deployed at your site, the work doesn’t stop after initial setup. Software versions change, new modules get added to the reflash sequence, and scripting adjustments are needed as your requirements evolve. Getting those updates onto every tool quickly and accurately, without disrupting operations or requiring a site visit, is a critical part of keeping reflash campaigns running smoothly. That’s what Movimento’s OTA update process is built for.
Without OTA capability, every one of those scenarios means the same thing: someone has to physically connect to each device, load the updated script by hand, and verify the result. For operations running dozens of tools, it creates delays, introduces risk, and pulls your people away from the work that actually matters.
Movimento’s OTA capability eliminates that bottleneck entirely.
From Request to Reflash, Without the Wait
When you need a change, whether it’s a new software version for a module, an additional module added to the flash sequence, or a script adjustment to address a field issue, Movimento’s engineering team prepares the updated release and uploads it to the Reflash Nuvolo Cloud. From there, the update reaches every assigned PUMA tool automatically.
Each PUMA device checks in with Nuvolo Cloud at the start of every run. If a newer release is available, the tool downloads and installs it. For bench reflash operations, updates download in the background during normal use and install at the end of a run, so there’s zero downtime and no disruption to your operator’s workflow.
The critical safeguard: a PUMA tool won’t begin flashing a vehicle until it’s confirmed with Nuvolo Cloud that it’s running the latest authorized software version. No vehicle is ever reflashed with an outdated script, regardless of when the tool last connected.
Parallel Reflashing Travels with Every Update
PUMA’s ability to flash multiple modules simultaneously is one of its most significant advantages. A single tool can reflash seven or eight modules in parallel rather than sequentially, dramatically reducing per-vehicle flash time.
OTA preserves that capability through every update cycle. When Movimento pushes a new release, it includes the full scripting configuration for your campaign, including the parallel reflash setup. Updated scripts replace the previous versions, and the tool continues operating with the same multi-module, multi-channel capability it had before. There’s no reconfiguration step, no manual adjustment, and no risk that a parallel reflash setup gets lost in the update.
This means that when your reflash requirements change mid-campaign, the updated process, complete with parallel flashing across all configured modules, reaches every PUMA tool without anyone touching the device.
Verified Before a Single Vehicle Gets Flashed
Speed without accuracy is a liability. Movimento built verification into every layer of the OTA process to ensure that fast delivery never comes at the expense of reliability.
Every update package is validated using hash verification. Once the tool downloads and installs a release, it confirms the installed package against the expected hash value. The tool then reports the installed version and hash back to Nuvolo Cloud. Only after this confirmation loop completes does the tool clear itself to begin flashing vehicles.
If an update fails for any reason, the tool retries automatically on the next connection cycle. A failed OTA never results in a vehicle being flashed incorrectly, because the pre-flash cloud check prevents any tool from operating until it’s verified. The process is self-correcting.
Movimento engineers have full visibility through Nuvolo Cloud into which tools are running which release, across every project. If a rollback to a previous version is needed, any stored release can be retargeted to the fleet immediately.
Built for Connectivity in the Real World
PUMA devices support both cellular and Wi-Fi connectivity for OTA updates. Most deployments use the integrated cellular connection, since reflash operations frequently happen in outdoor lots, parking areas, and facilities where Wi-Fi isn’t available. If your connectivity needs change, Movimento can switch a tool’s connection mode remotely via OTA.
If a tool is out of range when an update is pushed, there’s no missed update. The device checks for the latest release every time it connects, and pulls it down automatically. There’s no window where an update can slip through the cracks.
Tested on Real Hardware Before Deployment
Every initial release and every subsequent update goes through validation before it reaches the broader tool fleet. Movimento’s engineering team tests scripts on physical modules or vehicles, verifying the reflash process from start to finish. For new OEMs or unfamiliar module configurations, this setup and testing phase typically takes one to two days.
Once validated, the release is uploaded to Nuvolo Cloud and deployed to the full fleet. This pre-release testing, combined with hash verification and the mandatory cloud check-in before each flash, ensures that quality is maintained through every update, whether it’s the first release or the twentieth.
Full Traceability, From First Flash to Latest Update
Nuvolo Cloud provides 100% traceability across your entire operation. You can see which vehicles have been updated, which software versions were used for each flash, and the current status of every tool in your fleet. This visibility extends through every OTA-delivered update, giving both you and Movimento a complete record of every action taken.
The result: reflash operations that stay current, stay accurate, and keep moving, with Movimento’s engineering expertise behind every update and your team in full control on the ground.
To learn more about Movimento’s OTA capabilities, contact our team today!