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

@janjoh please try the new firmware at https://www.dropbox.com/scl/fo/p0136wx04h8xf6ejwdnn9/h?rlkey=efrfwyb6o5tqid11gustz3uvy&dl=0 and use the new K parameter in your M950 command that defines the fan connection.

@chrishamm Thank you, it may be possible then, with some luck 🙂
I will do some experiments to see how far I get.

@chrishamm Thx for your reply, I have started already. I forked the repo on GH and created a branch for the translation off of v3.5-dev as I wanted to compile it and see how it looks.

It is pretty usable already at this point, but there are still a lot of strings to go, I'd say it is 75% complete. Unfortunately I can't test everything as I do not have everything on my machine, but I'll try to do my best.

Btw, this is the first time I have seen the 3D G-Code viewer, this webapp is seriously sophisticated now, I love it! Thank you for your and every contributor's work! 😉 👍

@tylersuard said in SOLUTION: Can't connect to Duet Web Control:

3.5.0-beta.4

@tylersuard said in SOLUTION: Can't connect to Duet Web Control:

= WiFi =
Interface state: active
Module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
Firmware version 1.26

Your firmware is quite out of date and there is a new branch of wifi firmware that may work better for you. I suggest you update.

https://github.com/Duet3D/RepRapFirmware/releases/tag/3.5.0-rc.3

You'll need Duet3Firmware_Mini5plus.uf2, and DuetWiFiServer.bin. And you'll need to manually replace the DWC files in the WWW folder with the files from DuetWebControl-SD.zip.

It would also be useful to know if you have the same issues with the 3.4.6 release.

https://github.com/Duet3D/RepRapFirmware/releases/tag/3.4.6

@ErlerPrint3D you can use Node-Red with @MintyTrebor fantastic set of nodes. https://flows.nodered.org/node/node-red-contrib-dsfnode
The data can then be fed into influxdb and visualised with grafana. This can also easily be ran on a raspberry pi on the network.
If you are going to run node-red on a pi, I suggest using this script to install it https://tech.scargill.net/the-script/ It'll also handle the install of grafana and influxdb

Thank you, that's what i've done, and now it works great

@janholtz said in DWC not loading on iPad:

Here's a trick I use to keep using my old iPad 3:

Have a windows machine / VM that can access the DWC - I use Chrome Enable Remote access on that machine Install one of the few RDP clients that still run on the old iPad (I use iFreeRDP) Follow these instructions to create a kiosk mode chrome session to DWC from the Windows Box:
https://dandelion-burdock.com/articles/chrome-kiosk-mode ? Profit!

For sh!ts and giggles I just created a new instance on Lubunu with xrdp, of you dont want to pay the Windows tax.

After Lubuntu install, create a dedicated duet user. sudo apt install xrdp search & install google chrome ( I REALLY would like to use firefox, but the resource usage inevitably gets out of hand) edit .xsession when logged in as duet :
add: exec /usr/bin/google-chrome --kiosk "http://192.168.1.8" (pease note 192.168.1.8 is MY duets IP address, yours will be different)

Frankly it looks better than the windows solution ...

Oh, enable the onscreen keyboard plugin if you ever want to enter gcode

Jan

@azs123 Update: I used linux to build DWC and it worked like a charm.

@jay_s_uk

Wow, DWC feels now MUCH more responsive!

Thank you!!!

Let's hope that will solve the 2nd issue too.

@DavidG_68kg_PLA No problem, I'll try to have it up this week/weekend ☺️

@Honey_Badger357 What version of Windows are you using? What part of the instructions isn't working for you?

... open Device Manager by pressing Windows Key + R and type devmgmt.msc, or launch from the Start menu by typing "Device Manager". On Windows 10, you can right-click on the Start icon and click on "Device Manager". Look for ... any "Generic USB" devices, which would indicate that the Duet driver is not installed. If a USB device does show ... as a Generic USB device, right click on the device. Click Install Driver and browse to the location of the driver that was downloaded at the beginning of this step. Continue setup by clicking "Next" until the device driver has been installed.

Ian

@dc42 The filename would be already very helpful.

https://forum.duet3d.com/post/332495

I would not expect that there are tons of duplicate file names in real live. And it would be acceptable to go trough 5 files. But going trough more than 50 is a nightmare. And I had the problem that RRF was complaining about spaces and widespaces in one line. There is almost no way to grep for that. A "debug mode" maybe? You can free up some memory by dropping a lot of things, I guess that 90% of the problems appear before the actual g-code gets executed. So why not simulating the entire process with more debug info?

Or just store the filename in a variable and print it out with the error message. Just something which gives us a better hind. I add M118s to every file at the moment to trace down the location of the "typo".

Cheers, Chriss

You'd need to type and hit enter on each field for the new temp to be applied. if you do this while the heater is still heating up, the update may show with a delay.

@India if you want this behaviour on all builds ran on this specific machine add it to your config file. You could also add it to the custom gcode your chosen slicer puts at the beginning of a build file.

Read through the detail for M669 here:

https://docs.duet3d.com/en/User_manual/Reference/Gcodes

@dc42, 3.5.0-rc.1
I will upgrade to rc2 later today to see what happens.

@fcwilt

Thanks appreciate the help.

@LeeElms

Lee, I am not very familiar with its use but I believe M118 can be used for that purpose. You can also use the "echo" command in macros to sent messages to the console as he macros progress. No G code required and no parameters required. just add a line "echo "sending note to console"" and when it is read in the macro it will be sent. The following example is my current deployprobe.g file. Hope that helps.

M564 S0 ; let travel outside print zone if sensors.probes[0].value[0] == 0 ; if sensor is value ia 0 do this, 0 = probe attached echo "Probe already attached" if sensors.probes[0].value[0] == 1000 ; if sensor is 1000 do this, 1000 = probe detached G1 X53 F20000 ; X position of klicky dock G1 Y347 F20000 ; Y position of klicky dock M400 G1 Y175 F12000 ; slide out of dock return to bed Y center G1 X175 F12000 ; slide out of dock return to bed X center M400 ; wait for moves to finish if sensors.probes[0].value[0] == 1000 ;Check to see if probe is attached 1000 = not attached G1 X175 Y175 F10000 abort "Attach probe FAILED!" else echo "Attach Probe Successfull" M564 S1