Advanced Search

Thank you very much for your answer. I will try, but all day today I tried to change a value in the gladevcp panel from the g code content. I researched a lot, tried a lot, but I was not successful.
example
test.ngc:
#<_hal[testpanel.hal_label]> = 1.0 it's doesn't work
#<testpanel.hal_label> = 1.0 it's doesn't work
#<_hal[testpanel.hal_label]> = #100 it's doesn't work
#100 = #<_hal[testpanel.hal_spinburon-fl]> I think its work

There is no problem reading the variable, but I could not manage to change the value of the variable.

ich habe in der letzten Anwort ein screen von probe-tab eingefügt,
schau mal da drauf, da ist Halui = halui zu sehen.

EBEN, Du sollst nicht 'Halui = halui' reinschreiben sondern 'HALUI = halui'
Also beim ersten ALLES GROSSBUCHSTABEN und beim zweiten alles kleinbuchstaben!

i actually solved the issue by triggering 2 successive relays to trigger the arc instead of just one. while the first is running field voltage, the other is running 230vac.

the whole system is better after reducing pingtimes.

the table+generator+copper bar is on one ground while the cnc is on another, but this didn't help with the error. the relays did.

I would love to see a video of the 8 spindles moving about.

If that counts, to me the "odd machine" is my small gear hobber. After buying a 2nd hand hob and trying to use it I fell into the rabbit hole.
There should be some effort to make it more userfriendly. I still have to change some parameters in the .hal to get it to work, based on the gear at hand. 

Andy Pugh provided the necessary help to get it up and running.
 


 

andy@file03:~/linuxcnc/configs/my_LinuxCNC_machine_QTDragon$ cat pause_pin.py
print('\nUser command file for pause pin found\n')

# import the handlerfile to get reference to it's libraries.
# use <screenname>_handler
import qtdragon_hd_handler as SELF

# needed to instance patch
# reference: ruivieira.dev/python-monkey-patching-for-readability.html
import types

############################################
# add new functions for new HAL pins to call
############################################

# external pin will call this
def external_pause_changed(data):
    # only if runnung a program
    if not SELF.STATUS.is_auto_running():
        return
    # only on true state of pin
    # mean can only pause with the external pin
    # toggle might be nicer...
    if data:
        # set pause button
        self.w.action_pause.setChecked(data)
        self.w.action_pause.clicked.emit(data)

        # set spindle pause button
        self.w.btn_spindle_pause.setChecked(data)
        self.w.btn_spindle_pause.clicked.emit(data)

# unpause machine if external offsets state is false
def external_offset_state_changed(data):
    # only if running a program
    if not SELF.STATUS.is_auto_running():
        return
    # only if machine in on
    if not SELF.STATUS.machine_is_on():
        return
    # only if pin is false
    if not data:
        print('automatic unpause')
        # set pause button
        self.w.action_pause.setChecked(data)
        self.w.action_pause.clicked.emit(data)

###############################################
# add hook to make HAL pins at the right time
###############################################

# add a HAL pin with a call back
def after_override__(self):
    try:
        pin = SELF.QHAL.newpin("external-pause", SELF.QHAL.HAL_BIT, SELF.QHAL.HAL_IN)
        pin.value_changed.connect(external_pause_changed)

        pin = SELF.QHAL.newpin("external-eoffset-state", SELF.QHAL.HAL_BIT, SELF.QHAL.HAL_IN)
        pin.value_changed.connect(external_offset_state_changed)
    except Exception as e:
        print(e)

# Here we are instance patching the original handler file to add a new
# function that calls our new function (of the same name)
# defined in this file
self.after_override__ = types.MethodType(after_override__, self)

#########################################
# override disable_spindle_pause method
#########################################
def disable_spindle_pause(self):
    if self.w.action_pause.isChecked():
        # set spindle pause button
        self.w.btn_spindle_pause.setChecked(True)
        self.w.btn_spindle_pause.clicked.emit(True)

# instance patch voodoo
self.disable_spindle_pause = types.MethodType(disable_spindle_pause, self)

#####################################
# override pause key binding method
#####################################
def on_keycall_pause(self,event,state,shift,cntrl):
    if state and SELF.STATUS.is_auto_mode() and self.use_keyboard():
        if not SELF.STATUS.stat.paused:
            external_pause_changed(state)
        else:
            self.w.btn_spindle_pause.setChecked(False)
            self.w.btn_spindle_pause.clicked.emit(False)

# instance patch voodoo
self.on_keycall_pause = types.MethodType(on_keycall_pause, self)

##############################################
# modify stop button to call an MDI command
##############################################
self.w.action_abort.setProperty('abort_action',False)
self.w.action_abort.setProperty('true_python_cmd_string', 'ACTION.ABORT();ACTION.CALL_INI_MDI(0)')
 

