You are a very good teacher !! I saw many videos but no one has this much details .. really an expert made this video.. i will recommend this video for someone starting with someip
Thnak you for you contribution Samir this video really taught me about SOME/IP you are a good teacher i hope you can upload similar topics about Automotive Ethernet, so im looking forward for more videos like this congratulations and greetings from Guadalajara Jalisco México
00:17 SOME/IP is a service oriented architecture for automotive ECUs. 02:57 SOME/IP supports complex data communication over Ethernet 08:16 SOME/IP is a scalable service-oriented middleware for vehicle networks. 10:52 Some/IP allows ECU to subscribe and receive information efficiently. 15:41 Some/IP is a pub/sub model for service discovery 18:34 Understanding the switch in automotive service-oriented architecture 23:13 Creating the AR XML file to describe SOME/IP 25:56 SOME/IP is a Linux-based, well-written, multi-threaded stack that configures using JSON files. 29:59 SOME/IP message structure overview 32:02 C code interface in Vehicle Spy allows for some IP interaction 36:15 AUTOSAR workflow for Some/IP 38:29 AUTOSAR focuses on virtual machine-based design and development.
I have one doubt, How come consumer ECU i.e. vehicle control ECU will give front distance information (methods) to SRR? Vehicle control ECU isn't just suppose to consume the information and not to give the information? How this protocol works in this case? And thank you sooo much for informative video. It was much much much needed. thanks
Thank you for good insight into SOME/IP! Here is a question, would appreciate your response - is SOME/IP meant for in-vehicle communication among ECUs OR it can be used for vehicle communication with outside world (say some backend servers over internet)?
SOME/IP is primarily designed for in-vehicle communication among ECUs. However, it can also be adapted for communication with external systems when needed, provided that appropriate security measures are implemented to safeguard the vehicle and its data. If you have questions or wish to discuss your specific use case further, please don't hesitate to contact our sales team at www.intrepidcs.com/sales. We are eager to learn more about your application and provide guidance as needed.
@@yogitabidkar4885 SOMEIP is an optional protocol. Its not needed to be used always when using AUTOSAR Ethernet . SOMEIP uses Ethernet as underlying layer. AUTOSAR Ethernet can be used without SOME/IP which is a very typical use case.
If I don't have arxml file to indentify services but i have source code, can I know available services and identifiers? If so, where should they be placed?
Sorry for the delay in our response. Our audio recording for ARXML presentation didn't work properly, If you send me an email at arughani@intrepidcs.com, I can share our presentation with you.
The presentet talked about how to get the SOME/IP behavior on Linux with some stack available. Can anyone please point me where I can find that and use? Thanks in advance.
Hi @vbhaarat90, please reach out to our sales team at intrepidcs.com/sales. We also added a new video about SOME/IP with our neoVI PI and VSpy X product. Watch it here th-cam.com/video/szG47mXeW1o/w-d-xo.html
Thank you so much.. This helped me a lot to understand about SOMEip.
You are a very good teacher !! I saw many videos but no one has this much details .. really an expert made this video.. i will recommend this video for someone starting with someip
Thnak you for you contribution Samir this video really taught me about SOME/IP you are a good teacher i hope you can upload similar topics about Automotive Ethernet, so im looking forward for more videos like this congratulations and greetings from Guadalajara Jalisco México
00:17 SOME/IP is a service oriented architecture for automotive ECUs.
02:57 SOME/IP supports complex data communication over Ethernet
08:16 SOME/IP is a scalable service-oriented middleware for vehicle networks.
10:52 Some/IP allows ECU to subscribe and receive information efficiently.
15:41 Some/IP is a pub/sub model for service discovery
18:34 Understanding the switch in automotive service-oriented architecture
23:13 Creating the AR XML file to describe SOME/IP
25:56 SOME/IP is a Linux-based, well-written, multi-threaded stack that configures using JSON files.
29:59 SOME/IP message structure overview
32:02 C code interface in Vehicle Spy allows for some IP interaction
36:15 AUTOSAR workflow for Some/IP
38:29 AUTOSAR focuses on virtual machine-based design and development.
I have one doubt, How come consumer ECU i.e. vehicle control ECU will give front distance information (methods) to SRR? Vehicle control ECU isn't just suppose to consume the information and not to give the information? How this protocol works in this case?
And thank you sooo much for informative video. It was much much much needed. thanks
Thank you so much for details overview of SOME/IP protocol..Looking forward more videos on Autosar Achitecture.
On the first slide ECU A and B are not according to the description. (Provider vs consumer)
Thank you for good insight into SOME/IP! Here is a question, would appreciate your response - is SOME/IP meant for in-vehicle communication among ECUs OR it can be used for vehicle communication with outside world (say some backend servers over internet)?
SOME/IP is primarily designed for in-vehicle communication among ECUs. However, it can also be adapted for communication with external systems when needed, provided that appropriate security measures are implemented to safeguard the vehicle and its data. If you have questions or wish to discuss your specific use case further, please don't hesitate to contact our sales team at www.intrepidcs.com/sales. We are eager to learn more about your application and provide guidance as needed.
7:45 In block diagram, Why SD (ServiceDiscovery) is Not shown as on top of SOME-IP ? From the path they look like 2 separate paths ? pls explain.
I need these slides please.
Thanks a lot.
Thank you for the video !
Good content
Having one doubt plz help me to solve the problem
Does autosar ethernet. Compulsary required somip protocol implementation
What will happen if I don't want to use someip protocol with ethernet ...can I simplely use ethernet in autosar?
@@yogitabidkar4885 SOMEIP is an optional protocol. Its not needed to be used always when using AUTOSAR Ethernet . SOMEIP uses Ethernet as underlying layer. AUTOSAR Ethernet can be used without SOME/IP which is a very typical use case.
The background image looks like Oakland University Engineering center front side.😅
It is! Our annual tech day has been hosted by the OU engineering center for a few years now!
If I don't have arxml file to indentify services but i have source code, can I know available services and identifiers? If so, where should they be placed?
on the first slide, why does ECUA and ECUB have he same IP address?
Thanks for this detailed video. What if I have to offer a service to an ECU through a simulated node? Should that be a multicast offering or unicast?
The Find/ offer will be always on Multicast(UDP)
Hi in your Talk you mentioned there is another someip then genivi , Can you please send the link of that someip.
Please what's mean an 'Entry' in someIp ??
hi, i'm unable to fing ARXML Video, where can i find it? thank you in advance :)
Sorry for the delay in our response. Our audio recording for ARXML presentation didn't work properly, If you send me an email at arughani@intrepidcs.com, I can share our presentation with you.
Please make a series on vsomeip from scratch
The presentet talked about how to get the SOME/IP behavior on Linux with some stack available. Can anyone please point me where I can find that and use? Thanks in advance.
Hi @vbhaarat90, please reach out to our sales team at intrepidcs.com/sales. We also added a new video about SOME/IP with our neoVI PI and VSpy X product. Watch it here th-cam.com/video/szG47mXeW1o/w-d-xo.html