Topics created by Omiclette

@phaedrux I don't see any hiccups, see below the M122 response after sending M302 P1 and G1 E15 F15 (step/mm = 85. I think you've found why I run into the problem with step/mm = 85924, I'll stick to 5370 and divide the feed by 16 to get my RPMs.

02/02/2022, 08:55:09 M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.4.0beta7 (2021-12-16 12:22:39) running on Duet 3 MB6HC v1.01 or later (standalone mode) Board ID: 08DJM-956BA-NA3TN-6J9FA-3SD6J-9ABAT Used output buffers: 1 of 40 (17 max) === RTOS === Static ram: 150664 Dynamic ram: 93776 of which 0 recycled Never used RAM 106160, free system stack 174 words Tasks: NETWORK(ready,23.2%,253) ETHERNET(notifyWait,0.2%,174) HEAT(notifyWait,0.1%,324) Move(notifyWait,0.0%,276) CanReceiv(notifyWait,0.0%,797) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,6.0%,58) MAIN(running,61.4%,1142) IDLE(ready,9.3%,30), total 100.0% Owned mutexes: === Platform === Last reset 00:02:08 ago, cause: software Last software reset at 2022-02-02 08:52, reason: User, GCodes spinning, available RAM 106276, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Step timer max interval 1012 MCU temperature: min 46.0, current 46.1, max 50.4 Supply voltage: min 0.1, current 23.4, max 23.6, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 0.1, current 11.9, 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: pos 103350, standstill, SG min 0, mspos 8, reads 4712, writes 11 timeouts 0 Driver 1: pos 103350, standstill, SG min 0, mspos 8, reads 4712, writes 11 timeouts 0 Driver 2: pos 103350, standstill, SG min 0, mspos 8, reads 4713, writes 11 timeouts 0 Driver 3: pos 0, standstill, SG min 0, mspos 584, reads 4708, writes 16 timeouts 0 Driver 4: pos 0, standstill, SG min 0, mspos 8, reads 4713, writes 11 timeouts 0 Driver 5: pos 0, standstill, SG min 0, mspos 8, reads 4713, writes 11 timeouts 0 Date/time: 2022-02-02 08:55:08 Slowest loop: 3.89ms; fastest: 0.05ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 2.4ms, write time 0.0ms, max retries 0 === Move === DMs created 125, segments created 3, maxWait 49338ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 1, completed 1, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], 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 3 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters 0 -1 -1 -1, ordering errs 0 Heater 1 is on, I-accum = 0.0 Heater 2 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 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 1122, received 757, lost 0, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 3770, free buffers 49 (min 48), ts 644/473/0 Tx timeouts 0,0,170,9,0,87 last cancelled message type 30 dest 127 === Network === Slowest loop: 5.49ms; fastest: 0.02ms 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 1 0 0 Socket states: 5 5 2 2 2 0 0 0 02/02/2022, 08:53:49 G1 E15 F15 02/02/2022, 08:53:22 M302 p1

Still on the list.

@t3p3tony Hello, I just did the firmware update to 3.4b7. Changing the S parameter from S0 to S1 now changes the rotation direction of the motor controlled by the 1XD board. Thank you for your help, the issue is solved.

@zapta Thanks for your input, I didn't think of taking an output signal from the Duet that would be generated by some gcode, that seems like a good idea especially as I could possibly borrow a NI acquisition board for the duration of my project. I will compare both solutions.

@o_lampe Thanks for your input, I will look into that!

Thank you Phaedrux for your response. This is my master's degree project I am doing at school. In my labotary, students have studied the MIM process with very low viscosity feedstock since the past 8-10 years. I am the first student to try and print their custom feedstocks. I designed and fabricated this inverted delta printer to validate that it is possible to print such feedstocks. I think the school will buy the Desktop Metal Studio during summer, but I won't be able to use it before the end of my program.
20034057-2353-4fce-9f4f-c7b01a5450a4-image.png
The piston type extruder has not been used a lot for 3D printing metal paste, because you need to remove air almost completely from the feedstock prior to printing due to the compressibility of air. Once this is done, controlling the flow rate is much easier with a piston type extruder because the is no slippage possible as with filaments and screw extruder. Filaments are not the best solution because it limit the solid loading (the amount of metal powder compared to the binder). Desktop proposes a 6 mm rod, which is better than filaments, but from what I read, there is still some slippage (some articles say that they increased the flow multiplier up to 127% to reduce the interlayer voids, which means that there is slippage). If I increase my extruder flow rate to 127%, the part will be overfilled by a lot.

I am not saying that the piston type extruder is without problems. I had great success with bigger nozzles (0.8 mm), but I am still working on making better prints with the 0.4 mm nozzle. If you guys are interested, I might be able to show what I am able to acheive with this setup, I just need to confirm with my supervisor that it is okay to do so.