Re: Bus-simulation with SocketCAN

[Sebastian Haas <dev@sebastianhaas.info>]

Hello Uwe,

would be great if could provide us example .sym files which utilize the 
whole feature set of the SYM file format.

Specifications or example codes are also very much appreciated. ;-)

Thanks for your support.

Cheers,
  Sebastian

Am 13.01.2012 22:09, schrieb Uwe Wilhelm:
> Dear Sebastian,
> if you need any help with the SYM File Format, please let us know.
>
> Best Regards
>
>   Uwe Wilhelm
>   PEAK-System
>   Sales&  Support
>
> -----Ursprüngliche Nachricht-----
> Von: linux-can-owner@vger.kernel.org
> [mailto:linux-can-owner@vger.kernel.org] Im Auftrag von Sebastian Haas
> Gesendet: Freitag, 13. Januar 2012 21:07
> An: Jan-Niklas Meier
> Cc: Oliver Hartkopp; linux-can@vger.kernel.org; s.grosjean@peak-system.com
> Betreff: Re: Bus-simulation with SocketCAN
>
> Hello together,
>
> Am 11.01.2012 09:38, schrieb Jan-Niklas Meier:
>> 2012/1/10 Sebastian Haas<dev@sebastianhaas.info>:
>>>> Implementing a restbus functionality in JAVA based on the Kajak library
> is
>>>> very easy - when  you are a JAVA developer ;-)
>>>>
>>>> I like your approach to get a restbus simulation in C.
>>>
>>> Well the simulation is written in Javascript, which is even easier than C
> or
>>> Java. I want it to be easy to use. The only dependency is NodeJS and you
> can
>>> write and run simulation and test cases from commandline within few
> minutes.
>>
>> I like the idea of using Javascript and especially NodeJS for restbus
>> simulation. At the weekend I will try to set it up at home and play
>> around a little bit :).
> Sounds good. I hope you like it and we can work together on it.
>
>>>> I wonder, if it makes sense for your project to adopt the XML-based KCD
>>>> format for CAN signal descriptions:
>>>
>>> I had a look at the spec, KCD looks pretty good, I think I will use it to
>>> replace the JSON description.
>>
>> \o/ Yay! That's a good idea.
> Yes KCD looks quite complete to describe a whole CAN network include the
> communicate. But I'm not yet sure how to extend it for specific features
> like other protocols.
>
> The basic idea was to have a NodeJS instance for each CAN node to
> simulate. Basically the API allows also to simulate many nodes within
> the same NodeJS instance. But I think it is easier for an developer to
> develop and test CAN nodes in different instances.
>
>>>> There's also a dbc input converter on the run to create KCDs:
>>>> https://github.com/dschanoeh/CANBabel
>>>
>>> Thats create, I was afraid I need to implement the converter myself. ;-)
> I
>>> hope they will extend to parse .sym files from Peak as well.
>>
>> We mostly have .dbc files we need to convert. Support for different
>> formats (and possibly even conversion in both ways) is planned. Do you
>> use PEAK .sym-files and could you provide some example files and help
>> finding bugs in a .sym-Parser?
> No I do not have any PEAK files, but I wonder @Stephane may help us.
>
>>> Do you know about BUSMASTER (https://github.com/rbei-etas/busmaster). If
> it
>>> weren't Windows (R) only it would be an interesting solution.
>>>
>>> Oliver, what must restcan provide to be useable for you in your daily
> work?
>>> Or what do you expect from such a tool?
>>
>> How lightweight is NodeJS? I would find this useful for quick and
>> dirty hacks in embedded units. Could memory (Flash and RAM) be a
>> problem on such devices?
> This thought came also in my mind. I wonder on which type of machines
> (available RAM) do you want run it?
>
> NodeJS just relies on STL and PThread. But I'm afraid STL is quite big
> ;-) ... Heap usage looks quite good IMHO. If I let signal_tx.js running
> the Gnome System monitor reports 2.3MB memory usage. If you also take
> shared libaries into account the footprint explodes up to 64MB. But I
> wonder if it is possible to compile NodeJS/V8 against a more memory
> sensible version of the STL.
>
> Cheers,
>    Sebastian
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
> --
> PEAK-System Technik GmbH, Otto-Roehm-Strasse 69, D-64293 Darmstadt
> Geschaeftsleitung: A.Gach/U.Wilhelm, HRB 9183 Darmstadt, Ust.IdNr.:DE 202 220 078
> St.Nr.:007/241/13586 FA Darmstadt, WEE-Reg.-Nr.: DE39305391
> Tel.:+49 (0)6151 8173-20 - Fax:+49 (0)6151 8173-29
> E-mail: info@peak-system.com - http://www.peak-system.com