Homing problem Ender 3 pro

[rjenkinsgb]

You don't seem to have the actual input connections defined for the endstops in your config, to connect specific switch input to their respective axes?

eg. This is what I have in mine for the endstops (with dual Z drives, hence two inputs on that):

; Endstops
M574 X1 S1 P"io5.in"                         ; configure active-high endstop for low end on X via pin io5.in
M574 Y1 S1 P"io2.in"                         ; configure active-high endstop for low end on Y via pin io2.in
M574 Z1 S1 P"io3.in+io4.in"                  ; configure active-high endstop for low end on Z via pin io3.in

[Roeland]

@rjenkinsgb Do you have a layout for the io numbers and the pins on the board? I use the Duet 2 wifi. On this board are the inputs written on the board to let you know which endstop should go where. And also connected as it should since it responds as it should in machine properties

[Phaedrux]

Can you post the results of sending M122 and M98 P"config.g" in the gcode console please?

[Roeland]

@phaedrux

[rjenkinsgb]

@roeland said in Homing problem Ender 3 pro:

Do you have a layout for the io numbers and the pins on the board? I use the Duet 2 wifi. On this board are the inputs written on the board to let you know which endstop should go where. And also connected as it should since it responds as it should in machine properties

OK, you are on firmware version 2 rather than 3.x; the M574 syntax is totally different in V3, hence it looking like something was missing. Ignore that multi-line stuff..

Can you move/jog the axes before trying to reference, and if so is positive movement towards or away from the endstop switch position?

[Roeland]

@rjenkinsgb it is possible to jog the Axes by using command"M564 H0" first or by giving the Axis a certain value first. Negative towards the endstop and positieve going away from the endstop.

[rjenkinsgb]

OK, what does the status show before trying to reference the machine and with it powered up while the axes are already away from the stops?

[Roeland]

@rjenkinsgb without using ''M564 H0'' it just says ''G0/G1 insufficient axes homed'' without further information. And then if I fill in some values for the head position it works for manual jogging, but cant print anything because it needs to home again, but doesn't give me any errors. When using "M564 H0" it allows me to move the head without homing, but still cant print because when it homes the head just slams into the endstops without any error codes. And I turn the power off as soon as possible.

It seems like the endstops do not communicate with the homing for some reason, but don't know why. And they do work under settings>machine properties.

[rjenkinsgb]

@roeland said in Homing problem Ender 3 pro:

without using ''M564 H0'' it just says ''G0/G1 insufficient axes homed''

Sorry, I meant the "machine properties" display like you posted a few hours ago, but with the machine turned on while the axes are already away from the endstops & without trying to move or home anything?

[Roeland]

@rjenkinsgb When the machine is turned on while the axes are already away from the endstops it gives the status "no" for all the axes that are away from the endstop.

[Phaedrux]

Your firmware is quite out of date. I suggest you update to at least 2.05

Download this zip file, and then upload it as is to the system page in DWC.

https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip

I think this will solve the G0/G1 error. I think it's because your hoiming files are using modern syntax G1 H moves but your old firmware only knows G1 S moves for homing.

[Roeland]

@phaedrux Thanks! that fixed it. But it went a bit troublesome. I got back from work and wanted to update my firmware but it kept disconnecting from my wifi. while nothing has changed with the wifi in the meantime. after several times trying to upload the software it finally succeeded. but now there is some trouble with the wifi..

[Phaedrux]

What is the trouble with the wifi exactly?

[Roeland]

@phaedrux When starting up it first connects to wifi, after 20 seconds or 1 minute or so it disconnects en starts reconnecting. it reconnects en disconnects again. after a while it just says wifi module is idle.

[Roeland]

@phaedrux I've only had this problem once befor when I first got the board about a year ago (it took a whille before I installed it on my ender), but somehowI made it work back then. And now it happens again.

[Phaedrux]

Is you send M122 again what wifi server version is now installed?

You're still only running the latest RRF2 version after this update, there has been nearly 2 years of updates since then in RRF3 including with the wifi server firmware.

Now that we know your homing issue was a syntax issue and the printer seems to be otherwise working (wifi aside) I think it would be a good opportunity to complete the firmware upgrade process and get to 3.3

If you still have access to DWC. Upload these 3 zip files, one at a time in the system tab. Don't extract them first. Reboot after each. Use M115 in the gcode console 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.x

For your config, might be a good idea to run through the configurator tool and generate a fresh set for RRF3.
https://configtool.reprapfirmware.org/Start

Backup your existing config files in the sys folder in case you want to switch back to RRF2. 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

[Roeland]

@phaedrux console.csv This is the response for M122 Picture of error. At this moment the wifi module has behaved for at least 10 minutes now. Maybe it was a temporary thing, but i still think it will be good to upgrade to RRF3

[Phaedrux]

The M122 is too long to view entirely on the paneldue. You'd need to use a USB terminal to see the full response.

upgrading the firmware will also reflash the wifi firmware which may be enough to solve the problem as it is.

[Roeland]

@phaedrux The install of RRF 3.0 was successful. and it homes as it should. The only problem I have right now is the setup of my thermistor. nozzle thermistor is n/a and bed thermistor thinks is is -273 C (almost 0 K).

[Phaedrux]

Yes you'll need to go on to RRF 3.3 and get an up to date config file set from the online config tool as the syntax for setting up the hardware has changed compared to RRF2.