Duet 2 v1.02 not responding

Phaedrux

Have you disconnected all other cables/hardware from the Duet when you use the USB connection?

thomasvanderwal

@Phaedrux no, do you mean the cables of the steppers et?

Phaedrux

Usually there is no issue with having things still connected, but if you're unable to get the Duet to show up, it may be helpful to disconnect everything else and remove the SD card. Then follow the firmware reset procedure from the start.

dc42

@thomasvanderwal you can leave the stepper motors connected, but if you have a PanelDue connected then put it on the Setup page, then press the Reset button on the Duet.

thomasvanderwal

@dc42 Yes I installed Duet2CombinedFirmware.bin by Bossa. But I think I have to install more files to see gcode etc. How can I manage that printer sees my sd card? I have to have Duet web control? The gcode must be placed in /gcode/ folder on sd.

The commando M997 S0 and S1 is now not working.

droftarts

@thomasvanderwal So you were able to get your PC to see it, and flash the firmware? But now it is not connecting to the network? It's possible it is not seeing the SD card. If you are connected via USB using YAT, can you send commands? Check if it is seeing the SD card by sending M39.

You shouldn't need to update the firmware using M997 S0, but what message do you get when you send that? If possible, send M122 and post the response (copy and paste the text into your reply).

Ian

thomasvanderwal

@droftarts Network is working (I can ping it) . I also can send commands from Duet console and also from pronterface. M39 gives : Error : No SD card mounted in slot 0.
So I mounted the card with M21. : SD card in slot 0: capacity........
I had to put all the .bin files in folder /sys. Otherwise I had an error that they where missing.
Now the firmware is installed. With M122: version 3.0 running.

Next challenges :

In webbrowser (ip address) the web control opens but it can't connect . It gives an error message beneath : incompatible firmware.
On the PanelDue->In screen control the button sd card gives error : error 2 accessing sd card
Homing failed

thomasvanderwal

@thomasvanderwal said in Duet 2 v1.02 not responding:

@droftarts Network is working (I can ping it) . I also can send commands from Duet console and also from pronterface. M39 gives : Error : No SD card mounted in slot 0.
So I mounted the card with M21. : SD card in slot 0: capacity........
I had to put all the .bin files in folder /sys. Otherwise I had an error that they where missing.
Now the firmware is installed. With M122: version 3.0 running.

Next challenges :

On the PanelDue->In screen control the button sd card gives error : error 2 accessing sd card

Homing failed

droftarts

@thomasvanderwal Which set of files did you flash to the Duet? RRF v3.0 is very old. You're probably using a newer version of DWC in the /www folder.

I suggest you

go to the latest release version of RRF here: https://github.com/Duet3D/RepRapFirmware/releases/latest
Download "Duet2and3Firmware-3.5.4.zip" and "DuetWebControl-SD.zip"
Unzip the first file, and copy " Duet2CombinedFirmware.bin ", "Duet2_SDiap32_WiFiEth.bin" and " DuetWiFiServer.bin " to the /sys folder on the SD card, AND the /firmware folder. Overwrite the files already there.
Connect to the Duet with YAT via USB, send M997 to update the firmware

Once it restarts, check if you can connect via DWC. If you can, upload the "Duet2and3Firmware-3.5.4.zip" to the Duet again. It will ask you if you want to do the firmware updates, press cancel.

If you can't connect (still wrong DWC version):

unzip "DuetWebControl-SD.zip"
copy contents to a new /www folder on the SD card
replace SD card in Duet and restart

Then RRF and DWC should be the same version. I don't know what version you were running before, so your config.g may need changing. Sort this out first!

Ian

thomasvanderwal

Web control is working!
Now the last 2 challenges :

On the PanelDue->In screen control the button sd card gives error : error 2 accessing sd card
Homing failed. With motor phase A may be disconnected reported by driver(s) 1

number 2: I may find in this forum?

droftarts

@thomasvanderwal Have you put an SD card in the PanelDue slot? How is the PanelDue connected to the Duet? To be able to use the SD socket on the PanelDue, it needs to be connected with the ribbon cable. See https://docs.duet3d.com/en/User_manual/Connecting_hardware/Display_PanelDue

