Height map - Scanning Error

[ArturoPin]

Versions

• Candle version: 1.1.7 and Candle 1.2.15b x64
• Firmware version: 1.1

PC info

• OS: Windows 10 Home Single Language, Version: 21H2
• OpenGL version: 4.6

Describe the bug After the scanning process of the heightmap the values remain as "nan".

I have an issue when I generate the Heightmap, I create a new one, set the dimensions, and I clic on the Probe button to start the scanning process. This begins and ends without displaying any error. But all values of the heightmap remain as nan.

To Reproduce Steps to reproduce the behavior:

1. Set the Origen
2. Open a *.nc file
3. Clic on the "Create" button on the Heightmap menu
4. Set the Heightmap settings
5. Clic on the "Probe" button
6. The Scanning process begins
7. The message "Job done" pops up after the scanning ended up. (The heightmap values remains as "nan")

Expected behavior I expected to see the values stored while the scanning is being executed or at least when the scanning has already finished.

Screenshots

Additional context I have tried on different versions of candle 1.1.X and 1.2.X but this issue is present on all.

[muhammadelmogy]

Under settings ->Heightmap: make sure heightmap probing feed is set to a proper value and is not empty! for example 20

[ArturoPin]

It is set to a value of 10

[ArturoPin]

Update: I'm using a Comgrow Robo 3018, I messaged the company and they told me that the router is not able to perform a heightmap, I cannot understand why. The router is using a controller based on a MEGA328P microprocessor running GRBL 1.1f. I am trying to contact the designer to get that information. But if anyone knows about this problem, can you help me to fix it?

[mar0x]

Hello. Please

1. enable console output for commands;
2. make sure Z-probe command configured;
3. connect your probe tool;
4. make sure letter "P" appears at the top-left corner of 3D view when you manually touch the probe;
5. perform a single manual Z probe.

I assume the tool starts moving down until it touches the probe. Please share the Z-probe command and complete console window output.

[ArturoPin]

Hello,

First of all, Thanks for your help. I'm new on this, but I hope I did what you said.

1. Using a serial monitor, I sent the code "G21G91G38.2Z-30F100".
2. The router started to move on the z axis, until I performed a manual Z-probe.
3. The router stopped but I didn't receive the letter "P", instead of it, I received only an OK.
4. I repeated the same on Candle and I got the same

Do you know what I can do?

[ArturoPin]

I don't know if it can help but my settings are: Grbl 1.1f ['$' for help] $0=10 $1=25 $2=0 $3=6 $4=0 $5=0 $6=0 $10=1 $11=0.010 $12=0.002 $13=0 $20=0 $21=1 $22=0 $23=0 $24=25.000 $25=500.000 $26=250 $27=1.000 $30=1000 $31=0 $32=0 $100=400.000 $101=400.000 $102=400.000 $110=800.000 $111=800.000 $112=500.000 $120=500.000 $121=500.000 $122=500.000 $130=180.000 $131=300.000 $132=45.000 ok

[mar0x]

It seems something wrong with your firmware. Here is my console output for the probe:

G21G91G38.2Z-20F10 < [PRB:0.000,0.000,-22.951:1]
ok

Regarding 'P' letter. It normally appears in main 3D view window when you touch the probe:

Candle constantly send '?' request and get the status back. This is the output from terminal (the lines started from '>' is my input and not displayed actually):

Grbl 1.1f ['$' for help]
> ?
<Idle|MPos:0.000,0.000,0.000|FS:0,0|WCO:0.000,0.000,0.000>
> ?
<Idle|MPos:0.000,0.000,0.000|FS:0,0|Ov:100,100,100>
> ?
<Idle|MPos:0.000,0.000,0.000|FS:0,0|Pn:P>
> G21G91G38.2Z-20F10
[PRB:0.000,0.000,-0.598:1]
ok
> ?
<Idle|MPos:0.000,0.000,-0.605|FS:0,0|WCO:0.000,0.000,0.000>

During height map probe Candle relies on [PRB:0.000,0.000,-0.598:1] response and get Z position from this response.

As soon as your vendor said the machine unable to probe, he maybe knows something we don't know regarding the actual firmware or schematic of your board :)

[mar0x]

Regarding your GRBL settings I would say the accelerations are pretty high ($120, $121, $122).

Also the travel over Z axis is 45mm ($132) and the hard limits are enabled ($21). Maybe the probe position is out of limits? Try to disable the hard limits ($21=0) and repeat the test.

Check the defaults here: https://github.com/gnea/grbl/wiki/Grbl-v1.1-Configuration .

[ArturoPin]

It seems something wrong with your firmware. Here is my console output for the probe:

G21G91G38.2Z-20F10 < [PRB:0.000,0.000,-22.951:1]
ok

Regarding 'P' letter. It normally appears in main 3D view window when you touch the probe:

Candle constantly send '?' request and get the status back. This is the output from terminal (the lines started from '>' is my input and not displayed actually):

Grbl 1.1f ['$' for help]
> ?
<Idle|MPos:0.000,0.000,0.000|FS:0,0|WCO:0.000,0.000,0.000>
> ?
<Idle|MPos:0.000,0.000,0.000|FS:0,0|Ov:100,100,100>
> ?
<Idle|MPos:0.000,0.000,0.000|FS:0,0|Pn:P>
> G21G91G38.2Z-20F10
[PRB:0.000,0.000,-0.598:1]
ok
> ?
<Idle|MPos:0.000,0.000,-0.605|FS:0,0|WCO:0.000,0.000,0.000>

During height map probe Candle relies on [PRB:0.000,0.000,-0.598:1] response and get Z position from this response.

As soon as your vendor said the machine unable to probe, he maybe knows something we don't know regarding the actual firmware or schematic of your board :)

I thought the same about the firmware. I did an upgrade to GRBL 1.1h and the problem was gone. About the accelerations.... Thanks for the advice, I'm new on CNC so I will read about it, to tune it up. Thanks