VSE_0000022_01 - Welcome to Scania Technical Information ...

VSE_0000022_01 - Welcome to Scania Technical Information ... VSE_0000022_01 - Welcome to Scania Technical Information ...

til.scania.com
from til.scania.com More from this publisher
01.05.2013 Views

FAQ © Scania CV AB 2012, Sweden VERA:17 Questions about VERA ECU update Issue 5 en Information owner: YSEC - IT Coordination YS products and systems, Scania CV AB

FAQ<br />

© <strong>Scania</strong> CV AB 2<strong>01</strong>2, Sweden<br />

VERA:17<br />

Questions about VERA ECU update<br />

Issue 5 en<br />

<strong>Information</strong> owner:<br />

YSEC - IT Coordination YS products and systems, <strong>Scania</strong> CV AB


Introduction<br />

Introduction<br />

The purpose of this document is <strong>to</strong> simplify troubleshooting problems with the<br />

VERA services. This document has been produced <strong>to</strong> help users and helpdesks at<br />

the distribu<strong>to</strong>rs and at <strong>Scania</strong> in Södertälje.<br />

For questions which are not answered here, please contact the helpdesk at your<br />

distribu<strong>to</strong>r, your SAIL coordina<strong>to</strong>r or use the FRAS fault reporting system<br />

depending on the type of question you have.<br />

The illustration below describes the support routes from workshop <strong>to</strong> the relevant<br />

department of <strong>Scania</strong> in Södertälje.<br />

FRAS<br />

SAIL<br />

1 Workshop<br />

2 Distribu<strong>to</strong>r helpdesk<br />

3 <strong>Scania</strong> in Södertälje with departments that handle 3.1 fault reports <strong>to</strong> FRAS,<br />

3.2 IT-related matters and 3.3 matters concerning SAIL<br />

The workshop always contacts the distribu<strong>to</strong>r’s helpdesk, which forwards the<br />

matter <strong>to</strong> <strong>Scania</strong> in Södertälje as necessary.<br />

2 © <strong>Scania</strong> CV AB 2<strong>01</strong>2, Sweden VERA:17


Questions about VERA ECU<br />

update when used with SDP3<br />

version 2.10 or earlier<br />

Question E1: How is an ECU update carried out?<br />

Answer: SDP3 contains general updating instructions and the Campaign and<br />

TI contain instructions specific <strong>to</strong> each update.<br />

Question E2: Why did the ECU update fail?<br />

Answer: Here are the most common reasons for an ECU update <strong>to</strong> fail:<br />

• No certificate.<br />

• The user does not have the right authority level (can be checked by<br />

trying <strong>to</strong> log in <strong>to</strong> VERA Operational Analysis).<br />

• The latest version of SDP3 is not being used.<br />

• The login details are incorrect (use SAIL login details).<br />

• Control unit in the vehicle is <strong>to</strong>o new.<br />

Questions about VERA ECU update<br />

• Communication error, i.e. Internet connection is interrupted. Check the<br />

proxy and authentication.<br />

If the update failure is not caused by one of the above, create a fault report in<br />

FRAS and attach the log files from SDP3.<br />

VERA:17 © <strong>Scania</strong> CV AB 2<strong>01</strong>2, Sweden 3


Questions about VERA ECU update<br />

Question E3: What should I do if downloading is interrupted?<br />

Answer: Try again. If downloading is interrupted again, create a fault report<br />

in FRAS and attach the log files from SDP3.<br />

Question E4: I get the error message that the vehicle is not covered by the<br />

campaign. Why is that?<br />

Answer: Check with your distribu<strong>to</strong>r that the vehicle is affected by the<br />

campaign.<br />

Question E5: Will any communication errors while I’m downloading<br />

software from <strong>Scania</strong> in Södertälje result in any damage?<br />

Answer: No, the update can be restarted if downloading is interrupted due <strong>to</strong><br />

a communication error.<br />

4 © <strong>Scania</strong> CV AB 2<strong>01</strong>2, Sweden VERA:17


Question E6: Is there some way of testing that my connection <strong>to</strong> <strong>Scania</strong>’s<br />

server is working?<br />

Answer:<br />

1 Start SDP3.<br />

2 Start demo mode and use the demo file<br />

TRUCK_YS2R6X20002<strong>01</strong>7813.txt.<br />

3 Start the job type ECU update.<br />

4 Start the update in the usual way.<br />

5 Enter your SAIL login details.<br />

6 The first stage, reading operational data, will fail since you are running<br />

in demo mode. Click Cancel when the first message is displayed and OK<br />

at the second message.<br />

7 After reading operational data, enter the number for ECU update<br />

