Advanced Search

Are the stepper motors 0.9 degree per step?
Should be written on the back of the motors.

in principle, yes,
but you would have to build the hal component in such a way that the ethernet packets are sent and received in parallel,
otherwise it takes too long.

EDIT:
but since udp is used, this can lead to collisions.
maybe send with minimal delay and then wait for the responses

Hi Linuxcnc community, 
I have installed OS in raspberry 5 and Instead of using IO expander I want to use individual ESP32+W5500 for every motor and generate step pulses. If this is possible please help me with the steps in achiving it.
Refer the image below and get what I want to achieve
https://drive.google.com/file/d/1JCuLksqd7dcpAcJ44GajRwzOFmay_xuQ/view?usp=sharing 
Thankyou

AFAIK with parallel port breakout, you will be able to do only step/dir signals - if those servodrives do accept step/dir then you definitely can reuse them. The problem will be the parallel port. It is slow and limits your I/O and also has become ancient relic in PCs. That is why most of folks are using Mesa boards. But for that we need to know more about the drives

The figures (scale) is correct.
So that would point to a mechanical issue(s).
Usual suspects are.
Stepper motor mounts, are they secure.
Ballnut mounts, are they secure. Ie ballnut to bracket, bracket to saddle.
Coupler mount between stepper motor and ballscrew.
Are these measurements the same all along the axis ?
Does velocity/speed affect this ?
If you disconnect the steppers from the drivers and manually turn the steppers is the issue still there.
If you directly turn the ballscrew is the issue there ?
Are the ballscrews clean and straight ?
Is there any lateral movement of the ballscrews ?
Are the ballscrews bearings in good order ? Are the ballscrews bearings at the fixed end plain ball bearings, plain bearings or angular contact bearings ?
Does the saddle rack or twist when moved ?

Hallo zusammen,ich habe schon eine Weile die QtDragon GUI im Einsatz und meine Maschine nun um einen Werkzeugtaster erweitert. Der Werkzeugwechsel soll halbautomatisch ablaufen (kein ATC, ich habe Spannzangen). Ausserdem ist der Werkzeugtaster aus seiner Halterung herausnehmbar sodass ich diesen auch zum Antasten der Werkstückoberfläche benutzen kann.Ich habe nun die INI und die HAL Dateien entsprechend der Dokumentation angepasst, bekomme keine Fehler angezeigt und die Routinen laufen wohl wie gewünscht ab.Ich bin nun so vorgegangen (alles aus dem Versaprobe Tab):1. Antasten der Werkzeugtaster-Höhe2. Antasten der Werkstück-Oberfläche (auch mit dem Taster)-> Die Beiden Werte werden automatisch in Probe HT und Block HT übernommen.3. Start meines Programms-> Maschine fährt zu Wechselposition. Nach Bestätigung des Werkzeugwechsels wird das Werkzeug vermessen und auch ein Z-Offset in der Werkzeugtabelle eingetragen. Das sieht soweit erstmal nicht schlecht aus.Der Nullpunkt der Werkzeugoberfläche wird auch aktualisiert (Auto Zero aktiviert), ist jedoch weit weg von der echten Nullposition.Hat jemand eine Idee warum dieser so falsch liegt oder ist meine Vorgehensweise bei der Vermessung einfach falsch?Anbei meine HAL- und INI Dateien.Danke schon im Voraus für eure Hilfe!

Hi,everyone,I've configured an ethercat controlled servo motor as a spindle with hal,and I was able to config it as a angular axis too .But ,now the demand is to switch it from spindle then the A angular axis dynamically,I dont know how to achive this.I've read about sample code in linuxcnc called millturn,but a little complicated.The problem seems that if there is a way to dynamically switch from a spindle to joint or joint to spindle in hal.I read about cia402 comp doc ,saying it's not possible for security reason.So,I dont know ,what is the best solution for a turn-mill or mill-turn machine.Because it need using one servo motor as both a spindle and an axis.I've added my hal in the attachment .Could anyone give me some advice how to make it in linuxcnc ? Thanks.

