Uploaded by No Name

releasenotes cs CZ(1)

advertisement
Release Notes
ODIS Service Release 4.1.1
Release Notes
ODIS Service Release 4.1.1
Status: 20.02.2017
Page 1 of 8
Release Notes
ODIS Service Release 4.1.1
Table of content
1.
Version information ........................................................................................................... 3
1.1 ODIS Service ................................................................................................................. 3
1.2 HardwareInfo.exe........................................................................................................ 3
1.3 Diagnostic data packets .............................................................................................. 3
2. New implemented features .................................................................................................. 4
3. New features inherited from ODIS Engineering ................................................................. 5
4. Fixed errors ............................................................................................................................ 6
5. Known limitations ................................................................................................................. 7
6. Supported vehicle projects ................................................................................................... 8
Help yourself
Status: 20.02.2017
Page 2 of 8
Release Notes
ODIS Service Release 4.1.1
1. Version information
1.1
ODIS Service
Current release 4.1.1: DCM-package in version 4.41.2 (RC398R)
1.2
HardwareInfo.exe
Version HardwareInfo.exe: V0.52.536
The HardwareInfo.exe is available in eShop.
1.3
Diagnostic data packets
The ECF version 31.1.0 is implemented. More details are described in the release notes of ECF
and the VW I-graduate-scheme.
Status: 20.02.2017
Page 3 of 8
Release Notes
ODIS Service Release 4.1.1
2. New implemented features
In ODIS Service 4.1.0 (RC396R) following new features are implemented:
Work package
Specifications reference
LP520
CCB 1934 - 5 new CU-requests for the GFS
LP521
CCB 996 – The readout from ECU-ident-data in the diagnostic entrance have to be
optimized in order to save time
LP522
CCB 1786 – In the diagnostic entrance step „identification“ (Bus master identification), the
link-check “3E 00” (Testerpresent with ECU reply) should be discontinued
LP523
CCB 1886 – Consideration of restart by update
LP524
CCB 1891 – Not entirely diagnosed ECUs should considered as plugged
LP525
CCB 942 – Implementation of an attribute for unauthorized DTC memory, in order to
steer the test plan while diagnostic entrance and diagnostic exit.
In ODIS Service 4.1.1 (RC398R) following new features are implemented:
Work package
Specifications reference
LP526
CCB 1834
OD: automatic selection of hardware key
LP527
CCB 1855
values
OD: Select list for possible ECU replies by using replacement
LP528
CCB 1957
Dialog „configure test execution“
CR QC18628
Logging of suppressed flash-error-messages for not fulfilled “Layer-Refs”
(see IGfsUi.lockUI(true))
CR
DTC exclusions in TBL – respectively the estimation
CR
Adjusting ODIS Debug Build scripts - Another OD product in build scripts.
Separating VW and T-Systems build
CR
Hyphen in setup dialogue VAS 6154
CR QC19116
Consideration of 4-digit diagnostic addresses in EcuInformationData
CR
Removal CCB 996
Status: 20.02.2017
Page 4 of 8
Release Notes
ODIS Service Release 4.1.1
3. New features inherited from ODIS Engineering
In ODIS Service 4.1.0 (RC396R) following new features from ODIS Engineering are taken over:
Work package
Specifications reference
CCB1589
Supporting of new VW-cross-section-specifications-sheets
Jira-708
DTC OBD – „Clear“ without function - 0001 Engine ECU
Jira-738
Output Diagnostic Test Mode / Basic Setting: Behaviour by selection of vehicle
overall measured values
Jira-761
Set focus by activating of the Coding-result-view
Jira-773
Determining of activation status from the button “Select” in the dialog “Specify VCI”
In ODIS Service 4.1.1 (RC398R) following new features from ODIS Engineering are taken over:
Work package
Specifications reference
Jira-773
Determining of activation status from the button “Select” in the dialog “Specify VCI”
Jira-775
Plain text coding: Input values set will be reset by loading of subsystems
Jira-822
Goodwill: Clearing of filter adjustment by changing of the OBD mode
Status: 20.02.2017
Page 5 of 8
Release Notes
ODIS Service Release 4.1.1
4. Fixed errors
In ODIS Service 4.1.1 (RC398R) following errors are fixed:
Defect ID
16858
18289
18419
18439
18719
18781
18874
18886
18969
19013
19036
19054
19082
19118
Summary
Update OS 2.2.4: VAS 6558-6558A: After an Update ODIS is listed 2 times in „Programs and
Features“
D-PDU-API synchronization error by “TesterPresent” while “Response Pending”
ODIS Service: NullPointerException by ECF-Job execution
(ECF_OPEN_LOGICAL_LINK_FAILED) (PM0054)
ODIS Service shoes inconsistent connection status (Vehicle crossed, ignition on)
Archiving LOG file (CCB_DS_878): No 20 files in the directory
Stress test: ignition is not visible
FB_2016.16.00_105.33.0_ODIS Service 3.1.3 in the diagnostic protocol the "technical"
version information of the GFS Data is missing
After changing the connection type, ODIS Service doesn’t show the Bluetooth connection
symbol
OS 3.1.3 Standard dialog by communication errors party not translated
OS 4.0.0 B40/4 FBT: "ODS4009E"-Error while diagnostic entrance – sporadic
After leaving of the diagnostic session through the function „Stop“  „without saving“, the
ignition status was not displayed correctly
OS 4.0.0 – In the diagnostic protocol of older vehicles, a drop-down menu for subsystems is
shown although no subsystems where present
Error ODS 4009E appears immediately after starting ODIS
The high current analysis doesn’t work: Exception while notifying diagnostic entrance
listeners
Status: 20.02.2017
Page 6 of 8
Release Notes
ODIS Service Release 4.1.1
5. Known limitations
Status
Limitation
Valid
CCB921 – configuration tool for WLAN-VAS 6154 in ODIS
The change from infrastructure mode into access point mode needs
manual intervention. The automatic change by using the button on the
VAS 6154 works.
Valid
With ECF 30.0.0 the simulated diagnostic entrance is no longer available.
Valid
CCB1771
Because of an error (QC17608) the function could be tested finally.
Valid
CCB1692
Provision of ECF with extended callback for the WLAN-connection strength
is missing (B40:03). In agreement with the VW product management the
delivery will be executed nevertheless. A part of the graphics is displayed
different, as shown in the requirements specification.
Valid
The connection between ODIS Service and the test automatization will get
lost by working without measuring technology or without measuring
technology simulation and by suppression of substitute value input or not
existing substitute value input.
Done (Retreat CCB
996 with 4.1.1)
CCB996
To the used job "ReadECUIdentificationUDS" the ECF delivers always the
value “FALSE” for the value isAcknowledged() in the response. There are
already questions about this to ECF in JIRA-770. Because the answers are still
pending and the job delivers correct values, the Flag isAcknowledged() will be
ignored by the job.
Done 4.1.1
CCB 1886
The identification of the response values from third party components is
working. Certainly the rollback isn’t working correctly after an error occurs.
The D-PDU API will not be uninstalled automatically in this case.
Status: 20.02.2017
Page 7 of 8
Release Notes
ODIS Service Release 4.1.1
6. Supported vehicle projects
Approved AUDI models
- All AUDI models are supported.
Approved Volkswagen models
- All Volkswagen models are supported.
Approved Volkswagen Commercial Vehicle models
- All Volkswagen Commercial Vehicle models are supported.
- Only immobilizer components can be diagnosed with the LT2.
Approved Seat models
- All Seat models are supported.
Approved Skoda models
- All Skoda models are supported.
Approved Bentley models
- All Bentley models are supported.
Approved Lamborghini models
- Only following Lamborghini models are supported:
o Gallardo from MY09-MY14 (Only immobilizer components and Radio PIN
Code)
o Aventador
o Huracán
Approved Lamborghini models
- The Bugatti Veyron and the Bugatti Chiron are supported
Approved MAN models
- The MAN Crafter is supported
Status: 20.02.2017
Page 8 of 8
Download