Best posts made by Shinomori

@phaedrux
I keep getting a "Post content was flagged as spam by Akismet.com" when I try to post a reply.

@phaedrux
I'll grab all that when I can make it over the the print lab.

I have a "set home macro" that I think was a "G92 X0 Y0 Z0", but I will double check it. We are looking to add a bltouch or some other mechanical bed sensor to the printer soon to avoid human error inaccuracies, but there doesn't seem much point if the printer won't run gcode with mesh compensation on.

The motion seems pretty good so far. Doing a dry run of a big 400mm cylinder in vase mode had pretty smooth motion. The goal is to print a part that is about 1m x 1.5m, but gotta get that first layer right first!

Thanks

@dc42
I haven't made it back over to the machine, but on the last test it did not exceed 5mm.
I think the farthest deviation was around 1mm on a 200mmx200mm, 3x3 grid used for that small test print.

It doesn't throw an error and seems to think it is still printing because the print duration estimates are moving around. The print head just stops moving. I don't remember if the extruder was still feeding and I think it wasn't responding to the pause print and I had to use the emergency stop. Probably because it thought it was in the middle of a print move and needed to finish that before pausing.

May need to update to 3.3. Are there mayor syntax changes that would require rewrite of all the system files?

Will update when I can make it over to the machine to get info off it.

@phaedrux
Sorry. Didn't see this reply. Here is the config.g.

; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Sun Feb 02 2020 14:18:25 GMT-0600 (Central Standard Time)

; General preferences
G91 ; send relative coordinates...
M83 ; ...but relative extruder moves
M550 P"duet3" ; set printer name

; Drives
M569 P0.0 S0 ; physical drive 0.0 goes forwards
M569 P0.1 S1 ; physical drive 0.1 goes forwards
M569 P0.2 S0 ; physical drive 0.2 goes forwards
M569 P0.3 S1 ; physical drive 0.3 goes forwards
M569 P0.4 S0 ; physical drive 0.4 goes forwards
M584 X0.0 Y0.1 Z0.2 E0.3 U0.4 ; set drive mapping
M669 K6 A0.0:-2265.0:0.0 B1725.0:1100.0:0.0 C-1740.0:1120.0:0.0 D2666.0 P1500.0
M350 X16 Y16 Z16 E16:16 I1 ; configure microstepping with interpolation
M92 X92.90 Y92.90 Z92.90 E396.00 U93.00 ; set steps per mm
M566 X900.00 Y900.00 Z900.00 E120.00 U900.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z6000.00 E1200.00 U6000.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z500.00 E250.00 U500.00 ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E800 U1000 I60 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 Z-05 S1 ; set axis minima
M208 Z1500 S0 ; set axis maxima

; Endstops
; WARNING: No endstops configured

; Z-Probe
M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
;M557 X50:950 Y50:950 S200 ; define mesh grid

; Heaters
M308 S0 P"temp1" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp1
M950 H0 C"out1" T0 ; create nozzle heater output on out1 and map it to sensor 0
M143 H0 S270 ; set temperature limit for heater 0 to 270C
M307 H0 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M140 H-1

; Fans
M950 F0 C"out7" Q500 ; create fan 0 on pin out7 and set its frequency
M106 P0 S0 H0 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out8" Q500 ; create fan 1 on pin out8 and set its frequency
M106 P1 S0 H0 ; set fan 1 value. Thermostatic control is turned off

; Tools
M563 P0 S"Extruder" D0.3 H0 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined
M564 S0 H0 ;allow move without homing
M557 R400 S200
; Miscellaneous
M501 ; load saved parameters from non-volatile memory
T0 ; select first tool

Here is the start of the gcode.

; generated by PrusaSlicer 2.3.1+win64 on 2021-05-06 at 23:24:46 UTC

;

; external perimeters extrusion width = 1.35mm
; perimeters extrusion width = 1.35mm
; infill extrusion width = 1.35mm
; solid infill extrusion width = 1.35mm
; top infill extrusion width = 1.20mm
; first layer extrusion width = 1.40mm

