Checks before every module write
The risk in remote programming is not the distance. It is starting a write on a connection or a battery that cannot finish it. So IgniteRemote measures both before programming starts, and refuses to begin when either falls short.
These checks lower the risk of an interrupted write. No software can remove it — a module can still be lost to a fault nothing on either end can see.
What is checked, and what happens
The numbers below are the ones the product enforces, not a brochure version of them.
The link has to be direct
A module write is refused on a relayed connection. The two computers negotiate a direct path first, and the programming button only appears once they have one.
Under 400 ms, under 15% resent
The typical round trip and the share of data resent are both measured on the live link. Over 400 ms or over 15% and programming does not start — diagnostics carry on regardless.
Battery between 10.9 V and 15.5 V
The supply is read through the interface, including the lowest it dipped to recently. Below 10.9 V a write is refused; above 15.5 V no note can pass it, because a charger that high damages the module it is meant to support.
A technician can overrule the low end
Below 10.9 V the technician can write a note and go ahead anyway — their call, recorded with their words. The note covers the rest of that tool link, not just one attempt. Above 15.5 V nothing lets it through.
The watch keeps running during the write
If the supply falls away mid-write the job is stopped, unless a note already covers the link. If the tool stops answering, both computers are told — the shop at 30 seconds, the technician at 60.
Every decision is written down
Each check, each refusal and each override note is recorded against the job before the car is touched, with the tool it ran on. It is there afterwards whether the write went well or not.
A refusal is a cheap problem
A technician who is told “not on this connection” puts the car on a cable, or puts a charger on the battery, and tries again ten minutes later. A technician who is not told starts the write anyway, and finds out when the module stops answering.
Diagnostics are never blocked by any of this. Read codes, read data, run routines on whatever connection you have — the gate stands between you and a module write, and nothing else.
Check your setup✓ Path: direct
✓ Typical round trip: 138 ms (limit 400)
✓ Resent: 7.2% (limit 15)
! Supply: 10.4 V (needs 10.9)
Programming refused — battery below 10.9 V.
Connect a battery support unit, or write a note to go ahead anyway.
Flash-Safe for generic USB passthrough
Everything above runs over J2534 tool sharing, which is what ships. The wider Flash-Safe work — connection-health monitoring, automatic pause and recovery for standalone key programmers and scan tablets shared over generic USB passthrough — is still being built, because the USB passthrough it sits on top of is still being built.
If your tool is an Autel IM608, an XTOOL tablet or similar, that is the path you are waiting for, and it is not available on any plan today.
See the roadmapDownload IgniteRemote for Windows
Install IgniteRemote and start a 7-day free trial of the plan you choose. Credit card required.
Windows 10/11 64-bit only. macOS and Linux coming later.