Thx for the link of the DWC 2.1.1 update, @droftarts

The Extrusion Control is now working.

@aego
Bearer you are right, I did not check the Erase all, Lock, and Boot from flash boxes. My failure to read the instructions quickly. Again sorry and thank you, thank you very much

Thanks much for reply, I wait for version RRF 3.02 🙂
Its super HW for control 3D printers.

Lada

@Alucardi said in Migrating to from 2.05.1 to 3.0 need help:

@Danal I want to be able to update if there is a upgrade that I want. Going to 3.0 saves me the trouble next time I want an upgrade.

Understood. My phrasing was poor. I was trying to encourage RC4 or 5.

@droftarts Join the club, I mostly fall in the even a blind squirrel finds a nut once in a while category : )

If you post a link to the online stuff I'm sure someone can nudge you in the right direction though

Ok, after successfully reinstalling firmware, I was able to connect to board with YAT via USB. After some debugging I created new configuration and web interface on new SD card - just to be sure (provided one was missing most of the files).

And BAM, DWC is present, now I can work from here.

@Stephen6309 Which one?

All okay, many thanks

@pro3d said in Endstops not working after FW upgrade to 3.01-RC4:

@droftarts

I am sure I was on RRF 3-RC3 stable so it was very weird. I did now do the config tool to get all the latest parameters and everything should be good - except temp issue somehow out of order. I made a new fan shroud and will do more testing

RRF 3.0 created some default endstops and fans, to try to smooth the upgrade path from RRF2. But that caused issue for some users. So as described in the upgrade notes for 3.01beta1, in RRF 3.01 no default devices are created:

If upgrading a Duet WiFi/Ethernet/Maestro from the 3.0 release, note that default fans are no longer created. Unless your config.g file already used M950 to create the fans explicitly, add commands M950 F0 C"fan0", M950 F1 C"fan1" and M950 F2 C"fan2" to config.g before your M106 commands. Likewise, default endstop switches are not set up, so you will need to set up X and Y endstops (and Z if needed) explicitly, using one M574 line for each, and specifying the port name. Example: M574 X1 S1 P"xstop".

@bearer ,Now it works perfectly, thanks a lot for the explanation

A closing update: I had the DHCP pool of IP numbers overlapping the statically assigned IP numbers so the router remembered what IP number was previously assigned. Once that configuration error was corrected, DHCP IP addresses were correct.
I still have the 0.0.0.0 entry which is now pointing to an Epson printer. I have no idea what the story there is but it has nothing to do with the Duet so I am closing this thread out.
Unfortunately, I have no idea what really was happening but I will set up the macros as suggested by Phaedrux - thanks!

Yes that's normal. The Duet wifi 1 was renamed to Duet 2 Wifi to allow more differentiation from the older Duet 0.6 boards.

There is: Duet 2 Wifi, Duet 2 Ethernet, Duet 2 Maestro, Duet 3 6HC.

When you updated the firmware, it started using the new name. Nothing else has changed other than what's new and different in the firmware.

If M291 is essential to you, unfortunately yes.

There is a major upgrade to DSF due later this month, which may include M291 support.

Hat geklappt, danke!!
Habe gemacht, die Datei in das Verzeichnis sys kopiert, dann auf FW 2-04 aktualisiert, dannach erst auf 2.05 - diesmal gab es keine Fehlermeldungen, danke. Habe dann festgestellt, dass die WebControl doch wieder zurückgesprungen ist auf 2.0.4, habe das auch nochmal auf 2.0.7 upgedatet, jetzt scheint es alles zu stimmen, supper, danke an alle beteiligte. Habe zwar nicht verstanden, was die Ursache war, aber Ergebniss ist so, wie gewünscht!

It worked, thanks !!
Did that, copied the file into the sys directory, then updated it to FW 2-04, then only to 2.05 - this time there were no error messages, thanks. Then I found out that the WebControl jumped back to 2.0.4, updated it to 2.0.7, now everything seems to be right, supper, thanks to everyone involved. Didn't understand what was the cause, but the result is as desired!

When you run M584 without parameters, what does it report?

When you send M98 P"config.g" are there any error messages?

In your config.g your G31 command is missing the XYZ offsets.

G31 X0 Y0 Z0

You'll need those for accurate probing results.

https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe

M584 X2 Y0:1 Z5:6 E3
Are you sure these are the correct driver assignments? You don't mention what board you're using, or what firmware version.

Your homeall looks to have some errors. First you're not using the z probe for homing.

G91 ; relative positioning G1 H2 Z10 F1800 ; опустить стол на __мм G1 H1 X-1000 Y-1000 F2400 ; X - домой G1 H2 X20 F1800 ;G1 H1 Y-1000 F2400 G1 H1 Z-1000 F1800 ; move Z down stopping at the endstop G90 ; absolute positioning G92 Z0 ; set Z position to axis minimum (you may want to adjust this) G92 X0

Are you sure you want to force the position of the X axis to be 0 at the end of homeall?

Hi David!
And thank you so much! Its not so clear what one should choose, but maybe there isnt many left off us using the older boards...
Grateful for fast reply!

ok..solved the Homing Problem...checked it several times that i choosed the active high endstops but in config.g they were active low...
Holy sh?* my first config after i bought the duet wifi was so easy compared to bring my Delta back to live now

Hey Danal, Thanks a ton! I'm back up... I had to step the wifi server version back, then I could connect again. Sometimes it's really nice to have a second set of eyes... The Ol' brain shuts off when I'm under pressure. I really sincerely appreciate you sparing me the obligatory lectures, and just saying "Dude! Do this!" I'll be sure to do my homework before hopping firmware versions again... Cheers!

It works.
The issue was the copy I initially downloaded, it might have been corrupted. Everything looked good [write, verify] up to the reset point, the board stopped communicating.
Thank you