Automotive and Embedded Networks

cancel
Showing results for 
Search instead for 
Did you mean: 

ADCS UDS RoutineControl VI

Solved!
Go to solution

Hello Experts,

                   I am using ADCS for the automation of the diagonositc of our ECU, I have implemented read data byID, write data by ID and many more. But geeting some problem in Routine control implementation.

                  

                   Even though That VI gives no error at all, but i am also not reciving the sucess true or false(Normally in other VIs we recive positive response then the error is not there and if we recive the negative response the error cluster shows error).

                    the code which is assigned and error is cleared is -8270. what can be the reason for the same.

A kind help will be apprecited and thanks in advance.

 

Regards

 Harry

 

0 Kudos
Message 1 of 9
(10,476 Views)

The error code means that a response was received, but could not be correctly interpreted as positive response to the command sent. You might try running the Diagnostic Monitor.vi example alongside with your application; this hooks into the diagnostic communication and displays the CAN frames exchanged. Maybe you can take a look at them (or post them here, so that we can take a look) and let us know what you saw?

 

Christian

 

0 Kudos
Message 2 of 9
(10,473 Views)

Hi there,

 Thanks for the quick reposnse, here is the simple VI which i am using in my automation. one question more.

0 Kudos
Message 3 of 9
(10,469 Views)

I noticed in passing that there is a bug in the implementation of the UDS Routine Control.vi of the ADCS. This bug will be fixed in the next version of the ADCS (scheduled for Q1/2010). As a workaround, you can fix it easily yourself:

 

1. Open the block diagram of UDS Routine Control.vi.

 

2. At the very bottom of the diagram, there is a Delete from Array block, which has constants of 2 and 0 wired to the length and index inputs. Change the constant 2 wired to length to 4.

 

3. Save the VI.

 

That's all. After that, the Routine Control VI should behave correctly.

 

Christian

0 Kudos
Message 4 of 9
(10,455 Views)

We can offer you a Beta Version of the Automotive Diagnostic Command Set 1.0.3 which contains this bugfix.

If you are interested please contact canpse@ni.com

 

Thanks a lot

Message Edited by Gibson on 12-01-2009 09:33 AM
0 Kudos
Message 5 of 9
(10,452 Views)
Solution
Accepted by topic author harjeemann

Hello All,

       I find the error and i was passing a value to the DATA in terminal as a array of 0; which should not be the case in our ECU, My fault but good to know about all this.

regards

Harry

0 Kudos
Message 6 of 9
(10,427 Views)

I did want to let the community know that the issue concerning the issue with the UDS Routine Control.vi of the ADCS has been documented on Corrective Action Request (CAR) ID: 201320.

 

This issue has been resolved in the latest version of the NI Automotive Diagnostic Command Set.

 

Thanks

Sarah S.
Applications Engineering
National Instruments
0 Kudos
Message 7 of 9
(10,246 Views)

I am also using ADCs toolkit to implement ECU program brushing.I would like to know how to use service 34 and 36, and what format should be used for the uploaded data .I have finished pre-programming and post-programming, but I don't know how to upload the data in the programming stage. Can I refer to your program, if that's convenient?

0 Kudos
Message 8 of 9
(2,990 Views)
0 Kudos
Message 9 of 9
(2,982 Views)