Posts made by Napalm1432

bump? still having this issue

Hey all,

I've just returned to my printer having finally got the right PSU.
I have the duet 085 with ethernet, and i had already done all my configurations, but now when i turn on the printer (hooked up to ethernet) the web interface is not loading at all, i simply get a 404 error.

I checked if it was recognized in the network via the router and it shows up there with the ip.
When i try connecting to the ip nothing loads. I have tried a different duet and the same issue occurs, also tried multiple sd cards.

I tried hooking up usb but it won't show up in devices at all so connecting trough usb was not possible for me either.

Does anyone know how to resolve this issue?
Let me know if you require more info.

Okay i have updated the firmware (just wondering is there another/newer version of dwc? running 1.22.6)
So far it seems like it keeps reading correctly, is there a way to keep checking if the sd card can be read every x seconds, without having to be constantly checking manually

For some reason it took a while for it to happen again, but here is the log from M122
This is with a different SD card (a new one from SanDisk) and the same happens.

=== Diagnostics ===
Used output buffers: 2 of 32 (21 max)
=== Platform ===
RepRapFirmware for Duet version 1.21 running on Duet 0.85
Static ram used: 44844
Dynamic ram used: 40964
Recycled dynamic ram: 208
Stack ram used: 1192 current, 5380 maximum
Never used ram: 6908
Last reset 00:02:13 ago, cause: power up
Last software reset at 2020-07-28 13:35, reason: User, spinning module GCodes, available RAM 6956 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00438000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 21.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 40.9, current 42.6, max 42.7
Date/time: 2020-07-28 15:54:00
Slowest main loop (seconds): 0.050156; fastest: 0.000104
=== Move ===
MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 100, MinFreeDm 100, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 10, completed moves: 10
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0, 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 ===
Free connections: 15 of 16
Free transactions: 23 of 24
Locked: 1, state: 4, listening: 0x20071bf8, 0x0, 0x0

Hi there,

I'm building a 3d printer using the duet 085 which i had still laying around, and am using the dwc too, i noticed though that it often happens that i get the error "can't read homex.g" for example, i then have to reset the machine for it to work correctly again.
Is this a hardware problem, or sd card problem or something else?

Also when using dwc it often has issues showing current states (for example having to refresh the page to see current temperatures) is there any cause/solution for this?

Yup my bad, it works now! (haven't tested with the newest version of Cura yet though)

okay, i changed the config to reflect this change, but still having the same issue, right now it also happened with the older cura's gcode.
It seems to not even be powered, might it help to include the extruder mapping in each M584?

EDIT: Never mind this comment, forgot to change my homing code, i'll be back after this!

I did some more testing, and a had a gcode made in the newer version of cura, because of the M106 command missing the P parameter, but it only fails on that motor with a file from this version of cura, before i used Cura 15.04.6 and in that version it doesn't have the problem with the motor

i do reassign the extruder in config.g at the end of the file

I'm currently only reassigning the axes in the homez.g file, and when I home manually everything is fine, only when i print a gcode it fails when homing.
Do i need to reassign the extruder everytime?

Soo it was solved, and it sort of still is BUT:
When i jog the Z motors they all work fine.
But when i start a print, somehow one of the motors loses strength again, but when i takeover manually it works again......
Getting quite sick of getting these lil bugs fixed
edit: i'm testing my last open drive right now, but it's sad that i would keep losing drive after drive
Edit2: issue remains after switching drives....

Hi, i'm almost finished with my printer, the last thing that's not working are the pwm fans, somehow my FAN0 connection is faulty, so i want to use FAN1 output, I used the M563 command to set the tool to use this fan output.
But when i send a M106 S255 it will not turn on, only when i use M106 P1 S255 it will work, but gcodes don't include the P parameter...
How would i fix this?
(Using duet 0.8.5, expansion 0.2, Firmware V1.2)

Okay so i checked, and yes, i did use a 24v one, i have multiple parts lying around, and assumed it was 12v, luckily i did have a 12V one, so i did the tuning with that, tested it out and it worked!!
However, i had to extend the wires of the heatercable, and i did this after tuning and testing, and now i get an error again that the temperature rises to slowly (not the expected 0.7c/sec (i already changed the dead time value, first it was 1.6c/sec)).
Do i have to retune the heater after extending the cable?

okay, i updated the firmware to V1.2, and am tuning the heater again, but everytime i get an error, Auto tune cancelled because target temperature was not reached, But it stops heating at about 160C while it's still rising

EDIT: I also just realised, i use a 12V power supply, and the heater cartridge SHOULD be 12v as well, but what happens if the heater cartridge is rated at 24v?

I notice on the wiki on how to install new firmware the instructions all say Duet 2 Wifi, but, i did see i need other files for the duet0.8.5, which i downlaoded, do i just follow the instructions for duet2wifi, using the firmware for 0.8.5duet ?

That's gonna be a night of reading but will do

After updating firmware, can i just put in my config.g and everything should work the same? or are there other changes i need to keep in account?

i'm not sure about the version nr, but it's the latest version before the update where you get a config_override.g when using the M500 command, Yes it does try to heat it up
Edit: It would be V1.16

I just finished building my printer, and used the autotuning feature to tune my hotend and heated bed, when testing from pronterface heating both elements work fine, but once i try to print something i get the following error:
[ERROR] Error: heating fault on heater 1, temperature rising much more slowly than the expected 0.0°C/sec

This seems like an odd issue, and i can't find where it's coming from.
I'm using the duet(eth)0.8.5 with the expansion 0.2

I got the following values from autotuning, which i put in config.g:
M307 H0 A79.9 C578.8 D8.5 B0
M307 H1 A181.3 C144.7 D8.6 B0

if more info is needed please ask me

EDIT: Some more info as to what exactly happens, from pronterface when setting hotend temp, it heats up fine, reaches target. When i print a gcode, it will heat up the nozzle to target temperature, but when it's close to the target, it returns the error noted earlier.

i'm using all on the expansion board, but i have 2nd extruder free, and regular Z connection free.
EDIT: Issue solved, just changed drives!