The installation of your court-ordered monitoring program is where the court order is transformed into an operational, effective monitoring tool. Inefficiencies in the installation of your monitoring program can create a multitude of problems that will become apparent at a later time. Properly installing your monitoring program results in few or no false positives, few to no disputes during service calls and an accurate compliance record that can be verified by monitoring agency personnel at any time.
This follows with a full account of the Service Installation sequence and full explanation of the key electrical decisions taken by the Installer. Subsequent Service obligations and their expectations are also fully described.
Pre-installation checks that determine whether the job proceeds
Assess the vehicle before you start to remove any panels. Check the battery voltage under load, check the charging system output, and check the ignition switch. An interlock draws continuous low-level current and logs any anomalies in voltage. If the vehicle has a marginal battery then power interruptions will be recorded as if the fuse had been pulled.
Be sure to check the client’s monitoring authority, required device settings, i.e. Whether you are required to install a camera, GPS unit or real-time reporting on the vehicle. Remember that jurisdictions and offense levels can vary and therefore need to be confirmed prior to the install to ensure that your unit is set up correctly to avoid potential returns due to incorrect settings.
Vehicle-specific complications
- Push-button start systems require a relay approach that interrupts the start circuit rather than a conventional ignition wire.
- Hybrid and electric vehicles have no cranking event in the traditional sense, so the interrupt point sits elsewhere in the ready-signal path.
- Fleet and commercial vehicles with aftermarket telematics may already have devices spliced into the same circuits, creating interference risk.
- Vehicles with anti-theft immobilizers can throw faults if the start circuit is opened without the correct wiring method.
Wiring the handset and control module
The four key connections are 1) Constant power (i.e. The monitoring device is powered up at all times even when the key is turned off). This connection must be fused and plug in quickly and simply. 2) Switched power (i.e. The device is powered up only when the key is in the IGN/S starting position). 3) Ground (i.e. Chassis earth). Most problems arise from poor earths, use a clean and tidy earth connection to a good earth point on the vehicle’s chassis and do not use an existing earth point for other accessories i.e. Make sure it is a clean connection specifically for the monitoring device. 4) Starter interrupt (i.e. Stop the vehicle starting until an adequate breath sample has been given).
Soldered connections must be heat-shrunk or made with approved connectors (e.g. Tam/tossa etc). Wiring must be loomed and cabled so that it does not get damaged by heat, vibration or movement etc and routed away from pedals and other components that could be damaged.
Handset placement
Position of Handset, Handset must be able to be reached from driving position, without stretching. Should not be mounted in a position to interfere with Airbag Deployment, Blocking of Instrument Cluster, or Obstruction of Gear Shift.
Calibration, client training, and the first test cycle
The completed vehicle is then powered up and placed in the monitoring mode, with the device calibrated against a certified reference for the starter interrupt to lockout & release. All programmed parameters, for the terms of the order, are also downloaded into the monitoring unit. The installer then fully cycles the monitoring device through a cold start, going through a rolling retest prompt & simulating a failed sample, to test the full operation of the starter interrupt.
Explain how the interlock works and the Breath Technique for the device(s) installed in the vehicle. Explanations should include the length of time the driver has to retest for a rolling retest prompt, the conditions for a lockout that is temporary versus one that is permanent, and the consequences of failing to attend for scheduled service. It is also important to explain the effects of mouthwash, foods, etc. That can cause a Positive Result and how waiting a few minutes and rinsing mouth out with water can allow a test to be taken at a later time.
Service intervals and what each visit involves
There are usually fixed monitoring periods that can be set on a calendar basis (e.g. Weekly, monthly etc.). If the driver misses a monitoring period the interlock will lock out until monitoring re-commences. Therefore it is important to set and inform the driver of the monitoring schedule before handover. Drivers who want this schedule handled correctly from day one are best served by booking ignition interlock device installation in Ontario through an authorized service centre that reports directly to the monitoring authority.
| Stage | Typical timing | Work performed |
| Installation | Day one | Wiring, calibration, training, documentation to monitoring authority |
| Early check | Within the first weeks | Data download, wiring inspection, correction of usage errors |
| Routine service | Recurring monthly intervals | Recalibration, log transfer, violation review, lockout clock reset |
| Removal | End of order | Circuit restoration, final data pull, compliance certificate |
Removal done properly
Deinstallation of the interlock is not a simple matter of pulling the handheld out of the vehicle. The starter circuit must be restored to its pre-installation condition and all wiring, including splices, must be completely removed and repaired as required. The vehicle must then be test-started several times to ensure that it is operating normally. Logs from the device must be retrieved and submitted to the monitoring center. As with installation, all documentation relating to the deactivation must be provided to the client. Wiring left behind in the vehicle could develop into a fault several months later and the owner would assume that the problem is being caused by the program.