Advanced Search

No that is an error of the logger color formatter. I have pushed a fix for that now.

I would be possible to disable an axis in hal,, the difficulty is returning to LinuxCNC control
without either generating a following error or a dangerous situation where you get a fast
uncontrolled return to the axis position before the axis was disabled.

Thank you that fixed that issue. Now I have an error "custom_postgui.hal pin pyvcp.ztouch does not exist". Im wondering if its not loading the file. z_touch.ngc and ztouch.xml are in my subroutines folder. I have attached them here. 

 

Added video link.

www.youtube.com/shorts/oJdvSVVuDD0

Thank you for your help!
The AX5201 is working fine in my test enviroment. Now I tried to switch to the real cnc machine, which uses an AX5203 with an AX5805 (Safety Drive Option) which is linked to an EL6900 module. Do you have exprience with this modules. Is there a way to use this in linuxcnc and see the TwinSave modules as a Black Box, as long as they are configured correct by TC3?
Is there a chance to bring this up and running?

Hi,
dein Setup passt soweit.
Ein extra Bremswiederstand brauchst du nicht, es sei denn du willst schwere Lasten schlagartig bremsen (Aufzug, Rolltor)
Netzwerkkabel: mindestens CAT6, wenn du Zugriff auf Industriestandart hast, dann die.
Netzwerkkarte: Intelchip und sollte als Ethercat kompatible Hardware gelistet sein.
Passende Netzfilter nicht vergessen.
Encoderkabel + Batterie: noch einer der sich mit dem Homing nicht rumärgern will.

Die Stepperonline Servos sin hier mittlerweile sehr gut erforscht.
Es gibt mehrere Topics mit Hilfestellungen und Beispielkonfigurationen.

My machine is a small horizontal boring machine with three axis DC servos and lead screws, which I would like to change to ball screws.
If I want to operate the machine manually, I simply turn everything off using the red button in axis (F2), but with ball screws I would need to enable/disable single axis using let's say hardware buttons. Would this be possible?
Currently I am using AXIS 2.9.8 with 7i92.
 

Well guess who's back in the news?

Ich habe mich jetzt nochmal writergehend informiert jedoch verstehe ich nicht was in dieser transm.comp immer beschrieben ist oder wie ich das auf meine Zwecke anpasse oder auch in meine config einfüge , ich habe mich ein wenig in classicladder eingelesen was ja an und für sich einer sps Programmierung nahe kommt wo ich mir auch zu helfen wüsste jedoch weiß ich nicht ob ich soetwas mit classicladder darstellen kann ich bin da ratlos . Und zu der skaliererei habe ich auch noch Fragen wie schreibe ich das denn generell richtig mit dem skalieren der +-10v spindel um diese auch im Rechts-und linkslauf benutzen zu können , eventuell kann mir da jemand mal unter die Arme greifen und dabei helfen ? Gruß Tom

With a traveling steady you can set the Z-offset for each tool.  The end of the stock will be the same position from the tool, but the tools will not be the same distance from the steady.

If you need the tools to be right up against the guide bush, then a traveling steady probably isn't what you want.

With a fixed guide bush the W-axis can set the edge (or whatever the control point is) of the tool right up against the bush.  You would touch off each tool just like on a non-bushed lathe, and jog the W-axis until all the tools have the same spacing (use a dowel) from the bush.  All tools would have the same Z-offset, but different W-offsets.

Tool changes would be something like:

• X move to clear the tool
• Z+ to pull stock back in to bush (if needed)
• W+ move away from bush to clear all tools
• X move to next tool
• W- to put new tool at face of bush
• Z- feeds stock out of the bush

Even if you add a Y-axis I think having a W-axis to adjust the Z-offset make sense.  Unless you have that adjustment, you are limited to using the same style or series of toolholder that puts the cutting edge in (more or less) the same Z-location.

Very small variations in Z-location can be dealt with using a Z-offset for each tool, but larger variations will mean some of your tools will not be cutting right at the guide bushing - reducing the benefit of a Swiss arrangement.  A W-axis would solve this  - giving you much more flexibility in tool holder and tool selection.

