linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Sebastian Haas <dev@sebastianhaas.info>
Cc: socketcan-users@lists.berlios.de,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
	Jan-Niklas Meier <dschanoeh@googlemail.com>
Subject: Re: Bus-simulation with SocketCAN
Date: Tue, 10 Jan 2012 11:29:24 +0100	[thread overview]
Message-ID: <4F0C1304.4060309@hartkopp.net> (raw)
In-Reply-To: <4F0B6B35.20104@sebastianhaas.info>

Hello Sebastian,

On 09.01.2012 23:33, Sebastian Haas wrote:

> just in case someone is interested in an easy to way to simulate CAN nodes or
> to test ECUs via CAN. I want to inform you that my recently started project
> restcan [3] reached a first milestone. Look at [1] to know what restcan is.
> 
> The milestone includes the following features:
> - support of SocketCANs' RAW channels incl. Rx filters
> - support of a rudimentary JSON-based message database format


Do you know the Kayak project from Jan-Niklas Meier?

Kajak is a JAVA based frontend and library, see:

http://kayak.2codeornot2code.org/

http://kayak.2codeornot2code.org/tutorial.html

And on github: https://github.com/dschanoeh/Kayak

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.

But checking your JSON description for CAN signals i stumbled about the
'intel' and 'motorola' tags which stand for 'little' and 'big' endian.

I wonder, if it makes sense for your project to adopt the XML-based KCD
format for CAN signal descriptions:

https://github.com/dschanoeh/Kayak/blob/ee6b459bddd1831ae99c1afcde01f315e4b454b4/Kayak-kcd/src/test/resources/can_definition_sample.kcd

Here is the XML schema definition:

https://github.com/dschanoeh/Kayak/blob/master/Kayak-kcd/src/main/resources/com/github/kayak/canio/kcd/schema/Definition.xsd

Maybe you can build your JSON description with an XSLT process from the well
defined KCD description.

There's also a dbc input converter on the run to create KCDs:
https://github.com/dschanoeh/CANBabel


> - support of receiving and decoding measurement values encoded in CAN
> messages, sending of such messages is also possible
> 
> See the examples in [5] to get an impression of using restcan.
> 
> Since my plans are big and I'm just one person with limited sparetime I ask
> everyone here to support this project with its mission to provide any easy to
> use way of accessing SocketCAN. See [4] for things I want to implement in the
> near future.
> 
> I hope Oliver is fine with "mis-"using the socketcan mailing list to announce
> this milestone of this very socketcan-related project. :-)


:-) This is not in my responsibility what is posted on SocketCAN-Users.
Btw. i put it onto the linux-can ML to continue the discussion there.

It's a good question, if we just do announcements on linux-can ML as i don't
know if the SocketCAN-Users ML will continue in the future.


> 
> [1] https://github.com/sebi2k1/restcan/wiki
> [2] http://sebi2k1.wordpress.com/2012/01/09/transmitting-and-receiving-physical-values-via-can/
> [3] https://github.com/sebi2k1/restcan
> [4] https://github.com/sebi2k1/restcan/blob/master/TODO.md
> [5] https://github.com/sebi2k1/restcan/tree/master/sample_scripts


Regards,
Oliver


       reply	other threads:[~2012-01-10 10:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4F0B6B35.20104@sebastianhaas.info>
2012-01-10 10:29 ` Oliver Hartkopp [this message]
2012-01-10 21:11   ` Bus-simulation with SocketCAN Sebastian Haas
2012-01-11  7:24     ` Yegor Yefremov
2012-01-13 20:08       ` Sebastian Haas
2012-01-11  8:38     ` Jan-Niklas Meier
2012-01-13 20:06       ` Sebastian Haas
     [not found]         ` <000901ccd237$aae943f0$00bbcbd0$@wilhelm@peak-system.com>
2012-01-14  9:45           ` Sebastian Haas
2012-01-15  9:13         ` Sebastian Haas
2012-01-15 14:39           ` Jan-Niklas Meier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F0C1304.4060309@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=dev@sebastianhaas.info \
    --cc=dschanoeh@googlemail.com \
    --cc=linux-can@vger.kernel.org \
    --cc=socketcan-users@lists.berlios.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).