Change the 'hallo' ('M110') command, that octoprint sends to Duet2 to 'M555 P2'. Then the connect works.

@Phaedrux Hello, I bought here https://www.filafarm.de/

The error is found. Thank you very much for your effort.
The most unlikely error in my opinion has occurred: The ethernet module is defective.

The downgrade to version 3.4.4 did nothing. So I removed the ethernet module from another 3d printer and installed it in my "problem" printer. The printer immediately received an ip address. Problem solved.

Hello @droftarts ,
I use an ethernet interface, not a wifi interface.

@jay_s_uk
Hello,
I was away for a few days and therefore could not answer. Here now the logs:

Send: M552 S0
Recv: Network stopped
Recv: ok
Send: M552 S1
Recv: ok
Send: M552
Recv: Network is enabled, configured IP address: 0.0.0.0, actual IP address: 0.0.0.0
Recv: ok

Any Idea?

Hello @Phaedrux,

thanks for your answer. Here are the results:

Send: M552 S0
Recv: Network stopped
Recv: ok

Send: M552 S1
Recv: ok

Any advice?

Hello,
I use a Duet2 with Ethernet.
After updating from V3.4.4 to V3.4.5 Duet2 does not get the IP address anymore.
There are all firmware files in /firmware.
The SD card is ok.
Paneldue works.
USB terminal with cut 5V supply also works.
A M115 via terminal results:
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.4.5 ELECTRONICS: Duet Ethernet 1.02 or later FIRMWARE_DATE: 2022-11-30 19:36:12

I am at a loss. Does anyone have any ideas?

regards,
Dirk

My config.g:

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat Apr 03 2021 02:40:13 GMT+0200 (Mitteleuropäische Sommerzeit)
; General preferences
G90                 ; send absolute coordinates...
M83                 ; ...but relative extruder moves
M555 P2 ; Marlin Mode

M550 P"Duet X-Max"    ; set printer name
; Network
;M551 P""                                       ; set password
M552 P0.0.0.0 S1                               ; enable network and acquire dynamic address via DHCP
M586 P0 S1                                     ; enable HTTP
M586 P1 S0                                     ; disable FTP
M586 P2 S0                                     ; Disable Telnet

; Drives
;M569 P0 S0                                     ; physical drive 0 goes forwards X Short60 Mod
M569 P0 S1                                     ; physical drive 0 goes forwards X Icarus
M569 P1 S1                                     ; physical drive 1 goes forwards Y
M569 P2 S1                                     ; physical drive 2 goes forwards Z
M569 P3 S1                                     ; physical drive 3 goes forwards E0
M569 P4 S1                                     ; physical drive 3 goes forwards E1
M584 X0 Y1 Z2:4 E3                               ; set drive mapping
M350 X16 Y16 Z16 E16 I1                        ; configure microstepping with interpolation
;M92 X94.25 Y94.25 Z400.00 E415.00        ; set steps per mm Extruder BMG
;M92 X94.25 Y94.25 Z400.00 E690.00        ; set steps per mm Extruder Icarus
M92 X94.25 Y94.25 Z400.00 E690.00         ; set steps per mm Extruder Icarus
M566 X300.00 Y300.00 Z120.00 E300.00      ; set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z900.00 E6000.00 ; set maximum speeds (mm/min)
M201 X2000.00 Y2000.00 Z15.00 E600.00    ; set accelerations (mm/s^2)
;M201 X800.00 Y800.00 Z15.00 E400.00     ; set accelerations (mm/s^2)
M906 X650 Y750 Z400 E1200 I30             ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                   ; Set idle timeout

; Axis Limits
M208 X-5 Y-5 Z0 S1     ; set axis minima
M208 X300 Y257 Z295 S0 ; set axis maxima

; Endstops
M574 X2 S1 P"!xstop"                            ; configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"!ystop"                            ; configure active-high endstop for high end on Y via pin ystop
M574 Z2 S1 P"!zstop+!e1stop"                     ; configure active-high endstop for high end on Z via pin zstop

M950 S0 C"exp.heater3"                        ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H10 F600 T3000 A3 R0.5  ; set Z probe type to bltouch and the dive height + speeds
                                              ; Set Z probe type/mode 9(BLTouch).
                                              ; H=Dive Height.
									          ; F=Speed the bed.
									          ; T=Travel speed to and between probe points (mm/min)
                                              ; A=Maximum number of times to probe each point  
                                              ; R=Z probe recovery time before the probing move
M98 P"0:/macros/sys/BLtouchSetDistPos.g"      ; set Z probe trigger value, offset and trigger height
M98 P"0:/macros/sys/BLtouchSetMeshGrid.g"     ; define mesh grid

