eclipse-opendut
Enablement of edge client (EDGAR) with automotive functionality
One story is about enabling the edge client (EDGAR) with further automotive protocols, i.e. CAN (currently only ETH), and other automotive functionality to communicate/ interact with directly connected DuT(s) or those which are accessible via other EDGARs as part of the VPN network.
Specific features for this story are:
- [x] Implement a CAN interface (beside current ETH) on EDGAR to enable CAN communication with the locally connected DuTs
- [x] Establish a communication link via CAN to other DuTs connected to the same EDGAR. Two or more DuTs connected to same EDGAR should use direct communication (not routed via VPN)
- [x] Establish a communication link via CAN to other DuTs located at different EDGARs that are part of the IP-routed network (VPN)
- [ ] #90 - Control relays, including standardized automotive clamps (Klemme 15/30) - General I/O for integration of sensors on DuT (e.g. power supply current monitoring)
- [ ] #115 - Integrate an (external) restbus simulation - Flashing of a DuT via EDGAR
Thank ypu @Ovomaltine85 for opening this issue. May you also setup a call so we can discuss the details and refine this issue further?
@Ovomaltine85 @eet1mu3: Could you add your real name to your GH account? I have no clue who you are. :smile:
Thank ypu @Ovomaltine85 for opening this issue. May you also setup a call so we can discuss the details and refine this issue further?
@Ovomaltine85 @eet1mu3: Could you add your real name to your GH account? I have no clue who you are. 😄
Good hint with the clear names ;-) Regarding the alignment call. This is definitely a good idea. Do you want to invite or shall we? There will be further colleagues working on this story. Not all of them are assigned to this Github org yet.
It may make sense to have the one or other discussion here at GH discussions to make our decision making transparent and documented.
Regarding the alignment call. This is definitely a good idea. Do you want to invite or shall we?
go ahead.
It may make sense to have the one or other discussion here at GH discussions to make our decision making transparent and documented.
of course.
The first three points of your list are CAN related and tight coupled. I like that they build up one each other and we always get something usable. But in my opinion we should split the other two apart into their own issues. Nevertheless we can track the whole progress within this issue.
