Advanced Search

tcbmetalworks wrote:

Here is updated nesting using sparrow algorithm. Im also including the github repo for anyone who wants to use the software or work on the software. 

-- snip --

Here is the github link github.com/xxhalflifexx-source/plasmacam
-- snip --

unfortunately, I can't find this one on github

tommylight wrote:

Brushes, that makes the motors Brushed DC, and from what i recall the drives for those are hard to find, so it does pay off to check if the existing ones are ok.

Ah, I think you're right. The big box with the Fagor computer in the top half, I can see what appears to be an analog brushed-dc multi-axis servo amplifier + psu in the bottom half of the box. With two fans attached.

Brushes, that makes the motors Brushed DC, and from what i recall the drives for those are hard to find, so it does pay off to check if the existing ones are ok.

You should be able to get the electrical information off the drives without removing them.  Might need a mirror to see the side of the drive.

Make & model number of the drive would be helpful.  Photo of any data/stickers would be helpful.  Photo of data-plate on motors would be helpful.

From the existing photos, the drive(s) appear to be a module-type arrangement.  There is a single AC to DC power stage part, and separate (smaller) control parts for each servo motor (axis motor).  Replacement drives, if you go that route, will most likely be individual drives that each have built-in ac rectification.

That's why your 'drives' look like one big box, and replacement drives you might have seen on the internet or forum posts look like separate boxes.

The reason I mentioned not using the existing drives is that those drives most likely require 3-phase power supplied to them.  You/we will know more once you get a drive model number off them and (hopefully) find a user manual.

Some 3-phase equipment will work when supplied single-phase power, albeit at reduced output.  However, not everything has that capability.

If you have 60 amps of single-phase 230VAC available, that translates to ~36A of 230VAC 3-phase using a Phase Perfect "10hp" phase converter.  Rotary phase converters may be a bit different, but that should give you a ball-park power budget.

If your existing servo drives require - guessing here - 30 amps, that only leaves ~6A for a spindle motor.  So you can see why it's important to know what they require before you can decide to keep them or not.

For wiring/electrical software, I like TinyCAD.  But I'm not a pro, and other people have other software they prefer.  Do a search on the forum - I think there was a discussion last year about schematic-building software.

Short answer: no.
Longer answer:
Kinda, TP1 and TP2 are different ideas/models/architectures, TP2 is what can be moved in a separate thread, because it was made to plan out of RT, TP1 idea was to run in RT, both are valid ways to solve the jerk-limit, so me and YY agree both can live, they are different approaches, with their own pros and cons, moving TP1 to a separate thread would basically mean TP2.
 

Synchronization of slave clocks can sometimes take a long time at start.
There is a warning in syslog if it takes more than 5 seconds, or is it 30?
Don't know how to fix it, more than hope the slaves' clocks run more equal
when not being nudged by the master.
Add pll-err to the halscope plot. 

grandixximo wrote:

I don't think I should hard code limits, it should be up to the integrator to setup the machine with proper cycle time and limits according to processing requirements 

@endian @rodw
TP2 in a separate thread should be the medicine that fix our ailments, filtering, NURBS, all will be taken into consideration, it is an active development and testing on our end, not ready to share yet.
 

Do you think that TP1 + TP2 should be in the separate thread ?

thanks

Thank you very much.

Any Update?

As of now, I can easily send 60amps at 220 to it.
I was going to trace the power in the unit, but need to get set up. I'm just spending my time around the beast for now trying to understand it and familiarize myself. More than anything else, i'm trying to come up with a system to document what I am doing. Any idea for software, or perhaps, some sort of step by step thought process on replacing, identifying and tidying up wiring?

If you don't have many amps, can you stomach the cost & hassle of a service upgrade? >> Ideally, no, but if I really have to, I don't really have a choice. I'm dug in.

How many amps do the drives require, and what voltage? Please help me here. Is this information that I read off the faceplates (this would be maximum draws) or is this something I read off the drives? I know where the drives are, and can easily pull one out to check.

Also, before I start fingering the components, is there a component in here that can hold a charge despite being dormant for a while? I think this unit has been sleeping for about 12 to 15 months, but I've heard of folks getting a nasty shock from fingering old TVs.

Thank you

Thank you!
-existing stuff
I don't see why I cannot use the existing drives for the existing servos. The intention was not to replace those at all. For the VFD, I very much want a water cooled VFD tho I have been told that it takes up a lot of extra vertical real estate. In the end, I'll be a one person outfit for a while anyway, so maybe I can just say screw you OSHA and just deal with the noise on that 16hp spindle. I will never use the full capacity, so as long as I can start it up, I think I should be alright. I imagine I can do some sort of a ramp up start with the VFD settings. That reminds me to check if it works.

-can I mix drives? the swivel head that I have will comes with yaskawa servos and no drives(or I can add drives). I cannot imagine there being as issue to mixing and matching. And concerns with mixing analog/digital?

**********
-if you still want to replace the drives, you have two choices in general: EtherCAT or Mesa with normal step/dir or analog servos (do not bother to look at steppers and close loop steppers)

I'll have to research this. I do not know if the current servos are closed loop ones. The ones on the X and Y axis are mts30r4-42. They have 3 power leads (2 bigger wires, 1 thinner). I've confirmed that I can get a voltage if i turn the servos by hand. The resistance is above the plate, but still under 2ohms. 4 brushes in good condition. There are 4 other pairs of wires that I found out are A, B, Index and Power. Haven't wrapped my head aroud thinking about them from first principles yet. Would this existing hardware affect any of my choices?

-For the Mesa/new drives, i would look for "position and velocity" mode drives (analog +-10V and step/dir) and also with encoder outputs (all have encoder inputs or absolute encoders, usually serial ones) so the loop can be closed in LinuxCNC with both types of control, makes life easier during use. Given the choice between analog and step/dir, choose step/dir.
>>> I'm going to research this paragraph a little more first.

I was wondering if there are good software or schematics for recreating the wiring. I found the Fagor 8055 manual, but it seems more like how to use it rather than how to fix it.

Thank you!

OK all do that, probably tomorrow.
 

Achtung Trollalarm Die Beschreibung ist denke ich zu unspezifisch.

Wenn ich der KI "ausnahmsweise" glaube gibt es tausende (verschiedene) Umrichtermodelle; Made in China.

Ich denke die Kollegen, die sich damit auskennen brauchen wenigstens ein Foto, vom Apparat, vom Typenschild oder irgendsowas.

Gruß Timo

On my setup it takes about 6 seconds to get OP, it's always been like that on my setup I have about 6 servos and 6 IO cards, you should link OP with emergency, you should not let anything be operational till all-OP is on. Without my patches, old Ethernet release there is no delay in OP?

You have to catch the spikes in the scope, scope the servo thread and you joint 0 Ferror or pos-cmd pos-fb

Without a scope reading it's hard to tell what's the issue.
 

@ruediger123
I believe the jerk is not matained, because it is not possible to maintain it with your cycle time and your tolerance, you are purposely settings the machine up to spike, and it will because there is no choice if it follows your thread cycle, if it follows your tolerance, and it follows your set feed, how do you propose this should be fixed? One of these limits should be relaxed, which one?

I don't think I should hard code limits, it should be up to the integrator to setup the machine with proper cycle time and limits according to processing requirements 

@endian @rodw
TP2 in a separate thread should be the medicine that fix our ailments, filtering, NURBS, all will be taken into consideration, it is an active development and testing on our end, not ready to share yet.