Advanced Search

I would use a new output pin that follows the state of estop. 

I think there is no simple answer now.. but from testing last few days its waaay good to control any hardware and smoothness is uncomparable...

I will share testing gcode in comming days .. but basically I go through all examples in nc_file folder and then my code.. my code will be avaible here

I am now searching the best solution of testing and validation ...there is not space for one lady said..

To prove all main stuff but idea is basicaly simole.. step by step test all avaible G code which I have from real machine but there is some limition of my time 

Btw 杨阳 is mika-net at forum? If am I wrong?
 

Hello Hartwig,
Thank you for your reply. I think my machine has some sort of EXE, its a board and the name is NCP59. But i dont know where to intercept the TTL signal from it. There is a version of this board with an extra digital output, but i dont have it on my machine. And buying 3 Heidenhein EXE is a step back. I would like to use a modern version of that.  Maybe a 7i85S or someting like that? 

And the Suplier you sent seams good and I will buy der 7i97T from him.


Here is a picture of the NCP 59:
(1, 2, 3 are X, Y, Z)

 

Thank you so much for the response, I have been going through a trial and a half with this install :') I bought some 2.2k 1/2W resistors just for this project, and have been battling to get a result

In halshow, none of the inputs change state, even the estop. But watchpin in the terminal shows clearly that estop, probe and for whatever reason, Z max (Home) limit switch change state even though it currently doesn't have a pullup. I only get a reaction from Z max when sensor is active.

I currently have a pullup on my X min, but can't get any reaction out of it no matter what state the proximity switch is in (on/off or jumper to GND) when using watchpin.

Just for reference as to wiring, I have all +wires > COM+> +WAGO fed by +FIELD, same setup for GND. Then individually connected sensor wires to MESA inputs. Pretty obvious, but just in case, I figured I best note it.

Also, I figured I will include multi readings in both states for all inputs with sensors on and off. X max excluding as I have found it to be dead. I will be replacing all of these anyway with PNP when they arrive. But was hoping to atleast get it running.

Readings are as follows:

X max DEAD
X min 3.9 off, 7.8 on
Y max 14.7 off, 18.4 on
Y min 12.3 off, 8.3 on
Z max 8.0 off, 14.9 on
Z min 12.4 off, 9.0 on

Readings might be telling or maybe not?

My GUI is also massive and a PITA, so I have mostly been doing my stuff through SSH. No matter what commands I send, I cant get the GUI to scale properly that's everything on the screen though, for whatever reason, my mini pc with Debian 12 cant seem to recognize the screen through HDMI. Any suggestions there would be absolutely amazing!

Should be good! Run it!

The way I would approach this (many ways).

First you need to look at the old controller and pray you see a step and direction text somewhere on the board, wire labels, anywhere.

If so follow the below. If not I'd probably see if I could find the software or manual to program the drives. Maybe chapgtp can help here?

If it's step and direction your life is easy
Step 1. Buy a 7i96 or 7i96s, if doing spindle speed control with a vfd S makes it a bit easier. (If you want to check sanity buy a stepper and drive to verify it works before testing the drives)
Step 2. Test the existing servo/stepper drives to see if they work. If you tore apart the wiring this may take some trial and error.
Step 3. Figure out the screw pitch and run through the pnf config

Finally that spindle looks usable...prob the easiest thing to save. Is it a 3 phase induction motor?

I'm not sure if auto resetting makes sense.

I don't think this would auto reset since I would still have to power the machine on in the ui to reset the drives. Also, the CL57T only allows resetting in this way for following errors and not overheating.

Currently my external estop is wired into the contactor latch for the drives/spindle power. Should I consider changing this?

Have a look at FlexGUI, seems easy to make and GUI you like/need/want
forum.linuxcnc.org/flex-gui/57726-flex-gui

Looking to join a thread on this topic and collaborate. Is there any progress on a Brake Press UI and a repo or something where I can use/contribute.
I'd prefer not to use a glade UI due to deprecation if possible.

I'm not sure if auto resetting makes sense. Often the alarm is raised when a motor overheats and it will need time to cool before engaging. An alternative would be to incorporate the enable signal into your estop circuit so the drives are only enabled when estop is off.
Cycling the estop will clear the error.

Johnny is on the right track. The following works well with qtdragon.
Tormach sell a granite surface plate with a hole in it for TTS tooling.
tormach.com/small-granite-surface-plate-...KYzs44ICkj1ujSHUakPj

Then you can insert your tools into TTS tool holders and pre measure them with a digital height gauge
www.ausee.com.au/products/digital-height-gauge-0-200mm-8
and record each tool's height into the linuxcnc tool table.
Measure the probe the same way as tool 99.
Then you just need select tool 99 and probe the top surface of your work piece. Now whenever a tool change is required, QTdragon's manual tool change will pause and let you change tools and resume your job.

 My thought was to use the tool setter to detect the toollength of the probe but a combination of multiple spring loaded buttons may throw off the actual tool length.

This should be easy enough to test.  Make a cut at a known height, measure the probe with the toolsetter, and probe the new cut.
 

What I do is put something flat like a 123 block in my vice. I lower the spindle without a tool in it so that it just touches the 123 block. I use TTS tooling so the nose of the spindle is what the tooling is going to seat up against when the tool is installed. With the nose of the spindle on the 123 block I make a note of the ABS Z value. Now I probe the 123 block. Now check the ABS value of the point where the probe tripped. Don't forget to account for the amount that the probe backs off after tripping. Min is .25 inch.

So if the ABS value of the nose on block is -12.000 and the ABS of where the probe was after the probe is -7.750 then account for the .25 backoff and the gives you -8.000 trip point. 12.000 - 8.000 = 4.000 so the probes effective length is 8". Put that value in the tool table as the length for tool 99 (The probe) Then when you touch of on the part it can take the Z position at touch-off and adjust it by the tool length of tool 99 and that value would be the Z would be at if the nose was on the part. Then when the length of the tool is applied Z will be what would put the tip of the tool on the part.

I hope this helps

So should something like this work:

Expected result would be, the alarm triggers the oneshot, which then triggers the amp-fault-in and in turn turns off the machine. The fault is also cleared 0.5s after the oneshot fires thus allowing me to turn the machine back on an clearing the ALM signal.

So the fault pin is only cleared when the drive is re-enabled?

That sounds about right and the fault is preventing me from clicking the machine on in the ui.