@RogerPodacter nevermind, i solved the issue by looking at the latest documentation: Gcode Meta
the echo command cannot have a space after the >.
Fixed code:
while true
if state.status == "processing"
if exists(global.runtime)
set global.runtime = {global.runtime + 10}
echo >"runtime.g" "global runtime = " ^ {global.runtime} ^ " ; AUTO GENERATED by daemon.g"
G4 S10 ;wait 10 seconds.
@dc42 Just to close this topic, RatRig seems to confirm they got a bad order of 4028 fans which were really 003's labeled as 001's. So here i am thinking i'm crazy or wiring incorrectly. Anyone who reads this in the future maybe will have an easier time!
@RogerPodacter said in Dual Markforged Kinematics Setup:
M669 K1 X1:0:0:0 Y1
0:1 Z0:0:1:0 U0:0:0:1; Matrix mapping for Axis - X:Y:Z:U
i solved my issue. maybe this helps someone in the future. i simply changed the Y matrix:
old
M669 K1 X1:0:0:0 Y1:-1:0:1 Z0:0:1:0 U0:0:0:1; Matrix mapping for Axis - X:Y:Z:U
new
M669 K1 X1:0:0:0 Y1:-1:0:-1 Z0:0:1:0 U0:0:0:1; Matrix mapping for Axis - X:Y:Z:U
@rogerpodacter here are my new specs. side note i used the format tool but it did not let me chose a cluster size, but it so happened to default using 32kb cluster size so that's good.
after only a few minutes, my DWC web interface is much more responsive. I will test a print nextl.
M122 S104 P10
10/11/2022, 8:02:50 AM SD read speed for 10.0MByte file was 1.69MBytes/sec
10/11/2022, 8:02:45 AM SD write speed for 10.0MByte file was 2.33MBytes/sec
Testing SD card read speed...
10/11/2022, 8:02:39 AM M122 P104 S10
Testing SD card write speed...
M122
10/11/2022, 7:59:57 AM M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.2 (2022-09-13 15:14:33) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: J6RFD-NR6KL-K65J0-409NN-LK02Z-7M5YU
Used output buffers: 1 of 40 (40 max)
=== RTOS ===
Static ram: 103684
Dynamic ram: 111348 of which 12 recycled
Never used RAM 23500, free system stack 136 words
Tasks: NETWORK(notifyWait,14.2%,240) HEAT(notifyWait,0.0%,342) Move(notifyWait,0.0%,276) CanReceiv(notifyWait,0.0%,774) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,339) TMC(notifyWait,1.2%,72) MAIN(running,83.5%,425) IDLE(ready,0.1%,30) AIN(delaying,0.9%,263), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:05:25 ago, cause: power up
Last software reset at 2022-10-09 18:10, reason: User, GCodes spinning, available RAM 23812, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00489000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 325705, completed 325705, timed out 0, errs 0
Step timer max interval 1472
MCU temperature: min 25.0, current 38.8, max 39.2
Supply voltage: min 23.9, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/10/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 15, reads 29543, writes 15, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 15, reads 29543, writes 15, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 15, reads 29543, writes 15, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 15, reads 29542, writes 15, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 15, reads 29543, writes 15, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 29549, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 29549, writes 9, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2022-10-11 07:59:55
Cache data hit count 610770690
Slowest loop: 6.14ms; fastest: 0.13ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.1ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 13, maxWait 32740ms, bed compensation in use: mesh, comp offset -0.016
=== MainDDARing ===
Scheduled moves 12, completed 12, 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 0 is on, I-accum = 0.3
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
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
=== Filament sensors ===
Extruder 0: no data received
=== CAN ===
Messages queued 2949, received 6681, lost 0, boc 0
Longest wait 2ms for reply type 6026, peak Tx sync delay 13, free buffers 18 (min 17), ts 1628/1627/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 12.94ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
= WiFi =
Network state is active
WiFi module is providing access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.27
WiFi MAC address ea:68:e7:e5:63:f4
WiFi Vcc 3.38, reset reason Power up
WiFi flash size 2097152, free heap 25296
WiFi IP address 192.168.1.10
Connected clients 1
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
M39
10/11/2022, 7:59:18 AM M39
SD card in slot 0: capacity 7.95GB, partition size 7.94GB, free space 7.69GB, speed 22.50MBytes/sec, cluster size 32kB
@dc42 Thanks, that makes it clear. I have no need for that particular SD card slot. I just wasnt clear if there was some other advantage, but i obvioulsy use Wifi for all my Gcode file uploads:)
I used the input shaper plugin, recorded motion with no shaper, then recorded motion with each of the other shapers activated, then i can compare. I have obvious spikes on my chart.
Your chart has literally no spikes at all. It would indicated you dont have any frame or belt issues with your printer, but i've never seen this. even the best printers still yield a peak resonance frequency. are you sure your accelerometer is tight, and at the proper location as close to the nozzle as possible?
@phaedrux yes so far today since i've done that it seems perfectly reliable. so it very likely could have been my computer causing this issue.
I guess a side note, only the DWC tab seems to grow in resources, its probably the console log constantly running...
@Phaedrux i did not get a chance to try these steps, but i think i am on the latest firmware.
i thought more about this and remembered in the last few days i added a liquid cooling pump, the standard PC type using 3 wire 12V 0.8 amp. the tach wire goes directly to the Duet board out4.tach, and the 12V and ground goes directly to a dedicated power supply.
once i removed this tach wire, this issue disappeared. this doesnt make sense why this would matter. when the printer did boot up, the pump RPM's gave a normal reading in DWC. so it worked correctly. but i guess something was causing a glitch with this setup.
12V+ - dedicated PSU
Ground - dedicated PSU
Tach - Duet board out4.tach
but i have my config as follows. perhaps i should remove the first portion out4?
M950 F5 C"out4+out4.tach" Q500
@fickert i had similar issues and i solved it nearly completely by increasing motor current. i would run my CoreXY motors at 1.4 amps using TMC2209 drivers, and these motors are rated 2.5 amps/phase. I raise the current to 2.0 amps, and the motors quieted down almost completely.
WARNING i had to add active cooling to my mainboard! My drivers overheated quickly until i added a fan on the mainboard. I use the Duet 3 Mini 5+, and a simply 4010 fan blowing across the driver chips keeps the board at around 39C. I added the fan to temperature control of the MCU temp, so the fan kicks on automatically when the board gets hot.
@jay_s_uk thanks, i think that fixed it. final gcode:
M308 S2 P"temp1" Y"thermistor" A"Chamber 1 Upper" T100000 B4725 ; Define Sensor as Chamber temperature
M950 H2 C"out1" T0 Q10 ; Define dummy Heater2 and spare pin as the heated bed, bind to Sensor0
M307 H2 B0 S1.00 ; disable bang-bang mode for the chamber heater and set PWM limit
M141 H2 ; map chamber to heater 2
M143 H2 S120 ; set temperature limit for heater 2 to 60C
M308 S3 P"temp2" Y"thermistor" A"Chamber 2 Lower" T100000 B4725 ; Define Sensor as Chamber temperature
@RogerPodacter Apologies, please close this thread as resolved. the entire time the CAN connection was lose. the factory one ironically. once i recrimped it, everything works normally. it was just coincidental timing, the carriage motion must have loosened it up.
i had similar bed issues. very likely, your physical wiring or tubing connected to the print head bumps up against the corner wall or frame of your printer in this corner, and it slightly pushes the probe and print head downward, appearing like the bed is raised. Since it only happens in that corner, very extreme, it very likely is physical force on your toolhead.
looks excellent, a voron will be my next printer.
i have this electronics setup on my printer (not a voron unfortunately) and i absolutely love the Duet system. I have the Duet 3 Mini 5+, toolboard 1LC, PanelDue screen, magnetic filament sensor. i want to keep expanding.
@Marius-Breuer i run a 12 volt Noctua fan connected directly to the 4 pin with no issues on a 3HC and a Duet 3 Mini 5+.
I dont recall that i had to change any wiring to make things work.
My fan is the Noctua NF-F12 industrialPPC-2000 PWM.
@Proschi78 thank you so much. removing that H2 seems to have fixed almost all of my issues. damn. let me try running some tests and see how this is working.
@Diamondback i have had multiple instances where i made a change to something, lets say in config.g, and it doesnt take effect until 2 times later. meaning the board reboots after a change, but it doesnt implement the change. and i troubleshoot and think i'm crazy, then a 2nd reboot and the change sticks.
Perhaps the same effect happens with mesh level.
I dont have an example i have in mind, and i could be at fault here and its user error by me. of course this doesnt seem to happen anymore as i get more familiar with Duet...soo i dunno!
@PCNoobNeedsMajorHelp yes you're idea is pretty much correct. you did not need another 24V 350 watt bed. a much better option would be to switch to a 110VAC mains powered bed which pulls directly from the mains power. and use a SSR (solid state relay) to break the hot line of the AC power going into the bed. control the SSR from the Duet mainboard.
solved my issue, it was simply my Tool 4 had D2:3 set when it should have been D1:2. i dont yet have motor 3 connected yet. silly mistake.
however, running an orbiter off the 3HC the motor runs very rough and i can feel slight vibration when i touch it running. the 1LC Orbiter is smooth as butter. yet both use 1A current, identical settings, identical wiring. is this normal behavior?
i experimented a bit removing that command but didnt have much luck resolving the issue. i think i finally have it working, using your advice i removed the G28 and replaced with a G30 at the end of bed.g and that seemed to give the behavior expected. it completes the cycle fully.
M290 R0 S0 ; clear baby stepping
M561 ; reset all bed adjustments
M400 ; flush move queue
; echo "Running bed4point.g"
;M558 F60 A6 ;A3 ; fix probe speed to 1mm/s
;G90
;G4 P250
if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
echo "not all axes homed, homing axes first"
G28
M401 ; deploy Z probe (omit if using bltouch)
G30 P0 X30 Y20 Z-99999 ;X30 Y20 Z-99999 ; probe near a leadscrew
G30 P1 X155 Y276 Z-99999 ;Y282 Z-99999 ; probe near a leadscrew
G30 P2 X279 Y20 Z-99999 S3 ; probe near a leadscrew and calibrate 3 motors
echo "Current rough pass deviation: " ^ move.calibration.initial.deviation
while move.calibration.initial.deviation > 0.005
if iterations >= 5
echo "Error: Max attemps failed. Deviation: " ^ move.calibration.initial.deviation
break
echo "Deviation over threshold. Executing pass" , iterations+1, "deviation", move.calibration.initial.deviation
G30 P0 X30 Y20 Z-99999 ; probe near a leadscrew
G30 P1 X155 Y276 Z-99999 ; probe near a leadscrew
G30 P2 X279 Y20 Z-99999 S3 ; probe near a leadscrew and calibrate 3 motors
echo "Current deviation: " ^ move.calibration.initial.deviation
continue
echo "Final deviation: " ^ move.calibration.initial.deviation
G0 X155 Y155 Z10 F9000
G30
;G28 Z
M402 ; retract probe (omit if using bltouch)
i just came across this thread. i just upgraded my CoreXY printer into an IDEX dual markforged kinematics printer, and i now experience this same jitter behavior.
after reading this thread, this behavior must be inherent to this type of kinematics. with CoreXY, the single head is equally tensioned from both sides with 4 belt connections. with dual heads, only 2 belt connections are present on each head. additionally, when the Y gantry moves, the stationary head still has its motor turn in the opposite direction to counter the drag movement.
for whatever reason, the stationary head is slightly out of sync. or possibly because the belts have the long/short end as mentioned earlier, there is slight jitter movement of the stationary head.
i tightened my belts and this greatly reduced the behavior. but its still present on violent acceleration moves. its noticeable because the stationary head is parked on the end stop, and the endstop clicks everytime the head jitters.