Tried again with halcmd verbosity turned up to maximum:
machinekit@beaglebone:~/grinder$ halrun -I -V
msgd:0 stopped
rtapi:0 stopped
hal_xinit:68 HAL: initializing component 'halcmd31844' type=2 arg1=0
arg2=0/0x0
hal_xinit:68 HAL: initializing component 'hal_lib31844' type=4 arg1=0
arg2=0/0x0
halcmd:
halcmd: loadrt hal_bb_gpio output_pins=807
<stdin>:2: insmod failed, returned -1:
rtapi_rpc(): reply timeout
See /var/log/linuxcnc.log for more information.
halcmd:
I got two additional debugging messages during halcmd startup.
ZERO additional debugging messages after the loadrt command.
ZERO additional messages in the log.
I think part of the linuxcnc->machinekit fork was to change
halcmd from an ordinary program to a client/server thing.
Apparently the -v and -V options aren't passed to the server.
So they are essentially useless, but still listed in the man page.
Yet another case of programming without documenting.
If the BBG + LCD wasn't such a nice little platform this is the
point where I'd throw up my hands in frustration and go back
to LinuxCNC...
--
John Kasunich
[email protected]
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
