> -----Original Message----- > From: Dewey Garrett [mailto:[email protected]]
> When using LIB:xhc-hb04.tcl, the loadusr command > is created automatically (so the loadusr directive > should *not* be included in user hal files): > > set cmd "loadusr -W xhc-hb04 $dashx $dashs -I $cfg -H" > > Ref(2.7): https://github.com/LinuxCNC/linuxcnc/blob/2.7/lib/hallib/xhc- > hb04.tcl#L485 > > A recommended way to learn about usage is to run > one of the provided sim configs *first* and study > the ini file (example for 2.7): > > https://github.com/LinuxCNC/linuxcnc/blob/2.7/configs/sim/axis/xhc- > hb04/xhc-hb04-layout2.ini Thank you. I did spend a lot of time trying to figure out the .ini file. But going to the doc file for xhc_hb04 and finding instructions for the .ini file and loadusr and then being redirected to, in effect, study a 565 line tcl program to learn how have a connection is probably not appropriate for a beginner. In addition to set msg "$msg Are permissions correct?\n\n" line #489 this next statement would have helped a lot since it appears that a running instance of xhc_hb04 is what causes that failure. set msg "$msg The config .hal should not contain loadusr -W xhc-hb04 ... \n\n" > > > If you have a Github account then you can edit the text in the web > > interface and create a pull request from there. You should make sure > > that you have selected the 2.8 branch before starting the edit. (Or > > maybe even the 2.7 branch) When you examine the two sets of documents in detail the rules like /etc/udev/rules.d/99-xhc-hb04.rules Is different in the README line #66 with "With a deb install, the rules file is installed as /lib/udev/rules.d/99-xhc.rules" specified instead. Which is it? My eyes literally glossed over the /lib/ instead of the /etc/ when I read that. I'll have to check if I have something in /lib. > > When making improvement pull requests, please note > that there are numerous differences in 2.7 and 2.8 > due to support of joints/axes updates. It will be a while before I get to that. I'm still trying to figure out what the "1/2" button on the pendant does and how to assign it to something. I suspect what perhaps isn't needed as much is an update to the README file etc. but a simple tutorial on how to install and connect a basic pendant with simple macros. They are there (sort of) even videos for MACH3 but far less for LinuxCNC. The other forums for LinuxCNC have lots of hits on people having trouble. But those tend, as usual, not to summarize a solution. Instead they have a suggestion. And then, if there is a reply, it's "Thanks that worked" and then nothing... What worked isn't clear. > -- > Dewey Garrett However, thank you for your work in creating the .tcl program. Eventually I'll understand how that relates to a being a xhc-hb04.hal file referred to in the documentation file. But I never made the connection that it is sort of the same. The syntax of the commands didn't match what was created with the "stepconf" program. And that's where I became confused. I'm going to guess here that the AXIS user interface starts by reading the appropriate .ini file on start up. If it sees a .hal file it reads it as a series of commands or sets up variables and constants. If it sees a .tcl file it runs it like a subroutine of the AXIS user interface code replacing the statements like, for example, net estop-ext => charge-pump.enable which are in effect created by 'makenet'? I come from the C, Pascal, AlgolW world where there's a compile/link/load (or program UV-EPROM/FLASH or read from disk). The idea of loading source code and executing it during runtime is rather foreign to me. John Dammeyer _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
