Greetings!
I have a VistaCNC P4-S(E) CNC Control Pendant for LinuxCNC. Following the instructions I get it t work fine w/ PathPilot.
The thing is, part of the instructions are to update the postgui_tormach_mill.hal file with some custom code. After the latest update, I had to redo the changes to postgui_tormach_mill.hal, which makes me believe that after each PathPilot update I’ll have to reapply the changes unless I can figure out some other way.
Has anyone else encountered this problem? If so, did they figure out a way to have changes they make to postgui_tormach_mill.hal persist across PathPilot updates?
Yes, this is expected and applies to most changes that people choose to make to pathpilot. While I don’t pretend to fully understand the update system, I’ve seen enough of the file structure to know that every new version creates a new folder with the version number.
Based on that, and the need to reapply changes after every version, I suspect that each update just unpacks new versions of the same files in the new folder. Somewhere, there must be a primary instruction that looks for the latest release number and loads from that folder, ignoring all others on the drive.
I have seen a few bits of information scattered around the web that people have found a way to launch an additional process from within that primary instruction to copy their changes into the new version automatically but that requires additional changes and coding that I’m not familiar with. David Loomes of xoomspeed might be able to help you there.
Has anyone tried this pendant on a Slant Pro 15L