Advanced Search

Like tommylight said and I want to add that you should also check /boot/armbiEnv.txt for the same UUID. When you see a /boot mount in fstab you could remove that line too.

Here it didn't recognize the ID option by the way, in that case just leave that away, alternatively you could issue the blkid command to see the UUID.

i have also noticed on my fanuc , mitsubishi machiens it seems when in a probe move there is no smoothing on any axis motion, its a much harder point to point move you can hear the differance on the machine axis when making prob moves onto a surface.
so dont think that the main stream controls use motion smoothing on probe moves as it seems they do not, when you are probiing it tends to not be that fast also, aprox 1000mm/min feed is common.
for the reasons mentioned before. as probining its key you always have a known probe detection trigger distance etc as this is what you calibrate a probe cycle for..

also
dont for get threading on lathes (G33 and g76) is another one you will skip for smoothing as it must follow the spindle encoder like tapping.

@tommylight
Do you have a Ascii Code for the Signs to move the C-Axis?
So, i think, it must be possible to search for the Signs on DE Keyboard.

What hardware are you using?

A system with a failing encoder might behave in this way.

Hello all!
I am using Linuxcnc, which came with the machine, and I am also using Easel as CAM/CAD software.

 I managed to get the G code to load, but it's showing me this inverted image.
I use Easel for my designs, but something is off unless it's just me doing the config wrong.

Additionally, i am trying to home axis but it's just telling me that switches are inactive with a grunt.

I can move the machine manually but I'm afraid config stuff feels like space magic x3 I am very new to this world and a lot of terms don't make much sense to me tbh. I am a Windows user primarily and Linux caught me off guard

Any help is greatly appreciated!!!

Surely a noob like me can figure this old cranky Elizabeth out.

Da Bilder etwas Totes sind und ich wirklich dankbar für dein Tool bin.
Ich möchte dir zeigen, was dabei herausgekommen ist, das war mein erster richtiger Test, denn ich konnte.

DANKE NOCH MAL !!! an der Stelle für das Tool.

VG Mücke

 

I'm using QTDragon HD and having issues when probing.

I am using the steps as outlined in the qt_auto_probe_tool.ngc file start off with.

From machine_log.dat (VIM line numbers precede each line)

 17 17:11:22 Loaded tool 0
  18 17:11:22 Tool 0: PROBE
  19 17:11:28 Cannot switch pages while in AUTO mode
  20 17:11:39 Versa Probe: Start Cycle: Go to Tool Setter
  21 17:12:08 Versa Probe: Start Cycle: Probe Tool Setter Z Height
  22 17:12:17 HISTORY Tool Setter height Z[-148.426]
  23 17:13:17 Versa Probe: Start Cycle: Probe Z Height of material
  24 17:13:27 HISTORY Probe Material Top Z[-115.031]
  25 17:14:47 Cannot switch pages while in AUTO mode
  26 17:14:52 Versa Probe: Start Cycle: Probe Outside Edges, Finish At Corner
  27 17:15:17 HISTORY Outside XPYP  Xp[0.302] Lx[0.000] Yp[0.027] Ly[0.000]
  28 17:15:56 Started program from line 1
  29 17:17:30 Tool 16: whiteside router bits - whiteside rd210
  30 17:17:47 Tool 16: whiteside router bits - whiteside rd210
  31 17:17:47  Probe Height: -148.4200
  32 17:17:47 Run timer stopped at 00:01:50
  33 17:17:47 Loaded file /home/andy/uploads/Large-Serving-Tray-REVISED-V2-POCKET-2.ngc
  34 17:17:47  Block Height: -115.0300
  35 17:17:47  Probe Result: 229.0947
  36 17:17:47  Calculated Offset: 262.4847
  37 17:17:47 Linear move on line 231 would exceed Z's positive limit
  38 17:17:47 Linear move on line 231 would exceed joint 3's positive limit
  39 17:17:47 invalid params in linear command
  40 17:17:47 Abort Parameter is [3]
  41 17:17:55 Started program from line 1
  42 17:18:17 Tool 16: whiteside router bits - whiteside rd210
  43 17:18:17  Probe Height: -148.4200
  44 17:18:17  Block Height: -115.0300
  45 17:18:17  Probe Result: 229.0912
  46 17:18:17  Calculated Offset: 262.4812
  47 17:43:20 Run timer stopped at 00:25:24

Here's the popup message:  NOTE the MDI line number 231 has no Z axis movement and the program file has not even started to execute. At this point the new tool change has already taken place and the new tool is being measured.

 

Not sure what is causing this but, after I "Clear all" the and restart the file from the beginning it runs as expected without the error.

Finally, worth noting is that I noticed my tool table appears to have been altered and is NOT from previous runs. Has many missing columns.
It appears as if something has written to the tool table when it should have not.
Here's a couple of lines in my current tool table that reflects this issue, note that tool 16 has the Z set.

T15  P15  D+6.350000 ;whiteside router bits - whiteside ru210
T16  P16  D+6.350000 Z+258.012190 ;whiteside router bits - whiteside rd210
T17  P17  D+6.350000 ;whiteside router bits - whiteside rd207

And here is a backup that I took a week or so ago:

T15 P15 X0 Y0 Z0 A0 B0 C0 U0 V0 W0 D6.35000 I0 J0 Q0 ;whiteside router bits - whiteside ru2100 -- 1/4 inch upcut spiral- solid carbide 
T16 P16 X0 Y0 Z0 A0 B0 C0 U0 V0 W0 D6.35000 I0 J0 Q0 ;whiteside router bits - whiteside rd2100 -- 1/4 inch downcut spiral- solid carbide 
T17 P17 X0 Y0 Z0 A0 B0 C0 U0 V0 W0 D6.35000 I0 J0 Q0 ;whiteside router bits - whiteside rd2074a --o-flute 1/4 inch downcut spiral - solid carbide 

Any ideas?

 

Not sure what infor to provide. My machine has suddenly decided to move a seems like random amount if I hit stop during a run. It did not use to do this. and sometimes it just stops where it is. But now I can't trust it. So for instance lets say it has moved to the first cut location and is spooling up the spindle. If I hit the stop button or esc button, it will slowly move in x/y/z. During the move the disp[lay will not update. Buit when it stops the DRO will update to correct position.

It does not loose its place, if I hit run it will go right back to the correct start position.
It will also do this if the spindle is up to speed and cutting. If I hit stop it will move.

If it was only X and Y, I could hobble through the job, but it may take a dive with Z which could plunge through my part.

The only changes I have made are I tried to install easy probe a few weeks ago. But seems like I have not had this issue until today.

BTW, running Axis.

If the index had a high enough duty cycle that you could use the software encoder
you could use a little hal magic to switch the RPM source from hardware encoder to
index only software encoder at some specific commanded RPM.