New Duet 2 extruder not working
-
@GG
did you make the changes pheadrux told you to do? -
Of course we will still try to help you. We just can't provide any hardware warranty, but I don't think you have a hardware problem.
-
@Phaedrux Thanks for that much appreciated. Yes Iv e now changed the M203 z to 600 and that made it work well. I can now home all 3 axis on dwc, consistently, but seems like panel due is reading a different config. Also setting z 0 offset tutorial says save z0 in config g In G31 command, I dont have a G31, do I just create one. My dwc version doesnt have system editor either ?? cause it says to use this to save Z0 reading, is mine later or earlier version ?
-
@GG said in New Duet 2 extruder not working:
Also setting z 0 offset tutorial says save z0 in config g In G31 command, I dont have a G31,
i would advise you to make any big changes in the online configurator and upload all files again after the changes. introducing a probe makes a lot of changes in the config, especially the homing.
my dwc version doesnt have system editor either ?? cause it says to use this to save Z0 reading, is mine later or earlier version ?
which version of dwc are you running? as far as i know all versions have an editor.
-
I think some screen shots or videos are in order so we can see what's happening.
-
From previous experience, the clone boards come with something like version 2.02 of RRF and can be near impossible to upgrade without using BOSSA. They also tend to come with DWC 1.
I would suggest using BOSSA to bring the firmware up to at least 2.05.1. After that, upgrading through system works fine. -
Ah yes we never did get the output of M122.
Regardless of what 2.x version, updating should be as easy as uploading the full zip file for 2.05.1 as is (don't extract first) to the sys folder in DWC.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
-
@Phaedrux it should be but I've had 2 cloned boards and neither would upgrade that way
-
Thats interesting; unless the sd card contents of 2.02 is missing the iap file for 2.02 its very strange the update wouldn't work, unless the microcontroller is a dodgy clone as seen on some arduinos with "atmega328" - but thats perfectly possible i guess.
-
either that or they've locked the firmware in a way that can only be overwritten by BOSSA.
And no manner of combined firmware files or anything would work. Nothing in console to say why. The firmware updates just weren't applied.
All very odd. -
@jay_s_uk said in New Duet 2 extruder not working:
locked the firmware
thats possible, could be interesting to see the output from the info button before writing a new firmware with bossa.
-
@Phaedrux This is the response to M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet Ethernet 1.02 or later
Board ID: 0JD0M-9K662-MGPSS-6J9DG-3S86M-KBVYZ
Used output buffers: 1 of 24 (14 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 92884 of which 296 recycled
Exception stack ram used: 320
Never used ram: 11860
Tasks: NETWORK(ready,764) HEAT(blocked,1232) MAIN(running,3800) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:01:10 ago, cause: power up
Last software reset at 2020-10-12 17:34, reason: User, spinning module GCodes, available RAM 11700 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 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 24.2, current 25.1, max 25.2
Supply voltage: min 12.0, current 12.0, max 12.1, 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: 2020-10-13 10:32:25
Cache data hit count 138625344
Slowest loop: 1.31ms; fastest: 0.08ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== 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: 3.89ms; fastest: 0.06ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state 5, link 100Mbps full duplex
=== Filament sensors ===
Extruder 0 sensor: ok
10/13/2020, 10: -
@Phaedrux said in New Duet 2 extruder not working:
Ah yes we never did get the output of M122.
Regardless of what 2.x version, updating should be as easy as uploading the full zip file for 2.05.1 as is (don't extract first) to the sys folder in DWC.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
@GG said in New Duet 2 extruder not working:
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet Ethernet 1.02 or later
So it looks like you have 2.05 installed, which is fine. Upload that zip file I linked above and see if it will install 2.05.1 and DWC 2.0.7 correctly.
-
@Phaedrux Tried to upload that zip file through the "upload system files " tab in dwc it shows them uploading but then the upload button circular indicator just keeps circling and no changes made even after reboot. I just need to know how to put my z offset "7.45mm" into the config. Definitely something strange with paneldue, when I try to home x it moves diagonally to the x endstop then when I home y it completes the z homing to bed centre. attached screen shot of dwc.as you can see all three axis homed from Paneldue but in a totally different way to DWC homing ?? also screen shot of system dwc showing no" system editor"
-
You have a sys folder inside of your sys folder. That's probably the cause of the problem.
When youve selected the system tab on the left the folder you see is the /sys folder on the SD card so if you've been putting files into another sys folder they aren't being accessed there.
-
@Phaedrux Yes you are right and looking at the date it is one I somehow created, however when I right click on the folder and try to delete it comes back with, " Failed to delete system, please make sure this .directory is empty,, also
Error:Failed to delete file0: /sys/sys -
@GG you can't delete folders that have something in through DWC.
Go into the folder and delete all the files first. then you can delete the folder -
If the files you've been editing are in that second /sys folder, you should move those files into the root /sys folder rather than deleting the files.
Another way would be to pop your SD card into a PC and edit the folder structure that way.
It should look like this: https://duet3d.dozuki.com/Wiki/SD_Card#Section_Creating_the_file_structure
-
@Phaedrux Thanks folks, I got rid of that sys folder within system folder but the paneldue still behaves strangely, If I try to home x with paneldue, it homes slowly diagonally to the x home position then tells me error G0/G1: insufficient axis homed, then if I press print to clear the error page, and press home y, it homes all very slowly. Back to previous question, how to put my Z offset into config g I guess the slicer will need this, do I just enter g31 and the offset . Chers
-
Ok now that you've got that sorted, please post your homex, homey, homez, and homeall files from the system folder that remains. Also your config.g from there as well.
The z offset for the probe is set in G31 in config.g
