Probing

edelec

Tlui sorry to hear of you wifes illness. Welcome back.

I have installed 2019-01-22-106 on V2.1

I have a test program as follows

%
G0 X0 Y0 Z10
M101
G91 G01 Z-50.0 F500.0

M102
G04P0

G90 G92 Z0.0
%

I have a wire connected to the Probe terminal, I have a wire connected to the GND-I terminal
I manually move to X-20 Y40 Z-30

I run test.nc
Beneath the Coordinate display the controller shows
2: G0 X0 Y0 Z10 Whilst the system is making that move and the cordinates are changing
When the coordinate display shows X 0.00 Y 0.00 Z 10.00 the line below the coordinate display shows
3: G91 G0 Z-50.0 F500.0
The controller shows  X0.00 Y0.00 Z10.00 busy and the Z axis does not nothing move

I the past I have tried with different installs and the Z axis has moved down but with no action when the wires are touched.

How do I get "Probe" to work?

ytliu

The Motion.out file size is correct.

Can you upload your configuration file (setting, uservar) to the forum?

tommygun

Hello, I ordered DDCS V3.1, and I have a probe, which is NC. How can I connect it to the controller? Thanks

Garikc

Good afternoon. I have a DDCSV2.1 controller, installed an alternative firmware from Pandora. In PROBE mode, the Z axis does not stop and continues to move forward. Where can I start solving the problem? What parameters need to be checked?

Assolo

ytliu Posted at 2019-10-13 07:10
The attached probe will be probed twice, you can customize it by following the prompts in the file a ...

Спасибо огромное! Все работает!

ytliu

The attached probe will be probed twice, you can customize it by following the prompts in the file and then install it to the controller.

Assolo

Здравствуйте. Подскажите пожалуйста, как можно реализовать второе, уточняющее касание зонда? Сейчас probe выглядит так. Запускаю Probe, ось z опускается до касания датчика и поднимается вверх. Хотелось бы второе касание на медленной подаче. Спасибо.

ytliu

Thank you, yes, I checked the program and must set #223 to 1 for the probe function to work.

gjh

I got it working - the critical item seems to be #223.

edelec

It was resolved by installing the factory original setting and uservar files. It seems that there was a corruption somewhere in the system which was cleared by overwriting these files. The probe terminal is now recognised.

gjh

So what was the end result of this? Did the probe input magically start working?
I am curious because I have the same problem but with a V1.1 unit. Originally 2016-x-x-73-NOR but now updated to 2019-03-20-107-NOR .
Still no joy (using mode 2). Is there some glitch in the software?