[LinuxCNC/linuxcnc PR#480] docs: fix command for launching pyvcp example

未分类 bolang 5个月前 (10-15) 31次浏览

Issue #480 | 状态: 已关闭 | 作者: KurtJacobson | 创建时间: 2018-08-10


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)

#1 – SebKuzminsky 于 2018-08-10

halrun starts the realtime environment (including HAL), while halcmd does not. So halrun will work if LinuxCNC is not running, and halcmd will work if LinuxCNC is running. Maybe the docs should mention both possibilities?


#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


原始Issue: https://github.com/LinuxCNC/linuxcnc/pull/480

喜欢 (0)