Advanced Search

I have a turning application that's better suited towards a constant RPM on the rotary. I have my A axis functioning fine right now with position control.

I'd love to be able to just issue a M3 S1000 $1 instead of playing with the inverse time mode approaches.

I've searched the forum and tried several things without luck. Honestly, anything HAL related is an instant headache nightmare for me. Believe it or not, I'm an embedded programmer and did ladder logic in college, but the HAL stuff just does NOT click for me. I'd be willing to pay for someone's time to figure this out for me. I have a project for my church that is way behind.

I'm using Probe Basic for the GUI. I'd be willing to give up some GUI control as long as I can issue gcode commands.

Attached are my current INI and primary HAL.

Tried: 
- Changing control_type from 1 to 0, but had no idea what else to do
- Considered the rosekins but that doesn't really apply to my needs

Other forum posts I've read:
-  C Axis as Second Spindle - LinuxCNC
-  Using A axis as second spindle with stepper motor - LinuxCNC
-  Lathe spindle question turning and milling. - LinuxCNC

Thank you.

HI
I am wanting to add an optional rotary function to my table, to have a tubing cutter.  With another controller and software I just switched the Y axis control output cable to the rotary axis motor.  This is also the way it is done with my desktop laser to use its rotary optional drive assembly.
On my table I and using LinuxCNC software with a Mesa 7I76E card and QTPlasmaC GUI.  I have tried to leave out the Y home/limit entry in the pncconf setup, but it will not enable the Y axis.  I understand the need to do the homing operation so the software knows where it is for running a G-code.  After the homing I can position any axis to a location and then zero out the DRO and use that as a start position for the G-code. 
What I want is the Y axis not needing to home to be active.  This would allow me to home X and Z and position the Y to a zero position manually.
Thanks for your time
Tom V 

Confusing? For me for sure:) 
I'm now surprised by this hobbing.comp and its installation as i don't see you used "loadrt hobbing"+"addf hobbing.0" in the previously attached files.
 

With -1 you ask the master not to synchronize the dc clocks for the slaves. I would think 1000 could be a good number, every 1000 cycles the master will synchronize the dc clocks of the slaves. The clocks will run with good precision by themself in between syncs.
Sounds like you got a weird setup with EoE, never seen that before. It is explained in the IgH ethercat master manual. A way to establish ethernet connection to a slave over ethercat. Doesn't happen by itself must be something in your setup.
The message "Slave did not sync after 5000 ms" may not be fatal, most likely its clock got synchronized later.
You can enable debug with "ethercat debug 1" and check debug messages with "sudo dmesg". Maybe you can get something out of that. There will be more messages about the synchronization and how that succeeds.

I think that this could probably be solved by using TCP kinematics. Then the probe positon could be fed into the kinematics (via a HAL pin).
If you expect this job to run for months and thousands of parts then it is probably worth considering. Otherwise the mechanical stop as suggested above is probably more expedient.

If you have a spare lathe compund slide (or similar) lying about you could mount the collet block on a slide, so that you can align the end of the work to a probe....

spumco wrote:

 4th axis build based on similar reducer.

Do you mean this one? bodgesoc.blogspot.com/2017/05/harmonic.html ? 

This is often due to the stepper driver "enable" pins being wired, but not properly conttrolled.
The stepconf wizard doesn't dribe the "enable" pins, and most stepper drivers have an enable that is "enabled" when unconnected.

I would generally suggest saving pins and not wiring the enables. There is no real need for an enable control on a stepper driver (they can't run away in a fault condition, unlike a servo)

Actually the 5I25 has connectors P2 and P3 which are logical ports 1 and 0 respectively.

The info on that Wiki page is possibly a bit confusing as it combines a HAL config that I used initially, with the GUI that I use with a more developed version.

The .ui file is a GladeVCP and would be loaded by a line in the INI like:

I also seem to have fogotten to mention the custom "hobbing" HAL component. This is installed from the attached file with the command "sudo halcompile --install hobbing.comp"

This is then loaded in the main HAL file with:
(It looks like I need to re-write that Wiki page)

danke Dir!

Ich hatte im Netz schon gesucht, aber bin immer nur auf Sachen mit Zeitzonen gestoßen – das hat bei mir nicht gepasst, weil bei mir auch die Minuten nicht gestimmt haben.

Über das Setzen des Termins hab ich's jetzt hinbekommen:


Dein Link hat mir trotzdem geholfen – danke nochmal!

Gruß
Mücke

It sounds like you homing sequence might not be homing all axes.
You should see a circle/compass rose/ crash-test dummy target appear next to every axis position readout when homing is complete. Are you seeing that?

I am a but puzzled too, there was talk of adding it to LinuxCNC, and a suggestion that it might already have been done. But I don't see any "axis2" in the code.

I am fairly sure that it _isn't_ the UI in sim/gaxis, but perhaps that could work for you?

not easily so if it happens again i might have to rethink things. this was on the X axis so not too much mass being moved. the whole machine is pretty light less than 100lbs the X might hit 20lbs if that. most of the weight is the t-slot table and gantry beam.

Yes, from the diagram, that sounds right.

All I can say is WOW.