Advanced Search

Most printers are made of 80x20, which while it works in the short term, fails slowly over time. Bolts come loose, pom wheels (that ride in the 80x20) wear out, belts loose tension, etc.

If your gonna build your own buy 1k in parts and make it with ball screws, linear rails, nema 23 motors, 400mm+ etc, steel frame preferably welded.

It'll take a lot longer to setup but will last for decades

I've had my Ender 3 Pro for a good time and have found it to be a good solid workhorse.
Far by the best mod was a glass build plate, was fighting with adhesion for a while, adhesion is that good now I have to use hairspray to be able to remove the printed item when it's all cooled down .
If I was to build my own I'd reduce the Z axis travel to about 150mm and probably go for about a 400x400 bed.
If I see "game changer" in a another YT review I'll be quite upset and may commit an act of unfathomable violence upon society.

could you show me a exmple? i dont understand how i can connect the carousel.comp with the spindle... i go in basement and checked again. m19r720p1 doesnt work...

i understand that this compnent is very useful but i dont understand how i can link it up with the spindle to turn the carousel.

I think it´s by design that everytime you generate the files, the rio.ini and several other files are overwritten. I have a bunch of customizations in several areas. E.G. Subroutine folder is different, Halui has custom MDI Commands,... 

At the moment I do manually copy the sections back. Is there a smarter way of doing that?

m19 r720 p1 doenst work. its limited value 0-360 this was the first i try.. i had another idea...

using 2 relays.. switching between 2 step/dir signals from the mesa.
when toolchange is called..

m5
g4 (some value)
switch the relay to get position mode from a stepgen
make the toolchange
toolhange done.. switch the relay back to the stepgen for velocity mode

this is the hardware solution... needs 3 extra pins... 1 for relays 2 for extra step/dir

but is this not possible without relays and inside the hal? thanks

I managed to find a way to spend a lot of money _and_ build the printer myself, by buying a self-assembly Prusa XL.
I don't regret it, though.

hitchhiker wrote:

m19 r360 p1
m5
m19 r360 p1
m5

 

This isn't the answer, nor even necessarily part of the answer, but M19 R720 P1 should work.

You couls consider using the carousel component and leave the spindle in velocity mode. Simoly use the spindle as a carousel motor and turn it on to change tools and off when the right tool is in position. (Use the slot sensor as the the strobe signal that "carousel" supports) 

Failures in spindle hal

I think that Granite Devices drives handle resolvers, but the current drive (IONI) only handles 700W. (you need at least twice that)
The older "Argon" drive might fit the bill, though it's a bit down on power compared to the existing drives.
granitedevices.com/oldsite/digital-servo-drive-argon
Lists the following feedback sources:
Incremental encoder
• Analog Sin/Cos encoder
• Resolver/synchro
• Serial SSI & BiSS (upcoming feature)
• Tachogenerator
• Hall sensors

What is the feedback system used for axis position? Are there separate scales, or does that rely on the resolvers on the motors too?

STMBL would work, but doesn't fit your "industrial" and "don't want to build it myself" criteria. (though see the thread about a new STMBL on this forum.)

Much easier to use another GUI.
PlasmaC and QtPlasmaC are made with that automation embedded into them as they are essential for plasma use.

kn612 wrote:

Is it possible to use stall force tolerance for z axis home and detecting the sheet metal in qtplasmac? 

Yes for a DC motor, no (at least not easy at all) for steppers.
For a DC motor you would need a reed switch and wind some 5-10 times one of the motor cables around it (not both), wire the reed switch to any input and set it in hal as limit switch or probe.

Emco use encoder from spindle for ramp up and down speed between toolslots and calculate the way in theorie.. then the other sensors looking for the real position

I have found 2 problems: in turning and tool-change operations.
I found a workaround since at this moment I have no time to really understand and find a solution for the errors.
So, please do not consider it a solution.
In the folder /home/your_user_name/nativecam/cfg/lathe/ you should find the
config .cfg files.
(Or maybe the files you are using are in /usr/share/linuxcnc/gladevcp/NativeCAM/cfg/lathe/)
Edit the turning.cfg file and search for the word "parent" (without quotes).
(maybe you could make a backup copy before editing)
I have found it in line 71, 99, 100
Place a semicolon (that it means comment) at the beginning of each line containing the word "parent".
Save the file.

Same procedure for the tool-change.cfg file.
Please comment lines 76 to 80 and 198 to 203 containing "parent"

The turning operation and the tool-change seems to work.
I don't know if there would be side effects.
Hope this helps.

Regards
Giovanni

I have built 5 of Voron 2.4 and 4 (i think, maybe more) or Voron Legacy.
This is after buying 11 or more of Creality CR printers (not the cheap ones, some pricing errors so got them all cheap).
Having got that out of the way, if you can get the Elegoo Centauri Carbon for 300-400$, get it, do not ask, do not think, just get it. For that price you can not source the parts only.
Now, building one will teach you a lot of things, a lot, but it will also want to shot it with a bazooka many times if you do not follow the instructions.
Voron has very good instructions, browse through them once or twice before even starting to order things, and if you do start ordering things, get a kit, it will save your hair if you have any left by then.
For a low budget, build a Legacy, but if you can stretch a bit, build the 2.4, it is a magnificent piece of engineering and it is a workhorse.
And in case you go all DIY, here is a version of 2.4 that uses linear rods for Y and Z axis instead of linear rails, easier to source and cheaper:
www.printables.com/@Toma3D_1991434/models

I think you need
[EMCMOT]
EMCMOT = motmod num_extrajoints=1

It's worth knowing that in many (but not all) cases INI file entries are simply copied into the HAL file.

Typically you will see:
(INI)
(HAL)
What you want to end up as the HAL command is something like

It doesn't matter what order the modifiers after "loadrt motmod" are, which means that you can either have the num_extrajoints as part of the [EMCMOT]EMCMOT substitution, or you can add it yourself to the loadrt..... line