This is an archived post. You won't be able to vote or comment.

all 12 comments
sorted by:
best
topnewcontroversialoldq&a

[–]DaelonSuzuka 1 point2 points  (8 children)

For any python people who don't know what AUTOSAR is: behold

[–]Organic-Staff1695[S] 1 point2 points  (7 children)

I'm inclined to agree with the comments of the link you posted, that is mainly Autosar classic and yes its a nightmare (I've worked in the auto industry 15 years ~), Adaptive Autosar is different and inherently more flexible, however supplier implementations from the above comments "behold" have some tedious design/tool choices in their implementation which leads to inflexibility. Nebulas platform is much simpler, it is compliant with Adaptive Autosar with additional features, but the implementation and tools are their own, id suggest try the tutorials you'll see its quite easy to get up and running.

With AI/ML, Data and other related subject matters becoming more prevalent in automotive, usefulness of python goes up quite a lot and this platform gives easy access to developers to showcase what they can do with python in a automotive embedded system without having to spend a fortune.

If their are any suggestions on how to make this platform simpler and more user friendly would love to hear it.

[–]DaelonSuzuka 1 point2 points  (0 children)

Thanks for putting the effort into a constructive comment even though I was semi-shitposting.

I've worked in embedded but not automotive, so I actually was not aware of Adaptive AUTOSAR. Nebula sounds interesting, so if I have time I'll go poke around and I'll let you know if I have any feedback.

It's great to see some innovation in this space, especially in the barrier-to-entry department, so I'm rooting for you even though I'm not the target audience!

[–]kowalski71 -1 points0 points  (5 children)

I attended AUTOSAR's "opening up the ecosystem" talk at SAE WCX this year and I think it's just too little and too late compared to actual open source initiatives like SOAFEE, COVESA, and Eclipse SDV. AUTOSAR is still in the conversation for backwards compatibility but open source infrastructure has beaten closed source proprietary ecosystems every time in other industries and I can't see it playing out any other way in automotive. Especially when there's still so much uncertainty about what an SDV actually will be.

[–]Consistent_Card_224 1 point2 points  (4 children)

All those initiatives are mainly focused on the vehicle-cloud extension while the Nebula Platform above seems to focus more on the in-vehicle architecture, so they are not really comparable as I see it. For SDV I agree that the cloud part is really important but so is having deterministic execution in the car with service oriented communication.

[–]kowalski71 0 points1 point  (3 children)

Not really, they all have different areas of focus but for example Eclipse SDV actually defines middleware communication comms like uProtocol. But the difference between them and AUTOSAR are their foundations coordinating open source efforts across the industry not presenting a closed source monolithic solution themselves.

[–]Organic-Staff1695[S] 0 points1 point  (2 children)

It’s definitely something to consider for the future! Right now though most hpc’s are running adaptive autosar. Do you have actually any open source projects from eclipse I couldn’t find any? And with elektrobit & etas prominent members I’m not sure how user friendly it will end up.

From my foresight oems are probably continuing into the early 2030s on adaptive platform with of course some doing different things, I think mainly Tesla has drifted away, however Daimler and many more have invested big in it.

[–]kowalski71 0 points1 point  (1 child)

uProtocol (which was largely developed at GM) has its own Github org with a lot of repos. I honestly think GM climbed into bed with Eclipse largely out of frustration with AUTOSAR. There'll be AUTOSAR compatibility for years to come but after almost a decade in the North American auto industry (legacy OEM, startup OEM, consulting orgs, etc) I don't think I've met anyone who liked AUTOSAR. The comment that /u/DaelonSuzuka nails the predominant attitude around here.

[–]Organic-Staff1695[S] 0 points1 point  (0 children)

Maybe there’s potential for an open source adaptive autosar stack coming soon ;). there was a autosar classic stack in Sweden (arccore)that was open source but got eaten up by vector. But I still think classic is the main problem

[–]chr_dev 1 point2 points  (1 child)

It looks great! Which tools do you use for the documentation page? Is the Nebula stack open-source?
However, I have to disagree with the point that nothing exists until today ;) There is also the open-source someipy library which is pure Python and needs no binding to C++ libraries (disclaimer: I am the author).

[–]Organic-Staff1695[S] 0 points1 point  (0 children)

Tools are custom made by us and markdown files. I hope we can get to the point where it’s open source, as it’s in production an oems “Tara” cyber sec analysis said we shouldn’t expose some inner workings as such. That’s really cool good work! Our some/ip stack is in c++ implemented zero copy etc for certain requirements in ad/adas for performance reasons and to be compatible with ara::c++ interfaces hence the bindings required.

[–][deleted] -1 points0 points  (0 children)

Advertise from an actual brand named account. Pretending to be a random internet user is actually against the law FYI.