Advanced Search

G53 G0 Z0 is irrelevant with any postprocessor. Re-read member bevins' explanation above for a better understanding of the difference between MCS and WCS.

In short G53 is your home position, ideally. Or a machine set safe-plane, depending on the machine builder's cfg.

THanks for your simulation check with a new installation, PCW!
OK, it  seems that my network configuration is magically faulty and can not be fixed to work with the lines in etc/network/interfaces, to reduce the ping times to my Mesa card in the normal way.

But, I don't want to install everything including Debian and LCNC completely new.
I think, I have to bite in the sour apple and fix it with the line
sudo ethtool -C eno1 rx-usecs 0   before each and every start of my LCNC Machine. I know that this works.
That wouldn't be comfortable but it works. And I can go further with my project.

My last step was to delete everything than the loop connection 127.0.0.1 from the /interfaces file,
configuring the Intel card with the network manager as before, and using the RTL8111 connection with Auto Internet.

The ip a with this connection is as follows:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:0a:cd:00:00:56 brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.55/24 brd 192.168.178.255 scope global dynamic noprefixroute enp2s0
       valid_lft 831324sec preferred_lft 831324sec
    inet6 2003:ce:5f08:8600:d50e:a6ab:524:e6ae/64 scope global dynamic noprefixroute
       valid_lft 6923sec preferred_lft 1390sec
    inet6 fe80::8e97:e3df:28fe:e8cf/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:23:24:5b:b4:ac brd ff:ff:ff:ff:ff:ff
    altname enp0s25
    inet 10.10.10.2/24 brd 10.10.10.255 scope global noprefixroute eno1
       valid_lft forever preferred_lft forever



What do you think? Any other solution?

Thanks again for your thougts and hints!
Hanno/arno

Hello,

Please excuse my crashing into this thread. I've found it very useful so far and managed to set up 6 out of 7 parts of my 30-year-old Gravograph Unica that I'm trying to convert to LinuxCNC running on a Raspberry Pi with a Mesa 7C80.

What's working fine so far are the 3 steppers and corresponding home switches X, Y & Z.

But: The spindle won't turn on.
I'd like to control it via PWM and as far as I can tell there should be PWM output on pin 2 of TB5 of the 7C80.
There's no useable output there, and I'm not sure where to search and what to do next ...

If there's any chance you could have a look at my .hal and .ini files, that would be very much appreciated
I also included the output of the terminal from where LinuxCNC was launched, and the output of "halcmd show signal spin".
Voltage between SINDLE+ and SPINDLE- seems to be just noise or in the mV-Magnitude.

Thank you for reading and best regards,
Erik
captain-panda

 
 
 
 

flylowgofastturnleft wrote:

hello,

If I understand, Z axis need to work in negatives value ?

This is the opposite with fusion 360.

How to have a good file from Fusion ?
 

its not opposite with Fusion. Up direction is positive in fusion. If you increase the Z value you fly, if you decrease it, you sink.
Think intuitively, up is +, right is +, depth is + and their respective opposite axis are negative direction.

G53 Z0 is at the upper limit of the spindle because it is safe location and a safe number.
You can very well change that value to be something like 200 instead of 0 from the ini file. but then 0 will be on your table and when you have long endmills, entering G0 G53 Z0 means goodbye endmill. But when G53 Z0 is topmost which is the convention, it doesnt change, safe, easier to remember than 200

you'll use g54 99% of the time. You need G53 for stuff like safe z retracts, toolchanges or to park your spindle when job is finished. So these moves will not be affected by where you zero your tool and workpiece.

Btw its possibly not the reason why linuxcnc is not starting to cut.

Hola, muy agradecido por las respuestas, como siempre.
He usado UbuntuStudio, por ser músico, no sabía de esas bondades. Derivada de Ubuntu?, tiene que ser?, en Debian no?, derivadas de ella, como Antix por ejemplo?.

Podré conectar directamente a mi netbook, con LinuxCNC 2.9.3, el torno GSK 980TDb?, tengo un salida vga sin conector, pero los puntos de conexión eléctrica están en el mother, esa netbook tiene un i3 no muy nuevo, 4 gigas de ram ddr3 y un ssd.
Dicho torno tiene un cable parecido en forma al vga, pero de solo 2 lineas de pines, para conectar, y al ver que sólo tiene 3 cablecitos, considero que puede ser posible adaptar una hermbra en el mother, ( asesorándome sus voltajes), y conectar dicho cable del torno.