M107
M104 S230 ; set temperature
;TYPE:Custom
G90
G29 S1

M109 S230 ; set temperature and wait for it to be reached
G21 ; set units to millimeters
G90 ; use absolute coordinates
M83 ; use relative distances for extrusion
; Filament gcode
;LAYER_CHANGE
;Z:0.8
;HEIGHT:0.8
G1 Z0.800 F4800.000
G1 E-0.60000 F2400.000
G1 X-12.321 Y4.326 F4800.000
G1 E0.60000 F2400.000
;TYPE:Skirt
;WIDTH:1.4
G1 F600.000

The procedure I am following is to tighten all the lines up until it is centered over a mark directly below. Then I set that as home. Then I lower it to near the bed and set home again. Double check tensions. Rehome if necessary. I then run a g29 mesh calibration. Try to manually match all points to same offset from bed as the home with a shim. This is usually way off in some points which is not surprising. Return to home and check if it has drifted. If no drift run the print.

If I run this gcode it starts as expected then hangs up after drawing it's first quarter circle. No errors. Web view seems to think the print is still running. It just stops.

If I comment out the g29 s1 it completes the print.

It is not a pretty thing but I can work on that once I know it will run a gcode. And the hang up on with the mesh compensation is very strange. Surfaces we are hoping to run this thing on will probably be even less flat than this as we proceed so we definitely need a mesh to help with printing.

Thanks. Sorry again for the delay.

Hi,
I am trying to setup a hangprinter with a duet3 running duetpi. I have managed to do a few small test prints so the calibration is at least close and it seems to be working. My build plate is a full sized piece of plywood so it is not very flat. I was trying to do a mesh compensation manually collecting the points and the duet interface shows it is captured. Many points are off by several mm which seems correct for the piece of wood and hence the need for a mesh compensation. My test print is a small cylinder in vasemode with a brim. If I run it normally it works. If I add the g29 s1 to the start gcode the print will start as expected but stop as soon as it completes a quarter circle and doesn't continue beyond that. Any thoughts? Thanks!

@phaedrux
The last one was just an output of the m122 and it refused it. I had a big post prepared with lots of details. I'll see if I take the M122 out if it works.

Thanks. I'll have to take a look through the changelog.

I did reflash the Pi SD card to the newest version and then run update/upgrade. Hostname on pi is duet3 and it does show up as that when I scan the network to find the ip address to connect to. Not too concerned about that one other than it was working before and now is not and that knowledge might help with diagnosing some change. scanning for ip and connecting is not much of a problem.

Should be remounting the boards and doing some more testing tomorrow.

@fcwilt We are working with a group that is wanting to print building sized objects with a custom material, but the printer needs to be easy to transport. I know of no other printer that can do such a large print volume with so few materials for the printer itself. So we proposed a hangprinter This is the first phase proof of concept. If it works we'll be moving to a v4 hangprinter with a pellet extruder. This is why the mesh level needs to be working. We are currently trying to print on 4x8 sheets and will eventually be printing straight to the ground.

@phaedrux Was in the area and stopped by real quick. Tried running a G90 or G91 right after establishing the home. Tried this with dive bigger than minima and smaller and with the Z minima set to 0. All cases the G30 worked but the G29 still did not.

Next step is to connect direct to duet with cable.

The dive is currently set slightly larger than the Z minima. Here is the current config.

; General preferences
G91 ; send relative coordinates...
M83 ; ...but relative extruder moves
M550 P"duet3" ; set printer name

