Help with XHC-HB04 Wireless Pendant needed

More
01 May 2018 03:43 #109884 by MDM3D
Warning: Spoiler!




Hello, I'm having some trouble getting my XHC-HB04 pendant to work above is the error log that occurs with start-up and I have been able to use the command line to send and receive command to the pendant but best I can tell there is a conflict with a probe pin any help is greatly appreciated. I think that I am almost there. I do have a nice probing page which I added a while ago that may be the part of the problem but would like to keep both the probing tab and the pendant working if possible. Thank you for your time.

File Attachment:

File Name: Mill.hal
File Size:3 KB

File Attachment:

File Name: Mill.ini
File Size:4 KB
Attachments:

Please Log in or Create an account to join the conversation.

More
01 May 2018 08:47 - 01 May 2018 09:22 #109888 by billykid
Hello
I have a working hb04, it does not work because you have two connections to motion probe input
hal: net probe-in => motion.probe-input
is ok
why and already in the ini file:
probe-z = motion.probe-input.
you have to make sure you only have one.
Attachments:
Last edit: 01 May 2018 09:22 by billykid.

Please Log in or Create an account to join the conversation.

More
01 May 2018 14:59 #109912 by MDM3D
So I am unable to have a UI button in axis and a physical button on the HB04 to activate a probe?

Please Log in or Create an account to join the conversation.

More
01 May 2018 15:43 #109919 by billykid
the probe electrically works already, after it must be used with g38.2 for example.

probe-z = halui.mdi-command-06
MDI_COMMAND=o100 call
Attachments:

Please Log in or Create an account to join the conversation.

More
02 May 2018 03:33 - 02 May 2018 03:35 #109995 by MDM3D
billykid, Thank you for your hb04.hal example. That allowed my machine to actually start and I can use my pendant as intended. Awesome! I am starting to understand the .hal files a little better. I have another question though, Where am I supposed to place the subroutine code?

Also can you please explain why
hal: net probe-in => motion.probe-input
means the same thing as
probe-z = motion.probe-input
because I read each line as independent of each other although they obviously interfere with each other?
I had assumed that I could have a bunch of different things look at the same "pin" state at the same time for things like conditional statements........
Last edit: 02 May 2018 03:35 by MDM3D.

Please Log in or Create an account to join the conversation.

More
02 May 2018 07:29 #110001 by billykid
Good ! first of all add this line in section ini

[RS274NGC]
PARAMETER_FILE = linuxcnc.var

SUBROUTINE_PATH = / home / cnc / linuxcnc / nc_files
your path

put o100.ngc in nc_files.

I try to explain myself but it's not my language I'm Italian :-)

net probe-in => motion.probe-input is the link you do not need anything else, after use with g38. *.
you can do operations with the signals first, but the motion component only wants one input.

Please Log in or Create an account to join the conversation.

Time to create page: 0.137 seconds
Powered by Kunena Forum