autosar: how to create some/ip configuration - etas.com · question o ethernet supports the service...

2018-06-28 © ETAS GmbH 2018. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights.

AUTOSAR: How to create SOME/IP configuration

Question

o Ethernet supports the service oriented communication through Service Oriented Middleware over Internet Protocol (SOME/IP) o How to create an AUTOSAR SOME-IP configuration in ISOLAR-A?

Answer

Basic information

o Configuring SOME-IP means configuring the following 3 elements: o Generic Ethernet o Socket Adapter o Service Discovery ("SOMEIP-SD")

o Generic Ethernet configuration o This involves the basic configuration of communication elements like Signals, PDUs, ECUs & Ethernet network information o This is "just signal oriented communication using the Ethernet network"

o Socket Adapter configuration o Socket Adapter connects the AUTOSAR PDU layer to the underlying Ethernet layer through Sockets o "It will act as a multiplexer or de-multiplexer" o Create IP table (IP & port configuration) o Create server port o Assign client port o Add PDUs to client/server port ("Map a PDU to the client port or to the server port")

o Service Discovery ("SOMEIP-SD") configuration o SOME-IP Service Discovery modules enable the service oriented communication o Create Provider/Server Services o Create Event Handlers and Map Routing Groups o Add Consumers for the Providers and Map Routing Groups


Step-by-step guide

Create a new AUTOSAR project 1. In ISOLAR-A → Menu bar → File → New → AUTOSAR Project

2. In dialog New AUTOSAR Project → Field Project name = "EthernetTestProject" → Click Finish button


Configure Service Interface and System Data Mapping 3. Create Sender Receiver Interface: In AR Explorer → EthernetTestProject → Software: Right mouse button click → Create Interface → Create

Port Interface → Elements | Sender Receiver Interface

4. In dialog New AR Element Creation → Click Finish button


5. On newly created SenderReceiverInterface_0: Right mouse button click → Open With → Generic Editor

6. Create Variable Data Prototype: In Generic Editor on SenderReceiverInterface_0: Right mouse button click → New Child → Data Elements |

Variable Data Prototype


7. Result:

8. At field Type: Click black triangle to open drop down list → Click on "sint16_least..."


9. On SenderReceiverInterface_0: Left mouse button click → Under Attributes → Field isService: Click black triangle → Click true

10. Result:


Create Component 11. Create Application Sw Component Type: In AR Explorer on Software: Right mouse button click → Create Component → Elements | Application

Sw Component Type



13. On newly created ApplicationSwComponentType_0: Right mouse button click → Open With → Component Editor

14. Click PPorts... link


15. In dialog Port Creation Dialog: Select the SenderReceiverInterface → Click OK button

16. Result:


Create Composition 17. Create Composition Sw Component Type: In AR Explorer on Software: Right mouse button click → Create Component → Elements |

Composition Sw Component Type



19. On newly created CompositionSwComponentType_0: Right mouse button click → Open With → Composition Editor

20. Click Auto Configure Composition button


21. In dialog Auto Configure Composition: Drag and drop ApplicationSwComponentType_0 into table cell of Component Prototypes

22. Click OK button


Configure System Data Mapping 23. Create new System: In AR Explorer on System: Right mouse button click → Create System Info → Elements | System



25. In AR Explorer on newly created System_0: Right mouse button click → Open With → Generic Editor

26. In Generic Editor under Attributes: Field Category: Hit CTRL and SPACE key


27. In Content Assist on ECU_EXTRACT: Left mouse button double click

28. Result:


29. Create new Root Sw Composition Prototype: In Generic Editor on System_0: Right mouse button click → New Child → Root Software Compositions | Root Sw Composition Prototype

30. At field SoftwareComposition: Click black triangle → CompositionSwComponentType_0


31. Result:


Configure Pdus & Signals 32. In AR Explorer → On EthernetTestProject: Right mouse button click → Open With → System Editor

33. Create new Signal: In System Editor → Signals → On right hand side, under Create New Elements → New Signal → Drag and drop New

Signal into table column Signal Name


34. In table cell Signal_0: Left mouse button click → Type Signal_Tx

35. In same table row in column Length: Left mouse button click → Type 8 and hit RETURN key

36. Result:

37. Repeat steps 33 to 35 for Signal_Rx


38. Result:

39. In AR Explorer → EthernetTestProject → System → System Info → System_0: Right mouse button click → Open With → System Data

Mapping Editor

40. In case there is dialog Open DataMapping Editor→ Click Yes button


41. Result:

42. In table column Signal Info, sub column System Signal/Signal Group: Left mouse button double click


43. In dialog SystemSignal selection dialog → On signal: Left mouse button click → Click OK button

44. Result:


Generic Ethernet configuration 45. In AR Explorer → On EthernetTestProject: Right mouse button click → Open With → System Editor

46. Create new PDU: In System Editor → Pdus → On right hand side: under Create New Elements → New PDU → Drag and drop New PDU into

table column PDU Type on ISignalIPdu

47. Result:


48. In column PDU/Signal in table cell ISignalIPdu_0 → Left mouse button click → Type new name Eth_Pdu_Tx

49. In same table row, column Length → Left mouse button click

50. Type 8 and hit RETURN key

51. Repeat steps 46 to 50 for Eth_Pdu_Rx


52. Result:

53. On right hand site under Available Signals: Drag and drop Signal_Tx to Eth_Pdu_Tx

