Please Help - How to Configure a 5 Axis Head-Head

There is voluminous documentation of QTVCP in the V 2.9 docs which will get you going editing panels using qtdesigner. 

As for the spindle issue, it looks like you are missing a fair bit in your hal file. Something probably went wrong when you created the basic config using pncconf.
I'm not familiar with that particular board but maybe this thread helps:
forum.linuxcnc.org/27-driver-boards/4603...n-tool-7i96s-spindle

Aciera
Okay, did that, now looks like I am getting python syntax errors, missing parenthesizes.  I have added image.  So maybe we are getting further along the program. Fixing those now, will report back.  

Also wanted to mention that it appears that postgui is pointing towards postgui_call_list.hal.  I placed the postgui verser code in custom_postgui.hal.  Should I change something here?


Rodw
I attempted qtdragon and got an error.  Image attached.  It looks like it cannot find b.  Assuming that is b axis.  Qtdragon explicitly states it is for 3 and 4 axis, so maybe it is lost with trying to find the b axis? 

IronManDylan wrote:

Also, completely different topic for a second..

I just tried turning my spindle on using LCNC and could not (realized I hadn't tried that yet so just made an attempt).  I don't think I have a pin wired for spindle in HAL.  Though there isn't really a pin number for the Mesa 7i96s.  It's called SPINDLE -, SPINDLE +, SPINDLE OUT.  It has been a minute since I physically wired it, but I am pretty darn sure I wired it correctly. Does anyone know what I need to change in HAL to get it moving? Here is my HAL stuff related to spindle as it is right now:

#*******************
# SPINDLE
#*******************
setp pid.s.Pgain [SPINDLE_0]P
setp pid.s.Igain [SPINDLE_0]I
setp pid.s.Dgain [SPINDLE_0]D
setp pid.s.bias [SPINDLE_0]BIAS
setp pid.s.FF0 [SPINDLE_0]FF0
setp pid.s.FF1 [SPINDLE_0]FF1
setp pid.s.FF2 [SPINDLE_0]FF2
setp pid.s.deadband [SPINDLE_0]DEADBAND
setp pid.s.maxoutput [SPINDLE_0]MAX_OUTPUT
setp pid.s.error-previous-target true
net spindle-index-enable => pid.s.index-enable
net spindle-enable => pid.s.enable
net spindle-vel-cmd-rpm => pid.s.command
net spindle-vel-fb-rpm => pid.s.feedback
net spindle-output <= pid.s.output
# ---setup spindle control signals---
net spindle-vel-cmd-rps <= spindle.0.speed-out-rps
net spindle-vel-cmd-rps-abs <= spindle.0.speed-out-rps-abs
net spindle-vel-cmd-rpm <= spindle.0.speed-out
net spindle-vel-cmd-rpm-abs <= spindle.0.speed-out-abs
net spindle-enable <= spindle.0.on
net spindle-cw <= spindle.0.forward
net spindle-ccw <= spindle.0.reverse
net spindle-brake <= spindle.0.brake
net spindle-revs => spindle.0.revs
net spindle-at-speed => spindle.0.at-speed
net spindle-vel-fb-rps => spindle.0.speed-in
net spindle-index-enable <=> spindle.0.index-enable
# ---Setup spindle at speed signals---
sets spindle-at-speed true

 

You would have had to specify a PWM output for the spindle for the configuration
utility to make the needed PWM setup and connections. Here are the connections pncconf
creates for a PWM driven spindle:

net spindle-index-enable  =>  pid.s.index-enable
net spindle-enable        =>  pid.s.enable
net spindle-vel-cmd-rpm-abs     => pid.s.command
net spindle-vel-fb-rpm-abs      => pid.s.feedback
net spindle-output        <=  pid.s.output

# ---PWM Generator signals/setup---

setp   [HMOT](CARD0).pwmgen.00.output-type 1
setp   [HMOT](CARD0).pwmgen.00.scale  [SPINDLE_0]OUTPUT_SCALE


net spindle-vel-cmd-rpm     => [HMOT](CARD0).pwmgen.00.value
net spindle-enable      => [HMOT](CARD0).pwmgen.00.enable

You would need to take the errors up with cmorely in the QTVCP section. I did see its 4 axis only but if that's the case, it really needs to support more axes. GUI's should not restrict linuxcnc's feature set to my mind.

You may get better error reports if you run linuxcnc from the command prompt. I use this command a lot to open the last config used.
 

Yes, looks like the python code has not been updated to where it needs to be. If it doesn't work out for you I'll have a look if I can get it working on my test machine tomorrow.

Also wanted to mention that it appears that postgui is pointing towards postgui_call_list.hal.  I placed the postgui verser code in custom_postgui.hal.  Should I change something here?

Should be fine like that.

Aciera
I chased out a bunch of bugs and think I have the python mess handled.  However, I have hit this bug and cannot seem to move past it.  Picture provided.  I do not know where 'probe.toolchange-change' is coming from, have looked through all the hal files.  There is not a "tool change" icon in probe_icon, so it is weird that something is trying to call that.  There were some things I forgot to comment out in main hal file that I updated but did not make a difference.  Have provided zip for reference.

PCW
Okay, I will try that now and report back

Rodw
....I'll try from terminal. 

PCW
I got the following error, image attached.  It appears that [SPINDLE_0]OUTPUT_SCALE is being called but isn't defined anywhere.  If I knew which pin to set it to I would but I don't...

More about spindle...
I commented out that line just to see what would happen and got some weird results.  I used the command m3 sXXXX and the spindle turned on.  But will only turn on to full speed. Even with the command m3 s1, was still spinning at 400hz (max speed).  Is this a scaling issues, or is something wired wrong? 

Another thing that I just thought about, there is not a feedback for spindle speed and my spindle takes a while to spin up, is there a way to set a delay after starting the spindle so that it does not start a cut before raising to full speed? Or is there a good way to feedback spindle RPM? I have a Huanyang Inverter.

Edit: ah, its scaled between 0-1 right now.  m3 s.5 sets speed to 200hz

You would need to add that constant to the spindle section of your ini file