IPMA - Image Processing Module A
Part number: H1BT-19H406-BG
Calibration level: H1BT-19H406-BG (latest known: N1BT-19H406-BA)
Strategy : JX7T-14F397-AH
Calibration: H1BT-14F398-AG
By information found online it should -Bx model should support:
LDW, LKA, DAS, AHB, TSR, WWA
While almost all the features are enabled by factory, Wrong Way Assist is disabled and gives configuration error when I write to the module using forscan.
Is it too early hardware? Or should I try firmware update, since it is available?
Probably. Firmware update would be a good bet. IPMA is reported to be a little finicky, so take your time. You will need to run a calibration after the firmware update.
Some of the IPMAs are so temperamental that any attempt to change the config/firmware triggers off a missing calibration DTC.
That even includes backing up the current config with ForScan and putting it back in without any changes.
And that’s what you’re getting wrong, there is no missing calibration DTC. It’s a popup that forscan throws while writing to the module (around 50%, probably because here there’s the block for the wwa function). And by throwing this error it doesn’t write to the ipma any new or old data.
When I have some time to spare I will try to update the firmware, since it’s available and it seems like the only possible issue here
I didn’t say you had a DTC.
I said that some versions of the IPMA are so finicky that ANY attempt to change config or update the calibration/firmware will throw a missing calibration DTC.
That would include a failed attempt.
ForScan 2.4.x now has an option drop down to kill all communication on the bus from other modules, you may need to change that.
Updated the IPMA module, update successfull.
Now I got DTC for U2100. Noticed that there is a problem with as built…
706-04-01 is now set at 0000-03C3-4018
my saved values are FFFC-27C3-4037
Writing to the module ok but the error keeps popping up, when I reload AB from the module it reverts to 0000-03C3-4018
You need to run the module calibration procedure, it can be done with ForScan.
You’ll need a road that’s decently straight with well marked lines that you can drive on at a set speed of 50-60mph for a mile.
While the existing config and calibration is saved using ForScan you can’t write the calibration back.
I ran the procedure twice… I’ll try again.
Just one thing maybe I didn’t understand:
when the bar reaches 100% it doesn’t end the procedure or pop up anything… is this the normal behaviour?
I guess it is normal since it says
Luckily, I had one-day access to FDRS and used it to run the Programmable Module Installation for the IPMA—problem solved in 30 seconds.
Side note: I noticed a lot of the updates shown in FORScan aren’t actually available in FDRS. I just installed the ones that were in fdrs, and called it a day.
With IDS and FDRS you’ll also see that some updates have other module pre-reqs that ForScan doesn’t show.
ForScan isn’t perfect for flashing every module on every model by a long shot.
This wasn’t my case, but I noticed for example, since I retrofitted front pdc forscan correctly reads the new PAM since it scans the can netwotk while fdrs from my understaning reads only this data from the vin since it still show the old PAM (the model that manages only rear pdc)
