winder / Universal-G-Code-Sender

A cross-platform G-Code sender for GRBL, Smoothieware, TinyG and G2core.
http://winder.github.io/ugs_website/
GNU General Public License v3.0
1.89k stars 765 forks source link

Probe Malfunction #1571

Open Mikewills70 opened 3 years ago

Mikewills70 commented 3 years ago

Hi,

I'm using a 3040T desktop CNC machine, coupled to a TinyG controller with homing limit switches and probe facilities. All work fine using ChiliPeppr. However, I wanted to swap over to a non-internet based GUI and found UGS.

The swap over worked well even though UGS declares an unknown version when it connects to the TinyG controller. It did detect the version once as 0.97, but normally just says Unknown Version. Despite this everything seems to work ok apart from the probe.

Automatic Homing - ok 4 Axis Test program (cutting air) - ran for 30 minutes without fault - ok

I attempted to add probing to refine the package and prepare for first cut, and followed the UGS video tutorial:

https://www.youtube.com/watch?v=kpz-6x_synE

But this is where I am struggling to get any results. Here's my problem:

  1. Home the machine
  2. Reset Zero
  3. Move to position above probe - G0 X50 Y25 Z-10
  4. Reset Zero or Individually reset X,Y and Z
  5. Probe settings - mm, G54, diameter 3.175, slow 100, fast 250, retract 5
  6. Z settings - thickness 20, probe distance / direction -10
  7. Initiate Probe

Results: The spindle does not move in any direction. The motors are not fired. The Visualizer immediately positions the probe at -10 and this is reported in the controller state (DRO).

By playing with the probe settings, I've also had very slow feeds in Z+ (not much help for probing), and other confusing behavior. If the probe does move and I touch the probe to the cutter (testing), the z movement immediately stops, but the cutter does not retract the specified amount. It just stops.

UGS Platform 2.0.7 TinyG controller Windows 10 x64

Any advise gratefully received. Thank you.

marshr32 commented 2 years ago

I know this is old but this may help someone else.

Not sure about your particular setup, but I don't use the probe module. Instead I made the attached macro and mapped it to a gamepad button (start in my case) Z probe macro.txt