Simple Remote Pendant errors

Clearly I have no idea what I am doing.

I am (presently) using this tutorial Remote Pendant

I have been struggling with getting any kind of pendant to work. In the incarnation of this attempt I have followed the instructions given within the above link by plugging the code into the custom hal file. The error I received is : custom_postgui.hal:62: Pin 'halui.jog-speed' does not exist

To clarify... the joypad is identified. I do have the loadusr -W hal_input -KRAL Logitech line added to the main Hal file. There is no other logitech items on my system. Also I do have the HALUI = halui line within the .ini file.

In short im debating on shooting the gamepad with the shotgun or waiting to see what you guys have here on solutions. I have attempted to deal with this issue by going with the pncconfig setup yet while it creates the pins hal is very new to me and I am sorting on how to do things with it yet wiring the pins to get the output needed is where my lack of education is. Nevertheless the tutorials such as the one linked above say nothing about defining the pins outside of what is given within that page unless it is an understood thing and not specified.

Any help on what Im missing or a point in the right direction would be grateful even if its just to spend more time learning how to engineer code before I can engineer wood.. thanks guys.

Your best bet is to post the relevant files, to let others have a quick look through.

A side note:

I copied the hal file where I had done the work and saved it elsewhere so I could bring it back in later, then wiped the original clean for another attempt.

With the custom hal clean I went back into the pncconfig and remapped the pins for each axis. Upon starting linuxcnc I see the pin and signals including the job-x-neg and ect... are showing true when a button is pressed.

Therefore correct me if I am wrong, what I would need to do is to go into custom hal, use the pins created and set jogspeed and or there I get lost.

I know there is more than one way to do this. My stubbornness says so LOL!

Sure thing brother... Not much there other than whats in the link above.

The ini file would help as well

Sorry I was in a rush. Had to pick up the family from the airport. I have the ini and also error message here.

I did manage to do some late night reading and I am better understanding how Hal communicates. From the error it would seem that the pin is not identified properly. So when you see this correct me if I am wrong, but to use the code in the above linked example I would need to go back and properly identify the pin or button on the controller.

Question... can this be done inside of the same custom hal file or does this need to be done through the main hal file of the machine?

error msg below:

Print file information:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc/modules
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/share/linuxcnc/tcl/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
LINUXCNC - 2.8.0~pre1
Machine configuration directory is '/home/jeff/linuxcnc/configs/machinetest'
Machine configuration file is 'machinetest.ini'
INIFILE=/home/jeff/linuxcnc/configs/machinetest/machinetest.ini
VERSION=1.0
PARAMETER_FILE=linuxcnc.var
TASK=milltask
HALUI=halui
DISPLAY=axis
COORDINATES=XYZ
KINEMATICS=trivkins coordinates=XYZ
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
Found file(REL): ./machinetest.hal
Found file(REL): ./custom.hal
Starting TASK program: milltask
Starting DISPLAY program: axis
Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script
Killing task linuxcncsvr, PID=4135
Killing task milltask, PID=4180
task: 144 cycles, min=0.000020, max=0.014572, avg=0.009043, 0 latency excursions (> 10x expected cycle time of 0.010000s)
hm2: loading Mesa HostMot2 driver version 0.15
hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2
hm2_eth: 10.10.10.10: Hardware address: 00:60:1b:10:41:ba
hm2_eth: discovered 7I76E-16
hm2/hm2_7i76e.0: Smart Serial Firmware Version 43
Board hm2_7i76e.0.7i76.0.0 Hardware Mode 0 = standard
Board hm2_7i76e.0.7i76.0.0 Software Mode 0 = io_spin
Board hm2_7i76e.0.7i76.0.0 Software Mode 1 = io_ana_spin
Board hm2_7i76e.0.7i76.0.0 Software Mode 2 = io_enc_ana_spin_fv
hm2/hm2_7i76e.0: 51 I/O Pins used:
hm2/hm2_7i76e.0: IO Pin 000 (P1-01): StepGen #0, pin Direction (Output)
hm2/hm2_7i76e.0: IO Pin 001 (P1-14): StepGen #0, pin Step (Output)
hm2/hm2_7i76e.0: IO Pin 002 (P1-02): StepGen #1, pin Direction (Output)
hm2/hm2_7i76e.0: IO Pin 003 (P1-15): StepGen #1, pin Step (Output)
hm2/hm2_7i76e.0: IO Pin 004 (P1-03): StepGen #2, pin Direction (Output)
hm2/hm2_7i76e.0: IO Pin 005 (P1-16): StepGen #2, pin Step (Output)
hm2/hm2_7i76e.0: IO Pin 006 (P1-04): StepGen #3, pin Direction (Output)
hm2/hm2_7i76e.0: IO Pin 007 (P1-17): StepGen #3, pin Step (Output)
hm2/hm2_7i76e.0: IO Pin 008 (P1-05): StepGen #4, pin Direction (Output)
hm2/hm2_7i76e.0: IO Pin 009 (P1-06): StepGen #4, pin Step (Output)
hm2/hm2_7i76e.0: IO Pin 010 (P1-07): Smart Serial Interface #0, pin TxData0 (Output)
hm2/hm2_7i76e.0: IO Pin 011 (P1-08): Smart Serial Interface #0, pin RxData0 (Input)
hm2/hm2_7i76e.0: IO Pin 012 (P1-09): IOPort
hm2/hm2_7i76e.0: IO Pin 013 (P1-10): IOPort
hm2/hm2_7i76e.0: IO Pin 014 (P1-11): Encoder #0, pin Index (Input)
hm2/hm2_7i76e.0: IO Pin 015 (P1-12): Encoder #0, pin B (Input)
hm2/hm2_7i76e.0: IO Pin 016 (P1-13): Encoder #0, pin A (Input)
hm2/hm2_7i76e.0: IO Pin 017 (P2-01): IOPort
hm2/hm2_7i76e.0: IO Pin 018 (P2-14): IOPort
hm2/hm2_7i76e.0: IO Pin 019 (P2-02): IOPort
hm2/hm2_7i76e.0: IO Pin 020 (P2-15): IOPort
hm2/hm2_7i76e.0: IO Pin 021 (P2-03): IOPort
hm2/hm2_7i76e.0: IO Pin 022 (P2-16): IOPort
hm2/hm2_7i76e.0: IO Pin 023 (P2-04): IOPort
hm2/hm2_7i76e.0: IO Pin 024 (P2-17): IOPort
hm2/hm2_7i76e.0: IO Pin 025 (P2-05): IOPort
hm2/hm2_7i76e.0: IO Pin 026 (P2-06): IOPort
hm2/hm2_7i76e.0: IO Pin 027 (P2-07): IOPort
hm2/hm2_7i76e.0: IO Pin 028 (P2-08): IOPort
hm2/hm2_7i76e.0: IO Pin 029 (P2-09): IOPort
hm2/hm2_7i76e.0: IO Pin 030 (P2-10): IOPort
hm2/hm2_7i76e.0: IO Pin 031 (P2-11): IOPort
hm2/hm2_7i76e.0: IO Pin 032 (P2-12): IOPort
hm2/hm2_7i76e.0: IO Pin 033 (P2-13): IOPort
hm2/hm2_7i76e.0: IO Pin 034 (P3-01): IOPort
hm2/hm2_7i76e.0: IO Pin 035 (P3-14): IOPort
hm2/hm2_7i76e.0: IO Pin 036 (P3-02): IOPort
hm2/hm2_7i76e.0: IO Pin 037 (P3-15): IOPort
hm2/hm2_7i76e.0: IO Pin 038 (P3-03): IOPort
hm2/hm2_7i76e.0: IO Pin 039 (P3-16): IOPort
hm2/hm2_7i76e.0: IO Pin 040 (P3-04): IOPort
hm2/hm2_7i76e.0: IO Pin 041 (P3-17): IOPort
hm2/hm2_7i76e.0: IO Pin 042 (P3-05): IOPort
hm2/hm2_7i76e.0: IO Pin 043 (P3-06): IOPort
hm2/hm2_7i76e.0: IO Pin 044 (P3-07): IOPort
hm2/hm2_7i76e.0: IO Pin 045 (P3-08): IOPort
hm2/hm2_7i76e.0: IO Pin 046 (P3-09): IOPort
hm2/hm2_7i76e.0: IO Pin 047 (P3-10): IOPort
hm2/hm2_7i76e.0: IO Pin 048 (P3-11): IOPort
hm2/hm2_7i76e.0: IO Pin 049 (P3-12): IOPort
hm2/hm2_7i76e.0: IO Pin 050 (P3-13): IOPort
hm2/hm2_7i76e.0: registered
hm2_eth: HostMot2 ethernet driver unloaded
hm2: unloading
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

