I'm happy to report that Dave's IR sensor works great with TinyMachine's PEI plate and WhamBam's PEX plate. It is ok on textured PEI, but I believe the uneven-ness of the texture throws off the height map slightly.
Best posts made by br7408
-
RE: David's IR Sensor: Questions
-
RE: New to Input Shaping
@dc42
I cannot thank you enough. Your selflessness, knowledge, and advice you've given over the last few years has helped me immensely and taught me so much. There is always a lazy answer, but you always take the time to explain. I hope Duet is paying you extremely well. I'll run into a snag or two, and I archive the forum, and its usually your advice that always leads me to a solution. Very rarely have I seen such efficient/ problem solving subject matter experts, and very few like you left anymore. Thanks. -
3.5 + feedback
Duet Mini 5 wifi and 1LC toolhead on a 500x500 corexy.
I I've been running it for 2 days. No issues have appeared as of yet. Print quality is much better; PA & IS appear to be working quite well.
I am trying to compensate a Y axis issue that is beyond simple frame resonance, because it is purely a fault of my own, due to my gantry movement design. I was actually able to apply the input shaping specifically to the Y axis and tune a fair amount out; enough that I am seeing results. Part of it is also being able to tune feature jerk settings in the newest Orcaslicer RC release. I will redesign the gantry later on to remove the issue.
I still think the biggest issue is that the DWC IS interface needs more diagnostic options and a better explanation how it works and how to use it. I can see a lot of people trying to get IS to work but not really understanding what they are looking for or ideas on how to effectively utilize it. They get frustrated and run off to Klipper.
-
RE: Flagged as Spam??
I'm having the same issue. My post keeps getting flagged as spam.
-
RE: Flagged as Spam??
@br7408 said in Flagged as Spam??:
I'm having the same issue. My post keeps getting flagged as spam.
I tried posting from a different computer and it works now. Wierd.
-
RE: Issues with pressure advance since RRF 3.4
My slightly modified Creality 5 pro prints FLAWLESS prints in ASA within +/- .03mm, and perfect corners every time, and has printed several hundred of these prints for two years now in numerous sizes and detail; with no PA or IS applied.
I wonder what the true problem is here…
If you’re relying on current software to fully tune out harmonic and flow issues of your printer, you simply need to slow down your outer perimeter print speed and accept the limitations of your printer.
Without a full feedback loop of accurate algorithms, no current software will be able to adjust for all conditions and provide the accuracy that people seem to think is expected. What is happening instead is we turn into the feedback loop and chase countless inconsistencies.
You will be more successful and efficient resolving resonance/pressure issues by improving the physical design of the printer than you will be expecting software to resolve it.
I’ve been fighting this shit for over a year now, and I’m tired. I’ve finally figured out that simply slowing down outer perimeters, turning down PA and turning off IS & optimizing outer perimeter jerk/accel/speed gives me the best and most consistent print and I don’t need to re-tune for every nozzle size or material. Yes, its slower. Its also much less filament/nozzle dependent and more consistent. I can still print infill and supports at insane fast speeds to cut down on time.
If you really want super speed, buy a Bamboo and deal with their proprietary bullshit.
-
RE: Issues with pressure advance since RRF 3.4
Not sure why you seem to be so offended as my comments were not even a reply to your post specifically. I guess that is what the internet has become these days.
I feel it absolutely is on topic. The entire industry right now is using printing and movement speed as a selling point to their machines, and this entire topic is based on software algorithms that are implemented SOLELY to improve printing speed. My Creality 5 Pro is not a Bowden machine, as you assume. It is also only one of four printers that I own. I only use it as an example because it is the one machine that prints consistently with zero corner issues or resonance with zero PA or IS applied and it does this due to the specific reasons that I highlighted.
I have been tuning my Duet-based CoreXY printer for a very long time, using and implementing just about every approach possible, and with each approach, it always comes back to the same basic principle, which I adequately highlighted. Software is not going to make a machine faster when it has specific analog traits and limitations that vary beyond the capability of the software. Yes, it is fun to try, and yes, I can find one or two prints and apply a limited amount of IS and PA and eventually get them perfect... But when I go from a .6 to .8 nozzle and an entirely different material viscosity, or even filament brand... guess what... I need spend another 6 hours tuning IS, flow rate, PA, ect. to get that next print perfect, or I can just slow down and print it in 4 hours instead of 2 or 3 and already have been done with the print. Perhaps my view from a business owner standpoint is different because time to me is money.
You can try and speak for Duet all you want and become offended over some words. Quite the contrary to a defeatist attitude; my sole point is that one should be well aware of the limits of their machine and manage their expectations accordingly. The Bambu comment was because I actually am on loan with one right now to test and study. I am not a fan of proprietary machines, and never have been. The requirements of my business are well beyond the size capabilities of a Bambu. I do feel like they have gotten a few things right because this machine indeed uses feedback to adjust for changing analogous conditions per print and per material and the results are quite evident.
I can assure you the Duet engineers are studying the same technology as well and doing their best to determine future implementation. The bigger burden is on the Duet engineers to design an open source software that works across any machine, which of course is a much greater challenge, and I have nothing but commendation for Duet, Dave Crocker, and the hard work they have put in to meet customer expectations to date. I would not be in a Duet forum with over a thousand dollars invested in numerous Duet boards if I was not a huge fan of both their product and their work.
-
David's IR Sensor: Questions
I'm building a 500mm CoreXY and unable to use bltouch, due to the magnetic field of my custom bed.
I want to run David's IR sensor, as the form factor is perfect for my printhead design. I am normally used to printing on PEI flex sheets, but I understand that will not work with this sensor. I do not have the means to bake a black grill paint coating underneath a PEI sheet.
I am considering going with the Buildtak black nylon surface. Will this work ok?
Also, are there any other recommendations any other flex sheet build surfaces that will work well with this sensor, with similar characteristics to PEI? I print ASA about 90% of the time.
Thanks
-
RE: David's IR Sensor: Questions
@Norder Thank you very much for that information. I will look into that plate and report back what I end up going with.
-
RE: David's IR Sensor: Questions
@Norder I tried that with what magnetic shielding tape available at a local store. Minimal improvement as these magnets are very strong.
Latest posts made by br7408
-
RE: Scanning Probe Mounting Issue
Thanks guys. Undersized countersink screws were my best idea as well. I guess I will go that route. I can probably CAD in a slightly raised index to better stabilize the board and give the screws a little more surface bite at the screw head. I will just back-load the heat inserts.
-
Scanning Probe Mounting Issue
So I am reading that the probe should be 1-2mm above the nozzle. That's fine, but how is one expected to use screws to mount the scanning probe as the screw heads will protrude down below the nozzle and smash into the print. Can I please get some clarification on this as to how high I can mount the scanning probe above the nozzle?
2mm is definitely not going to work, even with low profile screws.
"The bottom of the SZP coil should be around 1 to 2mm above the tip of the nozzle, so that when scanning the bed the G31 trigger height can be set to around 2mm to avoid the nozzle contacting the bed, while keeping the coil fairly close to the bed."
-
RE: 3 Bed Scanner Questions
@T3P3Tony said in 3 Bed Scanner Questions:
@becky9 thanks for the feedback. The spring steel plates i tested on my toolc hanger (which has a Mandala Roseworks Bed with strong magnets on it) do not show the point magnets through. Once of those is a generic spring steal bed, the other is a Wham Bam one (quite old though, not sure when i first got it)
Thanks for the info. I am using the Mandala Rose Works bed with WhamBam pex sheets. Hopefully I’ll have similar experience.
-
RE: Hotend Heater Overshoots Badly
Hi Ian. I was looking into that, as well as PID fan compensation. My part cooling fan is run off of the main board, through a CPAP tube. I also reasoned that this hotend would likely benefit from a heatsock/insulator but the Slice offering is about $50 USD.
I built this printhead purely for a promotion, so I just need it to run well enough for now to get a print or two out of it. I will work out a more efficient implementation later.
-
RE: Hotend Heater Overshoots Badly
Somehow I fixed it.
I added the M501 at the end of the config.g.
I was not changing the K value; I was changing the R value; that was a mistype.
It looks like I had gotten some strangely high K values from the M307 yesterday. I tried another PID today and it dropped way down and its working properly now. This hotend seems to be much more affected by my fan as well.
I also updated to the newer RC2 firmware; although I doubt that made any difference.
-
Hotend Heater Overshoots Badly
I normally try to research ad nauseum to solve problems myself, but this one really has me stumped. I just installed a Mosquito Magnum Pro 2.85 hotend, running a Duet3 wifi and 1LC toolboard.
I did the PID tuning at 230, and the tunes come out fine; relatively consistent numbers on 3 separate PID tunes, with no errors during the tunes.
When I go to set a temperature, it overshoots very rapidly, and I get a fault.
-
I have raised/lowered the M307 K value 10%. The guide says to lower it but I've also seen Dave tell people to raise it in this forum, so not sure.
-
I have tried lowering the M307 S value (0.7).
-
I even disassembled the hotend to verify the heater is 24V. It is indeed a 24V, 52W Slice Engineering heater.
-
I've observed heating cycles; the rate on the graph is very smooth, with no weird spikes or abnormalities.
-
I went to just try setting temps at various increments. On the first try at 100, it quickly shot past 100, faulted, and hit 121 before cooling off.
Here is all the information and configs. Hopefully I'm just missing something stupid. I also understand this is a pretty massive heater and it may take some effort.
M307 H1:
Heater 1: heating rate 1.516, cooling rate 4.830, dead time 8.83, max PWM 1.00, mode PID, calibrated at 23.5V Predicted max temperature rise 42°C PID parameters: heating P13.3 I0.938 D82.4, steady P13.3 I1.044 D82.4
config.g:
; Configuration file for Duet 3 Mini 5+ (firmware version 3.3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.16 on Sun Apr 16 2023 22:41:37 GMT-0400 (Eastern Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"BR1" ; set printer name M669 K1 ; select CoreXY mode ; Wait a moment for the CAN expansion boards to start G4 S4 ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0.0 S0 ; physical drive 0.0 goes forwards M569 P0.1 S0 ; physical drive 0.1 goes forwards M569 P0.2 S0 ; physical drive 0.2 goes forwards M569 P0.3 S1 ; physical drive 0.3 goes forwards M569 P0.4 S1 ; physical drive 0.4 goes forwards M569 P0.5 S1 ; physical drive 0.5 goes forwards M569 P121.0 S0 ; physical drive 121.0 goes forwards M584 X0.4 Y0.3 Z0.2:0.1:0.0 E121.0 ; set drive mapping M350 E16 I0 ; configure microstepping without interpolation M350 X16 Y16 Z16 E32 I1 ; configure microstepping with interpolation M92 X81.07 Y80.90 Z800.82 E825.00 ; set steps per mm for .8mm ASA filament M566 X720.00 Y720.00 Z10.00 E3000.00 ; set maximum instantaneous speed changes (mm/min) M203 X16000.00 Y16000.00 Z600.00 E6000.00 ; set maximum speeds (mm/min) M201 X6000.00 Y6000.00 Z100.00 E3600.00 ; set accelerations (mm/s^2) M906 X1400 Y1400 Z1600 E600 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X-245:245 Y-250:250 Z0:460 ;XY axis minima ; Endstops M574 X1 S1 P"io0.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io0.in M574 Y2 S1 P"io1.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io1.in M574 Z1 S2 ; configure Z-probe endstop for low end on Z ; Bed Leveling M671 X-253.5:-1:253.5 Y-243:267.5:-243 S5 ; define positions of Z leadscrews or bed levelling screws M557 X-200:200 Y-190:210 S20 ; define 5x5 mesh grid ; Z-Probe M950 S0 C"121.io0.out" ; create servo pin 0 for BLTouch M558 P8 C"121.io0.in" H4 F120 T12000 R0.2 A20 S0.005 ; set Z probe type to DuetIR and the dive height + speeds avg 5 probes tolerance .01 ;M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved G31 P50 X27.33 Y73.71 Z2.888 ; set Z probe trigger value, offset and trigger height M556 S50 X0 Y0 Z0 ; set orthogonal axis compensation parameters M557 X-200:200 Y-190:210 P5 ; define mesh grid ; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B3950 A"Bed" ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 Q11 ; create bed heater output on out0 and map it to sensor 0, lower switching frequency 11hz ;M307 H0 R0.456 K0.916:0.000 D3.79 E1.35 S1.00 B0 ; old heater PID parameters 100C given from PID tune 14May23 M307 H0 R0.460 K0.487:0.000 D3.36 E1.35 S1.00 B0 ; PID parameters 110 C 22May23 M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 110C M308 S1 P"121.temp0" Y"PT1000" ; configure sensor 1 as thermistor on pin 121.temp0 M950 H1 C"121.out0" T1 ; create nozzle heater output on 121.out0 and map it to sensor 1 M307 H1 R1.516 K4.830:0.000 D8.83 E1.35 S1.0 B0 V23.5 ; PID from 22Jan24 Mosquito Pro Ind 230 celsius M143 H1 S295 ; set temperature limit for heater 1 to 295C ; Fans M950 F0 C"!out4+out4.tach" Q25 ; create fan 0 on pin out4 and set its frequency M950 F1 C"121.out2" ; create fan 1 at extruder toolboard M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M106 P1 T40 H1:1 ; set extruder 121 fan to run at 40° extruder temp ; Tools M563 P0 S"Mosquito Magnum" D0 H1 F0 ; define tool 0 G10 P0 X0 Y10 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ;M572 D0 S0.050 ;PA for .8 ASA ;M572 D0 S0.07 ;PA .6 ASA ;M572 D0 S0.045 ;PA for 1.2 ASA ;M572 D0 S0.05 ;PA for .6 Nylon ;M572 D0 S0.085 ; PA for .8 PETG ;M572 D0 S0.065 ;PA for .4 PC ; retraction ;M207 S0.5 F3000 ; retraction amount and speed ASA .8 ;M207 S0.8 F2700 ; retraction amount and speed ASA 1.2 M207 S0.25 F2100 Z0.3 ; retraction for PETG .8 ; Accelerometer and Input Shaping M955 P121.0 I41 M593 P"zvd" F25.4 S0.0 ;configure direct connect display M918 P2 E-4 F2000000 M950 E0 C"io3.out" T1 U3 ; create a RGB Neopixel LED strip with 3 LEDs on the Duet 3 Mini 5+ 12864_EXP1 header M150 E0 R255 U255 B255 P255 S1 F1 ; display led M150 E0 R0 U0 B255 P255 S1 F1 ; left encoder led M150 E0 R0 U0 B255 P255 S1 F0 ; right encoder led ; Custom settings are not defined ; Miscellaneous T0
config-override.g
; config-override.g file generated in response to M500 at 2024-01-22 21:21 ; This is a system-generated file - do not edit ; Heater model parameters M307 H0 R0.460 K0.487:0.000 D3.36 E1.35 S1.00 B0 M307 H1 R1.516 K4.830:0.000 D8.83 E1.35 S1.00 B0 V23.5 ; Workplace coordinates G10 L2 P1 X0.00 Y0.00 Z0.00 G10 L2 P2 X0.00 Y0.00 Z0.00 G10 L2 P3 X0.00 Y0.00 Z0.00 G10 L2 P4 X0.00 Y0.00 Z0.00 G10 L2 P5 X0.00 Y0.00 Z0.00 G10 L2 P6 X0.00 Y0.00 Z0.00 G10 L2 P7 X0.00 Y0.00 Z0.00 G10 L2 P8 X0.00 Y0.00 Z0.00 G10 L2 P9 X0.00 Y0.00 Z0.00
M122:
m122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.1+ (2023-11-03 17:18:21) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: GS9VZ-V296U-D65J0-40KMY-L713Z-RU7ZK Used output buffers: 3 of 40 (20 max) === RTOS === Static ram: 102812 Dynamic ram: 128244 of which 12 recycled Never used RAM 10348, free system stack 200 words Tasks: NETWORK(2,nWait,15.7%,228) HEAT(3,nWait,0.0%,356) Move(4,nWait,0.0%,358) CanReceiv(6,nWait,0.0%,774) CanSender(5,nWait,0.0%,336) CanClock(7,delaying,0.0%,350) TMC(4,nWait,0.7%,108) MAIN(1,running,82.7%,670) IDLE(0,ready,0.0%,29) AIN(4,delaying,0.8%,264), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:29:28 ago, cause: power up Last software reset at 2023-12-25 09:52, reason: User, Gcodes spinning, available RAM 11228, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 MCU revision 3, ADC conversions started 1768450, completed 1768450, timed out 0, errs 0 MCU temperature: min 19.6, current 33.2, max 33.2 Supply voltage: min 24.0, current 24.1, max 24.2, 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: 3 queued, 3 completed Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 18, reads 27499, writes 18, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 18, reads 27499, writes 18, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 18, reads 27498, writes 18, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 18, reads 27498, writes 18, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 18, reads 27499, writes 18, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2024-01-22 21:08:15 Cache data hit count 3375602439 Slowest loop: 60.74ms; fastest: 0.17ms === Storage === Free file entries: 20 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 4.6ms, write time 2.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 === DDARing 0 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === DDARing 1 === 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 === Movement locks held by null, 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 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 0, axes/extruders owned 0x0000803 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 15996, received 35418, lost 0, errs 0, boc 0 Longest wait 2ms for reply type 6053, peak Tx sync delay 261, free buffers 26 (min 25), ts 8842/8841/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 17.33ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 === WiFi === Interface state: active Module is connected to access point Failed messages: pending 0, notrdy 0, noresp 0 Firmware version 1.27 MAC address f0:08:d1:03:80:d7 Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 25056 WiFi IP address 192.168.1.135 Signal strength -36dBm, channel 0, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0
Thanks for your time.
-
-
RE: 3 Bed Scanner Questions
@droftarts Thank you. I will certainly order one then and try it out.
-
3 Bed Scanner Questions
I am looking into purchasing the bed scanner for use with my new prototype carriage (500x500 bed). I have read that it may have difficulty with the beds with embedded magnets, but should be ok once the build plate is in place. Has anyone tried this yet to confirm?
I cannot use a BL touch because the magnets in my bed are strong enough that it skews the results.
Is there any way to modify the scanning sectors so it avoids going directly over the magnets, or simply exclude the mesh data where the magnets are located?
Also, are there any CAD files of the bed scanner components available?
Thank you for your time.
-
RE: Duet Mini 5+ wifi Dropping Connection
@Phaedrux Specifically, which file is the 1.27 server version?
I'm assuming it was packaged with the older 3.46 firmware, and I'm assuming it is compatible with the other newer firmware versions I'm running?