Yes, the 7i76 is on P1 on both the 5i25 and the 7c81.

I ran pncconf on the 5i25 again. I don't know what I did earlier but now the stepgens are back on 0..2. So, obviously I screwed up something earlier.

What about the "sets" vs "setp" in
" sets spindle-at-speed true"

Please remind (show) me of the pause pin code you are using.

Not really of any use for the issue, But if I am afraid to brick the machine, I just put a 2nd hard drive in, swap the physical connectors and start playing. Not much risk and a new SSD cost me 15Euros.
I use a USB enclosure to transfer files between the "experimental" and the "working" system.

Thanks PCW, I found those 24/5v switches, now I have movement. Just a couple of other issues to sort out now

Thank you for the tips. Would you be able to help me with a tip or best of all give examples of how to do it, create a working configuration. Is the file I have good for configuration?

Thanks guys. I was following Andys instructions, and didn't rename all the signals names, as I figured the more I changed the more I would screw up, but it didn't help and I still ended up tied in knots.

Is switchkins useable with LinuxCNC 2.7? I have never updated the Maho to a Joints based version, as I am afraid of breaking a working system. I have that gearbox comp working and am loath risking bricking the machine.
Cheers,
Mark

Is the 7I76 connected to P1?
Did you check the stepgens?
 (stepgens on P1 would be 0..4)

Couple more questions/observations
I see this line in both the 5i25 .hal file and the 7i76e .hal file
sets spindle-at-speed true

Is sets correct or should it be setp?

In the 5i25 configs it starts the x-axis with stepgen.05
but in my 7i76 config it starts the x-axis with stepgen.00
What should I use with the 7c81 configs?

To answer your last question, yes
it reports boardname 7c81
9k gates
FPGA pins 144 and the rest of the info looks good to me (10 stepgens)

This 8 spindle gang router with 8 independent Z axis (using closed loop stepper motors), tandem servos for the Y axis gantry, and a servo on they X axis.
 
This machine has evolved a bit over time.  It was my very first Linuxcnc(EMC2) retrofit.  I have shared some details of it through the years.  Here is a link to what it looked like when I was first setting it up on Linuxcnc.
forum.linuxcnc.org/38-general-linuxcnc-q...-help?start=50#11052
The machine originally only had 3 joints, with a single servo moving a large (2ft x 8ft) aluminum plate up and down via a centrally mounted lead screw.  All 8 spindles were bolted to that plate with a hand actuated screw to fine tune each spindle's depth.  The Y axis was moved by a set of helical rack and pinion gears on each end of the gantry, connected together by a 12ft long torque tube drive shaft, then a 12:1 belt reduction to the servo motor.  The X axis was driven by a servo/lead screw combo.  After 20years of use all of the linear components needed refreshed, so we decided to redesign most of it.

X axis received the least change, changing from a high lead lead screw connected to the servo via a belt reduction, to a new 25mm x 5mm lead ball screw directly coupled to the servo, and new linear ways.

Y axis, got new larger linear ways, and replaced the rack and pinions with two 25mm x 10mm lead ball screws and 2:1 belt reduction to the old Y and former Z servos.

For the Zs, I removed the large 3/4inch thick by 2ft x 8ft plate, cut off 8 pieces 5inch x 24inch and milled them to mount a pair of linear ways and a ball screw for each spindle and a NEMA 23 closed loop stepper motor for each.
Here is a link to a Google photo album containing some photos of the pieces I milled for each of the 8 Z-axis joints.
photos.app.goo.gl/Tx2oYkS272xBUMvZ7

Then I'm attaching a copy of my config directory so others can see how I implemented the individual Z axis joints.  The Z axis is set up as a dummy master joint that automatically homes.  Each spindle joint is set up as an "extra" joint.  There is a GladeVCP panel that lets the operator enable and disable each of the spindles.  When a spindle is enabled, that spindle's Z-joint is connected to the dummy master's position plus a tool offset.  When it is disabled the spindle's joint is moved back up to it's home position.  This way only the spindles actually being used are ever moved with the Z axis. 

There are also buttons on the Glade panel for tool probing routines for each of the spindle Z-axis.  These disable all of the other spindle Z-axis and enable the one being probed, then sets the tool offset for that spindle according to the probe results.

Then I created a GladeVCP tab window for displaying and manipulating the tool offsets for each of the spindles.
 

 
 

ich habe in der letzten Anwort  ein screen von probe-tab eingefügt,
schau mal da drauf, da ist Halui = halui zu sehen.

ich glaube wir kommen so nicht weiter..

viele grüße und danke

karlhe