Warning - long, rambling Delta bed height mapping weirdness ahead

Culturedropout

Okay - having trouble with auto-mapping of bed heights.  I got tired of dragging my Windows 7 laptop downstairs, so I picked up a cheap used Dell Optiplex 755 tower with Windows 10 on it, and set that up to run the printer.  If I run bed height map on the Windows 10 machine, using direct USB host setup, it gets about halfway through the measurements and then Repetier Host stops responding and Windows eventually kills it.  If I run host/server on the same Windows 10 machine, it seems to work, except then I get things like this:

17:42:08.952 : Error:Apos x square

17:42:08.952 : Warning:Invalid delta coordinate - move ignored x:2384 y:5032 z:1316

17:42:08.952 : Warning:in queueDeltaMove to calculateDeltaSubSegments returns error.

17:42:08.952 : Warning:executeGCode / queueDeltaMove returns error

17:42:15.497 : Exception during socket read:Index was outside the bounds of the array.

.  

Connected to the server (running on Windows 10 PC, which is connected via USB to Arduino/RAMPS stack from my laptop via wifi.  Homed the printer, ran it down to 1cm or so above the bed, and then ran "Bed Height Map" from the tools menu.  Got this:

X: -60.00 -30.00 0.00 30.00 60.00

y: 60.00 29.73 29.73 30.93 30.93 31.76

y: 30.00 32.36 33.38 33.38 33.91 33.91

y: 0.00 29.72 29.72 31.46 31.46 32.36

y: -30.00 32.50 33.71 33.71 34.36 34.36

y: -60.00 27.13 27.13 31.34 31.34 32.50

17:06:31.848 : Repetier-Server successfully connected.

17:06:32.874 : FIRMWARE_NAME:Repetier_0.92.9 FIRMWARE_URL:https://github.com/repetier/Repetier-Firmware/ PROTOCOL_VERSION:1.0 

MACHINE_TYPE:Delta EXTRUDER_COUNT:1 REPETIER_PROTOCOL:3

17:06:32.874 : PrinterMode:FFF

17:06:36.742 : SelectExtruder:0

17:06:36.742 : X:0.00 Y:0.00 Z:320.000 E:0.0000

17:06:40.266 : X:0.00 Y:0.00 Z:292.000 E:0.0000

17:06:41.353 : X:0.00 Y:0.00 Z:262.000 E:0.0000

17:06:42.643 : X:0.00 Y:0.00 Z:212.000 E:0.0000

17:06:43.283 : X:0.00 Y:0.00 Z:192.000 E:0.0000

17:06:43.697 : X:0.00 Y:0.00 Z:182.000 E:0.0000

17:06:45.597 : X:0.00 Y:0.00 Z:152.000 E:0.0000

17:06:46.027 : X:0.00 Y:0.00 Z:142.000 E:0.0000

17:06:46.513 : X:0.00 Y:0.00 Z:132.000 E:0.0000

17:07:10.045 : Z-probe:27.13 X:-60.00 Y:-60.00

17:07:17.595 : Z-probe:31.34 X:-30.00 Y:-60.00

17:07:25.250 : Z-probe:32.50 X:0.00 Y:-60.00

17:07:32.869 : Z-probe:33.71 X:30.00 Y:-60.00

17:07:41.622 : Z-probe:34.36 X:60.00 Y:-60.00

17:07:50.461 : Z-probe:29.72 X:-60.00 Y:-30.00

17:07:57.994 : Z-probe:31.46 X:-30.00 Y:-30.00

17:08:05.659 : Z-probe:32.36 X:0.00 Y:-30.00

17:08:14.391 : Z-probe:33.38 X:30.00 Y:-30.00

17:08:22.124 : Z-probe:33.91 X:60.00 Y:-30.00

17:08:31.399 : Z-probe:29.73 X:-60.00 Y:0.00

17:08:38.403 : Z-probe:30.93 X:-30.00 Y:0.00

17:08:46.097 : Exception during socket read:Index was outside the bounds of the array.

17:08:53.793 : Exception during socket read:Index was outside the bounds of the array.

17:09:02.448 : Exception during socket read:Index was outside the bounds of the array.

17:09:11.167 : Exception during socket read:Index was outside the bounds of the array.

17:09:17.718 : Exception during socket read:Index was outside the bounds of the array.

17:09:25.352 : Exception during socket read:Index was outside the bounds of the array.

17:09:33.011 : Exception during socket read:Index was outside the bounds of the array.

17:09:40.650 : Exception during socket read:Index was outside the bounds of the array.

17:09:48.387 : Exception during socket read:Index was outside the bounds of the array.

17:09:54.842 : Exception during socket read:Index was outside the bounds of the array.

17:10:01.382 : Exception during socket read:Index was outside the bounds of the array.

17:10:09.027 : Exception during socket read:Index was outside the bounds of the array.

17:10:17.775 : Exception during socket read:Index was outside the bounds of the array.

Issued a G32 s2 command and got this:

17:15:57.407 : plane: a = 0.0406 b = -0.0361 c = 25.6700

17:15:57.407 : Transformation matrix: 0.999176 0.000000 -0.040591 0.001463 0.999350 0.036012 0.040565 -0.036041 0.998527

17:15:57.407 : CurrentZ:20.44 atZ:29.55

17:15:57.407 : Z after rotation:29.55

17:15:57.407 : Printer height:310.89

17:15:57.407 : Info:Autoleveling enabled

17:15:57.407 : X:-0.83 Y:80.68 Z:17.512 E:0.0000

17:15:57.407 : Info:Autoleveling disabled

17:16:10.055 : SelectExtruder:0

17:16:10.055 : X:0.00 Y:0.00 Z:310.875 E:0.0000

17:16:10.055 : Info:Autoleveling enabled

17:16:10.059 : Warning: Communication timeout - resetting communication buffer.

17:16:10.059 : Connection status: Buffered:0, Manual Commands: 1, Job Commands: 0

17:16:10.059 : Buffer used:0 Enforced free byte:7 lines stored:0

Ran Bed Height Map again after that and got this (also with lots of "Exception during socket read: Index with outside the bounds of the 

array." messages): 

X: -60.00 -30.00 0.00 30.00 60.00

y: 60.00 29.47 30.69 30.69 30.69 31.44

y: 30.00 27.81 27.81 27.81 29.47 29.47

y: 0.00 31.77 31.77 32.45 32.45 32.45

y: -30.00 29.43 30.61 30.61 30.61 31.77

y: -60.00 27.21 27.21 27.21 29.43 29.43

Is there anything you can suggest as to what might be going on (other than "It was aliens")?  Anything you'd like me to try?  Thanks for any help you can give!

-Bill

Repetier

Simple part is

Warning:Invalid delta coordinate - move ignored x:2384 y:5032 z:1316

which simply says you are not allowed to go there. Divide coordinates by steps per mm to get position in mm. Always think about the z probe offset that gets added to your coordinates so the summed up position must be allowed!

Exception during socket read:Index was outside the bounds of the array.

Host->server connection uses a websocket so I assume that is where it goes wrong producing that error. I have found a case producing this on connection when selected printer does not exists on server. That would be fixed on next host release. Otherwise I never saw that error message. So try going in host printer settings and reselect your printer and maybe it goes away. 

Timeout comes from G32 taking longer then timeout. Not critical here and with dev firmware and latest host/server it would also not happen any more as a new protocol fixes that problem.

Apart from this it seems to work. Just make sure to start bed height map at a low z like z probe bed distance + z probe height or lower otherwise first value will be wrong on at least newer firmware versions.