; Drives
M569 P0.0 S0 ; physical drive 0.0 goes forwards
M569 P0.1 S1 ; physical drive 0.1 goes forwards
M569 P0.2 S0 ; physical drive 0.2 goes forwards
M569 P0.3 S1 ; physical drive 0.3 goes forwards
M569 P0.4 S0 ; physical drive 0.4 goes forwards
M584 X0.0 Y0.1 Z0.2 E0.3 U0.4 ; set drive mapping
M669 K6 A0.0:-2265.0:0.0 B1725.0:1100.0:0.0 C-1740.0:1120.0:0.0 D0.0:0.0:2666.0 P1500.0
M350 X16 Y16 Z16 E16 U16 I1 ; configure microstepping with interpolation
M92 X92.90 Y92.90 Z92.90 E396.00 U93.00 ; set steps per mm
M566 X900.00 Y900.00 Z900.00 E120.00 U900.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z6000.00 E1200.00 U6000.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z500.00 E250.00 U500.00 ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E800 U1000 I60 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 Z-5 S1 ; set axis minima
M208 Z1500 S0 ; set axis maxima

; Endstops
; WARNING: No endstops configured

; Z-Probe
M558 P0 H6 F120 T6000; disable Z probe but set dive height, probe speed and travel speed
G31 P500 X0 Y0 Z0
M557 R400 S200
;M557 X-100:100 Y-100:100 S100 ; define mesh grid

; Heaters
M308 S0 P"temp1" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp1
M950 H0 C"out1" T0 ; create nozzle heater output on out1 and map it to sensor 0
M143 H0 S270 ; set temperature limit for heater 0 to 270C
M307 H0 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M140 H-1

; Fans
M950 F0 C"out7" Q500 ; create fan 0 on pin out7 and set its frequency
M106 P0 S0 H0 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out8" Q500 ; create fan 1 on pin out8 and set its frequency
M106 P1 S0 H0 ; set fan 1 value. Thermostatic control is turned off

; Tools
M563 P0 S"Extruder" D0.3 H0 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined
M564 S0 H0 ;allow move without homing
; Miscellaneous
M501 ; load saved parameters from non-volatile memory
T0 ; select first tool

@phaedrux I copied the basic delta config for motors and set home and tried G29 and it worked unless the M557 was too big then it threw the same errors. Converted back to HP config. Tried G1 movement commands in absolute mode well past the M557 limits and it was allowed and the printer moved to those locations. The G29 still threw errors for all points.

@shinomori Tobben said this on the hangprinter discord:
"
The failing test is here: https://github.com/Duet3D/RepRapFirmware/blob/3.4-dev/src/GCodes/GCodes4.cpp#L644

It looks like Hangprinterkinematics.h/cpp don't implement the function IsReachable()

The very old RRF version I had on my previous prototype had that function implemented. But is seems it has fallen though the cracks in my latest RRF work. Making a pull request now"

He sent me this fw file. Where it is working and print continues with mesh enabled. Duet3Firmware_MB6HC.bin

Thanks for help guys .

How would I know when those fixes are in the main branch? I'm not really git fluent yet.

@dc42 I understand. The current fw that I was sent has the mesh leveling working so I am ok for now. Just want to keep and eye out for whenever the official fw has the fix so i can jump to that one or avoid it if it is missing. Thanks!

@dc42
On the current version of RRF Running G29 resulted in nothing but errors. I haven't gotten a mesh since updating from 3.0 to 3.3. The .bin Tobben sent allowed me to get a mesh and run a print using G29 S1 in the gcode. I am not certain any compensation actually happened as it was a small print, but it finished the print and on 3.0 it wouldn't even finish the first line.

G31 was here:
; Z-Probe
M558 P0 H5 F120 T6000; disable Z probe but set dive height, probe speed and travel speed
G31 P500 X0 Y0 Z0
;M557 R100 S50
M557 X-100:100 Y-100:100 S100 ; define mesh grid

I would prefer to use the default FW, but this one is working at the moment. Tobben took some time out of his vacation to get me that fix so I really appreciate it and not surprised it was just a hacky fix.

I don't have a comparison from the old heightmap on 3.0 since the plywood we are trying to print on has warped and shifted since capturing the older one.(also I think some of my settings were wrong so it was capturing bad numbers)