On 05.05.2011 22:09, Kurt Van Dijck wrote: > On Thu, May 05, 2011 at 08:37:56PM +0200, Oliver Hartkopp wrote:
>> Hi Kurt, >> >> i tried to follow your documentation and have done this: >> >> root@host:~# IP link set vcan0 j1939 on >> root@host:~# IP addr add dev vcan0 j1939 0x20 >> root@host:~# IP addr add dev vcan0 j1939 0x30 >> >> (IP is the patched version of 'ip' on my box) >> >> Then i started in different terminals: >> >> candump -td -c -c any >> >> jspy -P >> >> and then invoked in a third terminal: >> >> echo 11223344 | jsr -v -v vcan0:30,0033 >> >> ... but nothing happens. After your patch i got further :-) with echo hello23 | jsr -v -v vcan0:20,3333 30 i got with candump this: vcan0 18333020 [8] 68 65 6C 6C 6F 32 33 0A i got with 'jsr vcan0:30' this: hell i got with 'jspy -P' this: vcan0:20,03300 30 !6 [8] 68656c6c 6f32330a where i don't know if the output from 'jsr vcan0:30' is correct ?!? When extending the payload data with 'echo hello234 | jsr -v -v vcan0:20,3333 30' 'candump -td' tells me: (022.199332) vcan0 18EC3020 [8] 10 09 00 02 02 00 33 00 (000.000046) vcan0 18EC2030 [8] 11 02 01 FF FF 00 33 00 (000.000034) vcan0 18EB3020 [8] 01 68 65 6C 6C 6F 32 33 (000.000008) vcan0 18EB3020 [3] 02 34 0A (000.000055) vcan0 18EC2030 [8] 13 09 00 02 FF 00 33 00 with 'jspy -P' : vcan0:20,03300 30 !6 [9] 68656c6c 6f323334 0a But with 'jsr vcan0:30' i still got this: hell --- The questions: 1. Is the behaviour of 'jsr vcan0:30' correct like this? 2. Can you tell me, what's going on the second candump? I expected something like this BAM (628.395620) vcan0 18ECFF20 [8] 20 09 00 02 FF 00 33 00 (000.050093) vcan0 18EBFF20 [8] 01 68 65 6C 6C 6F 32 33 (000.050091) vcan0 18EBFF20 [3] 02 34 0A which i got, when invoking 'echo hello234 | jsr -v -v vcan0:20,3333' (without giving an explicite destination address). Regards, Oliver _______________________________________________ Socketcan-core mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-core