No tengo en claro que especificaciones necesita el LinuxCnc 2.9.3, que me encantó ver la nueva versión y ya lo descargué.
AvLinux, creo derivada de Debian, semejante a UbuntuStudio, y lo he usado también, porque es más liviano que UbuntuStudio.

_ Por ahí no me expresé bien, a Freecad lo pude instalar en LinuxCNC 64 bits, el tema es conseguirlo en la versión de 32 bits, que me ha vuelto a compartir y tengo instalado en los cpus viejitos, que ya he compartido. Muchísimas Gracias!...

Sometimes you need to select a different boot drive in the BIOS before it boots up
I had this issue this week on a PC I have used with LCNC for years

Odd, it looks like the A+, A-, B+, B- and 5 volt power is provided for a motor encoder

Two things.

First of all delete everthing before the MDI command for G54. So delete(pr comment out):

MDI_COMMAND=...
MDI_COMMAND=...
MDI_COMMAND=...
MDI_COMMAND=...
MDI_COMMAND=...
MDI_COMMAND=...
MDI_COMMAND=G10 L20 P1 X0MDI_COMMAND=G10 L20 P1 Y0
MDI_COMMAND=G10 L20 P1 Z0
MDI_COMMAND=G0 X0
MDI_COMMAND=G0 Y0
MDI_COMMAND=G0 Z0

The mdi commands haveto be in the right order like in the hal.

Second. Delete the "[...]" after the parameters in your ini. Or use "#" for comments.

Julian

you are missing a signal name after net and before the pin name.net my-plasmac-vel plasmac.current-velocity => scale.2.in

Answered elsewhere. But you still are not providing any useful information. 

The ISO has changed so you may have the broken one. Fixed in the last couple of days.
Download the iso from the downloads page and reinstall that. 
It is tested and working.

Sorry, was busy



@Mecanix
nice board !, but i answer you tomorrow, need sleep now

I'd bet decent money that the gear looking thing the pins engage IS the C-axis gear.  It's painted, but shows no real signs of wear... because your lathe didn't have the C-axis option.

The pins are strange.  Pneumatic lines to actuators, and proxy sensors if the pins are retracted... fishy.  No idea what they do, other than maybe they're part of an alignment mechanism.

Hypothesis: Perhaps when C-axis is commanded, the main spindle rotates slowly to the encoder index, then one of the pins drops in place (indicating gear alignment with axis servo), then is retracted with the air after the C-axis servo is swung in to engage the bull gear.  That way the gear alignment isn't dependent on the encoder index pulse if the belt is replaced.

If you can find a pic of another lathe I bet you'll see a servo and some sort of swing-arm bracket so a spur gear on the servo can be brought in to mesh with the spindle gear using an air or hydraulic cylinder.  Just like the miniature version on my lathe.

I think asking on Practical Machinist would be your best bet, or call Hardinge and see if they've got any older repair/parts manuals.

Hi, 
Im trying to get probing working
currently it looks like working all the functions I need but cant set up tool dia measurement

It test the dia with Z=0*, not 0*-Z_CLEARANCE

so the flow is
1. do probe_tool_with_toolsetter
1.1 touch TS
1.2 go back Z_CLEARANCE (Z = *0 + Z_CLEARANCE)

2. perform XMinus
2.1 Go to X+ # move X - edge_length- xy_clearance
2.2 Go down with z_clearance_down (Z = Z - Z_CLEARANCE == *0)
2.3 Perform probe('xplus')

on 2.3 I have an issue, since its try to locate the edge of the TS with Z = top_of_TS == *0

lcnc: 2.9.3

So I tried with a PC with Debian 12 and LinuxCNC 2.9.2 and
everything works as expected. I did setup the real time interface
in the network manager and just added the interfaces file settings
for IRQ coalescing.

OS version

Linux EliteDesk800G3 6.1.0-18-rt-amd64 #1 SMP PREEMPT_RT Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linux

Debian release:

 

interfaces:

 

ip a result: