Advanced Search

So, how did you get this to work:I thought it meant to add 16 to the P word in the M19 command but that does not work as only values 0,1 or 2 are accepted by the interpreter.

I hope that Kuka Robot will be enough to operate in my home.
Ac motor drive
but need installation guide and details

My network supports max imput 220vac, I am not in an industrial environment.
This may be possible but 220v input drive electricity going to the motor can be up to out drive motor 380v but I don't think it is needed because 220v 15 20A would be enough

If it works, don't mess with it.

I absolutely agree.

Had the same issue yesterday, PCI-E Sunix card, works perfectly but the error shows up whenever LinuxCNC is started.
Did not bother with it, but i did notice LSPCI does not show loaded module for it at all, but it does show all the other info with addresses and stuff.

Hi Tommy. I installed your build. It works well, loads quickly.
If in the ini file DISPLAY = axis, the screen does not load.
If this is replaced with DISPLAY = gmoccapy or with
DISPLAY = qtvcp qtdragon
PREFERENCE_FILE_PATH = WORKINGFOLDER/qtdragon.pref
it works fine. Maybe I don't understand something.
Translated in Google.

Parameter 82 did the trick! It was set to 600 by default, now I set it to 1000, and works perfectly up to 170mm/s velocity.

That's what I'm starting to realize! Thanks for adding to my confidence on this route.

I have found some good encoders - I'm thinking of going with 10000 PPR for X and Z and 800 PPR for the turret and the live tooling motor as the latter won't need much in terms of resolution, while the Z and especially X will need as much as I can get/afford (maximum count rates of A-B Ultra3000 2.5 mHz).

 

Hi all

Not sure if this is still relevant. I am using this "new" orient comp from Andy (recompiled it as orient2). And I have to say, this actually works great!

The only thing I changed is: uncomment "is_oriented = 0" (otherwise I was not able to run multiple M19 commands in a row).
This changes the behavior of the -is-oriented pin --> So i use the oneshot function to make the signal stay true longer and activate the spindle brake and some other stuff. Might add another input to the comp, so the i"s-oriented" pin can be reset with M5 or an other signal...)

Before I saw this, I had to use tallas83 idea to orient a spindle (which requires much more signals/pins  & connections).

This should be added to the main fork in my opinion (maybe this was already done)?

One improvement in my setup would probably be to run the indexing only once (and then change the mode to 0) and after that do a few orientation commands. That should make it a bit faster as a constant rehoming is not necessary after every orientation (espescially if the spindle is not running in velocity mode in between).
 

It works well in text mode.

I don't think there would be any Mini ITX Boards with onboard GPU and we don't have the space for PCIe GPUs in the system.

Luckly I installed a disk brake on my lathe's spindle during the retrofit (brake is operated with pressurized air). This works pretty well for holding the spindle during cutting in a specific angle.

Make sure the drive enables work so a runaway is stopped
before damage occurs. Alternatively, decouple the linear axis
from the motors.

A blind setup has about a 50% chance of a runaway because
either the encoder direction or analog output polarity are reversed
resulting in positive feedback = runaway.

I have gotten the spindle to react in CSS it's doing the opposite getting slower as x moves in. But I'm more concerned about the spindle speed changing is not smooth. Everytime it's adjusting the speed it jerks and it's not smooth. Video clip below.

youtube.com/shorts/1r4Jos8_Y1k?si=ZHSdJYkjGlDulI3B