web control tool error
-
@siam Hi Slam,
The crimps on the thermistor havent changes (i havent put the duet plugs on as i wasnt needed from what ive read, please tell me if im wrong)
Config.g below
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 16 2021 15:54:40 GMT+0000 (Greenwich Mean Time); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"" ; set printer name; Network
;M551 P"" ; set password
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 backwards
M569 P1 S1 ; physical drive 1 goes backwards
M569 P2 S0 ; physical drive 2 goes forwards
M569 P3 S0 ; 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 E93.00 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E1200.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 X600 Y600 Z600 E600 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X-5.5 Y-10 Z0 S1 ; set axis minima
M208 X220 Y220 Z250 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"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 X-49 Y9 Z1.597 ; set Z probe trigger value, offset and trigger height
M557 X-15:165 Y20:230 S20 ; define mesh grid
;M557 X5:205 Y5:165 S20 ; Define mesh grid; Heaters
M308 S0 P"bedtemp" Y"thermistor" T98801 B4185 ; 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" T98801 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
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; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 C"Part Cooling" S0 H-1 ; set fan 0 name and value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 C"Heatsink/Hotend" S1 H1 T45 ; set fan 1 name and value. Thermostatic control is turned on
M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P2 C"PartCooling" S1 H1 T45 ; set fan 2 name and value. Thermostatic control is turned on; Tools
M563 P0 S"PrintHead01" 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
M575 P1 S1 B57600 ; enable support for PanelDue
M501 ; load saved parameters from non-volatile memory
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
T0 ; select first toolthank you for your help so far!!
-
2000 degrees normally indicates a connection issue as @SIam mentioned.
Try another thermistor in the port to prove, please.Also please post your 'config-override.g'
P.
-
@paulhew and a M122 please...
I see you have 2 issues. BLT and this.
Have these 2 faults just happened?P.
-
sorry apparently this post has been considered as spam :s i will respond asap
-
@prior123 @paulhew @paulhew @paulhew Sooo, i dont have any spare thermistors i only have the one for the heated bed and also the hot end, is there another way i would be able to test another way? so i dont have to wait for the delivery. These were working just a week ago, they have just happened however its happened as i changed from the standard Ender 3 board over to the duet 2 wifi. this change over is where ive had these issues (which is why i probably wrongly assumed that the hardware was functioning)
See below config-override.g
; config-override.g file generated in response to M500 at 2020-09-17 16:06
; This is a system-generated file - do not edit
; Heater model parameters
M307 H0 A160.4 C611.0 D0.6 S1.00 V23.5 B0
M307 H1 A340.0 C140.0 D5.5 S1.00 V0.0 B0
; Workplace coordinates
G10 L2 P1 X0.00 Y0.00 Z0.00
G10 L2 P2 X0.00 Y0.00 Z0.00
G10 L2 P3 X0.00 Y0.00 Z0.00
G10 L2 P4 X0.00 Y0.00 Z0.00
G10 L2 P5 X0.00 Y0.00 Z0.00
G10 L2 P6 X0.00 Y0.00 Z0.00
G10 L2 P7 X0.00 Y0.00 Z0.00
G10 L2 P8 X0.00 Y0.00 Z0.00
G10 L2 P9 X0.00 Y0.00 Z0.00Jack
-
This post is deleted! -
Sorry the span bot doesnt like it being posted
-
@prior123 I take it you are aware you are running really old firmware and a Beta?
2.03beta3....If I am reading this correctly, you have a config for RRF3 and a board running RRF2.x
Config-overide is not doing anything to affect the bed heater.
Try making off the connector using the Duet hardware, if you can.
Under RRF2 you need to use different commands.
https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_Software_setup_Duet_2_WiFi_Ethernet_running_RepRapFirmware_Num_2M307 H3 A-1 C-1 D-1
M558 P9 H5 F100 T2000P.
-
@paulhew ok thanks i will rewire and try this as well as the firmware coding changes. Apologies if these are dumb questions but i am abit of a newbie as im sure you have realised (rofl)
does the
M307 H3 A-1 C-1 D-1
M558 P9 H5 F100 T2000Need to be put in a certain section or can i just put it at the bottom?
also do i need need the G31 X0 Y0 Z0 P25 that was also on that page?
Thanks again
-
@prior123 Also sorry its just came to mind, are you saying i should 'downgrade' the firmware as its not compatible with the board?
-
@prior123 If this is a new build...
Upgrade to RRF3, you might find that most of your config should work as it look likes it was configured for RRF3.The giveaway was the M308 and M950 commands which are RRF3.
You can only try.
P.
-
this is amazing thank you!! its helped massively!!! the only thing left is that the BL touch isnt stopping upon trigger, any more ideas?
Below is my now amended Config.g
Thanks again
-
@prior123 M112 M999
Error: Z probe was not triggered during probing move
Error: Homing failed -
@prior123 it feels like it is failing at the G90 code however i dont know where this gets set
-
@prior123
Going from RRF2 to RRF3, you also have to replace/edit some more files...
Best would be to generate a complette set with the config tool -
@prior123 , @DIY-O-Sphere has a good point, to create a new set of files using the configurator.
this is your Z Probe section
; 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 X-49 Y9 Z1.597 ; set Z probe trigger value, offset and trigger height
M557 X-15:165 Y20:230 S20 ; define mesh grid
M307 H3 A-1 C-1 D-1
M558 P9 H5 F100 T2000
;M557 X5:205 Y5:165 S20 ; Define mesh gridRemove the 2 strikethrough lines from your config. just incase they are clashing.
Also go through this instruction.....
https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_Duet_2_WiFi_Ethernet_without_expansion_board
Checking the wiring, Perform the commissioning and Testing and then
https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe
for final checks......Please post your, bed.g, deployprobe.g, retractprobe.g, homex/y/z.g and homeall.g please, if the above does not work.
Regards,
Paul -
If you still have access to DWC. Upload these 3 zip files, one at a time in the system tab. Don't extract them. Reboot after each. Use M115 to verify the firmware has been applied.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
That will get your firmware and DWC up to date.You can see the change logs here:
https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.xFor your config, might be a good idea to run through the configurator tool and generate a fresh set for RRF3.
https://configtool.reprapfirmware.org/StartBackup your existing config files in the sys folder in case you want to switch back to RRF3. IT’s easy to switch back and forth, just upload the zip file for the version you want and then upload your config files.
These documents will come in handy during the conversion.
https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview
https://duet3d.dozuki.com/Wiki/Gcode -
