Run
Create VMConnect a wallet, choose a machine, and create a virtual machine in the console.Bench workspaceOpen the injector coding workspace after you install a machine in Console.Diesel injector codingCoding and calibration workflows across live injector families.Documentation
Documentation
Last reviewed:
Profile Overview
Confirm identity first, then run workflow in one continuous session context. This route is intended to be the primary workflow reference for Bosch LP1-9K546-AA operations.
Brand
Bosch
Part Number
LP1-9K546-AA
Part (Compact)
LP19K546AA
Coding Family
Bosch IMA / ISA
Injector Family
BOSCH
Recommended VMs
bosch-ima-02
Recommended Virtual Test Benches
Use one of these virtual machines for coding this injector profile.
Extended catalog · Lane 02
bosch-ima-02
Bosch · IMA / ISA · Lane 02
2,378 profiles
Extended catalog lane. Workflow families on this lane: IMA-7.

Part Search Terms
Use these part-number variants when searching this injector coding workflow across service tools and documentation.
Operator Guidance
Profile-specific hint
Use Bosch CRI routines with this exact part. Keep profile selection locked from input to final result.
Quality checks
- Part number on injector and selected profile must match exactly.
- Keep the same VM lane active from lookup to final output.
- Keep coding family unchanged from start to finish.
- Use validated measured values before final encode.
- Repeat verification when injector setup or bench conditions change.
Workflow
Follow this sequence without changing active profile or coding family mid-session.
Step 1
Create or reopen the matching VM
Start with bosch-ima-02 so the correct lane and workflow stay attached to this profile from the beginning.
Step 2
Load this exact profile in bench
Select part LP1-9K546-AA and confirm brand, lane, and coding family before entering values.
Step 3
Run decode or encode
Execute the coding action inside the same machine session and keep the active lane unchanged until the result is validated.
Step 4
Save and close session
Store the final output with the active VM trace so this operation remains auditable and repeatable.

