Hmm, I thought that was what the P103 was for (I'm still learning RRF). My thermistor is on the Duex5 "E2_Thermistor3" pins so would I need to add an X-command in that line like this:
M305 S"Bed Heater" P103 X3 R4700 T100000 B4725 ..........; thermistor inside the Keenovo heater
Edit: That fixed it! The bed heater now shows up under + Extra.
Thanks you so much for the help!
Certainly, I got this config from another user that has the same machine and have tweaked it to make it work for me. Mine does not have a PanelDue but I didn't think the code in there would affect anything (it's a Core XY machine):
; Configuration file for Duet WiFi (firmware version 2.03 or newer)
; executed by the firmware on start-up
; General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like Marlin
M575 P1 B57600 S1 ; Comms parameters for PanelDue
M564 S1 H1 ; Forbid axis movements when not homed
; General setup
M667 S1 ; Select CoreXY mode (2.03RC1 and below)
M669 K1 ; Select CoreXY mode (2.03 and up)
; Network
M550 Voron ; Set machine name
M552 S1 ; Enable network
M586 P0 S1 ; Enable HTTP (for DWC)
M586 P1 S1 ; Enable FTP (for remote backups)
M586 P2 S0 ; Disable Telnet
; --- drive map ---
; _______
; | 6 | 7 |
; | -------|
; | 5 | 8 |
; -------
; front
; Drive directions
M569 P0 S1 ; A
M569 P1 S1 ; B
M569 P3 S1 ; Extruder #1
M569 P4 S0 ; Extruder #2
M569 P5 S0 ; Z1
M569 P6 S1 ; Z2
M569 P7 S0 ; Z3
M569 P8 S1 ; Z4
; Motor mapping and steps per mm
M584 X0 Y1 Z5:6:7:8 E3:4
M350 X16 Y16 Z16 E16:16 I1 ; Use 1/16 microstepping with interpolation everywhere
M92 X80 Y80 Z400 ; Set XYZ steps per mm (1.8deg motors)
;M92 X160 Y160 Z800 ; Set XYZ steps per mm (0.9deg motors)
M92 E560:560 ; Set Extruder steps per mm (Mobius 3)
;M350 Z16 I0 ; disable Z interpolation
; Drive currents
M906 X1200 Y1200 Z1200 E1000 ; XYZ and E current
M906 I30 ; Idle current percentage
M84 S120 ; Idle timeout
; Endstops
M574 X2 Y2 Z0 S1 ; Set NC endstops for X and Y, no Z endstop (we have multiple probes instead)
M208 X0.1 Y0.1 Z0 S1 ; Set axis minima
M208 X299.8 Y309 Z275 S0 ; Set axis maxima
; Bed leveling
M671 X-65:-65:365:365 Y-20:380:380:-20 S20 ; Define Z belts locations (Front_Left, Back_Left, Back_Right, Front_Right)
M557 X25:275 Y25:275 S25 ; Define bed mesh grid (inductive probe, positions include the Z offset!)
;M557 X25:275 Y25:275 S50 ; Define bed mesh grid (bed piezo)
; Accelerations and speed
M98 P"/macros/print_scripts/speed_printing.g"
; Bed Heater
;M305 P0 R4700 T100000 B3950 ; Set thermistor + ADC parameters for heater 0
;M307 H0 A90.0 C700.0 D10.0 S1.00 B1 ; Bang-bang bed
;M143 H0 S110 ; Set temperature limit for bed heater to 110C
; Bed heater, dual thermistor setup (one for the heater + one for the bed)
M305 S"Bed Plate" P0 R4700 T100000 B4725 ; Stud thermistor on the edge of the plate
M307 H0 B1 S1 ; 100% PWM, bang-bang mode
M305 S"Bed Heater" P3 R4700 T100000 B4725 ; thermistor inside the Keenovo heater
M143 P100 H0 X3 A2 C0 S110 ; make sure silicone heater stays below 110°C
M143 P101 H0 X3 A1 C0 S125 ; make sure silicone heater shuts down at 125°C
M143 H0 S110 ; maximum bed temperature
; Hotend #1 heater
M305 S"Nozzle" P1 X501 R4700 ; Set thermistor Configure PT1000 for heater 1
M143 H1 S300 ; Set temperature limit for heater 1 to 300C
; Hotend #1 heater
; M307 values are for reference only, RRF stores them in config-override.g via M500 after a PID calibration.
;M305 P1 R4700 T100000 B4725 C0.0000000706 ; Set thermistor + ADC parameters for heater 1
;M307 H1 A454.1 C235.9 D4.5 S1.00 B0 ; 104GT2 PID, 30W heater
; Chamber temperature sensor via temperature daughterboard pins on Duex
;M305 S"Ambient" P104 X405 T21 ; Set DHT21 for chamber temp
;M305 S"Humidity [%]" P105 X455 T21 ; Set DHT21 for chamber humidity
; Disable unused heaters (so they are hidden on the PanelDue)
M307 H2 A-1 C-1 D-1
;M307 H3 A-1 C-1 D-1
M307 H4 A-1 C-1 D-1
M307 H5 A-1 C-1 D-1
M307 H6 A-1 C-1 D-1
M307 H7 A-1 C-1 D-1
; Select inductive Z probe on powerup
M98 P"/macros/print_scripts/activate_z_probe.g"
; Fans
M106 P8 S1 I0 H1 T50 ; E3D V6 Hotend fan, turns on if temperature sensor 1 reaches 50 degrees
M106 P7 S0 I0 H-1 ; Part cooling fan, no thermostatic control
M106 P6 T45:65 F50 H100:101:102 ; Electronics bay fan, turn on gradually if MCU is over 45C or any TMC driver is over temp
M106 P5 S1 H0 T50 ; Chamber filter fan, turn on when bed is hotter than 50C
M106 P2 S1 I0 H1 T50 ; LED, turns on if temperature sensor 1 reaches 50 degrees
; Tools
M563 P0 D0 H1 F4 ; Define tool 0, use fan #4 for M106
G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
; Pressure advance
M572 D0 S0.2
M501 ; load config-override.g
T0 ; select tool 0
@Phaedrux Thanks and Wow! That new look is going to take a little to get used to! That upgrade alone didn't change the tool setting to allow me to see my other thermistor but I'll take some more time to look through the code. I'm sure it's something I'm just not seeing.
It's interesting, found this while trying different things. I went into settings and then over to the tool tab and I can add another heater and it shows up fine in my tools however it's gone as soon as I reboot DWC, I don't see 2.07 available here: link text what changes would I need to make to go to RRF 3?
@Phaedrux said in Heater Error with Dual Thermistors:
What firmware version and DWC are you using?
I just updated the firmware to the latest stable release 2.05.1 and that didn't make a difference, DWC is at 1.22.6
I did change the following (bold) in the code below and I'm not getting the error but still cannot see the other heater in the tools or the chart so not sure if it's working:
M305 S"Bed Heater" P3 R4700 T100000 B3950........; Beta3950 thermistor inside the Keenovo heater
M143 P100 H0 X3 A2 C0 S110......................................; make sure silicone heater stays below 110°C
M143 P101 H0 X3 A1 C0 S125......................................; make sure silicone heater shuts down at 125°C
M143 H0 S110.....................................................................; maximum bed temperature
@jens55 said in Heater Error with Dual Thermistors:
@p40whk said in Heater Error with Dual Thermistors:
The Duet Web Control only shows the "Bed plate" and not the "Bed Heater" so not sure how to get that to display either:
click on '+Extra' and you should see the bed heater listed. If you want it graphed there is a checkbox for that
Extra only shows me this:
Selecting "Show in chart" doesn't actually show the heater under "Tools" or "Heater" (it's the same as my image above) but does add the MCU temps a dashed line in the chart, it's almost as if it doesn't recognize the second bed thermistor:
I'm still struggling with the errors though. Can't do anything with bed heat as it stands now.
Hi,
I keep getting a "Temperature reading error on heater 103" when I try to turn the bed Plate to Active.
My setup is a thermistor inserted directly into the edge of the heat bed (it's a spare E3D V6 thermistor hooked into the Thermistor0 location) and I have the thermistor from the Keenovo heater hooked up to my Duex5 at the "E2_Thermistor3" pins. Not sure if I have that addressed right in the Config file but I've tried a few variations and still get the error,
Here's the way my config.g is set now:
; Bed heater, dual thermistor setup (one for the heater + one for the bed)
M305 S"Bed Plate" P0 R4700 T100000 B4725 ..............; Stud thermistor on the edge of the plate
M307 H0 B1 S1 ..................................................................; 100% PWM, bang-bang mode
M305 S"Bed Heater" P103 R4700 T100000 B3950........; Beta3950 thermistor inside the Keenovo heater
M143 P100 H0 X103 A2 C0 S110......................................; make sure silicone heater stays below 110°C
M143 P101 H0 X103 A1 C0 S125......................................; make sure silicone heater shuts down at 125°C
M143 H0 S110.....................................................................; maximum bed temperature
The periods are just in there to make it easier to read her on the forum they are not in my config file.
The Duet Web Control only shows the "Bed plate" and not the "Bed Heater" so not sure how to get that to display either:
I suppose I could do without monitoring the actual heater (I like using the build plate thermistor for more accurate temp readings) but it would be nice to use both. Any help would be appreciate.
Thanks
@Phaedrux said in Heater Fault problems:
@p40whk said in Heater Fault problems:
The terminals on my Duet seem to be a little loose
What exactly do you mean by this?
Well, you can wiggle them with your finger as if the solder joints aren't solid.
However, I think I have found the issue. I took a Multimeter to the terminals as it was heating and got a consistent voltage so I ruled that out. Happened to have a spare thermistor for a hotend and clamped that to the bed to see if that was the iss. That was it. no issues with heater faults and the graph on the temp panel is smooth as silk.
Been having trouble with heater faults on my bed lately and not sure what steps to take next. Temp vs Time map is erratic when heating but seems to stabilize at around 90c (if it gets there before faulting). I have checked the wiring, re-crimped the terminals, and checked their connections and this hasn't done a thing.
The terminals on my Duet seem to be a little loose however I am not sure that is the issue given that the erratic temps go away after it reaches temp.
I have a Keenovo silicone heater and the thermister is built into the heater so not sure how I would replace it short of drilling a hole in the aluminum build plate and putting a new one there.
I have access to the bottom of the heat bed while it is heating and using a piece of metal to "massage" the area where the thermister is (checking for a loose connection) does not change the erratic behavior.
Any suggestions of what to try next would be appreciated.
Thanks dc42, I went back in and did the reassignment of the drives and it seems to be working however I could not get the X or Y axis to home. It was late and I was falling asleep so I didn't get a chance to troubleshoot.
I did use a multimeter and checked the resistance of motor pairs and that wasn't an issue, and my M350 and M906 commands do come after the M584.
Just need to figure out why the X an Y axis won't home and I'll be happy. Using the procedure linked above, X and Y both move in the correct directions but there must be something wrong with my Home files preventing them from working right.
Thanks Deckingham, I did not realize I had to assign the unused drivers.
The reason I was not using 1-3 was more of a location and wire routing decision. Most of the stepper motors are close to the Duex5 so I have shorter wire runs and cleaner wiring. I also planto add additional extruders in the future so I will use those at a later time.
I did put a meter on my motors and verify that they are wired right, I also ran the check stepper motor test here [https://duet3d.dozuki.com/Wiki/Choosing_and_connecting_stepper_motors#Section_Checking_connected_stepper_motors](link url) And it is definitely the Z motors that are giving me the trouble.
I try assigning the other motors and see what that does,
I've got a Duex5 connected to my Duet WiFi2 and am using Drive 5 and 9 for my X and Y motors and drives 6,7,and 8 for a three leadscrew Z-axis on the Duex5. Everytime I try to home either axis using home all or individually the Z-Axis moves (only drive 7) and I get no movement out of my other drives.
This is how they are setup in my config.g:
; Drives
M569 P0 S1 ; Physical drive 0 goes forwards
M569 P1 S1 ; Physical drive 1 goes forwards
M569 P2 S1 ; Physical drive 2 goes forwards
M569 P3 S1 ; Physical drive 3 goes forwards
M569 P4 S1 ; Physical drive 4 goes forwards (Extruder)
M569 P5 S1 ; Physical drive 5 goes forwards (Y-Axis)
M569 P6 S0 ; Physical drive 6 goes backwards (Z-Axis)
M569 P7 S0 ; Physical drive 7 goes backwards (Z-Axis)
M569 P8 S0 ; Physical drive 8 goes backwards (Z-Axis)
M569 P9 S1 ; Physical drive 9 goes forwards (X-Axis)
M584 X9 Y5 Z6:7:8 E4 ; Three Z motors connected to driver outputs 6,7,8 Drive 5 controls X, Drive 9 Controls Y, Drive 4 controls E
; Motor order: Left (1), Right (2)
I am also getting the following error:
Warning: motor phase A may be disconnected reported by driver(s) 6 7 8
Warning: motor phase B may be disconnected reported by driver(s) 6 7 8
I am using the standard cables that came with the steppers so not sure if the wiring is correct for the Duet as I haven't put a meter on them.
Just wondering where I should begin troubleshooting as I'm not sure what is causing this, any help would be appreciated,
Thanks
I'm setting up a new printer with the Duex5 and have a fan I want to run all the time on the stepper drivers. My Duex mount has a provision for a fan next to the "Internal 12V" pins and I am powering the board as specified in the instructions from my duet wifi with 24 volts.
As configured, I do not get any power from these pins, do I need to add the jumper for them to work or do I have a faulty board? I commissioned the board before adding full power and everything seemed to be okay so not sure why there is no power to these pins (as tested with a meter).
Any help would be appreciated.
Thanks!
As many times as I was on that wiki page I never scrolled down far enough to see the "Connecting 4 wire fans" instructions!" I'll admit I'm a bit embarrassed but thank you for helping me out!
I've read through quite a few Fan wiring threads and I seem to confuse myself the more I think about this.
I'm running a 24V PSU with a 24V-12V DC-DC Converter but not sure which pins to wire the PWM and Speed Signal to. I'm guessing that the RPM Speed Signal goes to the V_FAN Input and the PWM (+5V) Signal goes to the FAN0-?
I've attached a wiring diagram of what I'm thinking is right. Can someone please confirm or correct me if this is wrong?
Here's a quick video of the end of the first print and start of the second print.
@jasperkm said in Mid Air Prints unless I Restart:
@p40whk could you check if there is a G10 command at the end of the .gcode file that you're running? (just before the end gcodes will run)
0_1550429099237_3030_filament_guide_v2.gcode
I've attached the file I'm currently printing. Checked a few others as well and there is no G10 command present.
@phaedrux said in Mid Air Prints unless I Restart:
@p40whk said in Mid Air Prints unless I Restart:
@randomfactoid said in Mid Air Prints unless I Restart:
@p40whk what values does M207 return ?
I'm in the middle of a print right now, where/when would I use the M207 command?
M207 sets the parameters for firmware retraction. If you haven't set it up in the slicer to use it, it won't tell you anything. If you were using it, you'd know.
That's kind of what I thought, it's not set up in my slicing program.
I'm waiting for the first print to be done and I'll take a video of what it does when I go to print a new print.
@randomfactoid said in Mid Air Prints unless I Restart:
@p40whk what values does M207 return ?
I'm in the middle of a print right now, where/when would I use the M207 command?
@randomfactoid So I just checked and don't have G10 anywhere in my code and am not using M207 yet I still have this issue. So, my problem even though related does not seem to be the same.