OK, I see what you mean, the change_button is an input pin of the component, when it is triggered the component will set the changed pin high.
Some days, I wonder why I get out of bed. haha Sorry for all the chatter. Joe ----- On Apr 5, 2017, at 1:48 PM, Joe Hildreth j...@threerivershospital.com wrote: > Sebastian, > > Thanks for the information and the patience with me. In the config created by > stepconf on my machine I see the following in the hal file. > > loadusr -W hal_manualtoolchange > net tool-change iocontrol.0.tool-change => hal_manualtoolchange.change > net tool-changed iocontrol.0.tool-changed <= hal_manualtoolchange.changed > net tool-number iocontrol.0.tool-prep-number => hal_manualtoolchange.number > net tool-prepare-loopback iocontrol.0.tool-prepare => > iocontrol.0.tool-prepared > > So to add the external button, assuming it is on parallel port pin 15 I would > add the following? > > net tool-changed-btn iocontrol.0.tool-changed <= parport.0.pin-15-in > > I thought that there would need to be some separation of the two output pins, > parport.0.pin-15-in and hal_manualtoolchange.changed in order to feed it to > the > input pin iocontrol.0.tool-changed. That is why I thought of using the OR > gate. I was led to this reasoning from the > http://linuxcnc.org/docs/2.7/html/hal/basic-hal.html page with this line ( I > have Marked with ***): > > ============= > A pin can be connected to a signal if it obeys the following rules: > > An IN pin can always be connected to a signal > > An IO pin can be connected unless there’s an OUT pin on the signal > > *** An OUT pin can be connected only if there are no other OUT or IO pins > on > the signal > =============== > > It looks like I didn't quite understand that. > > Joe > > ----- On Apr 5, 2017, at 1:03 PM, Sebastian Kuzminsky s...@highlab.com wrote: > >> On 04/05/2017 09:58 AM, Joe Hildreth wrote: >>> I have a good portion of the manpage written for this user component, >>> but have a question. >> >> Great! >> >> >>> If one wanted to use the hal_manualtoolchange.change_button as an >>> external button, should this input be ORed with the >>> hal_manualtoolchange.changed and then the OR output sent to >>> iocontrol.0.tool-changed this giving the option of either the dialog >>> continue button OR an external button? >> >> No. >> >> hal_manualtoolchange treats its .change_button input pin exactly like it >> treats a click on the button in its GUI window. >> >> The intended use of that pin is for if you want a physical button on the >> machine's control panel to let the operator signal completion of a >> manual tool change. You'd bring the physical button into HAL (via a >> parport input pin or a hostmot2 gpio input or similar), and wire it >> directly to the .change_button input. Then when LinuxCNC executes M6, >> hal_manualtoolchange will pop up its GUI window, and *either* a mouse >> click in the GUI or pushing the physical button will signal to >> hal_manualtoolchange that the tool change is complete. >> >> >> -- >> Sebastian Kuzminsky > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
