Jin^eLD reported on IRC that the command to launch the tiny.xml PyVCP example did not work. If using halcmd instead of halrun -I it does work. halrun with the -I flag should be the same as halcmd (if I understand it correctly) but it does not seem to work. This may be a bug in halrun …
评论 (3)
#2 – KurtJacobson 于 2018-08-10
@SebKuzminsky It does not seem to make any difference if LCNC is running or not.
With LCNC running:
“`
kurt@TC0:~$ halrun -I loadusr pyvcp -c mypanel tiny.xml
halrun: too many arguments
Without LCNC running:
``
kurt@TC0:~$ halrun -I loadusr pyvcp -c mypanel tiny.xml
halrun: too many arguments
This seems to work fine either way:
halcmd loadusr pyvcp -c mypanel tiny.xml`
#3 – SebKuzminsky 于 2018-08-10
Heh, you’re right, that halrun command is just totally broken.
halcmd loadusr works without the realtime environment loaded, I guess because it doesn’t use realtime. halcmd loadrt only works if the realtime env is started (for example via
#1 – SebKuzminsky 于 2018-08-10
halrunstarts the realtime environment (including HAL), whilehalcmddoes not. Sohalrunwill work if LinuxCNC is not running, andhalcmdwill work if LinuxCNC is running. Maybe the docs should mention both possibilities?