FOUND it- well, most of the problem. It appears the Wiki itself has an error here! What you need is:
loadusr -W xhc-hb04 -I xhc-hb04-layout2.cfg -H That "xhc-hb04-layout2" is the CONFIG file, not the ini. I believe you can specify it without the file type suffix and it hunts down the .cfg, but if you specify an .ini suffix, it does as ordered and grabs the .ini. An ini file doesn't any info it needs and it'll quietly execute and exit without making any HAL connections. But no errors. http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Using_A_XHC-HB04_Wireless_MPG_Pendant Says "In xhc-hb04.hal you can change your keyboard layout preference: loadusr -W xhc-hb04 -I xhc-hb04-layout1.ini -H" Well that doesn't look right. Like I say, it needs the .cfg, the .ini won't work. I found another web page guide that clued me into the ".cfg" requirement. Danny On 4/20/2016 5:29 AM, Gene Heskett wrote: > On Wednesday 20 April 2016 02:29:18 Danny Miller wrote: > >> It's loading without error. The LCD works, the handwheel does jog >> the axes, and the selector knob does change the axes. But none of the >> buttons function, including the Step Size, so it's stuck moving by >> 0.001". >> >> I have LinuxCNC 2.7.4 and the Linux Preempt-RTK. I did what was >> specified about adding USB permissions. >> >> So 7i92_general_XHC20.ini is the main ini file. I added a >> [XHC_HB04_CONFIG] section which gives setup parameters. I added >> HALFILE = xhc-hb20.hal to the [HAL] section. >> >> xhc-hb20.hal is a renamed copy of a modified xhc-hb04.hal. The homing >> routines don't exist, nor does an A-axis, so that's removed. Loadusr >> got changed to the local name "loadusr -W xhc-hb04 -I >> xhc-hb04-layout20.ini -H" >> >> xhc-hb04-layout20.ini has layout2.inc added into it directly. For >> whatever reason layout2.inc didn't seem to be loading correctly into >> it so I just added it. >> >> The HAL viewer does show there's an XHC section. However (I'm not in >> front of the machine now) IIRC the halui.mdi-command-01 etc didn't >> seem to exist under halui. I found what should have been the STEP++ >> pin but it didn't show TRUE when I pressed it. But I'm not sure how >> that works, if it's a momentary press and I just manually reload the >> HAL status I would probably never catch it. >> >> Thanks, >> Danny > The halmeter is pretty close to real time, so if you can find that > signals name in the show-hal, halmeter can tell you whats going on in > millisecond response times. > > This might be a case for a rockhopper run, but that, by the time it is > blown up enough to be readable, will take posterizer set for 6 to 12 > pages on a complex machine to show it all legibly. That can be a quite > informative troubleshooting tool. Rockhopper has one gotcha, it does > not record and draw, a pin with no target defined. > > And many times, a sudo dmesg -c, start linuxcnc, then a fresh dmesg might > show you errors. All are handy tools. > > Cheers, Gene Heskett ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
