Thank you both for your help. I misunderstood what a core xyu is. My printer is a supposed to just be a core xy with an additional axis for the tool change mechanism. (my printer is most similar to E3D's tool changer 3D printer.)
Best posts made by SamKudarauskas
-
RE: Y axis moving significantly slower than X axis
-
RE: Incompatible Software Versions
@droftarts I was able to flash the firmware using Bossa on a windows partition of my macbook. Everything now works as it should. Thank you all of your help.
Sam
Latest posts made by SamKudarauskas
-
RE: Incompatible Software Versions
@droftarts I was able to flash the firmware using Bossa on a windows partition of my macbook. Everything now works as it should. Thank you all of your help.
Sam
-
RE: Incompatible Software Versions
@droftarts thank you for your help, I do have access to a Windows machine so I will try to flash the new firmware with Bossa.
Sam
-
RE: Incompatible Software Versions
@Phaedrux My duet is orientated in such a way that the 4 LEDs are top right on the board. From left to right the colors are green, red, red, blue when the usual 24V is supplied and when just the 5V from my computer is applied it is green, red, off, off. (also from left to right)
The DIAG/ STATUS LED is solid red when under 5V and is off under 24V. Does this mean the firmware has been erased? If so what do I do?
Thanks for your help.
-
Incompatible Software Versions
I just connected my duet 3 expansion 3HC to my duet Mainboard 6HC and updated the firmware on both of them to 3.5.1 yet on startup I get the error that they are running two different firmware levels. When I run M115 it returns that the MB6HC is running 3.5.1 and when I run M115 S0 (or it might have been M115 S1) it returns that the 3HC is also running 3.5.1 (all of these updated files were from https://github.com/Duet3D/RepRapFirmware/releases)
Since I still had the same error I then uploaded the file named Duet2and3Firmware-3.5.1.zip as suggested by the https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_firmware page. These files uploaded and the mainboard then restarted. The DWC never reconnected however. I tried turning everything off and on but I always got the browser error that that address could not be reached.
I then disconnected the power and tried to see if updating the files had just changed the IP address of my duet. I attempted to follow the instructions found in https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_Duet but I never got a return reply from the duet when I sent it any g code commands such as M115. The original time I had to set up its IP address I had some difficulties with getting Serial Tool to work. This time, as before, when I plug the duet into my computer (I am on a MacBook Pro) it shows up as a communications device, but it doesn't say duet anywhere either. I know the cable I am using is capable of sending data as well as power because it is my xbox's wired controller cable.
Edit: (It does show up in serial tools as usbmodem14301 as the guide says it might)
I'm out of ideas for other things to try other than completely wiping the firmware. (I've also tried just pressing the reset button and that does nothing as well)
Thanks for your time,
Sam -
RE: Storing current tool number across power cycle/ system restart
@dc42 Ok, thank you for your help. I will try that. How would I configure the switch and how would I check its status in a system file such as homeall.g?
Als, do you know if T R1 would work in my scenario? Or would it only work in a resume.g file?
-
Storing current tool number across power cycle/ system restart
My current tool changer 3D printer forgets what the current tool is when the power is cut or the system is restarted. What I want to happen is if a job is started and tool 0 is still selected for whatever reason that it homes the xy axis, puts the tool back and then continues the homing process. I am attempting to do this as a failsafe incase the tool isn't put back for some reason because it can not home the u or z axis with any tool currently selected.
So far I've gotten it to put the tool back if I simply instruct it to home all axis without cuttng the power or triggering a restart, however if I cut the power or just trigger a system restart with the DWC it doesn't try to put the tool back because it doesn't think one is selected.
I've taken a look at https://docs.duet3d.com/en/User_manual/Tuning/Resume but it doesn't appear to cover how to store and retrieve any secondary data such as the current tool number in my case. Additionally, system files such as resume.g don't seem to trigger if no job is active when the DWC tells it to restart.
Bellow are my relevant files. (note I don't currently have a resume.g set up yet because, correct me if I'm wrong, it doesn't run when the DWC triggers as system restart)
config.g
; Configuration file for RepRapFirmware on Duet 3 Main Board 6HC ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.5.0-rc.3 on Fri Mar 15 2024 11:41:50 GMT-0400 (Eastern Daylight Time) ; General M550 P"Duet 3" ; set hostname ; Accessories M575 P1 S0 B57600 ; configure PanelDue support ; Network M551 P"Knights24" ; set machine password M552 P0.0.0.0 S1 ; configure Ethernet adapter M586 P0 S1 ; configure HTTP ; Smart Drivers M569 P0.0 S1 D2 ; driver 0.0 goes forwards (X axis) M915 P0.0 S1 ; set StallGuard threshold M569 P0.1 S0 D2 ; driver 0.1 goes backwards (Y axis) M915 P0.1 S1 ; set StallGuard threshold M569 P0.2 S0 D2 ; driver 0.2 goes backwards (Z axis) M915 P0.2 S1 ; set StallGuard threshold M569 P0.3 S0 D2 ; driver 0.3 goes backwards (Z axis) M915 P0.3 S1 ; set StallGuard threshold M569 P0.4 S1 D2 ; driver 0.4 goes forwards (U axis) M915 P0.4 S2 ; set StallGuard threshold M569 P0.5 S1 D2 ; driver 0.5 goes forwards (extruder 0) ; Motor Idle Current Reduction M906 I10 ; set motor current idle factor M84 S10 ; set motor current idle timeout ; Axes M584 X0.0 Y0.1 Z0.2:0.3 U0.4 ; set axis mapping M350 U16 I0 ; configure microstepping without interpolation M350 X16 Y16 Z16 I1 ; configure microstepping with interpolation M906 X900 Y900 Z900 U400 ; set axis driver currents M92 X160 Y160 Z400 U200 ; configure steps per mm M208 X0:300 Y0:300 Z0:300 U0:270 ; set minimum and maximum axis limits M566 X900 Y900 Z12 U30 ; set maximum instantaneous speed changes (mm/min) M203 X9000 Y9000 Z180 U4000 ; set maximum speeds (mm/min) M201 X600 Y600 Z20 U50 ; set accelerations (mm/s^2) ; Extruders M584 E0.5 ; set extruder mapping M350 E16 I1 ; configure microstepping with interpolation M906 E900 ; set extruder driver currents M92 E397.5 ; configure steps per mm M566 E120 ; set maximum instantaneous speed changes (mm/min) M203 E3600 ; set maximum speeds (mm/min) M201 E250 ; set accelerations (mm/s^2) ; Kinematics M669 K1 ; configure CoreXY kinematics ; Probes M558 K0 P9 C"io4.in" H5 F120 T6000 ; configure BLTouch probe via slot #0 G31 P500 X4 Y-70 Z0.7 ; set Z probe trigger value, offset and trigger height M950 S0 C"io4.out" ; create servo #0 for BLtouch ; Endstops M574 X1 S3 ; configure X axis endstop M574 Y1 S3 ; configure Y axis endstop M574 Z1 S2 ; configure Z axis endstop M574 U1 S3 ; configure U axis endstop M915 X Y Y R0 F0 H400; manually added for sensorless homing ; Mesh Bed Compensation M557 X15:245 Y20:215 S80 ; probe from X=10 to 245, Y=10 to 245mm with a mesh spacing of 80mm ; Sensors M308 S0 P"temp0" Y"thermistor" A"Heated Bed" T100000 B4725 C7.06e-8 ; configure sensor #0 M308 S1 P"temp1" Y"thermistor" A"Nozzle" T100000 B4725 C7.06e-8 ; configure sensor #1 ; Heaters M950 H0 C"out0" T0 ; create heater #0 M143 H0 P0 T0 C0 S140 A0 ; configure heater monitor #0 for heater #0 M307 H0 R0.401 K0.333:0.000 D13.12 E1.35 S1.00 B0 ; configure model of heater #0 M950 H1 C"out1" T1 ; create heater #1 M143 H1 P0 T1 C0 S300 A0 ; configure heater monitor #0 for heater #1 M307 H1 R1.804 K0.293:0.000 D9.68 E1.35 S1.00 B0 V24.1; configure model of heater #1 ; Heated beds M140 P0 H0 ; configure heated bed #0 ; Fans M950 F0 C"out5" ; create fan #0 M106 P0 S0 L0 X1 B0.1 ; configure fan #0 M950 F1 C"out4" ; create fan #1 M106 P1 S0 B0.1 H1 T45 ; configure fan #1 ; Tools M563 P0 D0 H1 F0 ; create tool #0 G10 P0 Z-4.55 ; set custom offsets for tool #0 M568 P0 R0 S0 ; set initial tool #0 active and standby temperatures to 0C
homeall.g
;; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v3.5.0-rc.3 on Fri Mar 15 2024 11:41:50 GMT-0400 (Eastern Daylight Time) ; ; home Y ; M400 ; Wait for current moves to finish G91 ; relative positioning G1 H2 Z10 F12000 ; lift Z relative to current position M400 ; wait for current move to finish M913 X25 Y25 ; drop motor current to 25% M400 G1 H1 Y-400 F10000 ; move quickly to Y axis endstop and stop there (first pass) G1 H2 Y5 F12000 ; go back a few mm G1 H1 Y-400 F5000 ; move slowly to Y axis endstop once more (second pass) G90 ; absolute positioning M400 M913 X100 Y100 ; return current to 100% M400 ;home X ; M400 ; Wait for current moves to finish M913 X30 Y30 ; drop motor current to 30% M400 G1 H1 X-400 F10000 ; move quickly to X axis endstop and stop there (first pass) G1 H2 X5 F12000 ; go back a few mm G1 H1 X-400 F5000 ; move slowly to X axis endstop once more (second pass) G1 X5 ;offset so tool doesnt hit belt G92 X0 ;sets current x pos as 0 M400 ;G1 H2 Z-10 F6000 ; lower Z again M564 S0 H0 ; allows temporary movemnt outside of homed axis T-1 M564 S1 H1; ; M98 P"homeU.g" ; home U axis ; home Z var xCenter = move.compensation.probeGrid.mins[0] + (move.compensation.probeGrid.maxs[0] - move.compensation.probeGrid.mins[0]) / 2 - sensors.probes[0].offsets[0] var yCenter = move.compensation.probeGrid.mins[1] + (move.compensation.probeGrid.maxs[1] - move.compensation.probeGrid.mins[1]) / 2 - sensors.probes[0].offsets[1] G1 X{var.xCenter} Y{var.yCenter} F6000 ; go to bed centre G30 ; probe the bed ;M98 P"bed.g" ; mesh bed ;G92 Z0 ;sets current z pos as 0 ;M400 G90 ;absolute positioning
homeu.g
M400 ; Wait for current moves to finish M913 U100 ; drop motor current to 20% ;U34.5 M400 G91 ; relative positioning G1 H1 U-400 F10000 ; move quickly to X axis endstop and stop there (first pass) G1 H2 U5 F12000 ; go back a few mm G1 H1 U-400 F5000 ; move slowly to X axis endstop once more (second pass) G90 ; absolute positioning M400 M913 U100 ; return current to 100% M400
Thank you for your time and I'm happy to provide any other files or test anything.
-
RE: Controling 120V 750W heatbed with SSR
@droftarts perfect, thank you for all of your help.
Sam
-
RE: Controling 120V 750W heatbed with SSR
@dc42 thank you for your help. Would this prusa heat bed work by being directly powered by out0 of my duet board? https://www.prusa3d.com/product/magnetic-heatbed-mk52-24v-assembly/
I'm fine with losing a few mm of build volume so long as it means simplifying my electronics setup.
Sam
-
RE: Controling 120V 750W heatbed with SSR
@dc42 @gtrider Thank you both for your help. I will heed your advice and pick a different bed heating option.
Would something like the 24V 400W Keenovo heating pad powered by my current LRS-350-24 power supply and controlled with a DC-DC SSR be a safer option? Or should I try to find a smaller bed that can be directly powered by my duet board such as the one by prusa that is 255 by 215? (I was originally looking for a build volume of closer to 280 by 280)
Sam
-
Controling 120V 750W heatbed with SSR
I am currently trying to wire my heated bed and I am not sure I have all of the correct components and I'm not sure how to wire it. I have a Keenovo heating pad 120V 750W, a meanswell SSR model number RS-25-24, and a meanswell LRS 350-24 (for my duet 3 mb6hc). Are these the correct components to power my heated bed? If yes that how exactly do I wire it? This guide: https://docs.duet3d.com/User_manual/Connecting_hardware/Heaters_bed doesn't have a wiring diagram for me to follow on it and I don't want to break anything.
Do I need any additional electronics to use this heated bed?
I would appreciate some wiring guidance along with any advice on what additional parts (if any) that I need. I apologize also if I missed an article that explains how to do this more clearly.
Sam