Topics created by vlex

@vlex said in G32 keeps exceeding bounds of M557:

All is good and dandy until the G32, after it all of the sudden the circle becomes an ellipse and a quite elongated one

are you 100% sure you have the probe offsets correct? if you have the probe XY offsets wrong that could explain some of the behaviour you are seeing.

See:
https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_testing#measuring-probe-x-y-offset

Thanks @dc42 FWIW I did end up wiring it as show in the diagram before waiting for input here it didn't fry the board, so I was happy for a while. Then configured the zprobe correctly, spent like 2 hours correcting the geometry and adding setting to the gcode so it works and it finally did, BUT THEN I broke the effector, so I'm back at square one. I'm logging here the links I used for posterity and for the off chance someone else is in my shoes in the future:

https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_Overview
https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe
https://duet3d.dozuki.com/Wiki/G32
https://duet3d.dozuki.com/Wiki/Calibrating_a_delta_printer#Section_Auto_calibration
https://docs.duet3d.com/User_manual/Reference/Gcodes

Alas the new docs don't have any of the useful steps in the old ones, but good they're still there.

I guess the thread can be closed..

So I got a new e3d volcano that i just assembled and ran a quick calibration cube test, which came out kinda okayish.. I think something is wrong with my geometry though - I run delta calibration with the points generated by the reprap config tool online (though I've moved one a bit because the irregular effector interferes with one of the belts). Everything seems to run just fine but then when I run a print with a raft or any other base adhesion aid it seems as if everything is skewed ever so slightly - in one corner seems the nozzle scrapes the bed, in the opposite it seems as if it's squirting molten filament in the air and gobbles it up in big goops during every consecutive pass. Used the edge of a metal ruler to ensure the bed is straight and it is as far as I can see i.e. within 0.1mm edge-to-edge. Perhaps it is worth noting that the bed is a weapons grade chinesium aluminum bed with the heater towards the electronics in the base of the delta and the bare aluminum surface towards the hotend. Not sure whether that is of any importance, or whether I'm doing something insanely stupid by having it all set up like that and I overlook something obvious, so confessing my sins upfront.

Here's the gcode the reprap tool generated:

; bed.g ; called to perform automatic delta calibration via G32 ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Feb 22 2021 09:18:29 GMT+0000 (Greenwich Mean Time) M561 ; clear any bed transform G28 ; home all towers ; Probe the bed at 3 peripheral and 3 halfway points, and perform 6-factor auto compensation ; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g. G30 P0 X0 Y84.9 H0 Z-99999 G30 P1 X68 Y-47 H0 Z-99999 ; <- moved this one to avoid interference with the belt. G30 P2 X-73.53 Y-42.45 H0 Z-99999 G30 P3 X0 Y42.4 H0 Z-99999 G30 P4 X36.72 Y-21.2 H0 Z-99999 G30 P5 X-36.72 Y-21.2 H0 Z-99999 G30 P6 X0 Y0 H0 Z-99999 S6 ; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors ; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed)

I decided that may be the self calibration is not good enough for the funky heated bed I've got so I followed the calibration guide here and used the escher bed calibration wizard to generate new code:

; bed.g file for RepRapFirmware, generated by Escher3D calculator ; 16 points, 7 factors, probing radius: 80, probe offset (0, 0) G28 G30 P0 X0.00 Y80.00 Z-99999 H0 G30 P1 X51.42 Y61.28 Z-99999 H0 G30 P2 X78.78 Y13.89 Z-99999 H0 G30 P3 X69.28 Y-40.00 Z-99999 H0 G30 P4 X27.36 Y-75.18 Z-99999 H0 G30 P5 X-27.36 Y-75.18 Z-99999 H0 G30 P6 X-69.28 Y-40.00 Z-99999 H0 G30 P7 X-78.78 Y13.89 Z-99999 H0 G30 P8 X-51.42 Y61.28 Z-99999 H0 G30 P9 X0.00 Y40.00 Z-99999 H0 G30 P10 X34.64 Y20.00 Z-99999 H0 G30 P11 X34.64 Y-20.00 Z-99999 H0 G30 P12 X0.00 Y-40.00 Z-99999 H0 G30 P13 X-34.64 Y-20.00 Z-99999 H0 G30 P14 X-34.64 Y20.00 Z-99999 H0 G30 P15 X0 Y0 Z-99999 S7

It constantly runs into errors like "Z probe already triggered at start of probing move" due to from what I can see the hotend not going back up between moves and essentially dragging the hotend across the bed towards the mid-test-points.

P.S. While writing this I notice the wizard generated code has no H-values like the reprap one does. I'll experiment with that and report.

The new volcano arrived a couple of days ago and I just finished assembling and reconfiguring the config.g to the new dimensions - the jitter turns out as suspected was due to a blockage in either the cold side or the heatbreak. Either way the new hotend now works just fine, except there's obviously some geometry quirks i need to take care (in a separate thread though).

This matter could be considered resolved. Thanks for the help!

@vlex said in Duet2WiFi net connection inconsistent between VIN and USB:

if this were documented anywhere

It is.

https://duet3d.dozuki.com/Wiki/Gcode#Section_M552_Set_IP_address_enable_disable_network_interface

P"ssid" (optional, RepRapFirmware 1.20 and later) SSID of network to connect to. The SSID and password must already have been registered using M587. If this parameter is not present, the Duet 2 WiFi will try to connect to the strongest network that is broadcasting its SSID and whose SSID has been registered using M587.

It's also the default behaviour of all wireless clients to connect to the strongest available network.