Giorgio Zoppi wrote on 2013-07-18: > AFAIK Linux supports SocketCAN, how can replace in C++ or C binding, > TCP with Socket CAN? I mean what have I to modify to support another > transport protocol (CAN, UDP, ecc)? Etch has different layers, among others a dedicated transport layer (see the archictecture at [1]).
At the moment for the C and C++ binding there exists only an implementation for Windows/PosIX TCP/IP sockets, but you can add a new transport layer which encapsulates the SocketCAN communication. You might want to take a look at EtchConnection/EtchTcpConnection and EtchSessionListener/EtchTcpListener (referring to the C++ binding, in C binding there are similar files). If you have any further question on this, don't hesitate to open a new discussion on the mailing list. Cheers, Martin [1] http://etch.apache.org/documentation/architecture.html#Architecture-EtchTheArchitecture > > > > 2013/7/18 Martin Veith <[email protected]> > >> Giorgio Zoppi wrote on 2013-07-18: >>> Ok. Just a question. Do you use it over CAN buses as well? >> Etch is based on IP. So if you would be able to serialize IP packets >> to CAN, it could work. >> >>> >>> >>> 2013/7/18 Martin Veith <[email protected]> >>> >>>> Giorgio Zoppi wrote on 2013-07-17: >>>>> How to help? >>>> Regarding the release: Testing whether the build and the tests >>>> (especially of the cpp binding) work out-of-the-box on your >>>> machine would be great. Maybe there is some more documentation >>>> needed or some dependencies are not clearly stated. >>>> >>>> In general: >>>> There are a quite a lot of open issues in our Jira e.g. some bugs >>>> in the C binding, open tasks for the Etch C++ binding, missing >>>> tests in the C# binding, ... >>>> >>>> Cheers, >>>> Martin >>>> >>>>> >>>>> >>>>> >>>>> 2013/7/17 Martin Veith <[email protected]> >>>>> >>>>>> Hi all, >>>>>> >>>>>> I think it is time to do our next Etch release. Therefore I'm going >>>>>> to check all our issues in Jira within this week in order to see, >>>>>> which changes can be integrated in the upcoming release. I'm >>>>>> planning to finalize the release at the end of next week (around >>>>>> July 26). >>>>>> >>>>>> Do you have any patches which should be included in this next >>>>>> release? Even tough, I think it would be good to release more >>>>>> often (e.g. once a month) in order to push bug fixes more >>>>>> frequently. So we can include any "at the moment not yet ready" >>>>>> patches in the next minor release. >>>>>> >>>>>> As this release will contain the new implementation of the C++ >>>>>> compiler and runtime, I would propose to do a major release by >>>>>> setting the version to 1.3.0. >>>>>> The C++ binding is still in beta and under testing, but it >>>>>> looks quite good what I have seen so far. >>>>>> >>>>>> Do you have any comments on that? Any other objections? >>>>>> >>>>>> Best regards, >>>>>> Martin >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >>> >> >> >> > >
