Advanced Search

I understand this currently comes with 8 digital inputs and 8 digital outputs, besides the analog I/O. If I later wanted to add additional inputs, would it be just a simple matter of stacking on additional input cards and updating my linuxcnc config, or would additional changes be needed?

Snowgoer- I get what your saying. I've heard enough "Can't you just...?" of my own. I know you can't please everyone, but I'm grateful for all your and everyone else's contributions.

I guess I'll see what I can do with axis. I do appreciate the plasmac statistics.
As a fabricator, most of my quoting involves chicken blood, planetary alignments and bs. I'll let you decide how much of each.

Does anyone quote by inches and pierces?

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