mini ir on duet2 wifi
-
Can you copy and paste the full config.g here?
Can you also send M122 and M98 P"config.g" and post the results?
-
This post is deleted! -
@phaedrux @phaedrux yes here ya go thanks!
CONFIG.G
; Configuration file for Duet WiFi (firmware version 3.3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Jan 10 2022 08:08:31 GMT-0600 (Central Standard Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Ender 3 Chad" ; set printer name M918 P1 E4 F2000000 ; configure direct-connect display ; Network M551 P"fsVP@Gag" ; set password M552 S1 ; enable network 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 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E420.00 ; set steps per mm M566 X900.00 Y900.00 Z24.00 E300.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 Z100.00 E5000.00 ; set accelerations (mm/s^2) M906 X800 Y800 Z800 E650 I50 ; 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 switch-type (e.g. microswitch) endstop for low end on X via pin xstop M574 Y1 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop M574 Z1 S1 P"zstop" ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin zstop ; Z-Probe M558 P1 C"zprobe.in" H5 F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height M557 X15:195 Y15:195 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 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 S200 ; set temperature limit for heater 0 to 200C 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 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S400 ; set temperature limit for heater 1 to 400C ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S1 H1 T45 ; set fan 0 value. Thermostatic control is turned on M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H T45 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency M106 P2 S1 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 are not definedM122
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later Board ID: 0JD0M-9P6M2-NW4SD-6J9DG-3S86T-KAPMM Used output buffers: 3 of 24 (22 max) === RTOS === Static ram: 23876 Dynamic ram: 79052 of which 28 recycled Never used RAM 8604, free system stack 134 words Tasks: NETWORK(ready,14.6%,233) HEAT(delaying,0.8%,314) Move(notifyWait,2.3%,321) MAIN(running,81.7%,403) IDLE(ready,0.7%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 09:12:24 ago, cause: software Last software reset at 2022-01-10 08:58, reason: User, GCodes spinning, available RAM 11492, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Step timer max interval 0 MCU temperature: min 27.2, current 28.6, max 30.1 Supply voltage: min 23.9, current 24.2, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/4/4, gc cycles 0 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: 2022-01-10 18:10:28 Cache data hit count 4294967295 Slowest loop: 7.22ms; 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 3.9ms, write time 0.0ms, max retries 0 === Move === DMs created 83, maxWait 22090037ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 2, completed moves 2, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 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: 15.43ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 2 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.25 WiFi MAC address 84:0d:8e:b3:b2:76 WiFi Vcc 3.40, reset reason Turned on by main processor WiFi flash size 4194304, free heap 18808 WiFi IP address 192.168.8.16 WiFi signal strength -62dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0M98"config.g"
FTP is disabled TELNET is disabled Error: in file macro line 63 column 13: M106: expected number after 'H'``` The error on line 63 is due to me not having a fan configured yet and I haven't yet messed around with it. Im still waiting on a blower pump for an external parts cooler fan mod. Thanks for your help! -
@andnosobabin said in mini ir on duet2 wifi:
the m558 commands. When I send m558 p1 it returns:
Error: m558: missing z probe pin namesWhen are you sending M558 P1? Why would you send that by itself anyway?
The commands in your config seem correct and produce no errors.
Have you tested the probe yet?
https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe
-
@phaedrux TBH I'm not sure what i was thinking when i sent that. I couldn't find a good guide and was jumping around and overthinking things i think. Im pretty sure the board works but im waiting on a magnetic bed instead of a pei sheet on an old ender glass plate.
When i put a sheet of paper on the bed tho and raise that to the sensor the light goes out. Does that mean its working?
Im still trying to figure out how to map the sensor to the bed too.
Thanks for your reply
-
@andnosobabin said in mini ir on duet2 wifi:
Does that mean its working?
Easiest way to check is to use the static test described in the link above.
-
@phaedrux OK I just got time to test things. Everything is working except when i run G29 i get the error: Probe already triggered before probing move started. I set the offset and everything in the link. The trigger height was 6.14 but it triggers well above that as well. like there are 2 trigger zones. Im using a flex steel sheet coated in textured pei but it happens with a sheet of paper too.
-
Are you using M558 P1 or M558 P8?
-
-
Can you try P8 instead?
-
@phaedrux Sorry for being almost a year old and reviving this post, life took over and I couldn't get around to working on this till now.
I got it working kinda 1 time. I could run G32 and G29 commands and it would probe the bed as expected but the height map was way off. I tried going back through everything I did (changing nothing) and now it wont even probe the bed it just raises and then crashes the nozzle into the bed ignoring my limit switch and gives me an error that the probe wasn't triggered during the move.
Here's the Z probe section from the config.g file
; Z-Probe M558 P8 C"zprobe.in" H5 F120 T6000 M557 X30:215 Y15:195 S20 ; define mesh grid G31 p500 X30 Y0 Z3.562Oh and I reran the M122 and M98 commands you said back in Jan and there were no errors shown.
Thanks Again
Brad -
Go through this guide to test your probe.
https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe
-
When i put a sheet of paper on the bed tho and raise that to the sensor the light goes out. Does that mean its working?
This is the reverse of what should happen, if you are using Duet3D/dc42s IR probe. What probe is this? The LED should be off when far from the bed, and light up when something is close. Also in DWC the probe value should be 0 with nothing under it and 1000 when triggered.
Check your wiring (though I’m not sure how it would work with incorrect wiring), see https://docs.duet3d.com/User_manual/Connecting_hardware/Z_probe_connecting#mini-differential-ir-sensor-by-dc42. If the probe isn’t the Duet3D probe, it might be that you need to invert the probe signal, by putting
!in the pin name, ie
M558 P8 C"!zprobe.in" H5 F120 T6000Ian
Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : TronXY X5S with Duet 3 MB6HC and Roto toolboard
-
@droftarts said in mini ir on duet2 wifi:
When i put a sheet of paper on the bed tho and raise that to the sensor the light goes out. Does that mean its working?
This is the reverse of what should happen, if you are using Duet3D/dc42s IR probe. What probe is this? The LED should be off when far from the bed, and light up when something is close. Also in DWC the probe value should be 0 with nothing under it and 1000 when triggered.
Check your wiring (though I’m not sure how it would work with incorrect wiring), see https://docs.duet3d.com/User_manual/Connecting_hardware/Z_probe_connecting#mini-differential-ir-sensor-by-dc42. If the probe isn’t the Duet3D probe, it might be that you need to invert the probe signal, by putting
!in the pin name, ie
M558 P8 C"!zprobe.in" H5 F120 T6000Ian
The following statement also does not match the IR probe of dc42...
@andnosobabin said in [mini ir on duet2 wifi]
... (it blinks when I move a piece of paper or anything on it)The dc42 IR-Probe does not "blink".
@andnosobabin
Can you post photos of the IR-Probe and its wiring on the Duet-Wifi ?DDA5X... 0.9° Stepper... Linearrails... Duet 2 Wifi... PT100 Board... Duet IR-Probe... Dyze Pro Kit up to 500°C.. etc
Thingiverse -
@phaedrux If i raise nozzle up 5 or 10mm and run the G30 S-1 command and run it it says "Error: Probe already triggered at start of probing move" if i go 20mm it runs but then triggers at 15mm above the bed and if i run G32 it probes the bed and returns:
"Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh.
110 points probed, min error 2.122, max error 3.172, mean 2.710, deviation 0.228
Height map saved to file 0:/sys/heightmap.csv"I re ran G92 Z0 and still the same issue. When i first picked this back up the other day I did all of this and it worked but the next day nothing worked
-
@droftarts I don't remember what was going on back then its not acting that way now tho it just wont trigger at a low height to calibrate it.
-
@norder I dont remember what was going on back then its not doing that now tho. I appreciate the quick reply tho!
-
@andnosobabin said in mini ir on duet2 wifi:
If i raise nozzle up 5 or 10mm and run the G30 S-1 command and run it it says "Error: Probe already triggered at start of probing move" if i go 20mm it runs but then triggers at 15mm above the bed and if i run G32 it probes the bed and returns:
It looks very much like the probe is mounted too low on the print head.
15mm too deep it seems, which can't be the case with a Duet IR probe from dc42 as it's meant to be fitted to the printhead at just 1.5mm above the print bed when the nozzle touches the print bed.However, we still do not know if the probe is really a Duet3D IR-Probe from dc42.
A photo of the probe and how it is mounted on the print head would therefore be of great help in order to be able to help you further with your problem.
At the moment there is not enough information to be able to provide specific help.When we read about a Mini IR here, in most cases we are talking about the dc42 IR, but what you write here does not fit the dc42 IR.
Google Translate
-- Original Text --Es sieht sehr danach aus, als wäre die Sonde zu tief am Druckkopf montiert.
15mm zu tief, so wie es scheint, was bei einer Duet IR-Probe von dc42 aber nicht der Fall sein kann, da sie mit nur 1,5mm über dem Druckbett an dem Druckkopf angebracht werden soll, wenn die Düse das Druckbett berührt.Wir wissen aber immer noch nicht ob es sich bei der Sonde wirklich um eine Duet3D IR-Probe von dc42 handelt.
Ein Foto der Sonde und wie sie am Druckkopf montiert ist, wäre daher eine große Hilfe um Dir bei Deinem Problem weiter helfen zu können.
Momentan reichen die Informationen nicht aus um gezielt helfen zu können.Wenn wir hier von einer Mini IR lesen, ist in den meisten Fällen von der dc42 IR die Rede, aber dass was Du hier schreibst, passt nicht zu der dc42 IR.
DDA5X... 0.9° Stepper... Linearrails... Duet 2 Wifi... PT100 Board... Duet IR-Probe... Dyze Pro Kit up to 500°C.. etc
Thingiverse -
@norder The sensor is mounted 1.5mm above the bed and the wiring seems to be correct as the sensor DOES function properly but I seem to not have the correct settings and it isnt behaving as i think it should. I will attach pictures to confirm this for you tho.
P.S. The capacitor is oriented differently because i moved it as it was in the way of a previous printhead not the current one.Thanks for your assistance!!
-
@andnosobabin
Everything seems to be fine so far.
However, I'm not the electronics expert now and have more basic knowledge than expert knowledge.
I would put the capacitor back in its original condition, since the protruding capacitor shouldn't cause any problems anymore.
For me it could be a source of error !?Here are my config.g settings of my IR-Probe.
The K0 is entered with me because I have two Z-Probes.
I kept the old BLTouch (K1) for print surfaces where the IR-Probe (K0) has problems, like glass, PEI or rough or textured surfaces.; IR-Probe M558 K0 C"zprobe.in" P3 H1.7 F120 T10000 B1 A10 S0.010 R0.4 G31 K0 P500 X0.6 Y22.3 Z3.162 ; Grid M557 X30:300 Y30:300 P9Maybe cleaning the IR-Optics will help ?
It could be that oil or grease from the linear rails got on there, or soldering grease when you were working on the print head or the IR-Probe !?Google Translate
-- Original Text --Das scheint soweit alles in Ordnung zu sein.
Allerdings bin ich jetzt nicht so der Elektronik-Experte und habe da eher ein Grundwissen als ein Expertenwissen.
Ich würde den Kondensator wieder in den Original-Zustand versetzen, da der hervorstehende Kondensator jetzt ja keine Probleme mehr bereiten sollte.
Für mich könnte es eine Fehlerquelle sein !?Hier mal meine config.g Einstellungen meines IR-Probe.
Das K0 ist bei mir mit eingetragen weil ich zwei Z-Probes habe.
Ich habe den alten BLTouch (K1) für Druckoberflächen behalten bei dem der IR-Probe (K0) Probleme hat, wie zB Glas, PEI oder raue bzw strukturierte Oberflächen.; IR-Probe M558 K0 C"zprobe.in" P3 H1.7 F120 T10000 B1 A10 S0.010 R0.4 G31 K0 P500 X0.6 Y22.3 Z3.162 ; Grid M557 X30:300 Y30:300 P9Vielleicht hilft ein reinigen der IR Optik ?
Es könnte ja sein dass dort Öl oder Fett von den Linearschienen drauf gekommen ist, oder auch Lötfett als Du am Druckkopf bzw am IR-Probe gearbeitet hast !?DDA5X... 0.9° Stepper... Linearrails... Duet 2 Wifi... PT100 Board... Duet IR-Probe... Dyze Pro Kit up to 500°C.. etc
Thingiverse
