Hi there!!! the setup is complete!! hopefully everything goes fine with this configuration, i just moved the 4th axis putting the conector in the extruder´s driver and works fine so far. i put the pictures here to see the mechanical configuration, and if you have any questions for the development of the firmware just let me know.!
Best posts made by ander
-
RE: Flying extruder with 4th axis
-
RE: Auto delta calibration issue
Hi, i just checked it and it was this, thanks for the help,you guys are giving a really nice support
-
RE: Flying extruder with 4th axis
Hi there!!!
a bit late but here goes my setup:
https://www.youtube.com/watch?v=ToBLN7YHWt4
Latest posts made by ander
-
RE: accelerometer not found DUET WIFI V1.2
@droftarts
Thanks for the help, it worked beautifly!! -
RE: Bed heating problem
@Phaedrux
After i made all the changes to the bed, and making calibration several times, i´m still in the same spot.
If i try to heat it up, the error pops out.
And yes, i put m500 after doing the calibration process -
RE: Bed heating problem
@dc42
Hi there!
I´m back with my Delta printer. i changed the bed and isolated a bit better, the sensor now is in between the heater and the bed, then i put an isolating foil, and underneath there is a really strong composite material.
I made some tunning procceses back and i couldn´t fix it.
The weird thing is that everything started when i updated the firmware. the one before was 2-3 years old and it wasn´t having any issues with the same bed system.
i also tried to change the sensor but the result was exactly the same
config(6).g
config-override(2).g
i´ll add some pics to see how is built.
-
RE: accelerometer not found DUET WIFI V1.2
I forgot to mention, the screen is telling : "accelerometer not found in specified port" when starting
-
accelerometer not found DUET WIFI V1.2
Hi there!
I have installed an accelerometer LIS3DSH on my duet wifi V1.2.
I was using an ethernet wiring to do the conection but the console was telling me that the accelerometer wasn´t found. I read in this forum that the wiring could be important so i changed the wire with a usb 3.0 cable.
The problem persists.
Sending the M955 P0 : Error: M955: Accelerometer not found
Here is my config.g:
config(5).g
Also, this is my wiring:
Can someone give me a hand please?
This is my M122:
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.6 (2023-07-21 14:08:28) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917Q9-GLMS8-6JTD2-3SD6P-9YD0B
Used output buffers: 1 of 26 (22 max)
=== RTOS ===
Static ram: 23896
Dynamic ram: 75136 of which 44 recycled
Never used RAM 13004, free system stack 184 words
Tasks: NETWORK(ready,11.4%,242) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) MAIN(running,83.4%,436) IDLE(ready,5.1%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:17 ago, cause: software
Last software reset at 2024-01-17 16:42, reason: User, GCodes spinning, available RAM 12800, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 36.2, current 36.8, max 37.2
Supply voltage: min 23.4, current 23.4, max 23.5, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2024-01-17 16:42:38
Cache data hit count 663459077
Slowest loop: 12.20ms; fastest: 0.18ms
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 0.7ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== 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 idle 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
LCD 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: 25.59ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8 -
RE: Bed heating problem
@dc42
Hi there, i´ll try to do those changes and try, and maybe try with another sensor too.
that will be next year maybe. i´ll keep you informed with the results.
thanks -
RE: Bed heating problem
@droftarts
I put the M307 in both( config.g and override)
as wasn´t working fine i made the tunning back again, and send M500 again:
Auto tuning heater 0 completed after 3 idle and 5 tuning cycles in 1133 seconds. This heater needs the following M307 command:
M307 H0 R0.950 K1.299:0.000 D1.36 E1.35 S1.00 B0
Send M500 to save this command in config-override.g
and still doesn´t work
The error i saw was the same as always:
Heater 0 fault: temperature rising too slowly: expected 0.47°C/sec measured 0.10°C/sec
by the way, when switching of and on again the console in the screen says Error: bad model parameters.
Doesn´t say anything in the DWC console but it does in the machine screen (i dunno if could be related)
This is the tunning picture, this time i made it until 80 degrees
-
RE: Bed heating problem
@droftarts
Thanks for the help
The tunning has been from cold, you can see that the blue line matches the red line in the beggining .
I tried the m307 you suggested and it did not work either.
the heating element is this style 400mm in diameter and works at 24v.
this heating element is attached to an aluminum plate 450mm in diameter and 4mm thickness.
Under the heating element is a material that covers all made out of trespa.
The output of the duet is attached to an SSR and then goes to the bed.
on top of the aluminum is a magnetic bed but the sensor goes all in one with the heating element as shown in the picture.
The weird thing is this problem started when updating to the latest firmware. before this was working fine.
I dissasembled the bed to check some things but everything is as it was before. -
RE: Bed heating problem
The error takes place a few seconds after activating the bed, either from cold start or a bit warm.
the tuning cicle it has been in cold always.
I just sent the m98 command and this is what it says:M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Endstop configuration:
X: high end switch connected to pin xstop
Y: high end switch connected to pin ystop
Z: high end switch connected to pin zstop
U: high end switch connected to pin e0stopWarning: Heater 0 predicted maximum temperature at full power is 240°C
Warning: Heater 1 predicted maximum temperature at full power is 656°C
Warning: Heater 1 predicted maximum temperature at full power is 660°CBy the way U axys is the 4th axys of my delta printer