As far as your parting tool goes, just get a different tool holder. You can get left hand or right hand, and pick from a million insert shapes that gets the tool as close to the guide bush as possible.  You might even be able to flip the holder upside-down and come at the stock from the opposite side - let gravity help clear the chips.  Just try to manage the holder orientation & LH/RH so you don't have to reverse the spindle during the cycle.

My suggestion would be to look for a parting tool holder that has different insert tip geometries available.  Get two of the same holders and use one for parting - maybe with a 5 degree lead to reduce the 'tit' - and use the other holder for partial or full-radius grooving.

I prefer screw-clamp parting/grooving tools.  The holders with inserts that just wedge-in aren't really stable for side-cutting.

You have two [HALUI] section one of which is empty, that could be the issue? what linuxcnc version are you using? I think only recently this has been fixed and properly supported, new parser landed on 11th of April, unless you are using incredibly recent version, your INI with double sections is not well supported

I'm about to cut some parts on some 1"(24mm), so I've been trying out pierce only for the first time.
I am running linuxcnc 2.9, so i think I might be missing some things in the parameters that are in 2.10?
A pierce delay of 1.6 seconds works fine in pierce only mode, but when I switch back to normal, I still have a 1.6 second pierce delay, which is obviously too long.
Is there a way to change the delay without editing/saving the g code file each time? I am using sheetcam to generate the gcode and i assume plasmac is set up for me to use the material files in plasmac, but even if i set up materials in plasmac, wouldn't I still need to edit/save the gcode or material file each pierce only operation?

Is there a way to access the pierce only offset if it's not in the parameters tab?

Trying to get analog jogging working on gmoccapy, linuxcnc 2.9.3 with mesa card.
Have followed a few separate threads and have com up with the following .starting with just the x-axis. The analog out from the mesa is approx 0 to 5v

 loadrt mux2 names=mux2_x,mux2_y,mux2_z
addf mux2_x servo-thread
addf mux2_y servo-thread
addf mux2_z servo-thread

loadrt and2 names=and-jog
addf and-jog servo-thread

loadrt deadzone names=deadzone-x
addf deadzone-x servo-thread

loadrt scale names=scale.x
addf scale.x servo-thread

setp scale.x.offset -1.00
setp scale.x.gain .416
net x-scale <= hm2_7i76e.0.7i76.0.0.analogin0 => scale.x.in
net gate-x-scale <= scale.x.out => mux2_x.in1 
net x-is-homed <= halui.joint.0.is-homed

net machine-is-on <= halui.machine.is-on => and-jog.in0
net x-is-homed => and-jog.in1 
net jog-allowed <= and-jog.out => mux2_x.sel

setp deadzone-x.threshold 0.1
net mux-x mux2_x.out => deadzone-x.in

net jog-x-analog deadzone-x.out => halui.joint.0.analog halui.axis.x.analog
setp halui.mode.manual 1
setp halui.joint.0.select 1

Am getting halui.joint.0.analog going from +1 to -1 ok and seems to be gated correctly if I unhome X.
Was getting
error: command [EMC_JOG_STOP] cannot be executed until the machine is out of E-Stop and turned on
when I didn't have the gating correct so it appears to be getting through to some extent 

I also seem to have a problem wit deadzone as configured above. It is letting through values like .006 when threshold is .1. If I change it to .2 it seems to behave better

The error when one calls a macro like o<x_touch> call keeps appearing
[QTvcp.COMMON.HAL_GLIB][DEBUG] REQUESTED:{'FUNCTION': 'request_macro_call', 'ARGS': 'ini-mdi-cmd-5'} (hal_glib.py:408)
[QTvcp.QTVCP.WIDGETS.ACTION_BUTTON][DEBUG] INI MDI COMMAND #: 5 (action_button.py:717)
[QTvcp.QTVCP.QT_ACTION][DEBUG] COMMAND= x_touch call (qt_action.py:234)
[QTvcp.QTVCP.QT_ACTION][DEBUG] CALL_INI_MDI command:x_touch call (qt_action.py:249)
emc/task/emctask.cc 70: interp_error: File not open.

I've already verified that the path is correct, and macros of type o<XXXX> call run fine with Axis.
Could it be that, as the error [QTvcp.QTVCP.QT_ACTION][DEBUG] CALL_INI_MDI command:x_touch call] indicates, it's trying to execute the x_touch call command and not o<x_touch> call?

You have not Stepper online A6 servos