J2534 PassThru Hardware from LPC to a Lower‑Cost MCU + New PCB (Same Released Windows Tooling)
Budget: $1,500 – $3,000 USD
Analyze the existing LPC-based device firmware/behavior (authorized reverse engineering / porting) and rebuild it on a lower-cost MCU (ESP/STM class) with a newly designed PCB.
- Same end-user functionality + same features + lower BOM cost by using cheaper equivalent components (same roles, validated performance).
MOST CRITICAL COMPATIBILITY REQUIREMENTS (MANDATORY)
- The device must remain compatible with OUR already-released Windows installer/driver package and PassThru tooling (no changes required on customer PCs who already use our released package).
- The device firmware/protocol behavior must match our released tooling expectations: command framing, timings, error codes, and state-machine behavior (bit-exact where required by the tooling).
- USB product behavior must remain compatible with our released Windows package (driver installation path, device enumeration, and user-visible device naming as defined by OUR released package). Any USB identifiers must be legally compliant and provided/owned by us (we will supply PID/VID allocation proof if applicable).
- We are not asking to spoof third-party USB IDs or impersonate another vendor’s product.
MECHANICAL / PCB SIZE REQUIREMENT (MANDATORY)
- PCB size must not change: 46.32 mm × 36.81 mm
- Same enclosure will be used.
- Mounting holes and connector physical locations must remain the same.
PROTOCOLS / FUNCTIONS (ALL MANDATORY)
All communication lines and supported protocols must work completely:
- CAN
- K-Line (ISO9141 / ISO14230)
- Any other J2534 protocols/features supported by OUR released tooling must behave exactly the same (no missing features).
J2534 FULL REQUIREMENT (NO MISSING FEATURES)
All J2534 functions used by OUR released PassThru tooling must work fully and correctly:
- PassThruOpen / PassThruClose
- PassThruConnect / PassThruDisconnect
- PassThruReadMsgs / PassThruWriteMsgs (including correct timeout behavior)
- PassThruStartMsgFilter / PassThruStopMsgFilter
- PassThruStartPeriodicMsg / PassThruStopPeriodicMsg
- PassThruIoctl (all required IOCTLs and parameters)
- PassThruReadVersion
- PassThruGetLastError
Note: Error codes and timing behavior must match exactly.
REFERENCE PACKAGE (PROVIDED AS A ZIP ATTACHMENT)
A single ZIP will be provided containing the complete original LPC-based project:
- original firmware .bin
- schematics/diagrams
- PCB/PCD files
- Windows release package materials (installer/driver payload) as reference for compatibility validation
NOTE ON LARGE FILES
- If attachments exceed platform limits, we will provide secure download links inside a small README text file (Gerber package and Windows release package can be split).
COST TARGET (THE MAIN PURPOSE)
- The selected chips/components (MCU + CAN/K-Line transceivers/interfaces + USB related parts + required drivers/protection parts) must provide the same function but at lower cost.
- The contractor must clearly explain every replacement: original part/function → proposed cheaper equivalent (part name, role, and cost target).
REQUIRED DELIVERABLES (MANDATORY)
1) New PCB design package:
- Gerber files
- Schematics + diagrams
- BOM (parts list) + alternative equivalents list (for availability/cost)
- Pick&Place / CPL
- Manufacturing and test notes (including test points)
2) New MCU firmware:
- Full source code
- Build/compile instructions
- Programming/flashing method and production steps
- Implementation must match the original LPC behavior (analysis + port)
3) Compatibility & test evidence:
- Proof it works with OUR released Windows installer/driver package and PassThru tooling (logs/test outputs)
- CAN and K-Line tests (connect, read/write, filters, IOCTL, etc.)
- Stability proof (no freezes/disconnects during long runs)
WHEN APPLYING (MANDATORY)
- Total price quote
- Delivery time (days/weeks)
- Main chip list and cost target (MCU, CAN transceiver, K-Line transceiver/interface, USB related parts, etc.)
- Short execution plan (how compatibility will be verified)
- Same end-user functionality + same features + lower BOM cost by using cheaper equivalent components (same roles, validated performance).
MOST CRITICAL COMPATIBILITY REQUIREMENTS (MANDATORY)
- The device must remain compatible with OUR already-released Windows installer/driver package and PassThru tooling (no changes required on customer PCs who already use our released package).
- The device firmware/protocol behavior must match our released tooling expectations: command framing, timings, error codes, and state-machine behavior (bit-exact where required by the tooling).
- USB product behavior must remain compatible with our released Windows package (driver installation path, device enumeration, and user-visible device naming as defined by OUR released package). Any USB identifiers must be legally compliant and provided/owned by us (we will supply PID/VID allocation proof if applicable).
- We are not asking to spoof third-party USB IDs or impersonate another vendor’s product.
MECHANICAL / PCB SIZE REQUIREMENT (MANDATORY)
- PCB size must not change: 46.32 mm × 36.81 mm
- Same enclosure will be used.
- Mounting holes and connector physical locations must remain the same.
PROTOCOLS / FUNCTIONS (ALL MANDATORY)
All communication lines and supported protocols must work completely:
- CAN
- K-Line (ISO9141 / ISO14230)
- Any other J2534 protocols/features supported by OUR released tooling must behave exactly the same (no missing features).
J2534 FULL REQUIREMENT (NO MISSING FEATURES)
All J2534 functions used by OUR released PassThru tooling must work fully and correctly:
- PassThruOpen / PassThruClose
- PassThruConnect / PassThruDisconnect
- PassThruReadMsgs / PassThruWriteMsgs (including correct timeout behavior)
- PassThruStartMsgFilter / PassThruStopMsgFilter
- PassThruStartPeriodicMsg / PassThruStopPeriodicMsg
- PassThruIoctl (all required IOCTLs and parameters)
- PassThruReadVersion
- PassThruGetLastError
Note: Error codes and timing behavior must match exactly.
REFERENCE PACKAGE (PROVIDED AS A ZIP ATTACHMENT)
A single ZIP will be provided containing the complete original LPC-based project:
- original firmware .bin
- schematics/diagrams
- PCB/PCD files
- Windows release package materials (installer/driver payload) as reference for compatibility validation
NOTE ON LARGE FILES
- If attachments exceed platform limits, we will provide secure download links inside a small README text file (Gerber package and Windows release package can be split).
COST TARGET (THE MAIN PURPOSE)
- The selected chips/components (MCU + CAN/K-Line transceivers/interfaces + USB related parts + required drivers/protection parts) must provide the same function but at lower cost.
- The contractor must clearly explain every replacement: original part/function → proposed cheaper equivalent (part name, role, and cost target).
REQUIRED DELIVERABLES (MANDATORY)
1) New PCB design package:
- Gerber files
- Schematics + diagrams
- BOM (parts list) + alternative equivalents list (for availability/cost)
- Pick&Place / CPL
- Manufacturing and test notes (including test points)
2) New MCU firmware:
- Full source code
- Build/compile instructions
- Programming/flashing method and production steps
- Implementation must match the original LPC behavior (analysis + port)
3) Compatibility & test evidence:
- Proof it works with OUR released Windows installer/driver package and PassThru tooling (logs/test outputs)
- CAN and K-Line tests (connect, read/write, filters, IOCTL, etc.)
- Stability proof (no freezes/disconnects during long runs)
WHEN APPLYING (MANDATORY)
- Total price quote
- Delivery time (days/weeks)
- Main chip list and cost target (MCU, CAN transceiver, K-Line transceiver/interface, USB related parts, etc.)
- Short execution plan (how compatibility will be verified)