I have BMW E9X models, I really want to code Angel Eyes as DRL in FRM3,
increase Angel Eye brightness, and mirror fold on lock/unfold on unlocking.
- ISTA-D NCSexpert for BMW E9X models
Just completed my first coding job with NCSexpert! I turned on my angel eyes as DRL instead of the high beams.
As I learn more about NCSexpert, I plan on coding the mirror folding on lock/unlock, increasing the voltage to the angel eyes so they can be (better) seen in daylight, and other cool shit.
Also, I found out that my 2011 328i has FRM3. Coding wise it’s the same steps as coding for FRM2.
Source of downloading ISTA D
PS: you can try at your own risk.
Tested version ISTA D:
https://www.eobdtool.co.uk/wholesale/newest-bmw-icom-software-hdd.html (NCS Expert 3.5.1)
Q: Can the current K+DCAN cables be used with ISTA D?
A: Yes. You need ICOM for ISTA/P and I’d recommend it for any flashing/programming on the MOST ring.
Q:Does ISTA D but heads with INPA on the same machine?
A: Not at all. I have them both installed on a couple different laptops and there’s no conflicts.
- The basic diagnostic tools in INPA for E9x models:
1) Functional Jobs: (a) see ID of ALL modules in vehicle; (b) read any Fault Codes saved in ANY of those modules, all in 2 minutes from connecting to OBD II Socket.
2) Connect to each individual Module (DME, JBE, EKP, CAS, IHKA, etc.) to: (a) get more specific info on any fault codes saved there, (b) to see Memory History, (c) read Freeze Frame or Infospeicher Data, (d) Clear Codes, (e) “Read Status” (Status Lesen) of real-time function of components such as fuel pump, coolant pump, IHKA flap positions, Radiator Fan, switch positions, temperatures, voltages, sensor inputs to the module, etc. (f) Activations (Steuern) which allow you to test operation of motors, injectors, etc. by keyboard entries rather than having to patch into a circuit.
For example, you can run radiator fan, coolant pump, fuel pump at various speeds and monitor temperatures or pressures associated with that component at the same time, such as monitoring (i) Engine Coolant Temp Sensor signal (coolant temp at top radiator), (ii) Radiator Outlet Temp Sensor signal (lower temp of coolant at bottom radiator hose) while you (iii) manually control Radiator Fan Speed, and you see all three on a screen with three bar graphs.
INPA is a diagnostic tool for monitoring/assessing function of components, in addition to simply reading Fault Codes, their definitions, and the conditions under which those codes were set (as well as mileage at the time). What INPA does NOT do is give you precise engineering data on the algorithms used by a module to set a particular code. It DOES tell you whether the code is currently present, and whether it would light the SES or other warning light.
I haven’t seen ANY guides that List all the things you can do with INPA on an E9x, so I’m making my own, but it takes a LOT of time. My approach is to do a ScreenPrint (Shft+PrtSc) and then paste it to “Paint” and SaveAs jpg in a folder for the particular Module connected to, or “Functional Jobs” which is really the starting point. Then I am using an online translator to try to get a “technically-correct” English translation of the German, and entering the English in a Word outline that summarizes the functional capability of each screen.
When diagnosing faults in a system, it is also helpful to keep an electronic record of the faults and screen prints of any analog readouts related to the system, or even just baseline analog readouts saved when the system was operating properly, so I use the same jpg files saved in folders by Module for future reference (history of this particular vehicle). You CAN of course Print/Druck (F9) any screen, but I prefer to go paperless. If anyone has developed a way to Print to file or save a screen without having to paste to a program such as “Paint,” please advise.
The starting point would be “Functional Jobs” in which you can get a readout (in ~ 1 minute after connecting to the OBD II Socket) of ANY Fault Codes saved in ANY of the ~20+ modules of your particular vehicle. You simply select “Functional Jobs” in the Right-hand List Box and from the Main Menu (HauptMenu) select F4 (Error Memory or FehlerSpeicher) and then F1 (Read Error Memory/FehlerSpeicher Lesen).
If anyone reading this has a link or cite to ANY existing summary or outline of INPA functions, please advise.
If anyone reading this would like to share in developing such an outline, in pdf format for example, and has time to contribute, a group of interested Forum members could probably create something before our cars become obsolete.