1100<strong>01</strong>.<br />

8 If communication is working, a progress bar will be displayed and the<br />

software will be downloaded.<br />

9 Click Cancel and exit the work option.<br />

Question E7: Reading operational data failed. Can I continue with the ECU<br />

update?<br />

Answer: Yes, you can continue.<br />

Questions about VERA ECU update<br />

VERA:17 © <strong>Scania</strong> CV AB 2<strong>01</strong>2, Sweden 5


Questions about VERA ECU update<br />

Questions about VERA ECU<br />

update when used with SDP3<br />

version 2.11 or later<br />

Question E1: How is an ECU update carried out?<br />

Answer: <strong>Scania</strong> sets conditions specifying which control units are covered by<br />

an update. When the vehicle or industrial and marine engine is connected <strong>to</strong><br />

SDP3, these control units are compared with the conditions <strong>Scania</strong> has set<br />

and any updates are displayed in SDP3. The user can choose whether <strong>to</strong><br />

perform the software update or not.<br />

Question E2: Why did the ECU update fail?<br />

Answer: Here are the most common reasons for an ECU update <strong>to</strong> fail:<br />

• No certificate.<br />

• The user does not have the right authority level (can be checked by<br />

trying <strong>to</strong> log in <strong>to</strong> VERA Operational Analysis).<br />

• The latest version of SDP3 is not being used.<br />

• The login details are incorrect (use SAIL login details).<br />

• Communication error, i.e. Internet connection is interrupted. Check the<br />

proxy and authentication.<br />

If the update failure is not caused by one of the above, create a fault report in<br />

FRAS and attach the log files from SDP3.<br />

6 © <strong>Scania</strong> CV AB 2<strong>01</strong>2, Sweden VERA:17


Question E3: What should I do if downloading is interrupted?<br />

Answer: Try again. If downloading is interrupted again, create a fault report<br />

in FRAS and attach the log files from SDP3.<br />

Question E4: Will any communication errors while I’m downloading<br />

software from <strong>Scania</strong> in Södertälje result in any damage?<br />

Answer: No, the update can be restarted if downloading is interrupted due <strong>to</strong><br />

a communication error.<br />

Question E5: Is there some way of testing that my connection <strong>to</strong> <strong>Scania</strong> is<br />

working?<br />

Answer:<br />

1 Start SDP3.<br />

2 Start demo mode and use a demo file.<br />

3 Start the job type ECU update.<br />

4 Start the update in the usual way.<br />

5 Enter your SAIL login details.<br />

If you can log in with SDP3, the connection <strong>to</strong> <strong>Scania</strong> is working.<br />

6 Cancel at the first opportunity if you only want <strong>to</strong> test the connection <strong>to</strong><br />

<strong>Scania</strong>.<br />

Questions about VERA ECU update<br />

VERA:17 © <strong>Scania</strong> CV AB 2<strong>01</strong>2, Sweden 7


Questions about VERA ECU update<br />

Question E6: Is it possible <strong>to</strong> find out in advance whether an ECU update is<br />

available for a vehicle or industrial and marine engine before it is brought in<br />

for maintenance?<br />

Answer: In the VERA Conversion <strong>to</strong>ol (accessed via VERA under<br />

Applications at Sail.scania.com) there is an option <strong>to</strong> enter the serial number<br />

of the vehicle/engine (chassis or engine serial number) and product type.<br />

Then a list of the software updates that apply <strong>to</strong> the vehicle/engine control<br />

units is displayed. You can obtain more information from the document<br />

VERA Conversion – User instructions (VERA:04) which is published in the<br />

<strong>Technical</strong> <strong>Information</strong> Library.<br />

Question E7: Why does SDP3 indicate that spare parts programming needs<br />

<strong>to</strong> be performed on the vehicle or industrial and marine engine?<br />

Answer: If the control units of the vehicle or industrial and marine engine do<br />

not correspond <strong>to</strong> the specification (SOPS file), spare parts programming<br />

must be performed. Spare parts programming ensures that the SOPS file is<br />

updated with new information.<br />

Question E8: Why must spare parts programming be carried out on my<br />

<strong>Scania</strong> Communica<strong>to</strong>r 200?<br />

Answer: <strong>Scania</strong> Communica<strong>to</strong>r 200 can be updated remotely via the GSM<br />

network. Even if the control unit on <strong>Scania</strong> Communica<strong>to</strong>r 200 has been<br />

updated remotely, the vehicle's SOPS file will not have been updated. To<br />

update the vehicle specification, spare parts programming must be performed<br />

with SDP3.<br />

8 © <strong>Scania</strong> CV AB 2<strong>01</strong>2, Sweden VERA:17

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!