Heat chamber configation
-
@qdeathstar e2temp should work. Can you try duex.e2temp just in case?
-
@t3p3tony Neither one of those seems to work. I even tried to comment out the lines in the config and run them on the console in case the config file was explaining the "pin not available" issue. The other thing is, how does it know that "e2temp" is pin 35? Is it automatically assigned?
8:05:54 AMM308 S2 P"duex.e2temp" Y"thermistor" T100000 A45.7 C917.2 D32.7 Error: M308: Pin 'duex.e2temp' is not free 8:05:39 AMM308 S2 P"deux.e2temp" Y"thermistor" T100000 A45.7 C917.2 D32.7 Error: M308: Unknown pin name 'deux.e2temp' 8:04:40 AMM308 S2 P"e2temp" Y"thermistor" T100000 A45.7 C917.2 D32.7 Error: M308: Pin 'e2temp' is not free 8:04:23 AMM308 S2 P"e2temp" Y"thermistor" T100000 A45.7 C917.2 D32.7 Error: M308: expected string expression 8:02:45 AMM112 M999 8:02:44 AMConnection established! 8:02:32 AMConnection established! 8:02:32 AMPage Load complete! -
@qdeathstar the problem is an error on your M308 line, coupled with less than perfect error handling in RRF. The line you have is:
M308 S2 P"e2temp" Y"thermistor" T100000 A45.7 C917.2 D32.7 ; configure sensor 2 as thermistor on pin e1temp
Parameter A45.7 doesn't make sense, because the A parameter is the sensor name, so it should be a string. The first time I run this command, it reports this:
02/12/2021, 16:38:16 M308 S2 P"e2temp" Y"thermistor" T100000 A45.7 C917.2 D32.7 ; configure sensor 2 as thermistor on pin e1temp Error: M308: expected string expressionHowever, even though the command fails, by the time it detects the error is had already allocated the pin. So if you run the command again, it reports that the pin is not free.
I will look at improving this error handling in the next RRF 3.4beta.
-
You can see a list of all valid pin names here: https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Pin_names
You can't use exp.35 and duex.e2temp at the same time since they are the same pin.
@qdeathstar said in Heat chamber configation:
WiFi firmware version 1.21
It looks like when you updated the firmware not everything was updated. I suggest you upload the full 3.3 zip file as is, don't extract it first, to the system tab in DWC to get everything up to date.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
@qdeathstar said in Heat chamber configation:
M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED
I don't think you're able to define the mac address for the wifi module.
Note on the Duet 2 Wifi the MAC address is unique and set on the Wifi Module so this command has no effect.
@qdeathstar said in Heat chamber configation:
Error: Missing Z probe pin name(s)
The probe definition in your config is using the RRF2 syntax. It will need to be updated for RRF3.
https://duet3d.dozuki.com/Wiki/M558 -
Yes, I was in the process of making the coversion. Everything is different but it seemed like any change I made didn’t affect anything so I was kinda stuck. With what dc42 said though it makes sense. The A was one of the old variables from PID tuning in the previous version.
When I try to update The WiFi server, after I upload the file via the web control panel it says it can’t find the file, so I put that problem on the back burner.
-
@qdeathstar said in Heat chamber configation:
When I try to update The WiFi server, after I upload the file via the web control panel it says it can’t find the file, so I put that problem on the back burner.
Did you upload the full zip file? What file did it was was missing?
In 3.3 there is a new firmwares folder and it may be expecting some files to be present there that aren't actually there yet. Usually uploading the full zip file again is enough, but you may have to manually place the file it's missing where it expects it to be.
-
@phaedrux I was only trying to upload the webserver.bin file, after i uploaded the entire folder it still doesnt update. It reports:
M997 S0:1 Error: M997: File 0:/firmware/DuetWiFiServer.bin not foundOk, so i think i have everything figured out but the z-probe. At first, the bltouch would not deploy. Then i added the lines for the updated way of setting up a BL touch and then the bl touch deployed, but it will not retract or respond to any M280 commands, though when i send them it doesnt report any errors.
My M98 P"config.g" comes back clean and i have reported config.g and M122 below
M669 K1; M111 S0; M552 S1; M555 P2 ; Set output to look like Marlin M575 P1 B57600 S1 ; Comms parameters for PanelDue G21 ; Work in millimetres G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves ; Axis and motor configuration M569 P0 S0 ; Drive 0 goes backwards M569 P1 S1 ; Drive 1 goes forwards M569 P2 S0 ; Drive 2 goes backwards M569 P3 S1 ; Drive 3 goes forwards M584 X0 Y1 Z2 E3 M574 X1 S1 P"!^xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop M574 Y2 S1 P"!^ystop" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin ystop M574 Z1 S2 M667 S1 M350 X16 Y16 E16 I1 ; Set 16x microstepping with interpolation M92 X53.3 Y53.3 Z1500 E919.8 ;773 ; Set axis steps/mm M906 X1700 Y1700 Z2300 E1200 I60 ; Set motor currents (mA) and increase idle current to 60% M201 X1000 Y1000 Z100 E1000 ; Accelerations (mm/s^2) M203 X10000 Y10000 Z500 E3600 ; Maximum speeds (mm/min) M566 X300 Y300 Z200 E1201 ; Maximum instant speed changes mm/minute ; z Probe M558 P9 C"^zprobe.in" H5 F300 T3000 ; BLTouch connected to Z probe IN pin, free up MOD pin M950 S0 C"!^exp.heater4" ; M308 S0 P"bedtemp" Y"thermistor" T100000; 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 R0.441 C363.5 D1.73 S1.00 V12.0 ; 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 ; configure sensor 1 as thermistor on pin e0temp M950 H2 C"e1heat" T1 ; create nozzle heater output on e1heat and map it to sensor 1 M307 H2 B0 R1.535 C232.7 D6.00 S1.00 V12.0; disable bang-bang mode for heater and set PWM limit M143 H2 S280 ; set temperature limit for heater 2 to 280C M308 S2 P"e2temp" Y"thermistor" T100000 ; configure sensor 2 as thermistor on pin e1temp M950 H3 C"!^exp.heater3" T2 ; create chamber heater output on e1heat and map it to sensor 2 M307 H3 B1 S1.00 ; enable bang-bang mode for the chamber heater and set PWM limit M141 H3 ; map chamber to heater 2 M143 H3 S280 ; set temperature limit for heater 2 to 280C ; Fans M950 F0 C"fan0" ; create fan 0 on pin fan0 and set its frequency M106 P0 T45 S1 H1 ; set fan 0 value. Thermostatic control is turned off ; Tools M563 P0 D0 H2 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 ;lights M950 P0 C"exp.heater6" G31 X18 Y32.2 Z1.55 M671 X0:380:142.5 Y155:155:300 P0.8 M557 X10:360 Y10:300 S40 M208 S0 X360 Y345 Z320 M208 S1 Z-.20 ; set minimum Z T0 ; select first hot endM122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.0 or 1.01 Board ID: 08DAM-999TL-MQ4S4-6JKF6-3S86P-T4GVZ Used output buffers: 3 of 24 (6 max) === RTOS === Static ram: 23876 Dynamic ram: 75212 of which 0 recycled Never used RAM 15328, free system stack 190 words Tasks: NETWORK(ready,14.0%,237) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,340) MAIN(running,85.3%,467) IDLE(ready,0.6%,29), total 100.0% Owned mutexes: === Platform === Last reset 00:06:04 ago, cause: software Last software reset at 2021-12-03 01:05, reason: User, GCodes spinning, available RAM 15360, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 29.2, current 30.4, max 31.1 Supply voltage: min 1.2, current 1.3, max 1.4, under voltage events: 0, over voltage events: 0, power good: no Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Driver 0: position 0, ok, SG min/max not available Driver 1: position 0, ok, SG min/max not available Driver 2: position 0, ok, SG min/max not available Driver 3: position 0, ok, SG min/max not available Driver 4: position 0, ok, 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: 2021-12-03 01:11:13 Cache data hit count 4294967295 Slowest loop: 539.10ms; fastest: 0.12ms 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 4.2ms, write time 45.9ms, max retries 0 === Move === DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed moves 0, 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 = 3 -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: 539.28ms; 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 5c:cf:7f:2c:27:af WiFi Vcc 3.38, reset reason Turned on by main processor WiFi flash size 4194304, free heap 15056 WiFi IP address 192.168.1.250 WiFi signal strength -76dBm, mode none, reconnections 0, sleep mode modem Clock register ffffffff Socket states: 0 0 0 0 0 0 0 0 -
Here is an example config from the config tool for you to compare against.
; 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 Fri Dec 03 2021 12:46:33 GMT-0600 (Central Standard Time) ; General preferences M575 P1 S1 B57600 ; enable support for PanelDue 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 E420.00 ; set steps per mm M566 X900.00 Y900.00 Z60.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 X800 Y800 Z800 E800 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 X230 Y210 Z200 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 S2 ; configure Z-probe endstop for low end on Z ; Z-Probe M950 S0 C"exp.heater3" ; 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 X15:215 Y15:195 S20 ; define mesh grid ; 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 B0 S1.00 ; disable 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 M143 H1 S280 ; set temperature limit for heater 1 to 280C M308 S2 P"e1temp" Y"thermistor" T100000 B4138 ; configure sensor 2 as thermistor on pin e1temp M950 H2 C"e1heat" T2 ; create chamber heater output on e1heat and map it to sensor 2 M307 H2 B0 S1.00 ; disable bang-bang mode for the chamber heater and set PWM limit M141 H2 ; map chamber to heater 2 M143 H2 S280 ; set temperature limit for heater 2 to 280C ; 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:2 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 ; Miscellaneous M501 ; load saved parameters from non-volatile memory T0 ; select first tool -
@qdeathstar said in Heat chamber configation:
Error: M997: File 0:/firmware/DuetWiFiServer.bin not found
When you go to the system tab in DWC, there is a folder selector above the file listing. You can switch between the system folder and firmware folder. Switch to the firmware folder and then upload the full 3.3 zip file, as is, don't extract it first. That should hopefully get the files in the correct location.
-
@phaedrux Thank you.
I was able to get it updated after trying again.
However the BL touch is still an issue. I think i have it just like your example but it still not working, (responding to M401 or M402). I would think that means it is a wiring issue, but it was working fine previously and none of the wiring has changed. I have my config.g and deploy and retract files below.
M669 K1; M111 S0; M552 S1; M555 P2 ; Set output to look like Marlin M575 P1 B57600 S1 ; Comms parameters for PanelDue G21 ; Work in millimetres G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves ; Axis and motor configuration M569 P0 S0 ; Drive 0 goes backwards M569 P1 S1 ; Drive 1 goes forwards M569 P2 S0 ; Drive 2 goes backwards M569 P3 S1 ; Drive 3 goes forwards M584 X0 Y1 Z2 E3 M574 X1 S1 P"!^xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop M574 Y2 S1 P"!^ystop" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin ystop M574 Z1 S2 M667 S1 M350 X16 Y16 E16 I1 ; Set 16x microstepping with interpolation M92 X53.3 Y53.3 Z1500 E919.8 ;773 ; Set axis steps/mm M906 X1700 Y1700 Z2300 E1200 I60 ; Set motor currents (mA) and increase idle current to 60% M201 X1000 Y1000 Z100 E1000 ; Accelerations (mm/s^2) M203 X10000 Y10000 Z500 E3600 ; Maximum speeds (mm/min) M566 X300 Y300 Z200 E1201 ; Maximum instant speed changes mm/minute ; z Probe M950 S0 C"exp.heater5" M558 P9 C"^zprobe.in" H5 F300 T3000 ; BLTouch connected to Z probe IN pin, free up MOD pin G31 P500 X18 Y32.2 Z1.55 M557 X10:360 Y10:300 S40 M308 S0 P"bedtemp" Y"thermistor" T100000; 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 R0.441 C363.5 D1.73 S1.00 V12.0 ; 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 ; configure sensor 1 as thermistor on pin e0temp M950 H2 C"e1heat" T1 ; create nozzle heater output on e1heat and map it to sensor 1 M307 H2 B0 R1.535 C232.7 D6.00 S1.00 V12.0; disable bang-bang mode for heater and set PWM limit M143 H2 S280 ; set temperature limit for heater 2 to 280C M308 S2 P"e2temp" Y"thermistor" T100000 ; configure sensor 2 as thermistor on pin e1temp M950 H3 C"!^exp.heater3" T2 ; create chamber heater output on e1heat and map it to sensor 2 M307 H3 B1 S1.00 ; enable bang-bang mode for the chamber heater and set PWM limit M141 H3 ; map chamber to heater 2 M143 H3 S280 ; set temperature limit for heater 2 to 280C ; Fans M950 F0 C"fan0" ; create fan 0 on pin fan0 and set its frequency M106 P0 T45 S1 H1 ; set fan 0 value. Thermostatic control is turned off ; Tools M563 P0 D0 H2 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 ;lights M950 P0 C"exp.heater6" M671 X0:380:142.5 Y155:155:300 P0.8 M208 S0 X360 Y345 Z320 M208 S1 Z-.20 ; set minimum Z T0 ; select first hot endDeploy; i have also tried with without hte I1 but it doents make a differne.ce
M280 P0 S10 I1;and retract;
M280 P0 S90 I1; -
@qdeathstar said in Heat chamber configation:
none of the wiring has changed.
which pins are you physically wired to on the board? Your pasted config.g has shown exp.heater4 and exp.heater5 being used. Which is it?
Remove the
I1as it's not used in RRF3. Any pin inversion, if required, is done by adding!to the front of a pin name when it's defined. -
@phaedrux I changed which pin the yellow wire from the BL touch several times in my attempt to troubleshoot.
I guess that technical means the wiring has changed, but what I meant is from the board to the sensor.
Right now it is attached to the heater 5 pin. Is there a way to see if I have it plugged into rte correct pin, by toggling the pin high and low directly? I’ve triple checked trying to punt the pins but it’s possible it’s still wrong.
I’ve removed the I1 but there isn’t any affect. Did I1 mean inverted?
-
I suggest you connect to
Heater3 (pin 8)on the expansion board and use exp.heater3 in config.g as shown in my config example. -
@phaedrux heater 3 is used for my heat chamber. I guess I can map that to a different pin…
-
In that case, use heater 7
-
@qdeathstar said in Heat chamber configation:
e2temp
YOur config shows you using e2temp for the chamber heater. Is that even valid?
I suggest you take a closer look at my example config again and try to emulate that. In there it uses bedheat for the bed, e0heat for tool0 and e1heat for the chamber. Seems easier to use the main board connections before going to the expansion port.
-
e2temp is for the thermistor . It is working?
M308 S2 P"e2temp" Y"thermistor" T100000 ; configure sensor 2 as thermistor on pin e1temp M950 H3 C"!^exp.heater3" T2I am keeping e1temp and heater2 free in case I decide to go back to dual extrusion.
In any case, I don’t understand why it isn’t working. I should be able to use any pin with PWN correct @dc42 ?
I appreciate your help phaedrux.
-
I cannot figure this out.
I have even wired a bl touch right to the board and it is not working.
I have included a diagram of how i have it wired. It goes right from the board to the bl touch....
M669 K1; M111 S0; M552 S1; M555 P2 ; Set output to look like Marlin M575 P1 B57600 S1 ; Comms parameters for PanelDue G21 ; Work in millimetres G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves ; Axis and motor configuration M569 P0 S0 ; Drive 0 goes backwards M569 P1 S1 ; Drive 1 goes forwards M569 P2 S0 ; Drive 2 goes backwards M569 P3 S1 ; Drive 3 goes forwards M584 X0 Y1 Z2 E3 M574 X1 S1 P"!^xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop M574 Y2 S1 P"!^ystop" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin ystop M574 Z1 S2 M667 S1 M350 X16 Y16 E16 I1 ; Set 16x microstepping with interpolation M92 X53.3 Y53.3 Z1500 E919.8 ;773 ; Set axis steps/mm M906 X1700 Y1700 Z2300 E1200 I60 ; Set motor currents (mA) and increase idle current to 60% M201 X1000 Y1000 Z100 E1000 ; Accelerations (mm/s^2) M203 X10000 Y10000 Z500 E3600 ; Maximum speeds (mm/min) M566 X300 Y300 Z200 E1201 ; Maximum instant speed changes mm/minute ; z Probe M950 S0 C"exp.heater3" M558 P9 C"^zprobe.in" H5 F120 T6000 ; BLTouch connected to Z probe IN pin, free up MOD pin G31 P500 X18 Y32.2 Z1.55 M557 X10:360 Y10:300 S40 M308 S0 P"bedtemp" Y"thermistor" T100000; 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 R0.441 C363.5 D1.73 S1.00 V12.0 ; 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 ; configure sensor 1 as thermistor on pin e0temp M950 H2 C"e1heat" T1 ; create nozzle heater output on e1heat and map it to sensor 1 M307 H2 B0 R1.535 C232.7 D6.00 S1.00 V12.0; disable bang-bang mode for heater and set PWM limit M143 H2 S280 ; set temperature limit for heater 2 to 280C ;M308 S2 P"e2temp" Y"thermistor" T100000 ; configure sensor 2 as thermistor on pin e1temp ;M950 H3 C"!^exp.heater3" T2 ; create chamber heater output on e1heat and map it to sensor 2 ;M307 H3 B1 S1.00 ; enable bang-bang mode for the chamber heater and set PWM limit ;M141 H3 ; map chamber to heater 2 ;M143 H3 S280 ; set temperature limit for heater 2 to 280C ; Fans M950 F0 C"fan0" ; create fan 0 on pin fan0 and set its frequency M106 P0 T45 S1 H1 ; set fan 0 value. Thermostatic control is turned off ; Tools M563 P0 D0 H2 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 ;lights M950 P0 C"exp.heater6" M671 X0:380:142.5 Y155:155:300 P0.8 M208 S0 X360 Y345 Z320 M208 S1 Z-.20 ; set minimum Z T0 ; select first hot endM122
M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.0 or 1.01 Board ID: 08DAM-999TL-MQ4S4-6JKF6-3S86P-T4GVZ Used output buffers: 3 of 24 (11 max) === RTOS === Static ram: 23876 Dynamic ram: 74928 of which 24 recycled Never used RAM 15588, free system stack 206 words Tasks: NETWORK(ready,12.3%,237) HEAT(delaying,0.0%,341) Move(notifyWait,0.1%,340) MAIN(running,85.0%,467) IDLE(ready,2.7%,29), total 100.0% Owned mutexes: === Platform === Last reset 00:00:36 ago, cause: software Last software reset at 2021-12-04 21:21, reason: User, GCodes spinning, available RAM 15588, 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 Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 26.8, current 27.8, max 30.1 Supply voltage: min 1.2, current 1.3, max 1.4, under voltage events: 0, over voltage events: 0, power good: no Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Driver 0: position 0, ok, SG min/max not available Driver 1: position 0, ok, SG min/max not available Driver 2: position 0, ok, SG min/max not available Driver 3: position 0, ok, SG min/max not available Driver 4: position 0, ok, 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: 2021-12-04 21:35:46 Cache data hit count 1540836165 Slowest loop: 8.28ms; fastest: 0.12ms 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 5.1ms, write time 0.0ms, max retries 0 === Move === DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed moves 0, 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 Heater 2 is on, I-accum = 0.0 === 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.47ms; 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.26 WiFi MAC address 5c:cf:7f:2c:27:af WiFi Vcc 3.38, reset reason Turned on by main processor WiFi flash size 4194304, free heap 25200 WiFi IP address 192.168.1.208 WiFi signal strength -73dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 4 0 0 0 0 0 0 0 -
Have you tested the continuity of the yellow wire?
Does the BLtouch light up and do a self test when it receives power?
Do you have another probe to test with?
Do you have another printer to test the probe with? -
I replaced the bl touch attached to my printer with a spare I had.
So that is new wire and sensor. Continuity is fine. I don’t have a different printer sadly.
The bl touch has a red and a blue right on it. When I power off the printer it does it’s self test, but it doesn’t do it every time I reset the printer, only when power is cut. On the old software I thought I remembered it doing a self test every reset.
What I do Notice is that when I call M401 or M402 there is a high pitched whine sound, just loud enough to hear it. It makes the noise even with the bl touch unplugged.
It kinda sounds like a bad high frequency cap maybe? But it’s just weird that it was working before and I don’t know why it would make that sound only when the pin is PWMing.
