HELP
-
in reference to earlier update firmware
in the web interface systems tabnot sure where you are talking about i see upload a couple times and only system editors
-
@camassey it’s the big blue ‘upload files’ button under ‘file upload for /sys and /www folders’.
Ian
-
thanks.....i hit the button it goes to my downloads i pick the duet firmware file and it opens it up
so what part of this do i use and how
-
@camassey looks like you have extracted the zip file. Don’t. As @Phaedrux said:
Download this zip file. Don't extract it.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zipYou’re browser may be extracting it automatically. Turn that off if you can, so that you have a file “ Duet2Firmware-2.05.1.zip” downloaded, then upload that in DWC.
Ian
-
OHYA...that went smooth when you do it right.Do you have to hit the apply setting tab in the lower left?
-
@camassey I don’t think so. It should upload and extract all the files, then prompt for a reboot to install the firmware. If it doesn’t, send M997 S0 to install firmware update.
Ian
-
Excellent
going for three in a row here i think the next thing is the printers parameters.This is a Railcore kit build and the first thing they say is to My guess is this will put in all the specs.Is it the same procedure as the update was. -
@camassey I updated a Duet 2 Ethernet from 2.02 > 3.0 > 3.1.1 the other day, went seamlessly.
I can’t say for certain, because I can’t see the links, but yes, you can usually upload config files in DWC. Or remove the SD card, then copy the files over on your computer. Make sure the network settings are correct in config.g before you restart.
Ian
-
Thanks worked great
did all my stepper and limits test all good and have come to a grinding halt by a little BLTouch.On power up it does its up and down a couple time then stops in the up position with a solid on LED.
Z probe reads zero.Put in first command and pin drops LED is off, probe still zero.When you touch it probe it reads 1000 and the led starts to flash pin will go up and nothing works after that flashing LED -
@camassey If it's flashing it's probably gone into error state. When you touch it be careful not to force the pin at all. Just a slight touch will make it retract.
What firmware version are you running now? The M280 P3 commands listed in your photo will work in 2.x but not in 3.x as the P3 part will likely now be P0.
-
being very gentle with the probe, when you start to touch it there is a small amount of resistance ...like a magnetic feed back
is this the firmware -
Does the movement of the Z axis halt when you touch the pin? That's the important thing.
If you test it as actual homing you can reduce the Z axis motor current a bit in M906 and have your hand near the power switch to kill it if the homing fails and it looks like the nozzle will hit the bed. As described in the static test in this link: https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe
-
The above procedure produces the touch dropping and the bed dropping about 10mm
-
with this in the lower corner -
@camassey sounds like your bed is moving in the wrong direction or your homing files are wrong. A positive Z move should lower the bed (increase distance between bed and nozzle) and a negative Z move should raise the bed (decrease the distance between bed and nozzle). If this is correct, post your homeall.g file.
The probe reading 0, and 1000 when triggered, is also correct, though the alarm isn’t. Alarm can be reset by sending
M280 P3 S160
.Ian
-
i ran this earlier ad the bed was going the wrong way so i followed the steps and now is it goes in the correct direction as these instruction say.
thanks for mentioning the + and - direction been looking at it the wrong way keep thinking about my milling machines direction.
I ran the home all on the DWC X Y work but Z didn't while looking for the homeall file it came to life and homed the Z
it probed 3 time is that normal and now it say it's homed.
sorry....where do i find the homeall.g -
is this it
-
@camassey yes, that’s homeall.g, but all it’s doing is calling the other homing files. If one of them is causing an issue, post that one.
If you’re going to post files, it’s best to post them as text rather than screenshots, then people helping you can copy the text to show you what to change. Ideally format text with the ‘code’ style, which is the </> symbol on the editing toolbar. People are more likely to respond if you make it easy for them! Also, can you post a link to the instructions you’re using? Again, all you’ve posted is screenshots.
The multiple probes on Z will be due to the way the probe is set up in config.g and is normal. See the A parameter in M558: https://duet3d.dozuki.com/Wiki/Gcode#Section_M558_Set_Z_probe_type
Ian
-
I do apologies for my lack of knowledge and appreciate everyones patient and help. This all very new to me and have never dealt with any of it before.
Perfect example is your instructions above about how to post haven't got a clue where to start with that?????This is where i am following procedures
https://railcore.dozuki.com/c/RailCore_II
section S first moves -
If it probed 3 times that could be totally normal. If you're using the provided railcore config files and following their guide you are on the right track.
Are you able to jog the printer axis around after homing?