Topics created by Nazar

@Nazar you should map both drivers to Y in M584 and then have 2 pins listed in M574
E.g. M574 Y1 S1 P"io1.in+io2.in"
It will then home both together and stop them independently when the endstops are hit.
Make sure the order in M574 matches the order in M584

@dc42, thank you for your prompt reply, I highly apreciate it!

Macro runs automatically after machine’s restart

Printer is now online. Done! WiFi is disabled. Executing runonce.g... Network stopped Error: Failed to configure access point parameters: SPI timeout Error: Failed to configure access point parameters: SPI timeout Turn off the current WiFi mode before selecting a new one Done! Error: Cannot delete file 0:/sys/runonce.g because it is open Error: Cannot delete file 0:/sys/runonce.g because it is open RepRapFirmware for Duet 3 MB6HC is up and running.

Calling Macro through Pronterface

>>> M98 P"0:/sys/networktest.g" SENDING:M98 P"0:/SYS/NETWORKTEST.G" WiFi module stopped Error: Failed to configure access point parameters: SPI timeout Error: Failed to configure access point parameters: SPI timeout Turn off the current WiFi mode before selecting a new one - Connection was not established - WiFi module was automatically switched to Access Point Mode Send M292 to continue

Calling Macro through Pronterface but before turning off WiFi and Ethernet

>>> m552i0s0 SENDING:M552I0S0 >>> m552i1s-1 SENDING:M552I1S-1 WiFi module stopped >>> M98 P"0:/sys/networktest.g" SENDING:M98 P"0:/SYS/NETWORKTEST.G" Error: Failed to configure access point parameters: SPI timeout Error: Failed to configure access point parameters: SPI timeout Turn off the current WiFi mode before selecting a new one - Connection was not established - WiFi module was automatically switched to Access Point Mode Send M292 to continue Disconnected.

Unfortunately neither worked.

@Nazar what do you mean that the Z positions is not consistent?

@chrishamm thanks for the update; the last time I looked into this I couldnt figure it out (years ago).

@Nazar it shares the SPI connection with the SBC interface. So in principle you might be able to connect it to the SBC connector; but without spending more time looking at the differences I can't promise that it will work. In particular, I think the firmware may detect the board version and only make WiFi available on the 1.02 and later boards.

@Phaedrux I had the same issue on RRF3.5rc1. Downgrading the server to the version you linked helped.

This may be covered by the events system.

https://docs.duet3d.com/en/User_manual/RepRapFirmware/Events

@Nazar
You can check the success of any Gcode command using "result"
0= success, 1= warning, 2 = error

G30 ; home Z by probing the bed if result !=0 abort "Print cancelled due to probe error"

@mrehorstdmd said in EndStop Accuracy Test:

................ I ran into one problem with opto endstops in my printer- the work room where the printer sits has a large, east-facing window and sunlight falling directly on the printer interfered with them. It took a while to figure out what was going on, but closing the curtains on the window solved the problem. I've never had any other problems with them.

That reminds me of a similar issue I came across. I use a slotted opto switch to get my bed somewhere close at highish speed before homing "proper" using the nozzle. When I first tried to test the switch, it didn't seem to be triggering until I realised that it was seeing straight through the thin piece of paper I was using as a "flag". 😊 (It doesn't see though a piece of 2mm thick aluminium though). ☺

@Nazar using a mechanical relay will slow down the touch response. Why not use an opto isolator instead?

@Nazar you could set the standby temperature to 100C less than the active temperature in pause.g and then either deselect the tool or set the tool heaters to standby. Then reselect the tool or set the tool heaters to active in resume.g.

@chrishamm Thank you for your advice, it has worked.

An alternative way is also available by using the code below

if network.interfaces[0].actualIP = "0.0.0.0" || network.interfaces[0].actualIP = ""

@Tinchus you would use something like this

P{"copy and paste the IP number: "^network.interfaces[0].actualIP}

@nazar said in Duet 2 WiFi Board Help, 24V doesn't Work:

Are there any hints how?

Might help to see a diagram of your actual wiring setup.

Can you get a better lit photo of the board with some close ups in case we can see any damaged components.

have a look at this:
https://duet3d.dozuki.com/Wiki/Connecting_and_configuring_a_chamber_heater#Section_Using_multiple_temp_sensors_for_a_single_heater

as @Phaedrux suggests this can be customised with conditional gcode but you can also achieved using M143

e.g.

M143 H1 P0 S60 T2 A2 ; switch off heater 1 temporarily if it exceeds 60°C, using temperature sensor 2 to control this.

That will mean the heater gets switched off every time temperature sensor 2 temperature gets above 60C