On a lark, I tried something... I created a new profile for XYZ and a second new profile for XYZA (I think I also set the XYZA one to mm, whereas I forgot and default to inch for XYZ).

Amazingly, on the XYZ profile, Y and Z worked perfectly, X didn't work at all. This isn't a shock because the default values for X put it onto my A. So I hand edited the HAL file, and changed X to be on pins 16 and 17, and...

EVERYTHING WORKED!

So basically, at this point, I think I have a working system and just need to tune the .hal and .ini files (or learn how to do it). When I looked through the original file I had generated ESTOP_ON was ONLY on pin 1, not on 8, 9, and 14 -- so that explains why they never went high.

Thank you so much for nailing the problem in one comment, PCW!
Thanks for sticking around and constantly pointing me toward the finish, Cornholio!

Könnten Sie ein Video posten, das zeigt, was passiert?

Was passiert, wenn Sie eine der Beispiel-G-Code-Dateien öffnen?
 

Other things to check:

1. Do you have an Intel or Realtek Ethernet chip?
( there are chip specific things you can do to improve latency)

lshw -class network

Will list your Ethernet (and wireless) network hardware if you are not sure

2. Have you run a simple ping test like:

ping -i .2 -c 4 10.10.10.10
sudo chrt 99 ping -i .001 -q 10.10.10.10

The first command populates the ARP cache so the ARP lookup doesn't add time to the first ping
The second command should be run for a few minutes (and then stopped with a control C)
and the results posted here.
 

Other things to check:

1. Do you have an Intel or Realtek Ethernet chip?
( there are chip specific things you can do to improve latency)

lshw -class network

Will list your Ethernet (and wireless) network hardware if you are not sure

2. Have you run a simple ping test like:

ping -i .2 -c 4 10.10.10.10
sudo chrt 99 ping -i .001 -q 10.10.10.10

(use 192.168.1.121 instead of 10.10.10.10 if your 7I76E is set for that IP address)

The first command populates the ARP cache so the ARP lookup doesn't add time to the first ping
The second command should be run for a few minutes (and then stopped with a control C)
and the results posted here.
 

Google translate
Hello! I want to build a plasma cutter and am still very new to Linux. I created a test setup with a Thinkcenter, 7i96s and thcad 300. I think I have configured everything well. I also connected a stepper motor for testing, which also rotates at the correct speed. The only thing that bothers me is that in all the videos I find the burner position is shown, but mine isn't. Does anyone have an explanation/solution for this? But it's only in QTplasmac. If I use the GUI Axis then I can see the position. I hope it's just a small setting.
I installed it according to Talla83 from YouTube
uname -a
Linux Linuxcnc 6.1.0-18-rt-amd64 #1 SMP PREEMPT_RT Debian 6.1.76-1 (2024-02-01) X86_64 GNU/Linux

I've come up with something new. When I start the program I see the machine table with the limits but as soon as I press Home or something it disappears and I can no longer see the size of the machine table

Hi Everyone, 
I have just installed Probe Basic on my milling machine computer and I am wondering do I just run the PNCconf to get the folders and then just copy my working configuration from my original Linuxcnc to the Probe Basic folders?

Thanks
Mike

I am running linuxcnc 2.7 for a sherline ballscrew lathe that I just received. They had a disc that came with linux 2.6 but I opted to set things up on my own with stepconf and a parallel port adapter. I hooked everything up and got it all working but am getting a puzzling issue...For ever 1mm I move in Gcode, the machine moves 0.99mm. This means if I move it 5mm it end sup at 4.95, and if I move it 10mm it ends up at 9.9 and so on and so forth. I am using a perpendicular dial test indicator and this is for the Z axis. This would not be typical backlash behavior.

My question is...is this a lathe issue or a linux issue? I am using the sherline high torque stepper motors which are branded as "anaheim automation 23y204D-LW5-01"


EDIT: I used a better dial indicator and the problem was not as bad as I first thought HOWEVER - what I am noticing is that the lathe actually moves shorter only in the forward direction, going backwards it ends up dead on. But no matter how I change my backlash adjustment it does not fix it

