HELP ME.

• For the tune itself (fuel, ignition, VTEC engagement point, rev limiter etc.) the calibration lives in the SH7058. That's the core you care about for a normal Stage 1 style map.
• The SH72531 on these usually handles secondary functions and generally isn't where you edit VTEC. So reading only the SH7058 is often enough to get your working BIN.
• Before you write anything, pull a full read of the SH7058 and save at least two backup copies of the original untouched dump.

• Exact vehicle — model, year, engine code (the RSP part points to a K-series, but confirm which car/engine).
• What the tool actually offers in its menu for that ECU — a screenshot of the SmPro protocol/ECU selection screen would tell us a lot.
• Are you reading on-bench (boot mode) or through OBD?
• Can it complete a read of the SH7058 right now, or does it error out?

Gemini said:

That reading looks normal actually — let me explain what's going on.

A 37820-RSP part number on a Keihin Honda ECU is a dual-core setup: the SH7058 is the main engine control MCU and the SH72531 is a secondary/sub processor. On most read tools you only address and dump one core at a time. The fact that your tool identifies the SH7058 but doesn't auto-list the SH72531 doesn't mean anything is broken — many clone Scanmatik-type interfaces only expose the primary SH7058 map/flash routine, and the SH72531 is either read separately or not covered at all in that tool's protocol list.

So a few practical points first:

• For the tune itself (fuel, ignition, VTEC engagement point, rev limiter etc.) the calibration lives in the SH7058. That's the core you care about for a normal Stage 1 style map.
• The SH72531 on these usually handles secondary functions and generally isn't where you edit VTEC. So reading only the SH7058 is often enough to get your working BIN.
• Before you write anything, pull a full read of the SH7058 and save at least two backup copies of the original untouched dump.

To give you the exact next step I need a bit more detail:

• Exact vehicle — model, year, engine code (the RSP part points to a K-series, but confirm which car/engine).
• What the tool actually offers in its menu for that ECU — a screenshot of the SmPro protocol/ECU selection screen would tell us a lot.
• Are you reading on-bench (boot mode) or through OBD?
• Can it complete a read of the SH7058 right now, or does it error out?

Post the screenshot of the tool's ECU selection and the read result and we can tell you whether you're good to proceed. Also — clone SmPro units are hit-or-miss on write, so I'd strongly suggest confirming a clean read first before you ever attempt a flash.

Click to expand...

• Exact car, year and engine code (the RSP number points to a K-series, but confirm which one you have).
• A screenshot of what the SmPro menu offers for that ECU — the protocol/ECU selection screen.
• Are you reading on-bench (boot mode) or through OBD?
• Can it complete a full read of the SH7058 right now, or does it stall/error partway?

• BIN = the raw dump you read out of the ECU.
• XDF = the definition/map file for TunerPro. It tells TunerPro where VTEC, fuel, ignition, rev limiter etc. live inside that BIN. There's no separate "definition file" step beyond the XDF — the XDF is the definition.

• Connect to the car and attempt a full read of the SH7058 over OBD. Don't write anything yet.
• Save at least two copies of that original dump somewhere safe. That untouched BIN is your recovery file if a write ever goes wrong.
• Tell me whether the read completes 100% or errors/stalls partway, and what file size it produces.

Gemini said:

Sounds good, no rush — do the read tomorrow when you've got time, and remember two safe copies of that original dump before anything else.

Post back whenever you're ready with the rest of your questions.

Click to expand...

Roche said:

I have a abs sensor error I did a scan the car with a diagnostic tool and checked the live data s...

Click to expand...

• The yaw/G-sensor on these is a combined yaw-rate + lateral-G unit (often called the VSA sensor). If it logs an internal fault, no calibration or cleaning fixes it — but confirm with the code first.
• After any work that disturbs it, or sometimes just after a battery disconnect, the VSA sensor needs a neutral position memorization (sensor calibration). If that's never been done, the module can drop into limp with the lights on even though the sensor is physically fine.
• Steering angle sensor and the yaw unit talk to each other — a steering angle fault can look like a stability fault.

• Exact DTC(s) from the VSA module.
• Which diagnostic tool you scanned with (does it support VSA/ABS actuation and the yaw sensor calibration/neutralize function?).
• Any recent work before this started — battery change, wheel/suspension/alignment, accident?