Advanced Search

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?

The default setting of 20,000 corresponds to a maximum pulse frequency of 50 kHz. An LPT system with a high-quality cable and control board can handle much higher frequencies. 10,000 corresponds to only 100 kHz. I managed to stabilize the latency test at a level no higher than 2500.
My stepper motors run at speeds of up to 20,000 mm/min.

Hi endian,

thanks a lot.
I am using the generic driver.
Yes, the AX5125 is currently at slave 7. I will move it to the first position on the bus as soon as I am back in the shop.

The current active AX PDO entries in ethercat-conf.xml use subIdx="00", not 0x01:
0x0086:00
0x002F:00
0x0087:00
0x0033:00
0x00BD:00

Current active AX config:
generic
configPdos="false"
reduced PDO mapping
dcConf assignActivate="730" sync0Cycle="250000" sync1Cycle="0"
I also exported the AX5125 selected item from TwinCAT and now have the full SoE InitCmd export.

My next steps are:
move the AX5125 to the first position on the bus
change the active PDO subindexes from 00 to 01
move IDN 33072 to the end of the InitCmd list

I am very grateful for your help and also for your converter tool.
At the moment I am also using AI to help me work through this problem. I am not blindly copying what it suggests. I mainly use it to learn how this integration works.
My long-term goal is to add a second AX double motor drive as well, but first I want to get this AX5125 running and understand what I did wrong so I can avoid the same mistakes in the future.
What also makes me curious is that your export/converter result worked much better than my own attempt.
Do you have any idea what I may have done wrong when exporting or preparing the file?

PCW wrote:

Here is the encoder input circuit, you can check if the 26LS32 is faulty by seeing of the
outputs follow the input state. (the outputs are inverted from the TTL input levels)

 

If the pins are correct (3. 5. 13.), there are no movement on the not working channels.
Can I force 5v to this pins (via wire from 5v supply from the stepper pins) to see in hal show will it change or not?

 

If that is the same result for both cards, seems both are OK>
Check wiring and voltage at the Mesa inputs, might be to low to trigger.

PCW wrote:

Also the 26LS32 does not connect to the FPGA directly but rather through U13 (74CBT16211
level shifter) If U13 was damaged (by say a mistake in P1  connections) this could cause an
encoder issue as U13 is shared by the encoder interface and the P1 parallel expansion port.

You can do a quick check of U13 with mesaflash (assuming P1 is unconnected):

mesaflash --device ethernet --address [card-address] --rpo 0x1008

This should respond with: 0001FFFF (the all high open circuit port data for the parallel
expansion port = P1). Damaged U13 I/O pins that connect to P1 will typically be stuck low.

 

To the P1 just connected the axis indexes (1-5 pins - you did the firmware to me) 50-100Om through resistor as you wrote me (5v supply GND to the driver and from the driver back to the P1  through a  100Om resistor)
On the table there wont be a phisical connection to P1, just 5v supply.
Here it is (both has the same respond):
 

Going to try and explain the project in a way that y'all can imagine as I feel like it should not be too difficult to program in linuxcnc but I wanted to hear the community's inputs

project: Regular Taig CNC lathe with the 5c headstock. I have already converted the 5c headstock to a guide-bushing-esque headstock. My plan is simple: add a second linear "Z axis" that holds a servo that spins the stock and can also move forward and back to feed the stock through the guide bushing headstock. This guide bushing 5c headstock is thus unpowered.

My thought: Could I just have this new axis be the official Z axis, and have the native tag Z axis be another regular linear axis where it simply acts as one of the offset parameters when setting tool offsets? So the only movement the regular taig Z axis would do is move when switching to a different tool such as drills or boring bars of various lengths, while the newly added Z axis behind the headstock acts as the primary Z axis.

I have all of the build details down so I don't think that will be a problem, but I want to know if you guys suspect it will be hard to code in linuxcnc. I do have experience setting up regular lathes & 3/4 axis cnc machines.

spumco wrote:

Mods - please marked SOLVED

Done, thank you.

Holy #@)(*-balls!!!

Who would have thought RETAIN_G43 = IGNORE_G43?

G43 works on the same line as Tn M6, as well as on the next line.

More work left to do, of course... but after about 3 years I'm finally making chips on this stupid lathe.

Thank you all!

Mods - please marked SOLVED