web control tool error
-
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 -
