Possibly BAD battery??
03-09-2021, 08:46 AM
#51
New Members
Thread Starter
Yes Sean, I used INPA to read/clear errors. All other modules are OK except for these two modules, hence I posted only those two. I havent read detailed error report. Will try to turn the wheel lock to lock after starting the car tonight as Josh suggested and if the error still persists, will do a detailed error report and post it for reference.
03-09-2021, 05:45 PM
#54
New Members
Thread Starter
Ok, came home, started the car, all DSC related lights came on, drove it out of the garage and truned the steering wheel lock to lock and they all went away. Set date/time and it still had increased battery discharge warning, probably because of me using INPA and checking other stuff while the car is ON without engine running yesterday. Drove around the block with no issues, drove into the garage and turned off the car and turned ignition ON and the battery warning disappeared. Battery voltage is at 12.10V while it was at 12.11V yesterday when I locked the car. So, looks fine to me so far. Will use it regularly and report back if I find something off.
Thanks for everyone who has chipped in with tips/suggestions. Next on the list is to find someone to update my CIC and if anyone here is willing to do this, will pay for the work. I have all the hardware needed to do it but was unable to even start doing the update and spent many hours trying to resolve this.
Thanks for everyone who has chipped in with tips/suggestions. Next on the list is to find someone to update my CIC and if anyone here is willing to do this, will pay for the work. I have all the hardware needed to do it but was unable to even start doing the update and spent many hours trying to resolve this.
03-09-2021, 06:37 PM
#55
Super Moderator
Join Date: Jul 2011
Location: Augusta, GA
Posts: 3,599
Likes: 0
Received 311 Likes
on
298 Posts
My Ride: 05 530i M54
Model Year: 05 530i
Engine: 3.0 M54
So you have an ICOM to update through MOST. Is there an issue with it?
Last edited by seanjordan20; 03-09-2021 at 06:52 PM.
03-09-2021, 07:25 PM
#56
New Members
Thread Starter
The issue I am having is not being able to communicate with anything on MOST bus via ICOM-B. Everything works fine in Base mode which is what I use for INPA. But once I lock ICOM in MOST_ASYNC_ab625 using Easyconnect (after reserving the IP using Itoolradar) successfully, INPA fails to communicate with the car. Both LEDs turn Green on ICOM-B. I may be doing something fundamentally wrong or might be a simple thing, but I have spent hours trying to resolve it over the past year and gave up.
03-10-2021, 02:23 AM
#57
Super Moderator
Join Date: Jul 2011
Location: Augusta, GA
Posts: 3,599
Likes: 0
Received 311 Likes
on
298 Posts
My Ride: 05 530i M54
Model Year: 05 530i
Engine: 3.0 M54
You can't communicate with INPA after jumping to MOST. Your remote.ini should change. You can only have 1 port of communication. Either you want to work on INPA or WINKFP. Once you do the above you should be able to update through WINKFP. Once done close communication and restart ebidias and configure for INPA.
Also with 15a you are looking at failure. You need a minimum of 50a
Also with 15a you are looking at failure. You need a minimum of 50a
03-10-2021, 05:59 AM
#58
New Members
Thread Starter
As for my issues, I listed them over here
As soon as I open WinKFP, it shows proper Hardware Interface as REMOTE:MOST_ASYNC_ab625, but, every time it kept showing the following messages saying that an error occurred while setting ECU address as soon as I enter 63 for ECU address after selecting proper PABD and P-SGBD
[21:04:56.319] [2020-11-08] [<WinKFP Tool] 7017 PABD/CABD CI63F1 SetEcuAdr 820
[21:04:56.319] [2020-11-08] [<WinKFP Tool] ECU adresses are set - EDIABAS NET-failure (150…199) OPPS, STATUS_ROUTER: NET-0009: Timeout
[21:05:58.108] [2020-11-08] [<WinKFP Tool] 7017 Error COAPI2.CPP coapiRunCabd 6
[21:05:58.108] [2020-11-08] [<WinKFP Tool] ECU adresses are set - EDIABAS NET-failure (150…199) SET_ECU_ADDRESS
[21:05:58.141] [2020-11-08] [<WinKFP Tool] 7017 Error COAPIKF.CPP coapiKfSetGlobalPabdSgbdEcuAddr 5
[21:05:58.141] [2020-11-08] [<WinKFP Tool] ECU adresses are set - EDIABAS NET-failure (150…199) Run SET_ECU_ADDRESS Job
[21:04:56.319] [2020-11-08] [<WinKFP Tool] 7017 PABD/CABD CI63F1 SetEcuAdr 820
[21:04:56.319] [2020-11-08] [<WinKFP Tool] ECU adresses are set - EDIABAS NET-failure (150…199) OPPS, STATUS_ROUTER: NET-0009: Timeout
[21:05:58.108] [2020-11-08] [<WinKFP Tool] 7017 Error COAPI2.CPP coapiRunCabd 6
[21:05:58.108] [2020-11-08] [<WinKFP Tool] ECU adresses are set - EDIABAS NET-failure (150…199) SET_ECU_ADDRESS
[21:05:58.141] [2020-11-08] [<WinKFP Tool] 7017 Error COAPIKF.CPP coapiKfSetGlobalPabdSgbdEcuAddr 5
[21:05:58.141] [2020-11-08] [<WinKFP Tool] ECU adresses are set - EDIABAS NET-failure (150…199) Run SET_ECU_ADDRESS Job
03-10-2021, 08:34 AM
#60
New Members
Thread Starter
Sure, I guess that ini file changes based on the mode you select in EasyConnect utility. Will connect it again to the car tonight and set it up in MOST mode and link the copy of the ini file here.