@Phaedrux thank you for your prompt response.
Latest posts made by akhilnex
-
RE: Steps per mm keep changing
-
RE: Steps per mm keep changing
@Phaedrux Filastruder in USA was the supplier I used for both my old and new board. The purchase was first made on 26th May 2020.
-
RE: Steps per mm keep changing
Gentlemen, Thank you very much for all your help. I knew it was another 250 bucks at risk but I did order a new board and the problem is solved! I can put video file to share the difference. Does any one know if I can send the old board back for the RMA?
-
RE: Steps per mm keep changing
Still unsolved: Error stays (2.5mm increase in distance traveled for every 50mm movement) for all steppers on my board:
- Tried to erase and write firmware and new reprap code files.
- Tried different steppers, extrusion hob drivers( with and without).
- Played with speed, current, microsteps (with and without interpolation)
-
RE: Where to start with a comprehensive extrusion calibration?
@Phaedrux I have a question about non-linear extrusion calibration. My extruder drive moves in a non-linear fashion for every 50 mm distance travelled the amount of extrusion exceeds by 0.25mm. I wonder if this is something that can be solved by pressure advance setting.
-
RE: Steps per mm keep changing
@JoergS5 you are right. I will decouple the motor and test everything separately. I am not sure if slippage is an issue as its running over (+10% approx.) rather then under after calibrating for one distance setting.
-
RE: Steps per mm keep changing
@JoergS5 I haven't even gotten to the multi extruder yet. Just trying to get the extruder steppers to run correctly.
Once I get accurate reading on the filament movement, my next step will be to pass it through the heated multi-extruder. I guess that's the fun of building random design from scratch as every new step brings a brand new set of challenge!
-
RE: Steps per mm keep changing
Can an issue arise from having NEMA 23 and NEMA 17 running on the same board? Should they all be the same 23s or 17s?
-
RE: Steps per mm keep changing
Since X,Y and Z gantries are working fine, I am wondering if the NEMA 17 motors on E0,1,2 that I purchased from stepperonline are faulty. I am thinking about ordering atleast one different brand NEMA 17 and a regular extruder hob gear to check and see if it works any better.
-
RE: Steps per mm keep changing
@JoergS5 M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956L2-G43S8-6J9D0-3S46Q-9U2GD
Used output buffers: 3 of 40 (40 max)
=== RTOS ===
Static ram: 154604
Dynamic ram: 162740 of which 20 recycled
Exception stack ram used: 376
Never used ram: 75476
Tasks: NETWORK(ready,356) ETHERNET(blocked,436) HEAT(blocked,1200) CanReceiv(suspended,3820) CanSender(suspended,1488) CanClock(blocked,1424) TMC(blocked,60) MAIN(running,4512) IDLE(ready,76)
Owned mutexes:
=== Platform ===
Last reset 00:31:39 ago, cause: software
Last software reset at 2020-12-27 10:43, reason: User, spinning module GCodes, available RAM 75476 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN
Error status: 4
MCU temperature: min 40.6, current 41.1, max 41.5
Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
Driver 0: standstill, reads 20644, writes 14 timeouts 0, SG min/max 0/0
Driver 1: standstill, reads 20632, writes 27 timeouts 0, SG min/max 0/81
Driver 2: standstill, reads 20645, writes 14 timeouts 0, SG min/max 0/0
Driver 3: standstill, reads 20646, writes 14 timeouts 0, SG min/max 0/0
Driver 4: standstill, reads 20646, writes 14 timeouts 0, SG min/max 0/0
Driver 5: standstill, reads 20634, writes 27 timeouts 0, SG min/max 0/431
Date/time: 1970-01-01 00:00:00
Slowest loop: 999.77ms; fastest: 0.13ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.8ms, write time 29.6ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 373, MaxWait: 1347113ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 12, completed moves: 12, 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 = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -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 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 57.01ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8- Ethernet -
State: active
Error counts: 0 0 0 0 0
Socket states: 5 2 2 2 2 0 0 0
=== CAN ===
Messages sent 7600, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 0
Last transfer: 1899941ms ago
RX/TX seq numbers: 0/1
SPI underruns 0, overruns 0
Number of disconnects: 0
Buffer RX/TX: 0/0-0
- Ethernet -