Posts made by damaged_goods

@o_lampe Good thought but no the first layer appears clean.

Any ideas as to why I am getting these gaps in my concentric infill?

@dc42 stand alone. My file uploads went from taking several minutes to being instantaneous. Huge difference in speed. It remains to be seen how this will influence prints but I am enthused by this change.

I just replaced the micro SD that came with my board with a A2 rated 32gig and Wow what a difference. So so much faster!!!
Given that my printer is huge 1.5m x1.5m x 2.0m and the Gcode is huge it has to make a big difference.

@deckingman working perfectly. Thank you.

@deckingman said in 2nd extruder stepper to pull filament off 5 kg reel:

@damaged_goods said in 2nd extruder stepper to pull filament off 5 kg reel:

I am guessing that I can fine tune matching speeds by altering the ratio?

You could but it's a bit course. Obviously both extruders need to feed the same amount otherwise they'll be fighting against each other. You need to keep the hot end extruder the same and make any changes to the one that pulls off the reel (let's call it the "feeder"). So it's important that the steps per mm for each extruder is correct but if you need to make fine adjustments, then tweaking the steps per mm of the "feeder" extruder would give finer adjustment than changing the mixing ratio which will only go in 1% increments. You want to avoid the situation where the hot end extruder is pulling against the "feeder" extruder so it is preferable that the one pulling off the reel over extrudes slightly. So you'd want to reduce the steps per mm for that one slightly. i.e if 400 steps gave you one mm, and you "told" the firmware that it was 398 steps per mm, then 400 steps would give you (1/398*400 = 1.005mm. Obviously for a very long print, you might end up with quite a long loop of filament between the feeder and the hot end, in which case increase the steps per mm of the feeder slightly.
Edit. What you don't want is the filament between the two extruders being taught.

That is why I am adding the second feeder extruder.
Thanks again for your help

@deckingman said in 2nd extruder stepper to pull filament off 5 kg reel:

Now that I'm in front of my PC, I can give you a more comprehensive answer in case you haven't already figured it out. So define your tool (s) to use both extruders - e.g. M563 P0 S"Tool 0" D0:1 H1. Note that the extruder drives are referred to in the order that they were created in M584. So in your case, the extruder connected to the main board, drive 4 (0.4) becomes D0 in the M563 command, and the second extruder (0.3) is referred to as D1.
Then after M563, you need M567 to set the mixing ratio. As this is a "push-pull" arrangement we need to set both extruders to use 100%. So the command you need is M567 P0 E1.00:1.00 (where P0 refers to tool 0).

Thank you sir. I was just about to get into it. Your knowledge is greatly appreciated. It always makes me nervous when I start making somewhat blind changes to the config. It's been working so well!
I am guessing that I can fine tune matching speeds by altering the ratio?

@deckingman

'tools" that is what I was missing

I want to add 2nd extruder stepper, on a separate driver, to pull filament off 5 kg reel. Should be simple right?
M584 X0.0 Y0.5 Z0.1:0.2 E0.4:0.3
Driver 3 is the added stepper. which ever motor I list first works the other does not turn.
I initially tried running both motors (slightly different) off the same driver but the speeds differed. I thought using a spare driver would work as well.
Any ideas?

@chrishamm thank you

Hi all. I need to edit a very very large file to recover a failed print but the "edit file" is greyed out in DWC. Can it be done? Any suggestions? Ponterface struggles.

I built a very large printer with a heated bed that warped ridiculously with heat. I eventually broke it trying to level it so I started printing on the cold surface.
Long story short, I discussed the issue with my wife, a quilter. She suggested a basting spray she uses for sticking fabric together.
It worked amazing!!!
Stayed sticky through multiple prints.

@dc42 Thanks David. I can wait

@Phaedrux Thank you

@pro3d my printer is very large. The distance from the mainboard to the accelerometer is approx 5 meters. Will the ribbon wire in your pictures work?
thanks for any assistance,
David

Hi all. Duet 3 board is great, this is a design comment.
I have been messing with a 5ft x 5ft x 7ft build volume printer for 3 years.
It had a 8mm heated aluminum bed (too thin) that operated well but warped badly. I have since disconnected it.
I have had surprising success with using regular contact cement as an adhesive over duct tape on the aluminum bed, at room temperature.
This is just an observation for those hobbyists who can't spend thousands on a large heated bed.
I hope someone finds this useful.

@Phaedrux Thank you for your assistance. I really appreciate it!
I did not include an expansion board M122 because I don't believe I have one.
Thank you again. Hopefully I won't be bothering you any time soon.

@Phaedrux 2/20/2023, 10:41:54 AM M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.5 (2022-11-30 19:35:23) running on Duet 3 MB6HC v1.01 (standalone mode)
Board ID: 08DJM-9P63L-DJ3T0-6JTDJ-3SJ6M-T83BA
Used output buffers: 3 of 40 (25 max)
=== RTOS ===
Static ram: 152760
Dynamic ram: 97040 of which 160 recycled
Never used RAM 100712, free system stack 200 words
Tasks: NETWORK(ready,23.1%,176) ETHERNET(notifyWait,0.3%,443) HEAT(notifyWait,0.0%,322) Move(notifyWait,0.0%,351) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,333) TMC(notifyWait,7.9%,91) MAIN(running,68.4%,1083) IDLE(ready,0.3%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:12:35 ago, cause: power up
Last software reset at 2023-03-02 01:46, reason: AssertionFailed, Platform spinning, available RAM 100424, slot 2
Software reset code 0x4120 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0xf069b60c Task M��� Freestk 4294967295 ok
Stack: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 131
MCU temperature: min 17.4, current 34.2, max 35.6
Supply voltage: min 23.8, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0
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 0, mspos 8, reads 12817, writes 16 timeouts 0
Driver 1: standstill, SG min 0, mspos 8, reads 12819, writes 14 timeouts 0
Driver 2: standstill, SG min 0, mspos 8, reads 12819, writes 14 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 12820, writes 14 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 12820, writes 14 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 12818, writes 16 timeouts 0
Date/time: 2023-02-20 10:41:56
Slowest loop: 1171.63ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 3.5ms, write time 154.2ms, max retries 0
=== Move ===
DMs created 125, 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 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 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
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
=== CAN ===
Messages queued 6798, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 3778/0/0
Tx timeouts 0,0,3777,0,0,3019 last cancelled message type 4514 dest 127
=== Network ===
Slowest loop: 1171.52ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 2 of 8
= Ethernet =
State: active
Error counts: 0 0 0 1 0 0
Socket states: 5 2 2 2 2 2 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0

DWC 3.4.0 is installed at this time
I have no idea what an SBC is

@Phaedrux Yes although it did freeze several times and would not complete. I just prayed, ended the task and tried again. I reinstalled the sys file from backup and all seems back to normal.
Any idea what might have happened? I would like to attempt future firmware upgrades but now I am a little scared.