also, are you using an asus wifi router. ive had issues with mine at first and had to turn off a few settings. it was a nitemare to find. I think there is an app or something out there to "find all duets on my network".. might hunt for that.

Post your config.g and homall. You slicer start gcode. The results of M122 and the gcode file that won't print. Without that we're just guessing.

@Phaedrux said in DWC does not update Height Map:

It should be either FW 2.05.1 and DWC 2.0.7 for RRF2,

@comobileoutfitters Try updating to this combo.

Basically just upload this zip file as is to the /sys folder in DWC.

https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip

@tekstyle said in naming is off:

@T3P3Tony yes that worked!! thank you so much.

And if you desire you can use spaces:
01 My Macro 1
02 My Macro 2
03 My Macro 3

Frederick

@bearer said in "DCS is not started" error - Duet3:

just out of curiosity, was this with the same usb cable you succeeded with in the end?

no, I belive that was a different cable and the "non working USB-port".

(It worked when I used a different USB - port. At first I used the port on the backside of my Keyboard (I use a "Corsair K70 LUX"), that woked with the duet2, but not with the 3! In the end, I plugged the duet directly into the front of my PC and using the included cable from the duet2!)

@bearer said in "DCS is not started" error - Duet3:

when you get a new duet with a pre 3.0 it will break compatibility with dsf without either manually updating to 3.0 before using apt upgrade, or use bossa or sam-ba after apt upgrades to 3.1.1. shame this isn't highlighted better.
too bad about the series of unfortunate events sort of speak, but glad you got it sorted in the end

I didn´t kwon that unfortunately...
But now everything works, and I have some more knowlage for next time 👍 😀

Thanks again for your help!

Unfortunately I am still very much in 3D printer land, so I sort of want to have my cake and eat it too! Looking forward to a new version of DWC though.

Excellent its up and running again. Many thanks for your guidance.

What did you have in there that was throwing it for a loop?

@dc42 thanks david, i totally forgot that it is 3.3v, i connect to exp.heater5 and gnd, that was my mistake. is there a pin on the expansion post to turn on the leds without the use of expansion?

@bearer Excellent. It's a start. With that at least I can put it behind the haproxy Octoprint is using itself. Thanks!

It fixed it 🙂 cheers!

@fcwilt
thanks!

Heh, I guess so. Weird. I thought I updated everything correctly when I set this up a week ago, but I guess the DWC is still ancient.

Stand by...

Thank you

You are right; it is definitely related to something in the Pi.
I have a few of them... 2's 3's and 4's. I had been using a Pi 3 B+ as the SBC, mainly because it appears to have been used in it's development. So yesterday, just for grins, I pulled the Pi 3 and install a Pi 4 (4GB) in its place.

It works perfectly.

@bot Thanks bot!

What's happening is probably that you have Kapersky Anti Virus on your PC. For some reason it makes OCSP-over-HTTP requests to the Duet. This means that the requested filename is extremely long, like a virus attempting a buffer overflow attack.

In firmware 3.1.1 the warning is suppressed if the filename looks like an OCSP request.

@BlueSandbox with T0 you select tool 0, with T1 you select tool 1. Most often the slicer does this, and often the T0 is selected at the end of the config.g

Glad that helped. Now that you're current with 2.05.1 it's time to start considering the move to RRF3.