54. Result:

55. Repeat step 53 for Rx: Drag and drop signal Signal_Rx to PDU Eth_Pdu_Rx


56. Result:


Configure Ethernet Networks 57. Create new Ethernet network: In System Editor → Networks → Ethernet Networks → On right hand side, under Create New Elements → New

PhysicalChannel → Drag and drop New PhysicalChannel into table column Ecu/Controller

58. Result: new physical channel EthernetPhysicalChannel_0 created


59. On EthernetPhysicalChannel_0 → Left mouse button click

60. Type ETH_NW and hit RETURN key


Associate ECU & PDUs to the network 61. Create new ECU: On right hand side, under Create New Elements → New ECU → Drag and drop New ECU into table

column Ecu/Controller on ETH_NW

62. Result: new ECU EcuInstance_0 created under ETH_NW


63. On right hand site, under Create New/Map Existing Elements → Available Pdus → Click double downwards arrow to expand the view

→ 64. Under Available Pdus → Drag and drop Eth_Pdu_Tx into table column Direction on Transmit node of ECU instance


65. Under Available Pdus → Drag and drop Eth_Pdu_Rx into table column Direction on Receive node of ECU instance

66. Result:


67. In table column Vlan Config: Left mouse button click and type VLAN_CONFIG

68. In table column Vlan ID: Left mouse button click and type 1234

69. Result:


Configure Socket Adapter (IP address and port) 70. Create new TCP address: In System Editor → Networks → Ethernet

Networks → EthernetCluster_0 → ETH_HW → SoAdConfig → SocketAddress: On right hand side, under Create New Elements → New TCP

Address → Drag and drop New TCP Address into table column NetworkEndpoint on Ipv4

71. Result: New network endpoint NetworkEndpoint_0 created


72. In table row of newly created NetworkEndpoint in table column IP Address: Left mouse button click

73. Type 192.168.0.1 and hit RETURN key

74. In same table row (of NetworkEndpoint_0) in table column PortNumber: Left mouse button click


75. Type 20490 and hit RETURN key

76. Repeat steps 70 to 75 for further network endpoints:


Server and Client Port Configuration 77. Click on black triangle at Connection View icon

78. Click Connection View

79. Result:


80. On right hand side, under Available Network Ports → Click triangle on left side of Tcp Socket Address

81. Result:

82. Drag and drop TCP socket address 192.168.0.1:20490 into table column Server Port


83. Result:

84. Drag and drop TCP socket address 192.168.0.1:20490 into table column Server Port on entry Client Ports

85. Result:


86. On right hand site, on Available PDU Triggerings: Left mouse button click to expand the view

87. Result:

88. Drag and drop PduTriggering_0 into table column Client Port in cell 192.168.0.1:20490 [Tcp]


89. Result:

90. On the right hand site, under Create New Elements→ Drag New RoutingGroup into table column RoutingGroups in table row of newly

added PduTriggering_0

91. In dialog Add System Element→ Click OK button


92. Result:

93. Click black triangle at Connection View icon

94. Click on SOMEIP View


95. Result:

96. This is the view for Service Discovery ("SD") configuration, see next chapter


Service Discovery Configuration 97. Create new Service: On right hand site, under Create New Elements → Drag New Service to table column Service Details and table cell Server

Services

98. In dialog Create Service → Field SocketAddress: Click black triangle → Click on displayed socket address 192.168.0.1 :: 20490 [Tcp]


99. Fields AEP and ShortName are filled automatically → Click OK button

100. Result: Under Server Services a ProvidedServiceInstance_0 is created


101. Create new Event Handler: On right hand site, under Create New Elements → Drag New Event Handler to table cell

with ProvidedServiceInstance_0

102. Result:

103. On right hand side, under Create New/Map Existing Elements → Click AvailableRoutingGroups to expand the view


104. Result:

105. On the right sitde, under Available RoutingGroups: Drag SoAdRoutingGroup_0 and drop it in table column RoutingGroups of table

row EventHandler_0

106. Result:


From here on: Just follow the workflow provided above to continue as you want

o For example: o Complete Service Interface and Data Mappings o Continue configuration of Generic Ethernet by configuration of PDUs o Add Socket Adapter and Service Discovery modules o Update Routing Groups for Event Handlers

Additional information

What else can be done:

o Header Id Generation o Update the Routing Group for the Event Handler / Consumed Event Group which will show the Service and Signal details for the specific service o Header Id will be generated based on the Service Type, Service Id & Method ID o To Generate Header Id: Please ensure the System Data Mappings are available. o Header Id will be generated by editing the value of Event Id o Header Id will be changed based on the new Event / Method Id

Do you still have questions?

o You will find further FAQ articles on the ETAS homepage: www.etas.com/en/faq o Movies corresponding to FAQ articles can be found on the ETAS YouTube channel o Please feel free to contact our Support Center, if you have further questions. o Here you can find all information: http://www.etas.com/en/hotlines.php

This information (here referred to as „FAQ“) is provided without any (express or implied) warranty, guarantee or

commitment regarding completeness or accuracy. Except in cases of willful damage, ETAS shall not be liable for

losses and damages which may occur or result from the use of this information (including indirect, special or

consequential damages).

http://www.etas.com/en/faq

https://www.youtube.com/user/etasgroup

http://www.etas.com/en/hotlines.php

autosar: how to create some/ip configuration - etas.com · question o ethernet supports the service...

Documents