Advanced Search

Just get some cheap TB6600 drives, wire those directly to an old PC with parallel port, make the machine move.
No AI will help you with that, yet.

@spumco Wow the white looks so clean, got me a bit jealous haha. I'll try to keep all servos original, they probably have a better quality than some chinese servos, even though 30 years have passed.

@PCW Thank you, then it's a no brainer. Will start with the 7I97T and continue when the 7I84 is in stock.

By Rotary transfer I mean a milling machine with a rotary table with multiple stations, each station is like higly customized lathe, it holds a working piece and has multiple Units that perform a specific work on the piece.
Each Unit is composed by multiple axis depending on the complexity of the work, for certain a spindle and at least the z axis, but could even have x y z axis.

Something like this:
 

I also foud this to help define it: en.wikipedia.org/wiki/Rotary_transfer_machine

Thankyou all

 

Do you mean something like this:

 

[edit]
If so, that is not really an application I would choose LinuxCNC for but as a proof of concept why not. Although I would probably much prefer to use a PLC.

 

It started to be an issue mainly on very fast routers and plasma cutters, and when CAM started to be more readily available (and, to an extent, when it started being used by novice CNC-ers who assume that the smallest possible path length mush be highest resolution and therefore the best.

Exactly.
Here is a good example of how simply changing the CAM settings may fix slow Gcode execution despite the one line lookahead:
forum.linuxcnc.org/38-general-linuxcnc-q...ving-too-slow#306462

Hello,
I am new here and overall in the CNC world.

I just wondered if LinuxCNC is suitable for Multi-Station like Rotary and Linear Transfer Machines, that have many Units and Axis, at least many more than what I have seen in the examples.

And if not what would take to make it so?

Thanks in advance,
G.Pasotti

well... thanks for your help

I'm sorry but it's just like last time you asked for advice here:
forum.linuxcnc.org/27-driver-boards/5109...17x0?start=10#288989

You turn up with some hallucination and expect other people to make it come true for you.

Wow aciera youre right again. I cant believe that was the issue. But if anyone is seeing this in the future turn up your smoothing and tolerence in fusion 360.

My line segments are about 1 to .5 thou now (they were down at about a 10th before) and i can get up to somewhere about 60-80 percent of my feedrate which is way faster. Theres work to be done if I needed to cut a bunch of aluminum but this is a test cut for inconel, so this speed will work just fine!

Thank you sir!

I tried to reinstall everything from scratch, to no avail, the keys are not updated. I think we should intervene on the image

Joint 0 following error is the difference between 'joint.0.motor-pos-cmd' and ' joint.0.motor-pos-fb'.
If this exceeds the limits defined as 'FERROR' and 'MIN_FERROR' in the [JOINT_0] section a fault is triggered and you get an error message.

If you are getting joint following errors on startup I would suggest to have a look at pins 'joint.0.motor-pos-cmd' and ' joint.0.motor-pos-fb'. Possibly you are simply not connecting 'motor-pos-fb' with a value in your hal.

Hi,
I was wondering if anyone could comment on experiences (good, bad, indifferent) on Moons' Industries Ethercat drives, specifically M54S-24A5ECN.
www.moonsindustries.com/p/m54s-series-un...n-000004696351007109

If not, would it be possible to summarise in a general sense what things to watch out for / would need doing to make it work with LinuxCNC.
Thanks
P.S: first post in this forum - thanks in advance for all the hard work that has obviously gone into LinuxCNC and to the community!

Two things to note here.
1. Since this involves blending linear and angular joints try using inverse time (G93) instead of G94
2. Generally the CAM/PP will generate 4axis Gcode made up of short line segments. Since the MotionPlanner in LinuxCNC will fall back to one line look ahead for any move involving any other than X,Y,Z axes it is important that the line segments are not made too short. So to speed things up you should also try to get the CAM to generate longer line segments.

Not exactly the same manual but contains the same information in section 8.4.6:
assets.omron.eu/downloads/manual/en/sigm..._users_manual_en.pdf

Hello Gurpreet!

Could you please share whole pdf document? I am struggling with Yaskawa incremental encoders and their C channel in particular because at least those encoders I have use the C channel to commutate rotor position. And it seems that your manual might be useful.