2011/1/15 Oliver Hartkopp <[email protected]>
> On 15.01.2011 18:26, Wolfgang Grandegger wrote:
> > On 01/15/2011 06:18 PM, Oliver Hartkopp wrote:
> >> On 14.01.2011 09:35, Heinz-Jürgen Oertel wrote:
> >>> Am Freitag, 14. Januar 2011, 07:44:18 schrieb Oliver Hartkopp:
> >>>> e.g. try to use candump or cansend without commandline parameters (or
> with
> >>>> '-?')
> >>>
> >>> according to GNU guidelines and also POSIX
> >>> it should be '--help' (or '-h')
> >>>
> >>> Heinz
> >>
> >> Yes. Good point.
> >>
> >> Will add '-h' option to all canutils that are currently only supporting
> '-?'
> >
> > Or even better, if an *invalid* option is specified, and error message
> > and the usage string should be printed out.
>
> I checked that any indeed this is already the case ...
>
> So i finally wonder about the problems Willy got when invoking 'cansend -h'
> :
>
> hartko@host:~$ cansend -h
> Usage: cansend <device> <can_frame>.
>
It would have helped if was the same result as a mismatch canframe arguement
arguments :
Wrong CAN-frame format!
Try: <can_id>#{R|data}
can_id can have 3 (SFF) or 8 (EFF) hex chars
data has 0 to 8 hex-values that can (optionally) be seperated by '.'
e.g. 5A1#11.2233.44556677.88 / 123#DEADBEEF / 5AA# /
1F334455#1122334455667788 / 123#R for remote transmission request.
After having use those tools I can say they are really great. In a very
simple way I can do things that would require a can analyser. I am thinking
about embeding them onto my target for developement and integration works.
You really should spend some time into documenting this, because they are
very usefull.
>
> Regards,
> Oliver
>
_______________________________________________
Socketcan-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/socketcan-users