Debug file information:
Note: Using POSIX realtime
note: MAXV max: 1.000 units/sec 60.000 units/min
note: LJOG max: 1.000 units/sec 60.000 units/min
note: LJOG default: 0.250 units/sec 15.000 units/min
note: jog_order='XYZ'
note: jog_invert=set([])
custom_postgui.hal:62: Pin 'halui.jog-speed' does not exist
4135
PID TTY STAT TIME COMMAND
4180
PID TTY STAT TIME COMMAND
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime

Kernel message information:
[ 0.000000] Linux version 4.8.11-rt7 (jeff@cnc) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) ) #1 SMP PREEMPT RT Sun Apr 1 17:21:02 EDT 2018

****** Attempt number 2 ****** this is unrelated from the above method of attempt.
This attempt is strictly using the Pncconfig to set up the gamepad as a pendant. I have attatched the main hal file, the ini seems to be identical in every respect as to the one I already posted above.

There are no errors when I attempt to move using this method. Halshow, meter and so forth shows that the pin is wired to the proper places via the config. The problem simply is no motion is taking place on the machine. This may be a method that is easier to solve than the first attempt I have detailed above.

While the controller shows to be working within the software Halshow, there simply is no movement on the physical machine. Any ideas for this one? Or would it be best to abort this method entirely and stay with attempt 1?

Update.... I managed to go back to the first method I attempted to use in the original post and went back to square one. I redid everything and entered all the code again connecting it as described in the wiki tutorials. Upon starting linuxcnc NO ERRORS!!! YAY!!! But....

Still Nothing Moves on the physical machine at all... just like the second attempt in the post directly above this one with option 2. Its dead in the water. I push the number in order to get movement, then move the stick and nothing.

Halshow indicated everything is working properly but its a no go.

So if someone wants to try and simulate whats going on I will try to put the folder with all the main files here in this post. No cigars for me tonight.

Update: I still want to figure out what is going on with this and find the solution. It will not leave me alone until I find it and learn this and or what is taking place.

Nevertheless in the meantime until I do I am using a cheat and have success using a gamepad via qjoypad. It simply maps the gamepad buttons to emulate the predefined keyboard keys which linuxcnc uses. Still for me this is not the ultimate solution. I am one of those who wants to know how and why things work, or dont work.

Its not over.

Lets go back to the original hal listing:

custom_postgui.hal:62: Pin 'halui.jog-speed' is an indication that there is a syntax error.

But it looks OK...........

Comment out that line and see if it throws an error on the next line containing a halui string