วีดีโอ

Thanks for educating the whole comunity if there is any numerical problem available kind make on those as well

Very good presentation. TDMA = Time Division Multiple Access @17:35

I need these slides please. Thanks a lot.

Dear Friends. Good to continue working on SDV+. 1) I found correction/addition to the video, when the lecturer says ECU(more general Electronic Control Unit), would it be more clear to say/write GEM(General Electronic Module), ElectronicCU or ElectronicCM(Electronic Control Module) or just simply controllers in order not to confuse with Engine Control Unit (ECU as well and more specific)? 2) Which valuable functions, interfaces to implement in Cloud, IoT for whom? Which company, entrepreneur is interested seriously and ready to hire/employ me from here the thread (via email and Skype to exchange work results) to do research and development within specific custom domain of control modules?

Where is the slides that you explain from? And thanks so much.

very useful.

Excellent presentation!

very informative presentation, please call things as they are instead of surrendering to political correctness

Thank you for the great video. Where can we find the presentation?

Thank you.

i have to say, it contens many knowladege, and i reviewed several times, now i am abler to understand the function of switch. very appriciate.

thank you! great talk, straight to the point, while also offering a real deep understanding of all necessary details. imho a perfect overview by all standards

Great explanation, very useful and simply explained. Thank you! Looking forward to that 3hr AVB/TSN class :)

what vehicles would use this? Just doIP cars ?

Rather than good session, it is very very good session. If possible, can you post the video/session on Some/Ip header where sir was explaining the Entry and Optional field. I'm very curious about dip dive there. Thanks in Advance

This is awesome. What I have been trying to learn for months, I was able to grasp them in an hour. Thanks for this nice presentation.

I watched the presentation live. I think the title is somewhat misleading as it is way too generic to describe the actual content. The presentation deals with the vehicle's communication architecture: basic component level authentication and some encryption mechanisms at the lower layers in the OSI layer stack in a car. But what it does not deal with is the actual *software* architecture of a software defined vehicle. Things like: programming languages used, compiled code/interpreted code/bytecode, static or dynamic linking of sw modules, memory management, memory protection, buffer overflows, cross site scripting, SQL injections, risks of embedded virtualization, attacking AI models, safe and secure software update processes, attacking processors supply voltages, trusted platform module, attacking real-time behaviour of software, attacking wireless communication, attacking software logs, malicious code, code complexity, data manipulation on storage devices, ... "Cybersecurity in SDV Architecture" is not just a topic in a book on Automotive Ethernet. The authors have a very limited focus here. They end with key management for keys on communication link encryption being difficult, but actually leaving a whole world of attacks and security measures at the sw level unconsidered.

Guys, I love the short intro for Some ip, but please make sure that the written presentation is accurate and reflects the spoken part. You say that that udp is preferred for a payload of 1400 bytes, but it is written 1500 bytes. In the slide "What is a service" it is written: "Subscriber - subscribes using to the Eventgroup". Don't you mean Subscriber subscribes to the Event group? Please pay attention to details. This is important.

Great & very pedagogic presentation ! thanks !

impressive, inspiring, need to play more.

Thank you for this wonderful/training. It is extremely helpful to get into this automotive networking industry.

Thank you very much. My second day working as Network Protocol Engineer! Your video helped-me a lot to understand this protocol!

So when are we going to get rid of proprietary ad hoc modules in cars and replace them with generic compute/driver modules at 1/10 the cost?

.

.

In this SOA, what if the sensor modules are just raw data senders instead of service providers?

Good session, looking forward to more videos

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.

The best video so far i saw to understand the SOME IP concept.

Excellent!

Intrepid has really help me throughout my automotive career. Great presentation here from the ceo - wish he had more time to explain more. 😊

Big thanks for the presentaton, it helps me a lot.

What a wonderful video, thank you very very much!

Idid not get one thing. Sameer said in this video neovi pi can be used to profile some/ip stack. And at same time neovi pi have its own some/ip stack. So for profiling am i suppose to run some /ip stack on neovi pi?

Thank you so much man! I work in the automotive industry and wanted to know more about ethernet. Very nice explanation.

James is a very hard working and smart dedicated employee of Intrepid. Very happy to have him as a colleague and friend.

This is a great video for CAN bus RE. Thank you for resenting on this software. I do alot of this with simple CAN sniffing. I'll take a look at this software to see if the cost is possible to obtain.

Amazing expalnation, thank you very much Colt !

Very interesting and informative overview.

This is a very good explanation for the new generation vehicle E/E architecture.Thanks!

It's maybe not much LIN training, but more of a Vehicle Spy Entreprise software tutorial?

Good presentation . A few comments. Tesla has integrated the ADAS already to the central computer unit. We are also getting new SOCs which are designed to support running a mixed criticality ( in terms of safety and realtime) software stack in one SOC ( all the way up to ASILD). Moving the intelligence away from often microcontroller based ECUs is critical not only to enable easier software updates but also for being able to implement cross domain and cross ECU functions in the first place. This is one reason also why CAN having fixed communication scheme is quite useless in zonal architecture except for the last leg ( from zonal controller to dummy IO controller/ sensor)

how to download trial version

Very helpful video, thank you

in what time period we get the bus load 90(%)

Thank you for your amazing illustration and explanation

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)?

I forgot to mention in the video you can use these graphics on VividCAN as well.

Could I ask: what is some/ ip's location in the picture of Vehicle Networking Technologies?

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.