Am 08.07.2011 04:07, schrieb Stu Statman:
We have SocketCAN and the utilities up and running and can see the CAN
traffic flowing (Yay!). However, it's not clear to me that the cansend
utility is actually doing anything. If I use cansend to send in a frame,
I should see that in candump, right?
To be specific, I'm doing this :
cansend can0 18EA0001#03.F0.01
That's an ISO request for a Schneider inverter specific PGN. I copied it
directly from an earlier request, caught by candump, that a Schneider
utility app sent in :
can0 18EA0001 [3] 03 F0 01
The inverter sends out a valid reply to that, along the lines of
can0 19F00300 etc
However, when I attempt to send in that frame (using the cansend call
above), I don't see anything in candump; neither my request nor the
expected response shows up. Does candump ignore cansend calls from the
local machine? Did I construct the cansend call incorrectly? Do I need
to do something about that source address (1)?
No. In general this should work as you tried.
The frames you sent out with
cansend <interface> <frame-content>
should be visible for all applications on the local host.
E.g. you can (and should) try this with the virtual CAN interfaces:
Create a virtual CAN interface and use cansend/cangen and in a
different terminal candump.
As you wrote, that you can see incomming traffic, you should monitor
this (continuous) traffic with candump and then send (in another
terminal) a CAN frame with cansend. Does the incomming traffic stop then?
Regards,
Oliver
_______________________________________________
Socketcan-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/socketcan-users
