@jay_s_uk Awesome! Thank you

I dont have the paneldue here but it works now, I took my laptop from home and made it normally via YAT.

Thank you guys for the fast answers!

Regards

@droftarts the H7 should be disabled. The M307 H7 command gives the answer: "Heater 7 is disabled"
Also I have no M501 command in my config.g so there should be no override of the parameters.
In the config.g file I disabled the heater channel after the endstops are defined and before the M558 defines the bltouch as z probe I think this should be fine.

The z probe value is zero when there is a connection and 1000 if there is no connection.

Thank you for your help!

Edit: I just checked all the connections again and the yellow signal cable was not connected properly.
Really sorry for this but again thank you for your fast help!

Okay sorry guys I just found the problem even though I dont know how this could be.

It seems like the grounding point was not strong enough. I measured the VIN and it was only around 2-3V. So I used another ground point and not it works.
The old ground point was directly connected to the ground of the plug that goes into the printer. Now I connected it to the ground coming out of the power supply.

I did not knew that there could be any difference?
I mean the ground point from the plug also goes into the power supply.

But now it works, thank you anyways @jay_s_uk !

@oliof yes the machine has the M2504 stepper motors. I have 1000mA for the z motors and since I changed the driver everything works well

Okay sorry guys I just found the problem even though I dont know how this could be.

It seems like the grounding point was not strong enough. I measured the VIN and it was only around 2-3V. So I used another ground point and not it works.
The old ground point was directly connected to the ground of the plug that goes into the printer. Now I connected it to the ground coming out of the power supply.

I did not knew that there could be any difference?
I mean the ground point from the plug also goes into the power supply.

But now it works, thank you anyways @jay_s_uk !

@jay_s_uk thanks! Already tried to do the factory reset but nothing changes.

I pressed the two buttons and started the board. But its like the other times because just the blue led is on.

Hello guys!

I just installed a 1LC V1.3 toolboard to my Duet 3 Mini 5+ without a tool distribution board.
I am powering it a VIN (24V) and the CAN is connected as its shown in the documentary and I soldered the 120R resistor (I bridged it on the backside of the board with solder).
I placed the G4 S2 command in the config.g file.
When I send M115 B121 (I also tried M115 B10) there is no reaction.
Also only the blue LED is on.

I really dont know what could be wrong or why it is not working.

Can anyone help me or give me some tips I can try?

Thanks and best regards!

@jay_s_uk Awesome! Thank you

@phaedrux Thank you so much! It worked Really helped me.

I did all the steps and also updated via DWC again to 3.4.0.
I have to check the config files and stuff but everything is back working again!

There is just something strange:
The PanelDue is working but it shows only "Connecting" on the top right side. No printer name. Also it shows 0°C for nozzle and heated bed (DWC is showing the right temperatures). When I click on "console" there is nothing. Not even a "connecting..."

Is there something I have to upgrade to get the PanelDue working again?

Thanks again!

@phaedrux Thank you! I will try this when Im back at the printer (I think on monday).

Hello all,

I have a very strange problem with one of my printers.
The printer is running a Duet 2 Wifi and a DueX5 expansion board.

The printer was running normally on a RRF 2.05.1.
I then wanted to update yesterday and first updated to RRF 3.0. This worked without problems. Then I updated to 3.1.1, which also worked (of course most things did not work, because the config-file was not yet adapted to RRF3). Then I updated to 3.4.0 and immediately had no more control over the DuetWeb interface (I did all updates via the DuetWeb interface).
I left the printer behind for the time being (it's in a place where I don't go very often) and changed the config file to RRF3 at home.

Today I was back at the printer and wanted to put RRF3.1.1 back on it (last version that worked) and then see what happens.

But that didn't work, the printer started and showed something on the PanelDue, but it seemed like it had no connection to the SD card, because the temperatures were all at 0°C (thermistor and bed) and there was nothing in the console, not even a "Connected". It also did not connect to the WLAN. When I clicked on the SD card icon on the PanelDue, it said that there were 0 files, although there were also g-codes on the SD card.

I then tried several things, nothing worked, I had no access.
So I connected the board directly to the PC and checked the firmware. It was 3.4.0 installed.

I then tried to activate the WLAN directly with the M552 commands. Here the beginning worked, but when I wanted to enter the WLAN data with M587 I got the message "Error: M587: Failed to add SSID to remembered List".
I then entered M587 to simply get the list. I got "Error: M587: Failed to retrieve network List".
It looks to me like the printer can't communicate with the SD card (I formatted it in the meantime).
I also tried to update the Wifi software on my own. It always came the message that the file was not found (DuetWiFiServer.bin), although this was exactly with this name in the firmware folder. Of course I tried the sys folder too. Again it seemed that the SD card could not be accessed at all.

Then I thought okay enough, now I reset to factory settings via the jumper and flash a new firmware on it.
So I used the jumper, the board came into the right mode (both lamps on) and I flashed the firmware again with BOSSA (3.1.1). That worked. YAT confirmed the firmware version again (3.1.1). I tried again the WLAN settings, same problem as above. I then tried to put the WLAN data directly into the config-file, no success.
It looks to me like the board can't access the SD card, but it's the exact same one that was always used.

What could be the problem here, is it possibly something other than the SD card?

I will send you the answer of M122 for all the information (there it seems like the sd-card is fine or am I wrong?)

Sorry for the very long text - I hope someone can help me out.

Thank you guys!

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later + DueX5
Board ID: 0JD0M-9P6M2-NW4SD-6JTDJ-3S46Q-9TNRM
Used output buffers: 1 of 24 (2 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 93408 of which 20 recycled
Exception stack ram used: 256
Never used ram: 9408
Tasks: NETWORK(ready,1884) HEAT(blocked,1456) DUEX(suspended,160) MAIN(running,1720) IDLE(ready,80)
Owned mutexes:
=== Platform ===
Last reset 00:06:55 ago, cause: power up
Last software reset time unknown, reason: User, spinning module GCodes, available RAM 11312 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 29.7, current 33.0, max 33.4
Supply voltage: min 0.4, current 0.5, max 1.1, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Driver 5: ok, SG min/max not available
Driver 6: ok, SG min/max not available
Driver 7: ok, SG min/max not available
Driver 8: ok, SG min/max not available
Driver 9: ok, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 774595777
Slowest loop: 101.18ms; fastest: 0.09ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.1ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = -1 -1 -1 -1, chamberHeaters = 2 -1 -1 -1
=== GCodes ===
Segments left: 0
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
USB is ready with "M122" 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.23ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8
- WiFi -
Network state is starting2
WiFi module is disabled
Failed messages: pending 0, notready 38, noresp 0
Socket states: 0 0 0 0 0 0 0 0
=== DueX ===
Read count 1, 0.14 reads/min
ok

@oliof yes the machine has the M2504 stepper motors. I have 1000mA for the z motors and since I changed the driver everything works well

Hello!

Is it somehow possible to report the actual thermistor resistance that is measured right now?

I know M308 can report stuff from the thermistor but is it possible to get the actual resistance somehow?

Thank you!

@phaedrux I have one driver free and used it for the rear z motor.
Since then everything is working fine.
I will come back to this thread if the motor stops again but for now I think it is fine

Thank you!