Advanced Search

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

Hi,

I use a servo motor as lathe spindle motor. Positioning mode, step\dir signals. As you see in the video I need to tune the drive for lower RPMs than 10. Yes, I'll never use such low RPM's in a lathe but it still needs tuning on the drive. 

Which parameters should I play with?

Also I am unable to find a proper user manual for the AASD drive as the pdf I have the parameters ends at PN219 but I know there are many more. If you have the latest pdf and willing to share I'll be greateful.

Servo drive AASD 50A
Motor 110ST_M06030 (1.8kw)

Thanks in advance,
Suat

Sorry for the mistake I have attached my files here.

I do have that line in the post gui file. I also have those other lines you mentioned. Thank you for your help! 



 

You don’t have to apologize at all. I had a look at the index signal before, but not with the rest of the machine running. So I will test this with the axis drives and VFD running to make sure.

Thank you, but I have not executed any homing procedure. I thought that I should execute a homing procedure at least once. For example, let us assume that I utilize the index pulse homing method - 34. I execute homing once and then the servos have their reference from the absolute encoders.

Congratulations
I don't think the rest should be a problem

I didn't do anything too special compared with this guide  other than selecting "USB_CDC" for communication and then scanning on the available "Serial Port" options until the driver showed up. If yours doesn't, try a different cable.

Hallo zusammen,um überhaupt erst einmal ein Gefühl für Servomotoren und die zugehörige Antriebstechnik zu bekommen, möchte ich mir testweise ein kleines Servo-Setup zulegen.Aktuell schaue ich mir dieses Set von Stepperonline an:A6 Serie, 750 W, 2,39 Nm, mit Bremse, 17-Bit-Absolutgeber, STO
www.omc-stepperonline.com/de/a6-serie-75...a6-ec750h2b1-m17-sto Dazu habe ich ein paar Verständnisfragen:

1. Der Motor hat eine integrierte Haltebremse.
   Benötige ich dafür zusätzlich ein 24 V DC Netzteil, um die Bremse überhaupt ansteuern bzw. lösen zu können?
2. Im Handbuch steht auf Seite 12, dass ein integrierter Bremswiderstand vorhanden ist.
   Heißt das, dass ich keinen externen Bremswiderstand brauche, oder ist je nach Anwendung trotzdem noch ein zusätzlicher erforderlich?
3. Ich würde das Encoderkabel mit Batterie direkt mitbestellen.
4. Beim RJ45-Anschluss / EtherCAT:
   Reicht dafür ein normales handelsübliches Netzwerkkabel, oder sollte man hier besser ein spezielles, industrietaugliches Kabel verwenden?

Hier noch das Handbuch:
www.omc-stepperonline.com/index.php?rout...rvo_drive_manual.pdf Mir geht es wirklich erst einmal darum, die Grundlagen praktisch zu verstehen, bevor ich später größere Achsen auslege.Vielen Dank schon einmal für Eure Einschätzungen.Gruß
Mücke

Sorry, I forgot that. Can you get a scope onto the spindle encoder index pulse?