Matrix Keyboard controlling LinuxCNC

I've been thinking about this too.
I'm not shure what to do with that LCD. What do you have in mind?

See this thread.
forum.linuxcnc.org/41-guis/50116-new-ard...d-usb-pendant#281283

I think what would be doable is showing the current positions for XYZ for example or Spindle Speed and such.

Also to keep this thread to the topic of Matrix Keyboards we should propably switch to this thread forum.linuxcnc.org/show-your-stuff/48630-arduino-io-expansion

Sorry for the late reply, I've been a bit busy with work lately, I don't have time for further testing, it's China's National Day in a few days, I may need to update a few days later. Sorry again.

I may not be able to continue until after October 15th, but in any case, I will keep updating you on the latest developments and sending you a test video

     I have already tried all the functions of this application. But with the latest version the Latching Potentiometers / Selector Switches are not working for me, they always appear at zero:
Type  Dir         Value  Name   
 4  s32   OUT             0  arduino.LPoti.3.out     
4  s32   OUT             0  arduino.LPoti.4.out     
4  s32   OUT             0  arduino.LPoti.5.out     
4  s32   OUT             0  arduino.LPoti.6.out     
4  float OUT          497  arduino.ain.7     
4  float OUT          437  arduino.ain.8     
4  s32   OUT             0  arduino.counter.0     
4  s32   OUT             0  arduino.counter.1     
4  s32   OUT             0  arduino.counter.2     
4  bit   OUT          TRUE  arduino.din.29     
4  bit   OUT          TRUE  arduino.din.30   
 4  bit   OUT          TRUE  arduino.din.31   
 4  bit   OUT          TRUE  arduino.din.32   
 4  bit   OUT          TRUE  arduino.din.33     
4  bit   OUT          TRUE  arduino.din.34     
4  bit   OUT          TRUE  arduino.din.35     
4  bit   OUT          TRUE  arduino.din.36     
4  bit   OUT          TRUE  arduino.din.43     
4  bit   OUT          TRUE  arduino.din.44
In the previous version they worked for me without problem.I also found that the Trigger INPUTS (SINPUTS) inputs always start in the on state (TRUE), I don't know if this is a problem, I think they should start in the off state (FALSE)I attach my ,ini and .py files to see if the problem is a bad configuration.

Thank you for the feedback. I suspect there is a Bug in the LPoti section.

Not neccessarily related: i found two issues in your config.
1. SetLPotiValue = [1,1,1,1] should be SetLPotiValue = [1,1,2,1], since you entered float values (0.001) etc.

2. somebody else discovered the bug already and reported it back to me:
i didn't think somebody would want encoders and Joystick in one build.
So at this moment encoder 0 is used by the first encoder and if you connect the Joystick to A0, by it too.
Solution right now iis to connect both Joystick axis to Analog inputs with higher number than present Encoders.

So for example you could switch it with two LPotis.

Also i found a bug, i apparently missed to change LPoti to lpoti to have same pin scheme in Hal everywhere. I'll change that too.

Right now i am traveling, so unfortunately you have to wait for my update till monday at least.