Software bundle 3.4.0 Release Candidate 2 available

[Paddy]

I'm running a corexy with a duet WiFi2.

I've not used it for a while but have gone back to it. The first thing I did was to install 3.4rc1. When I went to print the x axis failed to home correctly.

I'm using optical endstops on x and y. When told to home all, Y correctly moves towards the endstop and activates it.

X however does not move towards the endstop, Instead it moves right about 50mm, away from the endstop and stops. If I tell it to home x again, it once again moves right by about 50mm.

It is like it thinks it has triggered the endstop. The endstop is connected and its LED is on, so the endstop is not being triggered by something else.

Below is what I have in my config.g and homeall.g. Has anything changed that would cause this?

In my config I have;

; Axis Limits
M208 X0 Y0 Z0 S1                                   ; set axis minima
M208 X200 Y190 Z150 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

My homeall.g is;

G91                     ; relative positioning
G1 Z5 F6000 H2          ; lift Z relative to current position
G1 H1 X-200 Y-190 F1800 ; move quickly to X or Y endstop and stop there (first pass)
G1 H1 X-200             ; home X axis
G1 H1 Y-190		; home Y axis
G1 X5 Y5 F6000          ; go back a few mm
G1 H1 X-200 F360        ; move slowly to X axis endstop once more (second pass)
G1 H1 Y-190             ; then move slowly to Y axis endstop
G90                     ; absolute positioning
G1 X30 Y15 F6000        ; go to first bed probe point and home Z
G30                     ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
G91                    ; relative positioning
G1 H2 Z5 F100          ; lift Z relative to current position
G90                    ; absolute positioning

[A Former User]

[Duet 3 with expansion boards] If an axis motor was controlled by an expansion board then if the endstop switch was already triggered when a homing move was commanded, unexpected motion sometimes occurred]

Does it mean the unexpected motion occured while printing or directly?
Cheers

RG

[dc42]

@gruna-studio said in Software bundle 3.4.0 Release Candidate 2 available:

Does it mean the unexpected motion occured while printing or directly?

Only when homing.

[A Former User]

@dc42
Thanks

[Paddy]

It is like it thinks it has triggered the endstop. The endstop is connected and its LED is on, so the endstop is not being triggered by something else.

On a fresh power on, I sent a M119 and indeed the x endstop is at min stop.

[chrishamm]

@rushmere3d There is an interactive prompt at the end of the update process asking you if the firmware on the board(s) should be updated. Did you confirm that with Y(es)? If you are not sure, you can reinstall the RRF package (which invokes the prompt) by running sudo apt install --reinstall reprapfirmware.

[dc42]

@paddy unfortunately many optical endstops are designed for 5V power and don't pull the endstop input down low enough when powered from 3.3V, even if they pull it low enough to light up the LED. You can usually fix this by changing a resistor on the endstop. See https://docs.duet3d.com/User_manual/Connecting_hardware/Sensors_endstops#h-33v-compatible-optical-endstop.

[Paddy]

@dc42 said in Software bundle 3.4.0 Release Candidate 2 available:

@paddy unfortunately many optical endstops are designed for 5V power and don't pull the endstop input down low enough when powered from 3.3V, even if they pull it low enough to light up the LED. You can usually fix this by changing a resistor on the endstop. See https://docs.duet3d.com/User_manual/Connecting_hardware/Sensors_endstops#h-33v-compatible-optical-endstop.

thanks for the reply.

I opened the wiring loom and found a damaged wire. Apologies for the forum noise.

[Rushmere3D]

@chrishamm

I didn't get that prompt.

When I tried to update to the unstable release a few days ago and it bricked my install I also didn't get that prompt.

However I used a new SD card and started again and that time I did get the prompt.

Seems a bit hit and miss?

[chrishamm]

@rushmere3d What did you get then, can you share a screenshot? The last prompt during the update process should look like this:

If the firmware version doesn't match the DSF version, things (probably) won't work well.

[Rushmere3D]

@chrishamm

OK, so don't have a screenshot from past attempts but I did notice it said the below when I tried going for rc1 to rc2

"setting up reprapfirmware (3.4-rc1)"

I've just used the sudo apt install --reinstall reprapfirmware command you mentioned above and this time it did download and ask me to update rc2. Odd?

[chrishamm]

@rushmere3d Perhaps you were on a really old firmware version when you tried to upgrade to RC1. I'll try that on my bench setup.

[Rushmere3D]

@chrishamm

When I updated to the unstable (rc1) I was on 3.3, it failed so I created a new SD card with the DuetPi lite image from the website and it worked. Then with that I tried to go to rc2 and I didn't get the update boards prompt. With the command you provided it worked.

[dc42]

Please can anyone else having issues with 3.4.0rc2 start a new thread to describe the problem.