Help with inductive NPN probe stuck at 1000
-
I am trying to get a inductive z probe set up however it reads 1000 on the web interface and when trying to home is says "Error no z probe" I followed the wiki guide "https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe" and directly wired it to the z probe input. I triple checked the wired and they are all connected and working with a multimeter. Ive tried going through dozens of posts online and each one says something completely different to another and cant find any tutorial on what exactly I need to have in my config.g for this to work.
Can someone please help a idiot like me and tell me exactly what I need to do to get this working. I have been on this board for over 2 months now trouble shooting all the issues its been giving me. I am pretty disappointed though with this last problem I hope I can finally have a fully functional setup.
; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.1.4 on Sat Oct 03 2020 10:18:18 GMT-0400 (Eastern Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"My Printer" ; set printer name ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; 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 M584 X0 Y1 Z2 E3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E220.00 ; set steps per mm M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2) M906 X1500 Y1500 Z1000 E1500 ; set motor currents (mA) M84 S0 ; Disable motor idle current reduction ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X230 Y210 Z200 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 M574 Z0 P"nil" M558 P5 C"zstop" H5 F120 T3000 ; set Z probe type to switch and the dive height + speeds ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; 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 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 M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; 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 M307 H1 B0 S1.00 ; 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 ; 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 are not defined M307 H0 A100 ; Heater Bed Temp Setting to avoid heating too slow error M143 H1 S420 ; extruder max temp
-
@rowow said in Help with inductive NPN probe stuck at 1000:
; Z-Probe M574 Z0 P"nil" M558 P5 C"zstop" H5 F120 T3000 ; set Z probe type to switch and the dive height + speeds
Remove the M574 Z0 P"nil"
Are you wired to the zprobe connection or to Zstop pin?
You're also missing a G31 command.
Can you post your homeall?
Also post the results of M122 and M98 P"config.g".
-
I wired it directly as the wiki stated without the diode to the z probe connection. please see the attached photo for clarification
What do I need to put in for the G31 command
homeall.g
; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v3.1.4 on Sat Oct 03 2020 10:18:18 GMT-0400 (Eastern Daylight Time) G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-235 Y-215 F1800 ; move quickly to X and Y axis endstops and stop there (first pass) G1 H2 X5 Y5 F6000 ; go back a few mm G1 H1 X-235 Y-215 F360 ; move slowly to X and Y axis endstops once more (second pass) G90 ; absolute positioning G1 X15 Y15 F6000 ; go to first bed probe point and home Z G30 ; home Z by probing the bed ; Uncomment the following lines to lift Z after probing ;G91 ; relative positioning ;G1 Z5 F100 ; lift Z relative to current position ;G90 ; absolute positioning
Results of M122 and M98:
5:00:20 PMM98 P"config.g" HTTP is enabled on port 80 FTP is disabled TELNET is disabled Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C 5:00:08 PMM98 ![Captddure.PNG](/assets/uploads/files/1607637956781-captddure.png) 4:59:59 PMM122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2-beta1 running on Duet WiFi 1.02 or later Board ID: 0JD0M-9K662-MGPSN-6J1D6-3S86N-KAX6Z Used output buffers: 3 of 24 (6 max) === RTOS === Static ram: 23916 Dynamic ram: 98916 of which 44 recycled Exception stack ram used: 256 Never used ram: 7940 Tasks: NETWORK(ready,221) HEAT(blocked,308) MAIN(running,456) IDLE(ready,20) Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:07:55 ago, cause: power up Last software reset at 2020-12-09 17:14, reason: User, GCodes spinning, available RAM 7924, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN Error status: 0x020 MCU temperature: min 21.9, current 24.4, max 24.9 Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: position 0, standstill, SG min/max not available Driver 1: position 0, standstill, SG min/max not available Driver 2: position 0, standstill, SG min/max not available Driver 3: position 0, standstill, SG min/max not available Driver 4: position 0, standstill, SG min/max not available Driver 5: position 0 Driver 6: position 0 Driver 7: position 0 Driver 8: position 0 Driver 9: position 0 Driver 10: position 0 Driver 11: position 0 Date/time: 2020-12-10 16:59:58 Cache data hit count 838659451 Slowest loop: 6.57ms; fastest: 0.15ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 1.4ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Movement lock held by 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 14.24ms; fastest: 0.00ms Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.21 WiFi MAC address f4:cf:a2:69:53:26 WiFi Vcc 3.36, reset reason Turned on by main processor WiFi flash size 4194304, free heap 15616 WiFi IP address 192.168.1.132 WiFi signal strength -50dBm, reconnections 0, sleep mode modem Clock register ffffffff Socket states: 4 0 0 0 0 0 0 0
-
No diode though as the wikipedia states it doesnt need one for my board version
"Duet 3, Duet 2 Maestro, or revision 1.04 or later of Duet 2 WiFi or Duet 2 Ethernet: you can connect the output of the sensor directly to the Z-probe IN pin." -
@rowow said in Help with inductive NPN probe stuck at 1000:
M558 P5 C"zstop" H5 F120 T3000
Well if you're wired to the z probe connector, you shouldn't have zstop as the pin name, you should have zprobe.
@rowow said in Help with inductive NPN probe stuck at 1000:
version 3.2-beta1
If you're wanting to run the beta releases you should probably update to 3.2 beta 4.1, or revert back to the stable release 3.1.1.
@rowow said in Help with inductive NPN probe stuck at 1000:
G1 X15 Y15 F6000 ; go to first bed probe point and home Z G30 ; home Z by probing the bed
You should probably change the X15 Y15 to position the probe at the center of the bed.
@rowow said in Help with inductive NPN probe stuck at 1000:
What do I need to put in for the G31 command
https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_G31_Set_or_Report_Current_Probe_status
The configurator produces this when a switch style probe is selected.
; Z-Probe M558 P5 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to switch and the dive height + speeds G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height M557 X15:215 Y15:195 S20 ; define mesh grid
For the G31 X Y Z offsets you'll need to measure.
https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe
-
Thank you, adding the following code has allowed the Z probe to start working. When the induction probe is in front of metal it reads 0 when not it reads 1000.
However now when trying to home the Z axis it says "error z probe already triggered"
-
In that case you will need to invert the signal by adding a
!
to the start of the pin name, like this.M558 P5 C"^!zprobe.in"
-
@Phaedrux Thank you so much! It finally works. Would be nice if they had all this simply on the wiki. Is there any proper place I can search for information or is the forums the only place. I think thats all for now but in the future it would be nice to have a up to date source of information.
-
@rowow Well you can image how many random probes are out there, so how exactly they work with the firmware varies quite a bit, making exact documentation for every single device out there impossible.
-
@rowow said in Help with inductive NPN probe stuck at 1000:
@Phaedrux Thank you so much! It finally works. Would be nice if they had all this simply on the wiki. Is there any proper place I can search for information or is the forums the only place. I think thats all for now but in the future it would be nice to have a up to date source of information.
It's already covered at the end of https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_NPN_output_normally_open_inductive_or_capacitive_sensor but some examples would make it clearer.