I'm using this external mosfet. If I use a different one, will the noise go away?
With Q50 the annoying sound is almost silent. Can I use it or will something break?
Posts made by jensus11
-
RE: BLTouch alternative for hotbed with magnetsposted in General Discussion
-
RE: BLTouch alternative for hotbed with magnetsposted in General Discussion
I want to test the F25 and became this message.
Fehler in Startdatei macro Zeile 69: exactly one of EFHJPSR must be given M950 H0 C"bed" T0 F25 -
RE: BLTouch alternative for hotbed with magnetsposted in General Discussion
That sounds good, what I have to change it?
M307 H0 R0.475 K0.931:0.000 D7.84 E1.35 S1.00 B0 M308 S0 P"e0temp" Y"thermistor" T100000 B3950 C7.06e-8 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bed" T0 ; create bed heater output on bedheat and map it to sensor 0 M140 H0 ; map heated bed to heater 0 M143 H0 S100 ; set temperature limit for heater 0 to 100C -
RE: BLTouch alternative for hotbed with magnetsposted in General Discussion
ok. I'll order an inductive one and try it out and then report back.
Unfortunately, I have a problem with my Keenovo heating pad. I've just installed it. When I want to heat the bed to 60 degrees, everything is quiet up to 55 degrees. From 55 degrees onwards the heating pad makes noise. A humming noise that only stops when it's turned off.
Do you have any ideas? The heating pad is new.
-
RE: BLTouch alternative for hotbed with magnetsposted in General Discussion
For me, it is definitely the magnet. The BLTouch measures 4 positions perfectly. Then the magnet comes and the pin is not retracted and flashes blue and red. There are also neodymium magnets which are embedded in the plate from below.
-
RE: BLTouch alternative for hotbed with magnetsposted in General Discussion
Hi oliof,
I have the BLTouch in V3.1, so with a nylon pin. I think the mechanism doesn't work with the strong magnets.
Can you tell me a good inductive/scanning probe?
-
BLTouch alternative for hotbed with magnetsposted in General Discussion
Hi everyone, I bought a new hotbed with magnets on the bottom. Unfortunately, the BLTouch doesn't measure properly. When it's over a magnet, it doesn't have enough power to pull the pin back and gives a message that the probe is in use.
What is a perfect alternative that works perfectly with magnets?
-
RE: Wifi 2.1beta6 from 3.5.0-rc.2/3 still disconnectingposted in Beta Firmware
Thanks, for the first time it looks really better.
-
RE: Wifi 2.1beta6 from 3.5.0-rc.2/3 still disconnectingposted in Beta Firmware
@rechrtb Do you give me the 2.1 beta7, please? I have terrible issues with my connection. That is so bad, that I have to restart the printer on every time.
-
RE: optimize heightmapposted in Tuning and tweaking
The bed can be adjusted with screws and Z has a stepper. Leveling via a 4 point macro, which doesn't work when I check it with paper. The 2 screws in the front are ok, only at the back both screws are too far away from the nozzle. If I manually level the heightmap comes from above.
4 point macro
M140 S70 M190 S70 M671 x43:214:214:43 y43:43:214:214 P0.7 ; The location of the four bed securing screws ;M558 P0 ; Uncomment this if you don't have a Z Probe G28 X Y Z ; Home Z G30 P0 X43 Y43 Z-99999 ; probe near an adjusting screw ; Front left screw G30 P1 X214 Y43 Z-99999 ; probe near an adjusting screw ; Front right screw G30 P2 X214 Y214 Z-99999 ; probe near an adjusting screw ; Rear right screw G30 P3 X43 Y214 Z-99999 S4 ; probe near an adjusting screw ; Rear left screw G28 Z ; Home Z ;M140 S0bed mesh
M140 S70 M190 S70 M98 P"homeall.g" G29 M140 S0 -
optimize heightmapposted in Tuning and tweaking
Hello,
I think my heightmap doesn't look that good. I would like to optimize it. Can you help me with this and take a look at my data/files?
Which data should I upload?Thanks
config.g
; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Sun May 24 2020 14:10:48 GMT+0200 (Mitteleuropäische Sommerzeit) ;############## General Preferences ################## G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"home" ; set printer name M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S1 ; enable FTP M586 P2 S1 ; enable Telnet M669 K1 ; switch to CoreXY mode ;############## Drive Direction ###################### M569 P0 S0 ; physical drive 0 goes backwards X M569 P1 S0 ; physical drive 1 goes backwards Y M569 P2 S1 ; physical drive 2 goes backwards Z M569 P3 S0 ; physical drive 3 goes forwards E ;############## Axis Mapping ######################### M584 X0 Y1 Z2 E3 ; set drive mapping ;############## Microstepping ######################## M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation ;############## Steps Per mm ######################### M92 X160.00 Y160.00 Z160 E692 ; set steps per mm ;############## Speeds and Feeds ##################### ;M566 X1000.00 Y1000.00 Z60.00 E300.00 ; set maximum instantaneous speed changes (mm/min) -Jerk M566 X800.00 Y800.00 Z60.00 E400.00 ; set maximum instantaneous speed changes (mm/min) -Jerk M203 X15000.00 Y15000.00 Z6000.00 E7200.00 ; set maximum speeds (mm/min) M201 X2000.00 2000.00 Z20.00 E3000.00 ; set accelerations (mm/s^2) ;M201 X1400.00 Y1400.00 Z20.00 E3000.00 ; set accelerations (mm/s^2) M906 X1200 Y1200 Z1600 E1000 I5 ; set motor currents (mA) and motor idle factor in per cent M84 S60 ; set idle timeout ;############## Axis Limits ########################## M208 X0 Y8 Z0 S1 ; set axis minima M208 X250 Y260 Z225 S0 ; set axis maxima ;############## Endstops ############################# M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop M574 Y2 S1 P"ystop" ; configure active-high endstop for high end on Y via pin ystop ;############## Z-Probe ############################## M558 P5 C"zprobe.in" H5 F400 T8000 ; create servo zprobe.in for BLTouch M950 S0 C"exp.heater3" ; set Z probe type to bltouch and the dive height + speeds G31 P500 X18.0 Y-43.0 Z2.82 ; set Z probe trigger value, offset and trigger height M557 X28:238 Y17:217 S25 ; define mesh grid ;M376 H10 ;############## Heaters ############################## M308 S0 P"bedtemp" Y"thermistor" T100000 B4838 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M143 H0 S100 ; set temperature limit for heater 0 to 120C M307 H0 R0.413 K1.227:0.000 D4.91 E1.35 S1.00 B0 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M143 H1 S285 ; set temperature limit for heater 1 to 260C M307 H1 R4.065 K0.547:0.000 D2.25 E1.35 S1.00 B0 V24.3 ; disable bang-bang mode for heater and set PWM limit ;############## Fans ################################# M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"fan2" Q25000 ; create fan 2 on pin fan2 and set its frequency M106 P2 S0:1 H1:0 T45 ; set fan 2 value. Thermostatic control is turned on ;############## Tools ################################ M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ;############## Custom settings ###################### M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss M575 P1 S1 B57600 ; enable support for PanelDue ;############## Miscellaneous ######################## M501bed.g
; bed.g ; called to perform automatic bed compensation via G32 ; ; generated by RepRapFirmware Configuration Tool v3.1.3 on Thu Jun 25 2020 17:43:46 GMT+0200 (Mitteleuropäische Sommerzeit) M561 ; clear any bed transform G29 ; probe the bed and enable compensationhomeall.g
; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v3.1.3 on Thu Jun 25 2020 17:43:46 GMT+0200 (Mitteleuropäische Sommerzeit) G91 ; relative positioning G1 H2 Z10 F10000 ; lift Z relative to current position G1 H1 X-260 Y270 F5000 ; move quickly to X and Y axis endstops and stop there (first pass) G1 H1 X-240 ; coarse home X G1 H1 Y260 ; coarse home Y G1 X5 Y-5 F5000 ; go back a few mm G1 H1 X-10 ; fine home X G1 H1 Y10 ; fine home Y M98 P"homez.g" G90 ; absolute positioninghomez.g
; homez.g ; called to home the Z axis ; ; generated by RepRapFirmware Configuration Tool v3.1.3 on Thu Jun 25 2020 17:43:46 GMT+0200 (Mitteleuropäische Sommerzeit) G91 ; relative positioning G1 H2 Z10 F10000 ; lift Z relative to current position G90 ; absolute positioning G1 X108 Y168 F15000 ; Move to the center of the bed. Adjust to the co-ordinates required for the centre of your bed M558 F800 ; Set the probing speed G30 ; Probe a single point M558 F180 ; Set a slower probing speed G30 ; Probe a single point G1 X0 Y260 F15000M122
M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-rc.3 (2024-01-24 17:56:24) running on Duet WiFi 1.02 or later Board ID: 08DLM-996AL-K6PSD-6JKD6-3S86T-KVGUZ Used output buffers: 5 of 26 (26 max) === RTOS === Static ram: 23224 Dynamic ram: 73068 of which 0 recycled Never used RAM 13780, free system stack 120 words Tasks: NETWORK(2,nWait 6,33.7%,194) HEAT(3,nWait 5,0.1%,327) Move(4,nWait 5,0.9%,283) MAIN(1,running,65.1%,742) IDLE(0,ready,0.1%,30), total 100.0% Owned mutexes: === Platform === Last reset 02:09:23 ago, cause: power up Last software reset at 2024-02-18 20:00, reason: User, Gcodes spinning, available RAM 12768, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x14 Aux0 errors 0,0,0 MCU temperature: min 20.5, current 42.5, max 42.6 Supply voltage: min 23.9, current 24.3, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/44/16, gc cycles 0 Events: 0 queued, 0 completed Driver 0: ok, SG min 0 Driver 1: standstill, SG min 0 Driver 2: ok, SG min n/a Driver 3: ok, SG min 0 Driver 4: standstill, SG min n/a Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Date/time: 2024-02-19 19:10:15 Cache data hit count 4294967295 Slowest loop: 235.95ms; fastest: 0.19ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 9 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 9.0ms, write time 478.8ms, max retries 0 === Move === DMs created 83, segments created 9, maxWait 6486772ms, bed compensation in use: mesh, height map offset 0.000, max steps late 1, ebfmin -1.00, ebfmax 1.00 next step interrupt due in 72 ticks, disabled Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 === DDARing 0 === Scheduled moves 2690, completed 2685, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.0 Heater 1 is on, I-accum = 0.3 === GCodes === Movement locks held by null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 3 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Q0 segments left 3 Code queue 0 is empty === Network === Slowest loop: 534.20ms; fastest: 0.00ms Responder states: 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 2.1beta6 MAC address XXXXXXXXXXXXXX Module reset reason: Turned on by main processor, Vcc 3.38, flash size 2097152, free heap 37616 WiFi IP address XXXXXXXXX Signal strength -38dBm, channel 3, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
RE: when changing the tool, the Z height changes at offset 0posted in General Discussion
The solution for my issue is in this post.
https://forum.duet3d.com/topic/29608/the-problem-of-restoring-z-height-after-toolchanger-tool-change
2 commands in the tpost#.g.
-
when changing the tool, the Z height changes at offset 0posted in General Discussion
Hello,
I have a problem with my Idex. When I make a tool change, the Z height changes. T0 has Z=0.24mm and when T1 is activated, Z changes to 0.13 mm, although the offset is 0. I tried and tested a lot.
The error is the G29 S1 in the boot code. If I disable that, Z doesn't change and stays the same on both tools. Is this a bug?code_text ```; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Sun Apr 26 2020 08:28:03 GMT+0200 (Mitteleuropäische Sommerzeit) ;############## General Preferences ################## G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"iDex" ; set printer name M669 K11 Y1:1:0:-1 ; select Markforged Kinematics Y to react with X and U ;############## Network ###################### M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ;############## Drive Direction ###################### M569 P0 S1 D2 ; physical drive 0 X M569 P1 S1 D2 ; physical drive 1 Y M569 P2 S1 D2 ; physical drive 2 Z M569 P3 S1 D2 ; physical drive 3 U M569 P4 S1 D2 ; physical drive 4 E0 M569 P5 S1 D2 ; physical drive 5 E1 ;############## Axis Mapping ######################### M584 X0 Y1 Z2 U3 E4:5 ; set drive mapping ;############## Microstepping ######################## M350 X16 Y16 Z16 U16 E16:16 I1 ; configure microstepping with interpolation ;############## Steps Per mm ######################### M92 X80.00 Y80.00 Z2400 U80.00 E744:738 ; set steps per mm ;############## Speeds and Feeds ##################### M566 X600.00 Y600.00 Z12.00 U600.00 E300.00:300.00 ; set maximum instantaneous speed changes (mm/min) M203 X15000.00 Y15000.00 Z2000.00 U15000.00 E3000.00:3000.00 ; set maximum speeds (mm/min) M201 X2000.00 Y2000.00 Z30.00 U2000.00 E1500.00:1500.00 ; set accelerations (mm/s^2) M906 X1200 Y1400 Z1200 U1200 E600:600 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; set idle timeout ;############## Axis Limits ########################## M208 X-234 Y-185 Z0 U-150 S1 ; set axis minimal M208 X150 Y135 Z330 U234 S0 ; set axis maximal ;############## Endstops ############################# M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop M574 Y2 S1 P"e1det" ; configure active-high endstop for high end on Y via pin ystop M574 U2 S1 P"e0det" ;############## Z-Probe ############################## M558 P9 H6 F120 T8000 C"^probe" ; set Z probe type to bltouch and the dive height + speeds M950 S0 C"servo0" ; Setup servo 0 as servo port on SKR ;G31 P25 X43 Y18 Z2.0 ; set Z probe trigger value, offset and trigger height G31 K0 P500 X43.0 Y18.0 U0.0 Z2.6 M557 X-150:140 Y-155:135 S30 ; define mesh grid ;############## Heaters ############################## M308 S0 P"e0temp" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bed" T0 ; create bed heater output on bedheat and map it to sensor 0 M140 H0 ; map heated bed to heater 0 M143 H0 S100 ; set temperature limit for heater 0 to 120C M308 S1 P"e1temp" Y"thermistor" T100000 B3950 M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M143 H1 S260 ; set temperature limit for heater 1 to 260C M308 S2 P"e2temp" Y"thermistor" T100000 B3950 M950 H2 C"e1heat" T2 ; create nozzle heater output on e0heat and map it to sensor 2 M143 H2 S260 ; set temperature limit for heater 2 to 260C ;B4260 ;Heizungsfehler M570 H0 P5 T15 S100 ; Bettheizung M570 H1 P5 T15 S270 ; E0 heizung M570 H2 P5 T15 S270 ; E1 heizung ;############## Fans ################################# M950 F0 C"fan0" ; create fan 2 on pin fan2 and set its frequency M106 P0 C"FAN0_T0_Bauteil" H-1 ; set fan 2 name and value. Thermostatic control is turned off M950 F1 C"fan1" ; create fan 3 on pin Heat2 and set its frequency M106 P1 C"FAN1_T1_Bauteil" H-1 ; set fan 3 name and value. Thermostatic control is turned off M950 F2 C"fan2" ; create fan 0 on pin fan0 and set its frequency M106 P2 C"FAN2_T0_Kühlung" H1 T45 ; set fan 0 name and value. Thermostatic control is turned on M950 F3 C"e2heat" ; create fan 1 on pin fan1 and set its frequency M106 P3 C"Heat2_T1_Kühlung" H2 T45 ;############## Tools ################################ M563 P0 S"Head_0" D0 H1 X0 F0 ; define tool 0 linker Wagen;X=0 Y=1 Z=2 U=3 G10 P0 X0.011 Y0.009 Z0 U0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C M563 P1 S"Head_1" D1 H2 X3 F1 ; define tool 1 rechter Wagen G10 P1 X0.951 Y0.217 Z0 U0 ; set tool 1 axis offsets G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C M563 P2 S"Dual Duplication" D0:1 H1:2 X0:3 F0:1 ; tool 2 uses both extruders, hot end heaters and fans, and maps X to both X and U G10 P2 X75 Y0 U-75 ; set tool 2 axis offsets G10 P2 S0 R0 ; set initial tool 2 active and standby temperatures to 0C M567 P2 E1:1 ; set mix ratio 100% on both extruders ;############## Custom settings ###################### M575 P1 S1 B57600 ; enable support for PanelDue ;############## Miscellaneous ######################## M501
-
RE: PanelDue IP address display issue (3.3/3.4-pre1)posted in PanelDue
@oozeBot said in PanelDue IP address display issue (3.3/3.4-pre1):
This is surprising now that the PanelDue has been updated to work with the ObjectModel, but you are right.. after some testing, my assumption of what is passed to the PanelDue was incorrect.
We recently made the decision to build our own version of the PanelDue firmware (that we will keep in parity with the latest official releases). One of the changes was to add in the Global object. So to "fix" the issue, we added a global variable that contains the SBC's IP and are populating the field on the PanelDue with it.. It's not elegant, but it works.
Where can I find your PanelDue firmware?
-
RE: Temperatures totally wrong 3.4 RCposted in Beta Firmware
Thanks @dc42, the version works as it should. The temperature fluctuations are history.
-
RE: Temperatures totally wrong 3.4 RCposted in Beta Firmware
@dc42 Unfortunately I can't test it. I have to wait until gloomyandy releases a new FW.
-
RE: Temperatures totally wrong 3.4 RCposted in Beta Firmware
@dc42
I tested it without the second K value. It's better but not good yet. With K0 it looks very good. -
RE: Temperatures totally wrong 3.4 RCposted in Beta Firmware
It really must be the transition from infill to top layer. If I only print the botton and then the top layer, it's ok. Exactly the same if I only print perimeter.
-
RE: Temperatures totally wrong 3.4 RCposted in Beta Firmware
I don't think that was the case in 3.4-b5. It is not possible for me to print a Temptower. The temperature is just fluctuating. With other parts I noticed that the temperature increases in the first layer of the top layer after the infill part.
If I reduced the Bridges fan speed, it's better. I think when the part fan changes fast and slow the fluctuating start. If the partfan is constant, the temperature is also constant.Tell me what to do to help.
100% Bridges fan speed in my test print
50% Bridges fan speed in my test print
should i upload the gcodes?
-
RE: Temperatures totally wrong 3.4 RCposted in Beta Firmware
@Hernicz
M307 H1 R3.149 K0.525:0.172 D6.85 E1.35 S1.00 B0 V24.0you mean like that?
M307 H1 R3.149 D6.85 E1.35 S1.00 B0 V24.0