Advanced Search

Hey thanks for your detailed response and definitely gives me some food for thought, I wanted to respond by point:

1. Yes plan is to remap T and use a W axis, and agreed that W would only be called during tool changes
2. My initial plan was to have a bushing with radial set screws to give enough friction to have the unpowered lathe headstock spin by friction, however, I agree I think it would probably be better to just slave two servos together so I will probably do that
3. I do plan to add a Y axis with two vertical axis at each end of the X axis cross slide but that is still a work in progress to design
4. I currently do have adjustable height tool holders and will use those temporarily
5. I do think I have space to slide the stock in - my maximum stock diameter will be 1/4 inch so around 6mm
6. As far as advancing the stock - I am not sure I am picturing what you are suggesting correctly, the new Z axis will be 12 or so inches so I will have about a foot of stock loaded in at a time, most of my parts are small so each bar of stock will be plenty of parts and I will just manually enter a new 12 inch bar of stock by retracting the new Z axis and unloading it. I don't mind this part being inconvenient for my use case as I only do very small volume parts
7. MOST IMPORTANT: so I have tried a traveling steady rest - the problem is, all of the tools have slightly different Z offsets (imagine a R handed 55 deg insert tool vs a parting blade - I guess I could solve this by having even more customized tool holders such that the actual cutting point of the insert of each tool type are all exactly lined up to the guide bushing, but I found this hard to do in my previous project which is why I was trying to pursue the W axis method (in addition to it being useful once I create the Y axis

Normal config should work as is from the wizard.
No need to change PID nor anything else for open loop stepper, there is nothing to choose, except the step/unit and maybe rarely timings.
Even if the drives are "closed loop", there is no difference from normal open loop stepper drives as the loop is closed on the drive, not in LinuxCNC.

Thank you for reporting back.
If you have a github account, could you please also post there about this.

Hello,

i have now change from axis to gmoccapy and what a wonder.. it works as exspected.. it looks like it is a bug in the AXIS-GUI.

So for comprehend the behaviour on Display Axis do following:

Change your Machine to Lathe:
Set in *.ini
Lathe = TRUE
Then Start LinuxCNC normal
Test moving on Axis - on my Lathe only X and Z
Touchoff Z-Axis set any value and click okay

After this you can not move the Z-axis again but X is moving normal.

Thanks for your reply.
Actually i have got it to work
optimizeMachineAngles2(1); this was set to 0
So it was: optimizeMachineAngles2(0)

I always say AI will bring us a lot of problems, even if i am using it for some things and for some things its great, like claude ai for building apps, scripts, etc. (e.g. the python script for surfacing timber stock works perfectly and looks really professional - it loads the gcode with one click to linuxcnc and i can just click start and even the simulation looks okay), BUT it was claude who told me to put a 0 there, it was 1, but unfortunately earlier i had other wrong settings.

Sorry guys for your time if you have read my long text.
Currently ROTARY POCKET is running and X stays at center, just moves a tiny bit for ramp in. I also checked the g-code for ROTARY PARALLEL LINE MODE and it give correct g-code, X stays at 0 (center of workpiece) and doesnt move.

When generating the g-code, i uncheck my machine configuration and use only the post processor.

Maybe this will help someone.
Br, Denis

Is your machine moving correct? I mean when you use MDI is it moving as expected?

On my machine the rotary axis is "a c-axis", but the Linux machine thinks it is the a-axis. No issue whatsoever I just put an a instead of a c into the g-code and I am done. (for now).

Given that the subscription cost almost 1.5k$ not surprising that there are not many answers.

Is there no one that could explain how it works?
I cant manage to get it to work, impossible. The X and Z axis always wants to turn around the rotary axis (making circles like they would move around th rotary axis) exactly like the end mill does in the fusion 360 simulation - workpiece is not moving but the endmill moves rotates around the workpiece - of course physically its not possible on the machine.,
The X axis should be on center, the rotary axis turns and Y axis moves along the workpiece and Z-axis adjustes the depth. I see videos of on youtube where it looks like it should, but i dont understand why i cant get it to work.

Just merged a fix for this in linuxcnc-ethercat upstream (commit 678314b, issue #457). For EL1014 units that map their inputs at 0x3101:01..0x3101:04 instead of the modern 0x6000/0x6010/0x6020/0x6030, you can now use type="EL1014-legacy" in your XML and the driver routes to the right PDO addresses. No more -typedb=false workaround needed for that variant. Untested on hardware on my end, if anyone has the affected revision, please confirm and post back.

Das ist eine lange Konversation, aber irgendwo muss der Gangwechsel diskutiert worden sein.

forum.linuxcnc.org/12-milling/33035-retr...-maho-mh400e?start=0

Ich habe das nur im Youtube so nebenbei mitverfolgt.

Ich frage gerade die künstliche Dummheit. Der Apparat scheint wirklich eine Meinung zu dem Thema zu haben.

Er schlägt vor erst mit comp den nötigen Gang zu bestimmen, mit

linuxcnc.org/docs/html/man/man9/comp.9.html

Oder sowas? 

linuxcnc.org/docs/html/man/man9/wcomp.9.html

Und dann wird vorgeschlagen mit einem separatem Ablauf den Gangwechsel zu machen. Irgendwie so :-.)States:

1. RUNNING
2. STOP_SPINDLE
3. WAIT_FOR_STOP
4. SHIFT_GEAR
5. WAIT_FOR_GEAR
6. START_SPINDLE
7. back to RUNNING

Aber vielleicht gibt es was fertiges? Soweit ich weiß hat irgendjemand das schonmal gemacht. 


Gruß Timo 

 

Hello,

i'm have some trouble if i set Lathe=TRUE in my *.ini file.

If i use the axis-gui i can see only axis X and Z - that is fine - but on the right overview i can also see y-axis Why?.

I want to set TouchOff my X-Axis to any value all is fine but if i TouchOff my Z-Axis - after set to any value after that i can not move the ´Z-Axis anymore. The selection field from Z-Axis goes blank and i see on the overview right the Y-Axis is moving continuous... that looks wrong.

If i disable Lathe-Modus in *.ini all works as exspected.

Have i to disable y-Axis in *.ini - and other stuff to prevent this failure?

Now i have set TRAJ and KINS to XZ and also comment out JOINT 1 bcause it is Y-Axis right?

It looks like if i use a LAthe i have to use x and y on the controller insted x and z axis  - the Lathe setting want to have Joint 0 and Joint 1 and not Joint 0 and then Joint 2??

Is there a specific sequence i have to use.. so Joint 0 and Joint 1 for two axes and not Joint 0 and Joint 2?
 

This sounds interesting, but I can see a number of challenges.

It'd be easy to define the original Z as "W" - which is interpreted by LCNC as another linear axis along Z.

Based on your description, you'd be using the new W to reposition the carriage for tool changes like a gang-tool lathe?

Assuming that's the case, one slightly tricky part - depending on your coding/cnc skill - will be setting up tool change macros.  You'll probably need to remap "T" to a macro/ngc file that moves X & W for each tool.  Idea being you never command the W-axis directly in a program - only during tool touch-offs.

You might also want to reconsider leaving the original spindle/head unpowered, presuming it still has the OEM spindle bearings and you've basically just stuffed a bushing in the spindle bore.

Without a rotating guide-bushing you will be limited to surface speeds way below desired for carbide tooling - unless you add a serious oil flow system to the guide bushing.  With the price of servos so cheap these days, consider powering the guide bushing with a small servo slaved to the main spindle motor.  That should reduce the lubrication requirements as the bushing will be rotating the same speed as the stock.

The biggest problem I see with the arrangement is that you have no Y-axis, and thus no traditional X/Y 'frame' like that used on a Swiss lathe.  Your tools will all be on the same X-axis plane so your stock/part will have to pass between the tools - again, like a gang-tool lathe.

One practical problem will be getting your tools on center.  You'll have to use shims (annoying), or adjustable-height tool mounts ($$) for all your tools insead of the Y-axis like on a regular Swiss.  Or home-made holders that you bore in-situ for round-shank tooling.

Related problem... do you have enough height above the current tool slide to pass stock over it and between tools?  I can't imagine that little thing being able to turn more than about 3/4" stock, but tool center height is something to consider.  It'll be significantly less frustrating if your center height is a 'standard' height and you can use off-the-shelf holders/fixturing.

Last hurdle... how to you plan to advance more stock once you've parted off?  Traditional Swiss have an auto collet closer in the sliding head, and a bar feeder that can positively locate & move the stock forward (and back).  Unclamp head collet, head slides back while bar-feeder stays put, head re-clamps.  At the end of the bar the collet opens, the bar-feeder pulls the remnant out, dumps it, grabs a new bar and away it goes.

Or are you planning to run one part at a time and advance the stock by hand?  If so, what's the point of the lathe?  If you want some of the benefits of a Swiss (guide bushing support for floppy parts) a traveling steady rest like Andy Pugh built would get you there with rather less work:



Not trying to rain on your parade here - just some food for thought.  Love the challenge, fingers crossed and all that.

Hi,
Can someone please give me some more information about how to use linuxcnc with mesa 7i76e for leadhine stepper controllers. I generated the config with pncconf but there is no way to choose open or closed loop. So the tool generated closed loop i found on github this config.

github.com/medicusdkfz/LotteCNC

so i changed also like he dose back to open loop but is this correct`?

# ---closedloop stepper signals---

#net x-pos-cmd    <= joint.0.motor-pos-cmd
#net x-vel-cmd    <= joint.0.vel-cmd
#net x-output     => hm2_7i76e.0.stepgen.00.velocity-cmd
#net x-pos-fb     <= hm2_7i76e.0.stepgen.00.position-fb
#net x-pos-fb     => joint.0.motor-pos-fb
#net x-enable     <= joint.0.amp-enable-out
#net x-enable     => hm2_7i76e.0.stepgen.00.enable

# ---openloop stepper signals---

net x-pos-cmd    <= joint.0.motor-pos-cmd
net x-pos-cmd    => hm2_7i76e.0.stepgen.00.position-cmd
net x-pos-fb     <= hm2_7i76e.0.stepgen.00.position-fb
net x-pos-fb     => joint.0.motor-pos-fb
net x-enable     <= joint.0.amp-enable-out
net x-enable     => hm2_7i76e.0.stepgen.00.enable

But what about the PID why i need the PID? Do i need to change anything on the PID settings? 
Dose anyone can share a config for a open loop steper for mesa 7i76e

Here i will share my working config and i will commit my progress here if anyone needs this

github.com/mgiaco/ecam_cnc

Thanks alot
mathias
 

I encountered the same problem.
My external Estop disables the servo drives through a saftey relay and triggers the Estop signal in Linuxcnc.
When I press the Estop during a program it seems like the program stops not as fast as the drives.
Therefore the GUI positions do not match the actual positions.

Volatile_Home works for my since Estop is the only condition which causes a difference, but I agree that a unintentional triggered limit should unhome the corresponding axis.
Is there a way to achieve this?

Ok, I'm not sure I can help you with the latency and the Y errors way out of scope of the probing issue, you had another 2.9 that was working ok, where you could patch my changes?