←back to thread

1321 points kwindla | 3 comments | | HN request time: 0.696s | source
Show context
swagasaurus-rex ◴[] No.43794426[source]
Very exciting! Electric vehicles have the ability to be very simple, much simpler than an ICE.

Although electric can't be 100% analog, I miss the old days when a car has no software updates, no telemetry, no privacy issues, no mandatory subscription for features.

replies(4): >>43794543 #>>43794546 #>>43794634 #>>43794711 #
the__alchemist ◴[] No.43794543[source]
Don't want or need analog: Just don't enshittify the digital! CAN bus is a great system; don't IoT it or use dark patterns.
replies(2): >>43796071 #>>43796368 #
AlotOfReading ◴[] No.43796368[source]
God no, CAN is horrible and the horrors people working around its limitations have brought into the world are even worse.
replies(2): >>43796731 #>>43801823 #
the__alchemist ◴[] No.43796731[source]
What limitations specifically are you referring to?
replies(1): >>43798544 #
1. AlotOfReading ◴[] No.43798544[source]
The packet size is a major one. The lack of larger packets leads to nonsense like the "freshness manager" in things like AUTOSAR's SecOC, or the addressing scheme. Every subsequent CAN extension has tried to rectify both of these in different ways and inevitably failed, which leads to the next layer up the networking stack reinventing the wheel badly. Eventually you end up with UDS.
replies(1): >>43799021 #
2. the__alchemist ◴[] No.43799021[source]
Yea, that 64-byte frame size. In practice, I've always seen it abstracted away into a layer on top, but if you're working low-level (e.g. implementing that layer), it's a pain. So, a given packet may be represented by multiple frames.
replies(1): >>43799337 #
3. rjsw ◴[] No.43799337[source]
I hold a patent on the design of a hardware offload engine to hide the handling of multiple frames from a main CPU.