A very very burned out ex-programmer. I try to limit my programming to keep the nightmares away (literal nightmares not the issues that always seem to pop up.
I apologize in advance if I become too aggressive or augmentative, but they do tend to sneak out when I'm in a manic swing.
Sorry everyone I wasn’t getting email notifications. I have never actually seen a ! In a command but ^ was common. The dozuki has this example M558 P9 C"^zprobe.in" H5 F100 T2000.
So ^ is pull-up regardless of value and ! Is invert. Ok.
So I’m betting that 3.0 let me use I1 but I have to use ! In 3.11
Thanks.
My Orion V2.0 on a Duet Maestro connected to an Ender 3Pro used to work fine. Red normally moving to blue when tapped. That was reflected in WebUI as 0 and 1000.
I took the printer apart and made some major changes (direct drive for my Bondtech and V6 (with the heatsink inside the bondtech), linear rails on X and Y, and dual Z with a second fine pitched screw) and then while I was restarting it I upgraded from 3.0 to 3.11.
Now no matter what gcode I use I always get backward results in the web UI. I've tried zprobe.in and ^zprobe.in as well as I1, nothing, I0, and I2 for a lark. The lights are still correct. I even had a spare orion board and switched it out and those are also correct, but no matter what settings I get 1000 and only 0 when pressing. This is nonfunctional since I can't start a probe triggered.
Here is the base gcode that the ^ and I1 are being added to with no changes in the web UI being wrong or the sensor showing the correct state.
M558 P8 C"zprobe.in" R0.5 F200 ;this has tried all kinds of tweaks
G31 X0 Y0 Z-0.1 P100 ;this is unchanged from when it worked
I've triple checked the wiring with a meter for both shorts between and within each of the three wires. I'm using the maestro zprobe port with 1 [in] = Green, [gnd] 2 = black, and 3 [3.3v] red. The piezo is connected from inner to outer as RBG (based on the print on the board that says V+ GND Sig.
Based on my understanding ^zprobe_in and zprobe_in should flip between the 0 and 1000 but they are not. Given I used two different Orion boards is something wrong with my Maestro? I did see a few posts where people say they had to switch ground and signal different from the documentation.
@droftarts said in E0 Thermistor faults:
Where are you seeing this? Because this is the configuration for the Ender 3 Pro for the RRF config tool: https://raw.githubusercontent.com/chrishamm/configtool/master/public/machines/ender3pro.json
It sets both thermistors to "thermistor":100000,"beta":4092
It uses the same template for RRF2 and RRF3.Ian
You are right I zipped through it just now. Sorry.
I found the source of the other number and what happened. I didn't use the defaults because the guide I was using said not to. I used my value of 10k for the bed heater's thermistor because it's aftermarket (GCR silicone with a new aluminum plate for better levelness [Part of why I liked the idea of using a Duet product - higher heated bed current support]), but according to the Dozuki site
Set the values for both Thermistor values as: R25 – 98801, B – 4185, R – 2200
Unfortunately for me I must have missed the 1 or typed a ` insead. That 98801 does match the github for Ender 3 Pro. So I have different value than template because I used guide and it didn't work because I mistyped. So yes, this was doubly my mistake. I make typos like that entirely too often, but usually autocorrect, triple checking posts, or something catches them for me.
Sorry again, and thank you to everyone for helping me find the issue regardless of where it came from.
@Danal said in E0 Thermistor faults:
-231 indicates an "open" circuit, nothing plugged in.
Please post your complete config.g, and a photo of where that sensor is plugged into the board.
I'm not sure you really should be asking people for complete config.g files. The password is stored plain text. It'd be stupid to expose a printer to the internet, but still that data should prolly be kept private.
The wiring diagram is actually off here as is shown in this zoomed pictures. The cluster of E0, E1, and Enclosure are not beside the stops, but rather behind the zstop.
E0 Thermistor highlighted in green and yellow. Right now it is in the open air just to rule out a short with the microswiss.
This is still mostly the autogenerated file and I expect most of it will need tweaking. But I haven't been able to heat the hotend enough to do the final tighter on my new all metal head, so I was focusing on heat first.
; Configuration file for Duet Maestro (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Mon Mar 30 2020 11:15:43 GMT-0400 (Eastern Daylight Time)
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Ender 3 Pro - Duet Maestro" ; set printer name
; Network
M551 P"12345678" ; this isn't my password for the duet, it the password for my luggage
M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet
; Drives
M569 P0 S0 ; physical drive 0 goes backwards
M569 P1 S0 ; physical drive 1 goes backwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S0 ; physical drive 3 goes backwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E128 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E741.00 ; set steps per mm
M566 X600.00 Y600.00 Z60.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z180.00 E6000.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z120.00 E5000.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E900 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X235 Y235 Z260 S0 ; set axis maxima
; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z
; Z-Probe
M950 S0 C"zprobe.mod" ; create servo pin 0 for BLTouch
M558 P9 C"zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X10:220 Y10:220 S20 ; define mesh grid
; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4092 ; 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 S150 ; set temperature limit for heater 0 to 150C
M307 H0 B1 S1.00 ; enable 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" T9880 B4185 ; 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 S275 ; set temperature limit for heater 1 to 275C
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
; Fans
M950 F0 C"fan0" Q20 ; 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" Q20 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on
; Tools
M563 P0 S"HotEnd" 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
; Miscellaneous
M501 ; load saved parameters from non-volatile memory
M911 S21 R23 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
T0 ; select first tool
EDIT: It works now. The autogen wizard has a typo that left off the 1 from 98801. That most likely is the issue, but it is unlikely but also possible that I had an unfortunately tremor/twitch in that field (<sarcasm>I just love my meds, side effects and all</sarcasm>).
EDIT to EDIT: Oh, yeah. Thanks everyone - especially for calling out that low number that made me check the git hub ender 3 pro baseline.
@DIY-O-Sphere said in E0 Thermistor faults:
@LostJen said in E0 Thermistor faults:
T9880
Never seen such a low value...could be T100000 but depends on the thermistor
It was autogenerated for the Ender 3 Pro. However looking at the github version (2.x firmware) it appears there is a 1 missing from the end. Perhaps a minor typo in the config file generator for V3 firmware?
Duet Web Control 2.0.4
Board: Duet Maestro 1.0
Firmware: RepRapFirmware for Duet 2 Maestro 3.0 (2020-01-03b3)
Thermistor for E0 constantly shows -231. Bed thermistor is ok. I've tried two different thermistors in the e0 slot and neither work even in open air. As a final test I used my known good bed thermistor (still hooked to the bed header) and it still shows bad. The next power on after I put that back shows it giving good measurements agani. This clearly shows it isn't the devices. Here is the G code for those two devices.
The e0 thermistor and spare were stock Ender 3 Pro. The bed heater is a NTC 3950 100K Thermistor.
; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4092 ; 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 S150 ; set temperature limit for heater 0 to 150C
M307 H0 B1 S1.00 ; enable 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" T9880 B4185 ; 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 S275 ; set temperature limit for heater 1 to 275C
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
Where do I go next. I specifically paid more this time around for a non-Chinese POS so I didn't have to deal with headers backward and pins mislabeled.