Hang printer - Print stops with mesh leveling

Shinomori

@phaedrux
The update seemed to work and the print continued past the hold up spot, but the UI was completely messed up.

If i just copy all the system files from the web ui and then copy them back. That should work?
I have limited time at the printer and it is a 20 minute drive to get to it so doing a fresh install and copy over config seems like more sure fire way to get up and going. I'll give it a shot when I get over to the printer later today.

Thanks

Phaedrux

Did you verify with M122 or M115 that the firmware was updated?

How was the UI messed up?

Shinomori

@phaedrux
Got locked out of the building till today.

Just getting in to work on the machine.
here is what m115 shows.

FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 FIRMWARE_VERSION: 3.0 ELECTRONICS: Duet 3 MB6HC FIRMWARE_DATE: 2020-01-03b3

Doing another update/upgrade on the duet pi, Then I will be copying the system files and doing a clean flash.

This is what the dashboard shows.

So I have no updates on printer function.

If I start a print the status page shows printing but never updates.
I can't connect to duet3.local anymore even though router shows that name. Have to use ip directly.
Console commands work fine and print will run just no status shown.

Shinomori

@shinomori I ran the update/upgrade again. It went through some files. Now update says everything is up to date.

m115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 FIRMWARE_VERSION: 3.0 ELECTRONICS: Duet 3 MB6HC FIRMWARE_DATE: 2020-01-03b3

Still have messed up UI.

jay_s_uk

@shinomori I suggest running Bossa to get your board updated https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_All_other_Duet_boards

Phaedrux

It looks like the DWC files were updated, but the firmware on the board itself didn't get updated.

Getting the board itself flashed to 3.3 with Bossa should get you back in sync.

Let us know how you get on with Bossa.

Shinomori

@phaedrux Ok
I updated the duet through usb with Bossa. Used "Duet3Firmware_MB6HC.bin". It seemed to take. reconnected the pi and I can ssh into the pi but getting a "failed to connect DCS is not started" error on the web interface.

Phaedrux

Are you able to communicate with the Duet3 over USB and YAT terminal to check the firmware version with M115?

Have you downloaded a fresh image of DuetPi?

Shinomori

@phaedrux I have the image but have not flashed it yet.

Phaedrux

I get the sense that your Duet3 and Pi image are from the early days of RRF3, so a fresh download of Duet Pi would be a good idea.

Shinomori

@phaedrux It was definitely very early. I'm not having any luck with yat or pronterface talking direct to the duet. I'll try flashing a new duet pi image and see how that does.

Phaedrux

When you flashed with Bossa was it able to read back and verify the firmware?

Does the duet show up in device manager as a USB device?

If we're still unable to get communication between the duet and Pi it might be beneficial to setup an SD card to use the Duet in standalone mode. If the Duet is connected to ethernet and there is a M552 S1 command in config.g to enable networking, and the DWC files are present in the /www folder you should be able to access DWC directly by IP address.

https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Running_in_standalone_mode

Shinomori

@phaedrux Connected with Bossa. Under info I get.

Hmmm I'm not sure the bossa flash is working. it keeps closing when I try to run something on it so i get no verifications.

Shinomori

@shinomori Our duet and pi are mounted on the ceiling with only power going to it. connecting to it over a wifi hotspot on phone.

Phaedrux

The Duet3 can be pretty picky about the USB cable for flashing.

Given your situation of being a bit remote and the install being a bit hard to reach our options are either getting a better USb cable or trying to setup an SD card for standalone mode provided the Duet3 still has firmware on it and hasn't been erased yet. Did you use the erase jumper?

What does the Duet show up as in the Device manager?

Shinomori

@phaedrux

Ok I've got the duet and the pi sitting on my desk now for easier work. I downloaded the firmware again. Plugged in with new usb that was in the box with the duet.

Shows connected to "ATSAME70x20" on com8. Try flashing "Duet3Firmware_MB6HC.bin". And I get a flash command failed error. Tried jumper on erase pins and reset button, but the diag light always stays just dimly lit. I'm messing up somewhere.

Phaedrux

@shinomori said in Hang printer - Print stops with mesh leveling:

   I'm messing up  somewhere.

Following these steps?

https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_To_update_via_USB_using_a_Windows_host

Using the Pi itself is also explained there.

dc42

@shinomori said in Hang printer - Print stops with mesh leveling:

Shows connected to "ATSAME70x20" on com8. Try flashing "Duet3Firmware_MB6HC.bin". And I get a flash command failed error. Tried jumper on erase pins and reset button, but the diag light always stays just dimly lit.

This typically means there is a USB comms issue. The bootloader puts the USB into full speed mode (I've no idea why) so the USB cable and port are quite critical. Try a different USB port on the PC, or a different USB cable. Also be aware of the possibility of USB ground loops (using a laptop running from its internal battery to do the programming is a good way to avoid them).

The Erase jumper must be removed before you do the actual programming.

Shinomori

@dc42 Ok I followed that set of instructions and it seems to have worked.

m115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet 3 MB6HC v0.6 or 1.0 FIRMWARE_DATE: 2021-06-15 21:45:56

After copying all my old config files back on I am getting this error sitting on the bench with only duet and pi:

Error: M669: Wrong number of values after '''D''', expected 3

Also can't connect to "duet3.local", but ip address works.
Here is 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 D2666.0 P1500.0
M350 X16 Y16 Z16 E16 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

JoergS5

@shinomori said in Hang printer - Print stops with mesh leveling:

Error: M669: Wrong number of values after '''D''', expected 3

RRF3.3 needs 3 parameters for D. RRF 3.01 eg didn't check the number of values of the D parameter, so the config is from an older RRF version. Better control of the anchor is a new feature of 3.3: https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x#reprapfirmware-33 "M669 when using Hangprinter kinematics now allows the XY coordinates of the D anchor to be specified". The "line build-up compensation" new feature sounds interesting also, whatever it is.

Documentation of https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareHangprinter is not current, you should set D0.0:0.0:2666.0 now.
The old D was only Z: "Dzzz Z coordinate of the D anchor (the XY coordinates of the D anchor are 0,0)".

I wonder why you don't have a M350 value for U (microstep value).

Also can't connect to "duet3.local", but ip address works.

duet3.local is a name which must be mapped to the IP address somewhere (where depends on your operating system). Maybe you changed the IP address in the past or used a second duet. Anyway, I would take the IP address for all accesses.