hi Håkan,
> Am 17.08.2016 um 22:22 schrieb Håkan Båstedt <[email protected]>: > > I just got the XHC-HB04 to work on my 3040 milling machine. > > I used the config in sim.axis.xhc-hb04/xhc-hb04-layout2_mm.ini > and in the sim/axis the wheel works but none of the > buttons. When starting machinekit there comes a number of > lines, like > xhc-hb04: found XHC-HB04 device > xhc-hb04: !!! <xhc-hb04.button-goto-zero> pin does not exist, continuing > xhc-hb04: !!! <xhc-hb04.button-half> pin does not exist, continuing > xhc-hb04: !!! <xhc-hb04.button-home> pin does not exist, continuing > > > and so on for all buttons, the rest is not so important. > > This can be traced to the "pin_exists" function in xhc-hb04.tcl > where the output of "show pin" is analyzed and fails because > the syntax is no longer what is expected by the tcl script. > > With that sorted the sim worked. > > Trying to insert this to my machine config, > I had to redo the pin_exists exercise.Then there were a few > duplicate definitions > ""Pin x was already linked to signal y", so removing those > got it finally going. Seems to work fine. > > I think it was a bit too troublesome to set up the pendant > and I have spent a fair amount of time googling this topic, > > What can be done to ease the setup and use of the HB04? > Fixing the tcl script, okay. > There are examples of configs for at least two other pendants > in machinekit.io but that is so different from the hb04 config > files that it is like two different worlds. The tcl script > obscures what is actually needed. Perhaps it would > be better to write a HB04 config example without tcl. yes While I am likely responsible for the halcmd output changes, I feel out of my depth to work on tcl - I cannot even read this stuff, and there is nobody around here who can - also given the popularity of the language it is unlikely we find anybody. Then, the very base of the 'TCL HAL bindings' - basing an API on the parsing the output of a command interpreter designed for interactive use - is hopeless; we might be able to patch things up given a detailed log but this will work only so long and break again. The best long-term solution is to rewrite those scripts in Python - I am happy to help if you want to take it on; in that case I would suggest opening an issue and we go from there - Michael > > > > > > -- > 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. -- 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.
