Advanced Search

Stahlwerk, Stamos, even my Kzubr is still working just fine, although mine has been siting idle for nearly 2 months, the rest are in use daily.
Stahlwerk has it's own website, and stuff there is cheaper that on Amazon
Vertical machine torch is from 40-50 usually
www.stahlwerk-schweissgeraete.de/zubehoe...r-p-80-cnc-edelstahl
70A with pilot arc is 450 but currently not available
www.stahlwerk-schweissgeraete.de/plasmas...-cut70-pilotzuendung
Here is the full list of plasma, mind the pilot arc and notice those with pilot arc have another red connector on the lower front.
www.stahlwerk-schweissgeraete.de/Plasmaschneider-CUT

Nah, i did my thing, no one started screaming at me, got more replies from Ausies than Americans despite aiming for Americans (i was convinced the silicium thing is just another "labeling everything wrong" American doing, obviously it was not), and all in all, a very civilized conversation.
Now moving on to "tabless" Elon-Tesla wrongly labeled batteries...
Should i start a new topic for that?
Or should i pick on Intel and AMD and Nvidia as it is still a hot topic?
Or Facebook/meta, twitter/x, adobe.....
ah the choices ...

The motion should follow the PWM value and that should follow the absolute position.
if homing is disabled, I would expect the starting position (and therefore PWM value)
to always be the same.

Not sure of the resolution of the Remora PWMgen, it's tough to do PC servo PWM
in software because the entire range of motion is controlled  by a 1 ms PWM width change
(so say a 50 KHz base thread would result in only 50 discrete positions)

One guess is noise/crosstalk on the step/dir interface, especially if
the drives have a input capable of accepting high speed step signals.

I tried both options. Version 2.9.4 is out. I'll try it and see if anything has changed.

I have RhinoCam do you know a post processer that will work with Linux CNC machines. I have A PrintNC 3 axis router. I have been using the Practical CNC post processor I have to add S0 M5 M30 at the end of the code to get it to work but it doesn't work all the time. When it doesn't work, I have to close Linux CNC and restart it then it will work. I don't understand why it dose that.
DB

I think I will put a pin in that route for a "try later" when the machine is dialed in and running properly.
I have seen some of the influencers comment on it, as a not for the novice crowd. It's a shame MESA
doesn't make a 3D printer controller board. But I guess that would also mandate a major add-on to
LinuxCNC. Oh well hope springs eternal.

@unknown Nope until now it's only at the master branch, when I see time I'll do a pull request for the 2.9 branch. You could possibly build from the 2.9 branch and apply the following patch with: git apply ../linuxcnc-rt-detect-6.12.patch

forum.linuxcnc.org/media/kunena/attachme...rt-detect-6.12.patch

Or just put "LINUXCNC_FORCE_REALTIME=1" in front of the LinuxCNC command of set it as a permanent environment setting

Thanks
Homing I am just gonna do the normal switch plus index for now. So 3 inputs out of my 24.

Other inputs I need are:
- Probe
- Laser tool setter
- Spindle clamp sensor
- Hard limits are either 3 or 6 switches but I will leave those off for now.

Not sure how you handle an MPG with this.

For outputs I have:
- solenoid for tool release
- solenoid for M7 mql

I will be using probe basic I think for this, i will need to figure out the rs485 for the spindle. It looks like I can read back the torque, and alarms, which is nice. My biggest issue on the old setup is the control is blind to errors and when the spindle or an axis stalls it just keeps on keeping on. Gotta get that all tied up.

Hi, sorry, do you mean something like this ?
 

 

Hi Linux CNC forum, 

I'm building on a small CNC for over two years now. Unfortunately, I've been running in some issues while milling circular pockets.  
machine specs: 
Traj XYZA 
y-axis 1190 mm max travel, 20 mm ballscrew with 10 mm pitch, two 750W AC servo (HLTNC) 
x-axis 900 mm max travel, 20 mm ballscrew with 10 mm pitch, one 750W AC servo (HLTNC) 
z-axis 185 mm max travel, 16 mm ballscrew with 5 mm pitch, high torque nema 34 stepper 
spindle - 2,2 kw rattmotor air cooled
Brain of the operation: raspberry pi 4b+ using a parallel port hat and a 5 axis breakout board 
I'm running the premanufactured PI4 optimized Debian Bookworm image. 

Y-axis settings as follows: 
max_velocity = 5000 mm/min 
max_acc  = 20000 mm/min2
min limit = 0 mm
max limit = 1190 mm 
stepgen_maxaccel = 40000 
scale = 10 steps/mm -> (not sure why i set this to 10 -> 200 steps/rev and 10 mm pitch shall result in 20 steps/mm) 
FERROR = 1
Min_Ferror = 0.25

The issue: 
See attachment for further details 
arcs/circular shapes are for any reason shifted in XY - direction, the error occurs above 250 mm/min and is almost unchanged between 1000-5000 mm/min. 

What did i test up to now: 

1. Change base_period up and down -> the servos are set to 200 "steps"/rev, 10 mm pitch -> thus 20 steps/mm resulting in below 2000 pulses per second on one axis. Base_period is set to 100k, shall be fine? Changing the base_period to 40k didn't change anything as well as increasing the base period to 150k. 
2. Change max_acc to 4x max_velocity and stepgen to 2x max_acc -> didn't change anything 
3. check mechanical stiffness and backlash -> everything feels tight and rock solid, the linear guide rails are 20x30mm using very massiv long carriers. 
4. kill all unnecessary PIDs on the debain system in order to reduce latency -> didn't change anything

added the .hal and .ini file as attachments. 

Any hint or recommendation on how to improve this would be appreciated! 

Thank you!
Michael 








 

I haven't had time to use halscope, I'll look at your recommendation for modifying the firmware.

I made a surgical modification to the AXIS GUI to optionally modify the behavior of an axis to use the ACTUAL_POSITION value as part of the offset value sent to the G10 L20 command during a workpiece touch-off.  This is only done if TOUCHOFF_ACTUAL = TRUE is set in the appropriate [AXIS_x] section in your .INI file.

This may not be the most general approach and may yet prove to have some bugs (e.g. i have not tested metric mode yet), but it works for my situation right now anyway.

I'm not sure if this is worthy of creating a PR to include in LinuxCNC, but for anyone who might want to see the change you can view the diff here:
github.com/tangentaudio/linuxcnc/compare...025%7D?diff=split&w=

cheers,
Steve
 

You need to share more about what you want to achieve. Sounds like you are going about things the wrong way...
cia402.comp is an interface between Linuxcnc joints and the ethercat cia402 servo drive.