Desired requirements for short term and long term usage

[rajsahae]

At the basic level with the most short term gains, the ability to send any message on the CAN bus manually. For example, using a current set of perl scripts, I have to perform 3 separate tests to send messages over a can dongle.

• Launch a daemon to initialize the can dongle
• run a second script to set the baud rate
• run a third script to send messages (that I specify) over the CAN dongle

These scripts are all structured a bit differently and they also depend on swig. There is a lot of external dependencies and it would be helpful if it was all wrapped up into a single library.

Secondly, in the near long term, I would like to have a text file containing the messages that I need to send, and then the library had the capability to simply broadcast all the messages in that file onto the CAN bus indefinitely.

Thirdly, in the actual long term, it would be nice if we could import a DBC file, and then send messages based on encodings from the DBC file.

Lastly, again in the long term, it would be beneficial to have the ability to take "memorator data", that is, stored CAN bus data in the form of a memorator file (we use something like this http://www.kvaser.com/zh/kvaser/news/32-news/174-memolight-revelead.html) and replay it back onto the CAN bus via the dongle.

That's all I remember from our discussion for now. If I remember anything else, I'll file another issue.