M140 P0 S55 Error: Invalid password!

[Dizzwold]

Hi Guy's,

Not had much time recently, but just fired up to do some more calibrating and thought I run a MBL and bed compensation.

I got a Invalid Password Error. Yes I'm running Duetpi on a Pi4, but I've not set any passwords so I don't knot what that's about.

Previously I had the blue Send button in the DWC kind of spinning like the beach ball while running the bed compensation, and after completing it would start another bed compensation.

This just happened again so switched everything of and rebooted, computer also and started again.

I've just typed M122 to get all the details for this post and I got the spinning button. I've actually managed to catch this in a screenshot.

It's still spinning now with no result from the M122. My computer and printer/Duet are 1.75 - 2m apart, in the same room separated by only myself and the chair I'm sat on.

If you look closely you will also see that my nozzle temp 2000˚, it's only a 40w! That good going, lol.

Just rebooted;

=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.2 (2022-09-13 15:17:43) running on Duet 3 MB6HC v1.01 (SBC mode)
Board ID: 08DJM-956BA-NA3TJ-6J9DA-3SN6T-9AAYV
Used output buffers: 2 of 40 (19 max)
=== RTOS ===
Static ram: 152664
Dynamic ram: 66068 of which 140 recycled
Never used RAM 131800, free system stack 216 words
Tasks: SBC(ready,0.6%,476) HEAT(notifyWait,0.0%,322) Move(notifyWait,0.0%,351) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,333) TMC(notifyWait,8.2%,91) MAIN(running,91.3%,923) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:02:20 ago, cause: power up
Last software reset at 2022-10-14 16:40, reason: User, GCodes spinning, available RAM 131512, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 133
MCU temperature: min 36.5, current 36.7, max 36.8
Supply voltage: min 24.0, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a, mspos 8, reads 49611, writes 0 timeouts 0
Driver 1: standstill, SG min n/a, mspos 8, reads 49611, writes 0 timeouts 0
Driver 2: standstill, SG min n/a, mspos 8, reads 49611, writes 0 timeouts 0
Driver 3: standstill, SG min n/a, mspos 8, reads 49611, writes 0 timeouts 0
Driver 4: standstill, SG min n/a, mspos 8, reads 49611, writes 0 timeouts 0
Driver 5: standstill, SG min n/a, mspos 8, reads 49611, writes 0 timeouts 0
Date/time: 2022-10-14 16:51:20
Slowest loop: 1.17ms; fastest: 0.06ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger* is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== CAN ===
Messages queued 187, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 104/0/0
Tx timeouts 0,0,104,0,0,83 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 5836/5836
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x2b1c8
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.2
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 39.16, max time between full transfers: 35.0ms, max pin wait times: 27.7ms/0.1ms
Codes per second: 0.05
Maximum length of RX/TX data transfers: 3096/936

Config.g