; Heaters
; heated Bed
M308 S0 P"bedtemp" Y"thermistor" T100000 B4092        ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0                                 ; create bed heater output on bedheat and map it to sensor 0
;M307 H0 B0 S1.00                                      ; disable bang-bang mode for bed heater and set PWM limit
M307 H0 R0.220 C768.703:768.703 D0.55 S1.00 V24.0 B0 ; disable bang-bang mode for 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
; Daragon Hotend
;M308 S1 P"spi.cs1" Y"thermocouple-max31855"   ; configure sensor 1 as thermocouple via CS pin spi.cs1
M308 S1 P"spi.cs1" Y"rtd-max31865"             ; configure sensor 1 as thermocouple via CS pin spi.cs1 
M950 H1 C"e0heat" T1                           ; create nozzle heater output on e0heat and map it to sensor 1
;M307 H1 B0 R2.592 C165.4:125.4 D7.29 S1.00 V24.1 ; Autotune mit 225°C with PT100 and Dragon HT/60W, without Silikonsock
M307 H1 B0 R2.525 C171.0:152.2 D7.05 S1.00 V24.1 ; Autotune mit 225°C mit PT100 und Dragon HT/60W, with Silikonsock
M143 H1 S350                                   ; set temperature limit for heater 1 to 350C
; Chamber Kammerheizung mit PT100 Sensor 2 
M308 S2 P"spi.cs2" Y"rtd-max31865"             ; configure sensor 2 as PT100 Sensor via CS pin spi.cs2 
M950 H2 C"e1heat" T2 Q10                       ; create chamber heater output on e1heat and map it to sensor 2
;M307 H2 B0 S1.00 R0.01 D30                    ; disable bang-bang mode for the chamber heater and set PWM limit
M307 H2 B1 S1.00 ;Bang Bang for Chamberheaters
M141 H2                                        ; map chamber to heater 2
M143 H2 S65                                    ; set temperature limit for heater 2 to 65C
M570 H2 P20	T15								   ; Configure heater fault detection
													;Hnnn Heater number
												    ;Pnnn Time in seconds for which a temperature anomaly must persist on this heater before raising a heater fault (default 5 seconds)
													;Tnnn Permitted temperature excursion from the setpoint for this heater (default 15C)


; Fans
M950 F0 C"fan0" Q500                           ; create fan 0 on pin fan1 and set its frequency
M106 P0 C"F0 Bauteil" B1.0 S0 H-1 L0.08        ; set fan 0 name and value. Thermostatic control is turned off

M950 F1 C"fan1" Q500                           ; create fan 1 on pin fan0 and set its frequency
M106 P1 C"F1 Hotend" S1 H1 T42                 ; set fan 1 name and value. Thermostatic control is turned on

M950 F2 C"fan2" Q500                           ; create fan 2 on pin fan2 and set its frequency
;M106 P2 C"F2 Kammer" S0 B2 L0.3 H-1            ; set fan 2 name and value. Thermostatic control is turned off
;M106 P2 C"F2 Kammer" S1 B2 H2 T45             ; Kammerluefter temperaturgeregelt ueber Sensor 2
;M106 P2 C"F2 Kammer" S1 B1.5 H2 L0.25 X0.5 T60:63
M98 P"0:/macros/sys/Kammerluefter_temp_geregelt.g"
; Tools
M563 P0 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

; Miscellaneous
M575 P1 S1 B57600                              ; enable support for PanelDue
M564 H0                                        ; Allow moves without homeing axis
M501                                           ; load saved parameters from non-volatile memory
T0                                             ; select first tool

Change the 'hallo' ('M110') command, that octoprint sends to Duet2 to 'M555 P2'. Then the connect works.

@jay_s_uk said in M555 P2 is ignored in config.g and Macro:

@turtletrumpet
This is a response from gloomyandy (maintainer of the LPC/STM32 port) when we were talking about Marlin compatibility for the TFT screens

The M555 P2 applies to the "GCodeBuffer" that it is applied to, think of them as "channels" that can be used to read an execute gcode. There are quite a few different gcode buffers in the system (If you run M122 it will list them towards the end of the output). This means that if you set it in say the config.g file (which in the WiFi version of the software is executed by the "File" gcode buffer), then that only applies to other things executed by the "file" channel/buffer, so if you use the "USB" channel to check the state of things you will see a different setting.

Effectively, send M555 P2 from octoprint and that should change the output accordingly

Thank you for the explanation.
If octoprint detects an error when establishing a connection via usb, the duet is stopped by octoprint with M112 (emergency stop).
This error is always received by octoprint because it responds to octoprint in reprap mode.
Therefore, I want to make sure that the duet is in "marlin mode" before establishing a connection.

@phaedrux said in M555 P2 is ignored in config.g and Macro:

Why do you say it's ignored in config.g?

Right after boot up if you send M555 by itself in the console what does it report back?

If I enter M555 P2 in config.g and check this after starting the board with M555, I get "reprap" as a response. The same happens when I enter the command M555 P2 in a macro and execute it.
If I set the command M555 P2 at the console of the web interface and check it with M555, I get the correct answer "marlin".
What am I doing wrong?

@alankilian
I know, I need "M555 P2" to use octoprint.