EDIT#2: could it actually be due to my dial indicator not being perfectly perpendicular to the saddle?

I borrowed .ini file settings some from the original disc and others made through the stepconf. 

-it is hard to find specs on sherlines ballscrews but I found that they said it was a pitch of 2mm

-I have only texted axis #2 so far (in the ini file)
-I purposely # out the backlash comp as I realized it was not backlash


Stepconf settings:

Driver microsteps: 2 (dont know where to find this online for my steppers, so kept generic)
leadscrew pitch: 2mm
pulley teeth: 1:1


Ini file below: 

# Generated by stepconf 1.1 at Wed Jul  3 10:51:18 2024
# If you make changes to this file, they will be
# overwritten when you run stepconf again

[EMC]
MACHINE = sherline
DEBUG = 0

[DISPLAY]
DISPLAY = axis
EDITOR = gedit
POSITION_OFFSET = RELATIVE
POSITION_FEEDBACK = ACTUAL
ARCDIVISION = 64
GRIDS = 10mm 20mm 50mm 100mm 1in 2in 5in 10in
MAX_FEED_OVERRIDE = 1.2
MIN_SPINDLE_OVERRIDE = 0.5
MAX_SPINDLE_OVERRIDE = 1.2
DEFAULT_LINEAR_VELOCITY = 2.50
MIN_LINEAR_VELOCITY = 0
MAX_LINEAR_VELOCITY = 25.00
INTRO_GRAPHIC = linuxcnc.gif
INTRO_TIME = 5
PROGRAM_PREFIX = /home/mg/linuxcnc/nc_files
INCREMENTS = 5mm 1mm .5mm .1mm .05mm .01mm .005mm
LATHE = 1

[FILTER]
PROGRAM_EXTENSION = .png,.gif,.jpg Greyscale Depth Image
PROGRAM_EXTENSION = .py Python Script
png = image-to-gcode
gif = image-to-gcode
jpg = image-to-gcode
py = python

[TASK]
TASK = milltask
CYCLE_TIME = 0.010

[RS274NGC]
PARAMETER_FILE = linuxcnc.var

[EMCMOT]
EMCMOT = motmod
COMM_TIMEOUT = 1.0
COMM_WAIT = 0.010
BASE_PERIOD = 50000
SERVO_PERIOD = 1000000

[HAL]
HALUI = halui
HALFILE = sherline.hal
HALFILE = custom.hal
POSTGUI_HALFILE = custom_postgui.hal

[HALUI]
# add halui MDI commands here (max 64) 

[TRAJ]
AXES = 3
COORDINATES = X Z
LINEAR_UNITS = mm
ANGULAR_UNITS = degree
CYCLE_TIME = 0.010
DEFAULT_VELOCITY = 2.50
MAX_VELOCITY = 25.00

[EMCIO]
EMCIO = io
CYCLE_TIME = 0.100
TOOL_TABLE = tool.tbl

[AXIS_0]
TYPE = LINEAR
HOME = 0.0
MAX_VELOCITY = 23.75
MAX_ACCELERATION = 750.0
STEPGEN_MAXACCEL = 755
SCALE = 400.0
FERROR = 1
MIN_FERROR = .25
MIN_LIMIT = -1016.0
MAX_LIMIT = 203.2
HOME_OFFSET = 0.0

[AXIS_2]
TYPE = LINEAR
HOME = 0.0
MAX_VELOCITY = 23.75
MAX_ACCELERATION = 750.0
STEPGEN_MAXACCEL = 755
SCALE = 400.0
# BACKLASH = 0.03
FERROR = 1
MIN_FERROR = .25
MIN_LIMIT = -1016.0
MAX_LIMIT = 431.8
HOME_OFFSET = 0.0
 

open a terminal and type
sensors
see what temperature the CPU is at while LinuxCNC is running, anything above 60 degree C should be mitigated by re-pasting the cooler or replacing the fan or with better cooling.
Some processors will handle over 90 degree, some Intel Xeons will throttle badly at 63 degree only!