@oc_geek

So I've added the following to my slicers layer change script:

M552 S0
M552 S1

That should solve any external network issues, now lets see!

@rew3 I don't see anything in that M122 report that would account for that problem. Here ar4 some suggestions:

Which browser are you using? Have you tried a different browser? When this next happens, connect a laptop running a terminal emulator (e.g. YAT) to the Duet via USB. Then send M122 via USB and save the result. After that, send M122 P104 via USB to run a test of the SD card.

@mdunfee have a look here
25748462-b6ad-4e09-bde8-b26de59c7988-image.png
You need to press the little arrow next to the system directory, you can then select menu directory

@phaedrux Hello again! I ended up doing a complete fresh reinstall from the configurator then made sure I was using the latest stable release.

Good news is I am now connected to DWC 3.3.0, bad news is I have a new issue here.

M122 printout is being flagged as spam by Akismet. I will try and snippet the relevant.

M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.0 running on Duet WiFi 1.02 or later + DueX5 ... Error status: 0 ... === Network === Slowest loop: 15.22ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 - WiFi - Network state is running WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.26 WiFi MAC address 48:3f:da:75:a8:d7 WiFi Vcc 3.36, reset reason Turned on by main processor WiFi flash size 4194304, free heap 26024 WiFi IP address 192.168.0.74 WiFi signal strength -63dBm, reconnections 0, sleep mode unknown Socket states: 0 0 0 0 0 0 0 0

@michaelr123 said in Connecting to DWC v3.3.0 via wifi:

Would going to a raspberry Pi 4 help at all?

Should be ok on a pi3, but the pi4 definitely has a lot more breathing room. It might be a useful way to see if it's a hardware problem with
the Pi itself, which does occasionally happen.

@t3p3tony said in DWC Object Browser object list:

@thedragonlord https://github.com/Duet3D/RepRapFirmware/wiki/Object-Model-Documentation

great! thanks

@gustav_seasony the REST API is only applicable when you have a SBC connected to the Duet. When running the Duet in standalone mode, use this API https://github.com/Duet3D/RepRapFirmware/wiki/HTTP-requests.

The Y.0. is strange, I would change it to Y0.0

And the M584 is doubled, I would remove one line. And according to docs, M584 should come before M669 if creating new axes. https://duet3d.dozuki.com/Wiki/Gcode#Section_M584_Set_drive_mapping

@phaedrux standalone mode, beta3, correct.

Did you update DWC along with the firmware?

Where are you sending M122 command? Do you have multiple DWC windows/connections open from multiple devices? Do you also have a paneldue?

@oozebot You could set the webcam update interval to 0 if you don't need it (I think). It may be necessary to change the HTTP request URL to prevent caching, that's why I added a new option to not append extra HTTP qualifiers. The latter might confuse cheap webcams though.

@phaedrux said in Layer times:

@imsother said in Layer times:

@phaedrux I'm using RepRapFirmware for Duet 2 WiFi/Ethernet 3.2.2 (2021-02-11) and Duet Web Control 3.3.0

Update your firmware to match the DWC version. They must be in sync for proper function.

I suggest you upload this complete zip file package to the system tab in DWC to get everything up to date.

https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip

Just did that, and worked perfectly! Thanks for all the help guys!

Test the trigger height of the probe at that point. It looks like it's triggering too early.

Do you have the page zoomed or something? Or perhaps it's just the large number of entries that doesn't fit well in the defined space.

@hsverre said in True Bed Leveling G32:

@fcwilt Hm. It seems like its adjusting the bed correct. Could it be that i might have a faulty stepper motor thats not doing its job properly by a mm or two, thats difficult to measure by eye.

Did you verify Z movement as I asked about.

Have you run G32 many times to see if it ever gets better?

It's possible to setup a loop which runs a max number of times or until a certain result is obtained.

From my bed.g file:

while true ; run leveling pass ; --- probe near bed corners --- G30 P0 X-140 Y-90 Z-99999 ; LF G30 P1 X-140 Y90 Z-99999 ; LR G30 P2 X140 Y90 Z-99999 ; RR G30 P2 X140 Y-90 Z-99999 S3 ; RF ; check results - exit loop if results are good if move.calibration.initial.deviation < 0.02 break ; check pass limit - abort if pass limit reached if iterations = 5 M291 P"Bed Leveling Aborted" R"Pass Limit Reached" abort "Bed Leveling Aborted - Pass Limit Reached"

@jay_s_uk Thanks. That's good to know. I'll take a gander at it when I get time.

You could try using access point mode for the Duet. This creates a access point on the Duet that you connect to directly from your control device.

https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M589_Configure_access_point_parameters

You can try unplugging the paneldue as well when using just USB power just in case the extra power draw from the panel is causing issues.

The results of M122 would be helpful.

Can you also provide the results of sending

M552
M552 S-1
M552 S0
M552 S1
M587