Unfortunately we do not accept new members for free, Now Registration cost 30€, if you are interesting Send Email to [email protected]
ISTA 4.46.xx problems and possible solution
05-03-2024, 14:18 PM,
(This post was last modified: 04-04-2024, 04:09 AM by CATAHA.)
Post: #31
|
|||
|
|||
RE: ISTA 4.46.xx problems and possible solution
Maybe the answer is more simple
BMW AG preparing for NEW gen vehicles and starting to move it's software to new ways(DoIP with ICOM acting as a DHCP server for assignment of CAR_Client IP_ADDR) Windows 12/13/14~ 64bit Increasing security and making it more of an individual bases ( BASE on ISTAGUI.exe.config ) ENET = DoIP Base on those files REGSVR32.BAT Rplus.ini REMOTE.ini EDIABAS.INI CHECK EDIABAS.INI(attached) 4.45.x 4.46.x ( Answer as follows: Instead of using "Autodetect" use IP_Addr of an ICOM, because autodetect calls for ICOM DHCP assignment of an IP_addrs for DoIP protocol client(s) but when using direct IP_Addr config bypasses DoIP_DHCP_REQUEST procedures ) EXAMPLE(i haven't tested yet): 1. This activates DHCP on ICOM, increasing wait time for connection, this method is been used if multiple ICOM(s) use one computer (3:1 multiple_sessions ) Interface = ENET ; (DoIP, DHCP utilization via ICOM or DHCP_SERVER) RemoteHost = Autodetect 2. This does NOT activates DHCP on ICOM, decreasing wait time for connection, this method is been used if connecting directly to computer (1:1) Interface = REMOTE ; (Direct connect PC_TO_ICOM) RemoteHost = 169.254.1.169 ; (ICOM_IP_ADDRS) ;============================================================================= [XEthernet] ;============================================================================= RemoteHost = Autodetect VehicleProtocol = DoIP,HSFZ ; (Can be reversed HSFZ,DoIP ) DoipGatewayAddress = 0010 ; ------------------ Beispiele fester IP-Adressen ; RemoteHost = 169.254.1.1 ; RemoteHost = 192.168.100.1 HeaderFormat = 0 TesterAddress = F4,F5 DoIPTesterAddress = 0EF3 ;----------------------------------------------------------------------------- ; VehicleProtocol ; Description : Transport protocol for Ethernet communication ; Value : [HSFZ|DoIP|HSFZ,DoIP|DoIP,HSFZ] | [0|1|0,1|1,0] ; HSFZ or 0 : Set up HSFZ connection with ECU ; DoIP or 1 : Set up DoIP connection with ECU ; HSFZ, DoIP or DoIP,HSFZ or 0,1 or 1,0 : Use protocol where the ECU answered first ; Default = HSFZ ; VehicleProtocol = HSFZ,DoIP ;----------------------------------------------------------------------------- ; DoipGatewayAddress ; Description : Diagnostic Address of the Gateway ECU (only for DoIP Gateways!) ; If there are multiple DoIP Gateways available, DoipGatewayAddress will be used as filter ; If the defined Gateway address can't be found (or can be foud multiple times), the error message "INVALID BUS CONFIGURATION" will be displayed ; Value : two-digit hexadeciamal, without leading "0x": ; 0010 : The DoIP Gateway ECU with Diagnostic address 0x0010 (16 dez) will be used ; FFFF : Deactivates filtering with Gateway diagnostic address (with this setting on using configuration RemoteHost=Autodetect only one! DoIP gateway can be connected) ; Default = FFFF ; DoipGatewayAddress = 0010 ;----------------------------------------------------------------------------- ; VehicleIdentification ; Description : Value = 0: If RemoteHost != Autodetect, ENET driver uses HSFZ to contact target ECU on given IP address ; Value = 1: If RemoteHost != Autodetect, ENET driver uses DoIP to contact target ECU on given IP address ; Default = 0 ; VehicleIdentification = 0 ;----------------------------------------------------------------------------- My preview's observations When I installed and used ISTA on Win10 with Group Policy been adjusted i had to adjust both settings EDIABAS.INI 1. [Configuration] 2. [TCP] When I used on Win10 without Group Policy been adjusted EDIABAS.INI 1 [Configuration] (ONLY) (05-03-2024, 08:32 AM)sebastianfernandes Wrote: Thanks to @sedoy and @bugfix to pointing out in the right direction, and Here is fix for this mess. I have edited ediabas.ini in both ista and ediabas. With this my ista works perfect and also INPA/tool32/etc. Copy both to respective ediabas location and ista location, assuming ediabas is installed in c:\ediabas, because .ini file is edited according to that. Also make sure you delete entry in SYSTEM VARIABLE ediabas_config_dir. |