can-bus

I was thinking of making use of Boost Asio to read data from a Socket CAN . There's nothing fancy going on in linux/can.h , and the device should behave like the loopback interface, and be used with a raw socket. Looking at the basic_raw_socket interface it seems that I can make use of basic_raw_socket::assign to assign the native socket created with socket( PF_CAN, SOCK_RAW, CAN_RAW ); This is what I have so far namespace can { class CanSocket { public: typedef boost::asio::ip::basic_endpoint<CanSocket> endpoint; typedef boost::asio::ip::basic_resolver_query<CanSocket> resolver_query; typedef

How can I create several virtual sockets and link them together to create a virtual bus? I want to simulate an application in which many nodes communicate to each other via CAN. All you need is cangw tool from can-utils . Create two virtual interfaces: ip link add dev vcan0 type vcan ip link add dev vcan1 type vcan ip link set up vcan0 ip link set up vcan1 Create routing rule, so that all packets coming to vcan0 will be sent to vcan1 : cangw -A -s vcan0 -d vcan1 -e Listen to vcan1 in one terminal: candump vcan1 And send packet from another terminal: cansend vcan0 123#0011 You'll see, that

Is it possible to start and run Vector CANoe from the Command Prompt and/or by using any other external script? This document tells you how to control CANoe from C++, C# etc. This by making use of the CANoe as a COM Server utilities. http://www.vector.com/portal/medien/cmc/application_notes/AN-AND-1-117_CANoe_CANalyzer_as_a_COM_Server.pdf CANOE simply loads a .cfg configuration file. For jenkins, I am using the Visual Basics script and using this loading perticular configration file. In this was it bypasses the "I accept" and other windows and loads the desired configuration also also using

We have a robot project where the motor controllers use CANopen for communication. I need to communicate with these motor controllers using a master microcontroller. The problem is that I need to develop a CANopen layer in this microcontroller, but I only know how to send and receive at the low level (CAN). I don't know much about the CANopen (PDO, SDO, Heartbeat, object dictionary, etc.). I tried to read the CiA specifications, but it was very complicated. I would appreciate it if someone could point me in the right direction or give me a good tutorial to program a simple CANopen layer. Since

I want to create program that would emulate CAN port for testing purposes for another big application. Program should send previously recorded data through this virtual CAN. Anyone has any experience with such thing? I'm thinking to establish virtual COM, and send through it data packed in CAN Frames. Could it work? And how could I establish virtual COM on linux? Found this thread Virtual Serial Port for Linux but sadly I don't get how could it be implemented into source code of program (beginner linux user and programmer under linux). Would love to read your experience and suggestions.

Using CAPL with CANoe to transmit big amount of data via ISO-TP on CAN. Is there a routine, that provides the handling of data segmentation embedded in CAPL or do I need to write my own interpretation? Take a look at the OSEK_TP CANoe demo. It shows how to transmit and receive data over ISO-TP ( Transport Protocol, ISO 15765-2 ). See the nodeA.can file and the OSEL_TP API reference for implementation details. Here is minimal example: Create and configure a connection: long handle; handle = CanTpCreateConnection(0); // 0 = Normal mode CanTpSetTxIdentifier(handle, 0x700); // Tx CAN-ID

I am trying to make a software, which runs under Windows and communicates with an ELM327 device. I created the first version and I went in my SMART ForTwo (SMART 451) vehicle and I managed to connect with the Instrument Cluster (Transmit CAN ID is 782, Receive CAN ID is 783). However I have a huge problem with Flow Control. Here is the log: TX: ATI RX: ELM327 v1.5a TX: ATE0 RX: ATE0 OK TX: ATSP6 RX: OK TX: ATH1 RX: OK TX: ATL1 RX: OK TX: ATCFC1 RX: OK TX: ATFCSM0 RX: OK TX: ATAL RX: OK TX: ATSH782 RX: OK TX: ATCRA783 RX: ? TX: ATST64 RX: OK TX: 1092 RX: 783 02 1A 87 TX: 1A87 RX: 783 10 16 5A