Advanced Search

Sorry for double posting, but i forgot this trying not to forget to upload pictures, namely:
PlasmaC and QtPlasmaC have very detailed time logs, so if you have more than one of the same design to cut, cut one after resetting the timers and check how long it took after the cut, then you know exactly how long the rest of them will take.
This is magnificent for more than one off cuts.

Axis GUI, included with LinuxCNC has such a feature in "File>G code properties" menu:


It is fairly useful when you know what it actually shows, like the actual feed time, nothing else, so no G0 moves, no probing, no compensation for feed rate changes, etc.
Takes a bit of time to get used to it, so for simple stuff with not much pierces i just double that time, for more complicated stuff like 286 cuts on a plate i just wing it to 4 or more times the shown time. Works fine for rough estimates.

I've given this some consideration in the past. At first thought, I think most of the data is there, but I don't think any of it is neatly sorted out. There is just so much that goes into affecting an accurate estimation of run time that the effort goes very quickly from "that would be easy" to "holy crap, this is impossible". You have so much to consider. You have the main cut moves - lengths, velocity, velocity reductions, accelerations (and acceleration with regard to allowed deviation from paths), dwell times, delays, probe time, number of probes, etc. I am sure there is a "close enough" approximation. But I've also done this long enough to know that "close enough" will only satisfy some people, and others will be upset when it's off by several seconds, let alone several minutes.

Maybe I will think on it some more, but no real promises.

I've only seen this in real life on one plasma system (not LinuxCNC related) - we have a table at work that the software gives an estimation. It's so wildly inaccurate it's laughable.

You can reverse the direction a motor goes, three ways: Swap one of the coil's wires between the driver and stepper, swap the DIR pins (or switch between DIR+/DIR- if you're not using both) between the mesa card and the driver, or change the software.
You do not need to do more than one of these.
I

Yes, thread order issues might not be noticed except that with
the step in position on the first index, a 1 servo thread delay
in position causes a huge spike.

It is arguable that this position step should not be present in the basic
motion hal pins, but is needed for compatibility with encoder counter
hardware that clears the count on index.

You guys are great, thanks. I will try your suggestions and will then put together all the files you asked for etc.
Thanks very much.

Is there an easy way to estimate a programs run time? I tried searching and couldn't find anything.
I know there is a stickied post on creating a sim, but that doesn't seem useful for quoting.

Thank you!

The comments and overall formatting you did I greatly appreciate, makes it much easier to follow for someone like me and I think I'm starting to get an idea of how most of it works, well atleast to some extent.

For now the spindle drive is always in position mode, it's just a servo drive/motor. It seems to work okay, but then again it's a bit early to tell.

I will test things on the actual machine in the upcoming days as it's a bit of a drive, but I have high hopes this time

I’m trying to tune my servos but I’m getting around 0.02mm ferror instantly regardless the speed which then quickly drops to a couple microns steady. Can you recommend a way to fix it or is it ok as is?

Oha SEW?
Wenn für dich die 512inc Encoder kein Problem sind und die Analog Ansteuern möchtest.
Kann ich dir meine Anbieten.
MDX61b mit Profibus Karte (dfb21b) komplett mit Kabeln und Motoren.
Könnten auch auf ethercat Hochgerüstet werden
 

Hey Leute,

hat jemand die Idee mit dem ThinkCentre und EtherCAT weiterverfolgt?

Ich habe mein System auf dem Raspi5 konfiguriert bin aber leider Hardwaretechnisch mit 2 Bildschirmen dort an sein ende gestoßen und wollte auf ein ThinkCentre M900 upgraden. Dieses Verfügt über den I219-LM Netzwerk Chip der EtherCAT fähig ist. Als ich jedoch das System oben hatte konnte ich den CAT nicht wie gewöhnlich also so wie ich es beim Raspi getan habe Online bringen. Gibt es Besonderheiten auf die zu achten sind?

Hi, I'm working on an ATC tool changer for a CNC lathe. The videos are in Polish, but you can turn on the dubbing on YouTube [EN]. This may not be a professional tutorial (it may not be in line with the art of writing software). However, I think it's a useful resource because it includes an example written from A to Z. An added bonus is the Stream Deck for tool changing, using talla83 as an example.

The entire series about the tool changer + dubbing [EN]

Part 1 (Mechanics):
Part 2 (Servo and Torque):
Part 3 (Stream Deck)
Part 3 FULL

Maybe my materials will be helpful to someone

Config www.dropbox.com/scl/fo/n8dhp3xcx0qecqnoo...t7y&st=s8xvag3p&dl=0

PCW wrote:

is spindle.0.at-speed  true?Also does the index work?Test by (either in halshow or with halcmd -kf)sets spindle-index-enable truewatch  spindle-index-enable in halshowit should go high with the sets command and then low when you rotatethe spindle past the index position.

 

Some progress, but still not quite there.

The error I was receiving ("Chosen spindle(0) not turning in G76")  when I tried opening my gcode file was occurring because I did not have a M03 (start spindle command), because I start my spindle manually. So now the program opens and runs, just not correctly.

