directions wrong and no zero...

HebigT

@fusedeep

You mentioned Y axis moving "up" or "down". Do you mean front to back, etc.

Just want to make sure you didn't mean Z axis.

Does your x-axis work as expected?

Can you also post your homey.g file?

FuseDeep

@hebigt

Non of the axis are heading to home, they do 5mm and stop.

The bed(Z) does a 5mm hop to allow for ther x and y move and then a 5mm drop back.

but the 5mm z is up then down, not down then up.

it's bloody irritating!

z file

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Wed Apr 20 2022 11:07:59 GMT+0100 (British Summer Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 Z-190 F1800 ; move Z down until the endstop is triggered
G92 Z0 ; set Z position to axis minimum (you may want to adjust this)

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

//

; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Wed Apr 20 2022 11:07:59 GMT+0100 (British Summer Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 Y-255 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 H2 Y5 F6000 ; go back a few mm
G1 H1 Y-255 F360 ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z-5 F6000 ; lower Z again
G90 ; absolute positioning

//

; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Wed Apr 20 2022 11:07:59 GMT+0100 (British Summer Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-205 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 H2 X5 F6000 ; go back a few mm
G1 H1 X-205 F360 ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F6000 ; lower Z again
G90 ; absolute positioning

FuseDeep

Main issues;

Option to extrude does not appear on web control even when nozzle at 220 degrees. buttons greyed out.
When selecting home for any axis, only 5mm movement along axis. Does not continue until micro switch/es

However it is now doing the 5mm hop down and back up in the correct direction (not sure what has changed there) when x and y asked to be homed.

Extruder and bed working fine heat wise.
Part cooling fan starts at 100% but should not, can't work out how to leave it on gcode control, it is currently not on temp control afaik.

Plus, temp controlled fan is not working, though does occasionally. Grr

DaveA

@fusedeep Are you sure the endstops are wired as described in the config.g? What is the state of the endstops before you try to move? D an M119 to see stop status.

FuseDeep

@davea said in directions wrong and no zero...:

M119

I am not sure what config G is telling me about my endstops?

They are micro switches Normally open iirc, at the home/start point and have worked fine for years, does that match?

FuseDeep

@davea said in directions wrong and no zero...:

M119

M119 saying all at min stop

?

fcwilt

@fusedeep

When you see an axis only moving a short distance when homing (you mentioned 5mm) what you are likely seeing is the fact the the endstop sensors are triggered by default. As a result the G1 H1 moves never happen as they stop when they sense a triggered endstop sensor. The short move you see is the G1 H2 move where you back off.

Frederick

DaveA

@fusedeep If I understand correctly M119 is reporting that all stops are active. Assuming that the actual axis is not at the stop but the M119 is reporting that the stop has been hit then I would expect exactly what you are seeing.
Check that the configuration of the M574 exactly matches what you have for switches paying close attention to the !
and ^ options.

samlogan87

You say your using normally open endstops. I am only doing this off memory as I am on holiday at the moment and am doing this off my phone but I am pretty sure you need to invert the pin as it is recommended to use normally closed. So to do that on the m574 line where you are defining your end stop you need to do P"!xstop"

Phaedrux

@fusedeep said in directions wrong and no zero...:

Main issues;

Option to extrude does not appear on web control even when nozzle at 220 degrees. buttons greyed out.

It sounds like the tool is not selected and I don't see a T0 in your config.g to select it at startup, so please try adding T0 at the end of config.g

When selecting home for any axis, only 5mm movement along axis. Does not continue until micro switch/es

This sounds like the endstop is already triggered at the start of the move and the 5mm movement you are seeing is the backoff movement. The last few posters have identified what needs to be done there.

If M119 says the axis are at the endstops when they are not physically there, then the endstop signal needs to be inverted.

So for each axis that says it's at the endstop when it's not actually you would need to add a ! to the pin name to invert it.

Like so
M574 X1 S1 P"!xstop"

Test homing carefully after that and make sure the axis are moving in the correct direction towards the endstop. If they move in the wrong direction, e stop/cut power. Report back if that's the case.

Part cooling fan starts at 100% but should not, can't work out how to leave it on gcode control, it is currently not on temp control afaik.

Plus, temp controlled fan is not working, though does occasionally. Grr

; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H0 T40 ; set fan 0 value. Thermostatic control is turned on
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H-1 ; set fan 1 value. Thermostatic control is turned off

; Tools
M563 P0 D0 H1 F0 ; define tool 0

This section has some problems. Currently it has fan0 as thermostatically controlled to turn on when the bed temp is 40c and also assigns that fan as the part cooling fan. Fan1 is setup as a gcode controlled fan.

To be able to tell you how to fix that I need to know which fan is physically located where. Ideally Fan0 should be the part cooling fan. If that is the case the section should look like this

; Fans
M950 F0 C"fan0" Q500 
M106 P0 S0 H-1 
M950 F1 C"fan1" Q500 
M106 P1 S1 H1 T40 

; Tools
M563 P0 D0 H1 F0 ; define tool 0

M552 S2 is correct to turn on the access point mode for the wifi.

FuseDeep

@phaedrux

Thanks for all of the above. it is starting to make sense.

Have the axis moving the right way, but not doing the slow bump return on homing however.

Major problem now, the green led by the wifi model is gone, so no wifi AND my laptop COM ports have literally F'd off.

So cannot connect to board at all.

Bloody annoying.

I have tried disabling com/lpt and restarting. my COM ports have literally gone and I can't fix it or connect to duet board.

Plus, there is no reason the wifi should have gone off, nothing got changed...

Really grinding my gears this time!

fcwilt

@fusedeep said in directions wrong and no zero...:

Major problem now, the green led by the wifi model is gone, so no wifi AND my laptop COM ports have literally F'd off.

This is with the USB cable still connected from your computer to the Duet?

Frederick

FuseDeep

@fcwilt

yes, no wifi and com ports totaly gone/dead.

Have tried a new terminal, no better.

Literally the entire com port part of my laptop is fried, AND the wifi to the duet is gone, so I cannot contact the board.

There is no reason for the wifi status to change.

This is getting silly now...

FuseDeep

@fcwilt

YAT won't re install as framework won't fully update. I uninstalled yat and am now using putty, but it is showing the same errors, no com ports.

fcwilt

@fusedeep said in directions wrong and no zero...:

@fcwilt

YAT won't re install as framework won't fully update. I uninstalled yat and am now using putty, but it is showing the same errors, no com ports.

When trying to communicate with the Duet via the USB cable was the Duet board getting power from another source via the Vin connections?

Was your laptop running of it's batteries or the charger?

Thanks.

Frederick

FuseDeep

@fcwilt @Phaedrux

I think my duet board is borked.

When I take out the mouse usb it dings at me, and when I put it back in it dings again.

No response to the usb plug from duet, nor wifi light(this should be on).

Balls.

FuseDeep

@fcwilt yes, board plugged into 24v feed as usual to run printer for testing.

FuseDeep

@fcwilt laptop on mains and battery works fine.

fcwilt

@fusedeep said in directions wrong and no zero...:

@fcwilt yes, board plugged into 24v feed as usual to run printer for testing.

I cannot be sure since I don't know the details of your 24 volt power supply and your laptop but it is possible, under certain circumstances, when the Duet is getting power from both sources (the 24 power supply and the USB cable) that damage to the Duet can occur.

I'm not saying this is what has happened but it might have happened.

If your Duet is damaged and you proceed with getting it repaired or replaced you might want to consider using my approach to getting a Duet up and running. I don't use the USB connection, rather I pull the SD card and connect it to my computer via a SD card reader/writer device. Then I create a minimal config.g file on the SD card with just the commands need to get the WiFi up and running. When the config.g file is ready I return the SD card to the Duet and apply power. Once WiFi is up then I can do the rest of the configuration via the DWC editor.

Frederick

Phaedrux

There is the possibility that it has been damaged by a ground loop through the USB connection.

Can you show a photo of the board when connected to just USB so that we can see the lights?
Same for when just connected to VIN.
Close up photos of the board may show if a component has failed as well, such as a regulator.
You can also check with your finger to see if any component gets very hot.

For more detailed steps on how to check what is working or not please go through this guide and let us now what you find.
https://docs.duet3d.com/en/User_manual/Troubleshooting/Duet_wont_respond