Advanced Search

Forgot to also include the nc_subroutines.

In manual_change.ngc (see attached zip file) there  are the lines:

; probe tool length
M64 P  #<_ini[pins]probing> ; turn on probing led

cat gladevcp.hal:

net tool-change  motion.digital-out-00   gladevcp.change-led
net tool-changed gladevcp.changed        motion.digital-in-00
net toolno       motion.analog-out-00    gladevcp.number


net probing        motion.digital-out-01  gladevcp.probing-led
net enable         motion.digital-out-02  gladevcp.enable
# net probe-contact  gladevcp.probe-contact motion.probe-input
# net probe-contact  gladevcp.probe-contact motion.probe-input

net reftool        gladevcp.reftool       motion.digital-in-01

net reflen         motion.analog-out-01   gladevcp.reflen
net currlen        motion.analog-out-02   gladevcp.currlen

I think the signals and pins for the lines with "net probing " and "net enable" are incorrect.

What to set here?
greez
chris

 

Gautham wrote:

Hi PCW,

I found a card locally that seems similar to the Sainsmart breakout you had mentioned. I'll add the link below. It says its for Mach3 and LinuxCnc, would this work with my Mesa 7i96s. Thanks so much for your help. Interface Board CNC 5 Axis
 

Yes, that looks exactly like a Sainsmart ST-V2 so 7i96s_5abobd.bin firmware
will work with that.

sivaraj wrote:

Any chance you used program numbers O9xxx or O8xxx .
 

No, from 5000-9000 are subroutines.

sivaraj wrote:

It should be in EDIT mode and EDIT key enabled.
 

Yes, of course.

sivaraj wrote:

Could you able to select different program to foreground or not? only the foreground program Number will run in Auto.
 

Yes, i can choose any existing program, and no, this one runs everything from the first program in memory, as noted in the manual.
This i understand why, it is a fully automated machine, so can have multiple programs run consecutively, for different materials and cuts.
-
My conclusion is there must be some setting that enables deleting those files/programs as a safety feature as not to accidentally delete them, i just have to find it.
Again, having the manual for the old control while the machine has new controls causes much more confusion than help.

That looks nice now!

Finally Fixed! Before and after pics attached.   



 

Hi all
After a couple of years, I am finally back and ready to making chips. I have a router, use steppers on parport. Linuxcnc is 2.9.4, debian:

Linux cnc0 6.1.0-35-rt-amd64 #1 SMP PREEMPT_RT Debian 6.1.137-1 (2025-05-07) x86_64 GNU/Linux

The router works, I can cut stuff etc. not the problem. The job that I want to do soon requires quite a few tool changes. So far I did it using the dowel method, but that is very time consuming. Sure an automatic tool changer would be perfect, but that's up for in a later stage. For now I have a tool length sensor, that I would like to use with my collet spindle to get tool length set after a manual tool change.

When I run tcdemo.ngc:

- goes to change position
- when I hit "Tool change complete", goes to zmax, tool sensor x and y, starts going towards the sensor.
- As soon as the sensor is touched, I get "Probe tripped during non-probe move" and program is stopped

How can I get over this?

I attach the relevant files in zipped folder "toollength_problem.zip"

Greez
chris






 

Hi, can you detail how you managed it, since other users have had problems? I'm having problems with rtai-modules-5.4.290_5.3.3-linuxcnc_amd64.deb
Another detail is that when I try to remove linuxcnc, I get another error. It says: Sub-process /usr/bin/dpkg returned an error code (1)

Hi, I am thinking about changing my existing VFD against one with Ethercat Option.
I found the Yaskawa GA 500 wich could be connected to ethercat using the YASKAWA, SI-ES3,U1000 interface card.
I didn`t find the vfd in the long list of the yet implemented devices so the question would be how to do so.
First option to use the esi file and to build the hal by myself could be a bit too hard oder too demanding for me.

The GA500 should be full cia402 compatible related to the documentations - does this make it as easy to integrate as with the servo drives?

What problems could occur?