Greenie problems configuring 6i25 with 7i77, using Granite Devices VSD-E drives

Frankly, the spindle encoder is a longer term project that I'm not worrying about right now. I ran the cable for it and figured I'd get my machine up and running before I do anything else. I don't have a tool changer on my machine and rigid tapping isn't something I regard as a mandatory feature and it is the only thing I can think of, off the top of my head, that will require the direct encoder feedback. So, my first order of business is to get this beast running as a plain old 3 axis CNC.

After I finish that, I need to make my control console. I'm already scratching my head as to what I need there. Clearly start and eStop buttons, possibly a brake enable... But what else? Stuff that isn't used as often can be accessed through mouse input on the screen. I need to start collecting pictures and asking questions about what other people have made and what they did well/poorly.

Once the control console is done, I am thinking about working on a 4th and 5th axis. I've incorporated spaces in my control for amplifiers to that end. And after that, I'll start to think about the spindle encoder.... Or maybe I'll swap those two around. Whatever the case, I don't regard either of these to be pressing issues. I'm more interested in just getting the machine working reliably and then creating a nice control panel.

I am a fan of the Touchy interface, which does everything with one MPG and between 3 and 7 hardware buttons.
linuxcnc.org/docs/2.7/html/gui/touchy.html

This is mine though I now have it full-screen so the system menu bar isn't visible.

I'm presently using Axis because I think that is what people said was the most common. I wanted to minimize confusion with people while asking for help during commissioning of the control. However, I think I'll likely go to Touchy at some point and then, eventually, I want to code some highly customized displays that emulate the Deckel Mode construction found on Deckel Dialog 3 machines.

With Touchy, can you also use a mouse and have dropdown menus (meaning... I know you don't *typically* need one, but does that mean you can't have one?)? I haven't played with it at all so far. In addition, are there any limitations (such as no touch probes or tool zool probes).

I bought a VistaCNC P4SE pendant that was delivered yesterday. That will likely be a major player in setup/jogging. I have to say that I am pleasantly impressed with its construction. I was worried that it would be kind of crappy but it actually feels quite the contrary.

Touchy has no drop-down menus. You can't do anything with it with a mouse that you can't also do with the touch panel.

You can run a simulator with the Touchy GUI without disturbing your existing configs. Just pick it from the config picker.

By default Touchy has no graphical preview. You get used to that, though it is possible to add one.

Had a delay due to work and the VFD problem. I just bought a new one and will look at the old guy later... Anyhow, I have a minor problem with integrating the VistaCNC pendant. This should be an easy one.

I have two HAL files:
hurco.hal:
vc-p4s.hal:
error when starting:
I get the error... I think. I have two things driving the same ping, halui.jog.0.plus. Those are jog-x-pos and jog.0.cont-plus (sourced from vc-p4s.jog.0.plus). My 'I think' is that I know that I have two outputs driving the same pin and that is bus contention; I'm not 100% sure my summary of *what* the two outputs are is correct, so confirmation there would be great.

My bigger problem, though, is how to solve this. It seems reasonable that I should be able to have a button on the control console and the pendant all initiate a jog. In fact, I can see three different jog buttons: the menu, a physical switch on the console, and the physical switch on pendant. But how do I do that? Hmmm... an OR operation? Is this the proper/sanctioned resolution for the case of two buttons?

hurco.hal:
vc-p4s.hal:
Note: at least this compiles, but I have to have that jog.0.plus.sig in there, which has no other use than to avoid an error. That seems suspicious. Also, how does one easily tell what is a pin and what is a signal. They seem rather ambiguous.

I can't say for sure with out seeing your whole halfiles.

But from what you have shown us you could simply do all you have above by just changing the signal names so they are the same.

Hurco hal:
vc-p4s.hal:
All hal pins can only ever be attached to one signal name. Each signal name (jog-x-pos is your signal name) can only have one output pin attached to it, but can be connected to as many input pins as you like.
"halui.jog.0.plus" is an input pin. (it receives info from a hal signal)
"vc-p4s.jog.0.plus" is an output pin (it sends info to a hal signal)
If your signal named "jog-x-pos" is not connected to another output pin (which I can't know without seeing your whole files) the above is all you need.