There is a way to find out if the serial interface, for example COM1, has been taken, but it is not possible to find out what programme has taken the interface.
Here, it is important that you only run winmsd if the Ediabas server is closed. Start Inpa using Inpaload. IPO to start the general reworking programme.
This corresponds to calling Inpaload. Prerequisite: The appropriate driver must be installed for the interface that you want to use. You only have to make the appropriate change to the line where the interface is entered. PDF for this. If the OBD. In the configuration menu, select Ediabas. There, you will find the desired information in the interface line.
However, you can also check in the Ediabas. Reason: No registry entries are made during the installation. The can be recognised by the yellow E in the task bar. This can be recognised by the green E in the task bar. The controller description files SGBD contain the controller-specific know-how. Each SGBD contains the order telegram of the respective controller and decodes its reply telegrams.
In the process, the raw data bytes is converted into directly useable variables Data types: int, long, real, string , i. For each controller variation, there is exactly one variation-specific SGBD. The file name of the SGBD without extension is the name with which the application programme addresses a controller variation or controller group.
There will be a list of all SGBDs by name with the current version number, the person responsible at BMW, and the name of the associated controller. Each job has a fixed name and any number of results. Jobs are independent of each other. There is no data exchange between jobs. A job corresponds to a function with one complete order. It usually reads data from a controller, analyses it and returns results that can be used directly by different applications.
A job normally works with one diagnostics telegram multiple in exceptional cases. These SGBDs are not used in production or in customer service. The group identifies the controller and starts the corresponding SGBD. The choice is made using the diagnostics, and as of E65 using the variation index in addition. Updating the group files as of the E65 has changed since February The table with the information about which controller must load which SGBD, depending on the diagnostics and variation index, was moved from the group file to an external table.
Reinhold Drexel, TI b What is it used for? Identification of the controller c When does it change? When a new SGBD is due 4. Data handling team b What is it used for? Identification of the ECU c When does it change? Normally, no changes must be made here after the installation.
One reason for a change to Ediabas. The Ediabas. If is set, then the maximum size of the file is 1 MB; for , it is a maximum of KB. ApiTrace: The ApiTrace file is activated by replacing the zero with a number from 1 to 7. The api. You can find information about the trace level in the Ediabas documentation. IfhTrace: The lfhTrace file is activated by replacing the zero with a number from 1 to 3.
The ifh. This function is activated by changing the zero to 1. Interface: You can directly change the interface here. The prerequisite is to have the appropriate driver installed for the interface. Excerpt form the Ediabas. There is one simulation file for each ECU. There is also a separate simulation file for each interface that is to be simulated.
The interface-specific return values are in the interface simulation files. The message that COM1 is already taken can be ignored in this case. Reason 1: ODB has actually been set as the interface in Ediabas.
Then, the entries in Tool Solution 2: Enter the interface that is being used in Tool You can activate the simulation mode e.
Notice, if you want to use the simulation mode, a simulation file for the interface will have to exist in the simulation path. Reason 1: In the Ediabas. However, you have connected an OBD connector. Solution 1: Modify the interface setting. Reason 2: The ignition is switched off.
Solution 2: Switch the ignition on. Reason 2: This error occurs if the EcuPath in Ediabas. Solution 2: Set the correct path. Reason: The old version msflxgrd. Solution: msflxgrd. Reason: The Tool Set was started twice in a very short period of time. Solution: Close all Tool Set processes that are running and start the Tool Set again with only one double-click. That design was improved upon by the UART chip. The serial port driver can program it to generate an interrupt at a particular fill level, thus reducing the interrupt rate as well.
But chips designs have the same kind of problem that software has, the original had a bug in the FIFO implementation. Fixed in the A, version 1. Problem was, the driver could not tell whether the machine had the buggy version of the or a good one. Simple chips like that don't have a GetVersion equivalent.
So it provided a property page that lets the user turn the FIFO support off, thus bypassing the bug. The odds that today you'll have the buggy version are zero. Turning the FIFO off is no longer necessary. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 7 years, 11 months ago. Active 5 years, 5 months ago.
0コメント