Also, update the PanelDue firmware to the latest: https://github.com/Duet3D/PanelDueFirmware/releases/latest
For instructions, see https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_PanelDue

For the homing error, you're going to need to tell us more about your machine. Send M122 and post the full response. Post your config.g and homeall.g. Post a picture of your printer, and the wiring. Most likely the wiring is not connected, so check the motor wires for driver 1, which is most likely to be the Y axis.

Ian

thomasvanderwal

@droftarts Sd card reading works!
motor phase problem solved. Wiring was wrong.
But homing is not going well.
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.0 running on Duet Ethernet 1.02 or later
Board ID: 08DDM-9FAM2-LW4SD-6JKDL-3SJ6N-KJZBY
Used output buffers: 3 of 24 (6 max)
=== RTOS ===
Static ram: 30516
Dynamic ram: 91292 of which 0 recycled
Exception stack ram used: 248
Never used ram: 9016
Tasks: NETWORK(ready,1040) HEAT(blocked,1240) MAIN(running,3740) IDLE(ready,156)
Owned mutexes:
=== Platform ===
Last reset 00:03:54 ago, cause: software
Last software reset time unknown, reason: User, spinning module GCodes, available RAM 8748 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 46.8, current 48.0, max 48.5
Supply voltage: min 24.6, current 24.8, max 24.9, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 422922851
Slowest loop: 3.14ms; fastest: 0.09ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 5.60ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state 5, link 100Mbps full duplex

thomasvanderwal

@droftarts ; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.4.1 on Tue Feb 11 2025 11:12:26 GMT+0100 (Midden-Europese standaardtijd)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-235 Y-215 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F6000 ; go back a few mm
G1 H1 X-235 Y-215 F360 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G1 X15 Y15 F6000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning

; Configuration file for Duet WiFi (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.4.1 on Tue Feb 11 2025 11:12:26 GMT+0100 (Midden-Europese standaardtijd)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"My Printer" ; set printer name

; Network
M552 S1 ; enable network
M553 P192.168.0.102
M554 P192.168.0.1
M553 P255.255.255.0
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E420.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 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

thomasvanderwal

@droftarts ; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X230 Y210 Z200 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z

thomasvanderwal

@droftarts Tractus 3d T650P is my printer

A part of the config.g couldn't be copied (2 reputations or something error)

droftarts

@thomasvanderwal Your Tractus is a delta printer, but your config.g is set up for a Cartesian printer? Do you have an old config that worked?

Otherwise, see https://docs.duet3d.com/User_manual/Machine_configuration/Configuration_linear_delta

Ian

thomasvanderwal

@droftarts no, a colleque got this printer from a company. He's gone
I am a educator at a technical school.

droftarts

@thomasvanderwal Okay. I think start again with the configuration tool, but this time select "Linear Delta" for Kinematic type. https://configtool.reprapfirmware.org/Configuration#kinematics

Tractus3D have renamed/been taken over by https://nexum3d.com/. You may be able to contact them and get them to send you a standard configuration for your machine. They are a Dutch company based in Amsterdam, i believe.

Ian

Phaedrux

@thomasvanderwal said in Duet 2 v1.02 not responding:

RepRapFirmware for Duet 2 WiFi/Ethernet version 3.0 running on Duet Ethernet 1.02 or later

Now that you're seeing some progress it may be a good time to update your firmware before you get too far with configuring. 3.0 is quite old now.

If you have access to DWC, you should upload the following zip files one at a time. It will prompt to install the firmware and restart. Then upload the next version, etc.

https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.5.4/Duet2and3Firmware-3.5.4.zip

The reason for uploading 3.0 again is to ensure all of the required files are present.

thomasvanderwal

I'm getting no response from the company. Can a new firmware work with a duet 2 wifi/ethernet?
I made a homedelta.g and a config.g with RepRapfirmware config tool. I selected delta printer and I think made the right choices with the parameters (sensors). But still homing is going bizar. How can I fix this? My rods are 230mm.
At what starting point do I have to position the nozzle? A message G28 0 0 gets a response that axes are not sufficient.
I put this in my config.g: M665 L230 R165 B100 H315 ; set delta radius, diagonal rod length, printable radius and homed height
Maybe this is wrong or my endstops are at another sensor or so?