Ok, made some progress, (I hope), maybe just screwed it all up.
Below is what I got just running G32, no homing before G32, just power up and enter G32.

3:52:28 PM 9 points probed, min error -0.139, max error -0.024, mean -0.072, deviation 0.037
Height map saved to file heightmap.csv
3:51:46 PM Leadscrew adjustments made: -0.112 -0.287 0.118 0.125, points used 4, deviation before 0.127 after 0.000
3:51:23 PM Leadscrew adjustments made: -0.413 -1.085 0.258 0.559, points used 4, deviation before 0.481 after 0.000
3:51:00 PM G32
Leadscrew adjustments made: -0.511 -3.126 1.381 3.300, points used 4, deviation before 1.721 after 0.000

Changed config.g
Changed bed.g
Added bed_probe_points.g

bed.g and bed_probe_points.g was put in sys folder

config (2).g

bed (2).g

bed_probe_points.g

I used some of the files from fulg/voron on github.

Please elaborate if I may have caused me trouble later doing it this way.
Your assistance has been greatly appreciated.

CarlJ

up dated config.g and bed.g
and a sketch of z layout if it helps

config (1).g
bed (1).g

After homeall, the dwc display shows Z value same as error 9.480.
Is this correct, or should it be something else.

Yes, X+ moves to the right, Y+ moves to the back .
Removed G29 from bed.g.
G32 gives this error and does not move, before removal of G29 error shows but still goes thru the motions.

7:09:17 AM G32
Error: G30: Some computed corrections exceed configured limit of 1.00mm: 9.480 9.480 9.480 9.480

Quick question does the P in bed.g need to be the same as the P in drive assignments?
Like it is P0 should it be P5

I have checked wiring and remeasured, made sure entered in the right order.
P5 (drive5) front left
P6 (drive6) back left
P7 (drive7) back right
P8 (drive8) front right

changed S on M671 back 0.5 (original setting)

If I run G32 back to back, I have to increase H in M558, and increase S in M671 to keep from getting error.
G30: Some computed corrections exceed configured limit.
Limit being what S is in M671.

Attached is bed.g config.g and software information.

Any help or guidance is greatly appreciated.
Thank You
CarlJ
config.g

bed.g

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later + DueX5
Firmware Version: 2.05.1 (2020-02-09b1)
WiFi Server Version: 1.23
Web Interface Version: 1.22.6

Very good, guess need to scroll down alot to see it.
Fixed that.
Now to proceed to next hurdle. Usually I find what I need looking thru the posts. So I don't make many requests.
It's been a learning experience.

Thank You

homeall.g This is a new setup on corexy printer (voron)
Been weeding out problems as I go, been slow but productive till this.

Message response is Bad command r0.2 when I activate z_probe_ macro.

[0_1581953284105_config](Uploading 100%)

homeall.g

activate_z_probe.g

go_to_bed_center.g

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later + DueX5
Firmware Version: 2.05.1 (2020-02-09b1)
WiFi Server Version: 1.23
Web Interface Version: 1.22.6

Going to use probe for homez is the plan, need to figure it out also.

Any help or guidance is appreciated.

CarlJ

Hello, maybe I should have started another thread.
Using this probe and setup I get Bad command r0.2
What is the function or meaning of r0.2
If more information is needed please let me know.

Thank You