; Configuration file for Duet 3 MB 6HC (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.13 on Mon Sep 19 2022 16:04:20 GMT+0100 (British Summer Time)

; General preferences
M575 P1 S1 B57600                                  ; enable support for PanelDue
G90                                                ; send absolute coordinates...
M83                                                ; ...but relative extruder moves
M550 P"Duet 3"                                     ; set printer name
M669 K1                                            ; select CoreXY mode

; Bed Adjustment Screw Positions
M671 X5:278:278:5 Y5:5:302:302 P0.5					; front left, front right, back right, back left

; Drives
M569 P0.0 S0                                       ; physical drive 0.0 goes backwards
M569 P0.1 S0                                       ; physical drive 0.1 goes backwards
M569 P0.2 S1                                       ; physical drive 0.2 goes forwards
M569 P0.3 S1
M569 P0.4 S0                                       ; physical drive 0.3 goes forwards
M584 X0.0 Y0.1 Z0.2:0.3 E0.4                           ; set drive mapping
M350 X16 Y16 Z16 E16 I1                            ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E330.00                  ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00                ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00            ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00                ; set accelerations (mm/s^2)
M906 X900 Y900 Z900 E800 I30                       ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                            ; Set idle timeout

; Axis Limits
M208 X-2 Y-8 Z0 S1                                 ; set axis minima
M208 X330 Y330 Z400 S0                             ; set axis maxima

; Endstops
M574 X1 S1 P"!io1.in"                              ; configure switch-type (e.g. microswitch) endstop for low end on X via pin !io1.in
M574 Y1 S1 P"!io2.in"                              ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin !io2.in


; Z-Probe
M574 Z1 Z1 S2									   ; set endstops controlled be probe
M558 P5 C"^!io3.in" H5 F120 T6000                 ; set Z probe type to switch and the dive height + speeds
G31 P500 X-46 Y-19 Z1.66                            ; set Z probe trigger value, offset and trigger height
M557 X19:244 Y-2:304 P9                           ; define mesh grid

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138       ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0                                 ; create bed heater output on out0 and map it to sensor 0
M307 H0 R0.187 K0.192:0.000 D1.89 E1.35 S1.00 B0   ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                            ; map heated bed to heater 0
M143 H0 S120                                       ; set temperature limit for heater 0 to 120C
M308 S1 P"temp1" Y"thermistor" T100000 B4138       ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out1" T1                                 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 R2.498 K0.275:0.349 D6.79 E1.35 S1.00 B0 V24.0  ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S280                                       ; set temperature limit for heater 1 to 280C

; Fans
M950 F0 C"out7" Q500                               ; create fan 0 on pin out4 and set its frequency
M106 P0 C"Print Cooler" S0 H-1                     ; set fan 0 name and value. Thermostatic control is turned off
M950 F1 C"out8" Q500                               ; create fan 1 on pin out5 and set its frequency
M106 P1 C"Extruder Cooling" S1 H1 T45              ; set fan 1 name and value. Thermostatic control is turned on

; Tools
M563 P0 S"Hemera" D0 H1 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
; Emergency Stop
M950 J1 C"io4.in"
M851 P1 T0 S0 R0


; Miscellaneous
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

T0

M501

What on earth is going on?

I'd be grateful for your input as I haven't a clue what's going with this. Let me know if you need any other info.

[dc42]

@Dizzwold as you are running in SBC mode I'll ask @chrishamm if he has any ideas.

[chrishamm]

@Dizzwold It takes a while for G32 to complete so it is completely normal that the "Send Code" button goes into "busy" state as long as it is running (which typically takes some time). Please post your bed.g as well.

PS: If you get a temperature of 2000C, that probably means you've got an intermittent connection in your wiring somewhere between Duet and thermistor.

[Dizzwold]

@chrishamm @dc42

Hi Guy's,

Thank you both for taking a look.

Here's my bed.g;

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.3.13 on Mon Sep 19 2022 16:04:20 GMT+0100 (British Summer Time)
;M561 ; clear any bed transform
;G29  ; probe the bed and enable compensation

G28			; home
G30 P0 X5 Y5 Z-9999				; probe front left
G30 P1 X278 Y5 Z-9999			; probe front right
G30 P2 X278 Y302 Z-9999			; probe rear right
G30 P3 X5 Y302 Z-9999 S4  		 ;probe rear left
G1 X0 Y0

[Dizzwold]

@Dizzwold

I'm still have the problem where every time I home all, G32 followed by G29, I get a network error and the bed compensation runs at least twice.
I also now getting the Warning for substantial Z offset?
I've rebooted both my computer and the Duet / Raspberry Pi SBC and reset my router?

[Dizzwold]

@Dizzwold
Is there a guide on how to network my Duet/Rpi 4b sbc directly, this wifi issue is a real pain in the backside?

[Phaedrux]

Can you connect the Pi via ethernet cable to your router/switch?

Have you done a sudo apt update sudo apt upgrade recently on the Pi?

[Dizzwold]

@Phaedrux

Yes. I didn't know if I just plugged the ethernet cable in, and was good to go, or if I need to set anything else up.

[Phaedrux]

It should be good to go just plugging it in.

[Dizzwold]

@Phaedrux

I'm just making all the ends for connecting a network. Something I've been meaning to do for a year or so, but in the meantime while still using Wifi, here's my latest bed compensation after M561, Home-all, G32 then G29, and after yet another network error whlie doing so;

[Dizzwold]

@chrishamm @dc42 @Phaedrux

Same problem connected to ethernet.

The bed compensation scanned twice, then about halfway through the 2nd scan (don't know why it's doing this twice in the first place), it through up the network error again.

I there away to find if this is my router or Duet3?

Just thought about that, so connected the RPi (as I'm using/in SBC mode), directly to my computer via ethernet.

Same problem?

On closer inspection while running bed compensation again, in places around the bed my Z probe (Tronxy TR Inductive glass sensor), is detecting and shown by the led on top of it, yet looking at the paneldue at the same time it's not detected?

Is this a problem with my Duet 3 board, because if it is, I may have issues as I purchased it in January 2021, yet only now installed it?

[Phaedrux]

Do you have a new high quality SD card to use in the Pi? I'm wondering if it's an SD card issue when it's busy.

You can backup your config files in DWC first. Then download a fresh DuetPi image and burn it on the new SD card.

https://docs.duet3d.com/en/User_manual/Machine_configuration/SBC_setup

[Dizzwold]

@Phaedrux

I was kinda thinking that earlier, so download each file from the DWC System Directory.

I'm not so sure I actually was connected via the ethernet (I'm on a 2009 mac).

An Ip scan shows 2 ip address for the Duet/Pi also.

In the mean time I hooked up a keyboard, mouse and monitor to the Pi and same thing again sensor led would signal a sense (if it didn't the bed would crash anyway), but sometimes nothing on DWC Z probe.

I'll go and find another sd card an try again tomorrow.

Does anyone no how to connect a 2009 mac on a network to the Duet/Pi? I can find the RPi's mac-address and Ip address. Do I use finder. go, connect to server, because it doesn't find anything. I've tried typing in both the mac-address and ip address in connect to server, it goes to connect, but then comes back with "There was a problem trying to connect to xxxx check" etc, etc, etc.

[Phaedrux]

@Dizzwold said in M140 P0 S55 Error: Invalid password!:

but sometimes nothing on DWC Z probe.

Sometimes the trigger is too fast for DWC to capture.

On the pi if you turn off the wifi that should force it to use the ethernet. If you use an IP address to connect to DWC you may need to switch to using the IP address of the ethernet port instead of the old wifi address.

[Dizzwold]

@Phaedrux

Would sending M552 S-1 disable wifi, then I can go through and test the current ip address's I have.

I was using duet3.local with no cables, then I tried xxx.xxx.x.20, but now I have xxx.xxx.x.39 and xxx.xxx.x.41, so If Idisable the wifi only one of these should work and be ethernet?

Ethernet port, ie ls /sys/class/net/, cat /sys/class/net/xxx/address?

[Phaedrux]

No, the M552 commands only work in standalone mode when not using the Pi. You'd have to manage the networking settings on the pi itself.

[jay_s_uk]

@Phaedrux m552 etc work if using the duetpimanager I think
Edit: they are usable. See here for info https://github.com/Duet3D/DuetSoftwareFramework/tree/v3.3-dev/src/DuetPiManagementPlugin

[Dizzwold]

@jay_s_uk @Phaedrux

Thank you your replies and help.

I've disabled wifi with;
sudo apt update
sudo apt full-upgrade
sudo apt install rfkill
sudo rfkill block wifi

Probe sensor led is detecting every time, but Duet/Pi in DWC is still missing probe points?

Is this an SD card swap now, the feed rate of the probe is 120, so it's not going particularly fast?

[jay_s_uk]

@Dizzwold what do you mean its still missing probe points? does it come up with anything in DWC?

[chrishamm]

@Dizzwold Those network errors aren't pretty but they should not affect the code being run on the Pi/Duet. These messages can only show up if the connection between Duet and your device is interrupted, but it's hard to say why exactly they occur. It might be a driver issue, but that is hard to tell. Do the same error messages show up on another device, e.g. on a smartphone or tablet?