I scoped with an actual scope the index signal as well as the other spindle quadrature signals and they are as expected (not sure on the polarity of the index pulse. It is low for most of a spindle rotation, with a brief blip high once per revolution.The program now runs, however it cuts and retracts in the wrong direction (X wise). It seems that the G76 command thinks more negative X is towards the center of the spindle center line and more positive is out and away from the spindle centreline.Even the graphic, shows -X towards the centerline ie. a deeper cut is more negative X), please see attached. Interestingly the animated graphic, shows the correct motion with a slow cut to the left then retracting out for the non-cutting return  Z movement in the real world -X direction (labeled as positive X in the graphic), and then cutting progressively deeper (real world X, graphic more negative X) on each pass..ngc file is as follows:

(huge 1.25 x 7 coarse external thread)
S100 M3
G90
G0 x-0.002 Z0.1G76 P0.1429 Z-1.0 I-0.0876 J0.005 K 0.0876G0 X -0.05 Z 0.1
M5
M30

---

Answers to your questions:

1) is spindle.0.at-speed  true?  Yes because it's hard set in HAL  (sets spindle-at-speed true)

2) Also does the index work? Yes, it is low for most of the revolution, and blips high momentarily as the magnet passes,See scope capture.
Test by (either in halshow or with halcmd -kf)

3) set spindle-index-enable true watch  spindle-index-enable in halshow it should go high with the sets command and then low when you rotate the spindle past the index position.  It does exactly that.

I think at this point I just need to resolve the backwards X movement.

I also noticed that when I use the cursor keys to jog the X-axis, they are backwards for the X-axis. Up arrow moved the cross slide down and visa versa.

If I flip the polarity of the X scale value in the ini file, the cursor keys are correct, but the actual cross slide move backwards.
Same thing if I flip the direction of rotation in the servo software, I can get the cursor keys correct, but the actual direction is backwards.

As expected flipping both gets me back to where I started.

I'm not sure if the backwards cursor keys have any correlation with the G76 working backwards for X but seems like there might be a link?

If I change the sign of the "I" term from negative to positive (which should change from external to internal thread mode), the program correctly cuts the thread, The graphic representation in axis shows an internal thread being cut, but the actual action is external resulting in a perfect thread.
 

Sorry für die späte Rückmeldung, ich bin leider nicht früher dazu gekommen, mir alles in Ruhe anzuschauen.

@ andrax :
Ich kann aktuell noch keine Bilder einstellen, da ich mich noch in der Auswahlphase befinde und den Motor sowie das Getriebe noch nicht habe.

Zu diesem Motor benötige ich außerdem noch weitere Motoren im Bereich 1,2 Nm, 4 Nm und 5 Nm. Deshalb überlege ich gerade, ob ich alles von SEW nehme, damit die Treiberwelt einheitlich bleibt. Allerdings ist SEW preislich schon noch einmal eine andere Hausnummer als Moons:
www.moonsindustries.com/c/servo-drives-a0104

Aktuell bin ich da noch hin- und hergerissen.

sivaraj wrote:

Based on the manual (download.sew-eurodrive.com/download/pdf/29194652.pdf), your motor appears to be an 8-pole motor.

Auf Seite 105 (3.7 CM3C100 / 3.7.1 Technische Daten) steht tatsächlich:
Polzahl = 8

Was bedeutet das für mich bzw. für die Auswahl des Treibers konkret?
Heißt das, der Treiber muss speziell zu einem 8-poligen Motor passen?
Oder hat das mit der Anzahl der Motorleitungen nichts direkt zu tun?

sivaraj wrote:

For an 8-pole motor to operate at 4500 RPM, it requires a frequency supply of approximately 300 Hz, which is supported by most modern drives.

Ok, das heißt also:
Der Treiber müsste ausgangsseitig ungefähr 300 Hz sauber liefern können, wenn ich die 4500 rpm überhaupt ausfahren will?

sivaraj wrote:

Please note that the 400 V value refers to the inverter-rated voltage, not the motor's rated voltage. You can find additional details in the following document (see page 44):
download.sew-eurodrive.com/download/pdf/29133866.pdf

Was bedeutet „inverter-rated voltage“ auf Deutsch genau?
Ist damit die Umrichter-Nennspannung gemeint?
Und ist der Umrichter in diesem Fall einfach der eigentliche Servodrive / Treiber, oder ist das noch einmal etwas Separates?

sivaraj wrote:

I found a similar motor with name plate details in this ebay listing:
www.ebay.de/itm/168190225800

Ja, der sieht vom Aufbau her tatsächlich sehr ähnlich aus wie die STEP-Datei, die ich bekommen habe.

sivaraj wrote:

Estimate the torque required

Aktuell schätze ich, dass ich abtriebsseitig im Normalbetrieb etwa 4.500 bis 5.500 Nm benötigen werde.
Alles darüber ist im Moment eher Sicherheitsreserve – und ein Stück weit auch Respekt vor der realen Anwendung.

Viele Grüße
Mücke