upgrade 3.3 stabe to 3.4 stable
-
hello
I have updated my Duet 3 Mainboard 6HC from version 3.1.1 to the actual 3.2 . 3.3 all okk always without problems via DWC web interface , from version 3.3 to version 3.4 stable ... everything loads correctly, is asked to update .. and after a few seconds resets as usual, but does not restart, I have to use bossa to be able to reinstall the firmware version 3.3 version 3.4 or later does not want to accept it in any way
What can I do to try to update it ?
thanks
-
What do you mean by restart? Do you mean that DWC no longer connects to the board after reset following the update? Unless you have a static IP address assigned, it could be that as a coincidence, when you updated, your router reassigned a different IP address to the mac on the board.
If you are talking about the blue Install Update on the Machine-Specific tab when you say it asks to update... mine says that as well. It may be that as long as the ZIP file is present, that option is also present. That is my guess.
-
no the update seems to go well ...when the card resets at the end of the update, the web page should restart but it doesn't connect anymore, and it doesn't change the ip ...I have the control router and it doesn't turn out to be connected to anything and the printer doesn't respond to anything it remains black in the screen, it's as if the update didn't go well or as if the update beyond 3. 3 is not compatible, if I reinstall the firmware 3.3 I find myself with the web updated to 3.4 but I can't load the firmware even with the later versions it doesn't accept more than 3.3
-
[Duet 3 MB6HC in standalone mode] [Duet 3 Mini Ethernet in standalone mode] [Duet 2 Ethernet] The default MAC address will change in this release. This means that your router is likely to assign it a different IP address from the previous one. If you have a DHCP address reservation for the Duet configured in your router, you will need to update it for the new MAC address.
In 3.4 the MAC address generation has changed. Are you sure this isn't what happened to you?
If you connect via USB terminal after the update are you able to send commands and receive responses?
-
@phaedrux thanks for the reply I'll try Friday with the usb cable ... but even if the MAC address changes and this could be the problem since my router is set up with armoured macs, if the mac changes it is not enabled to the network, but I would still see it trying to access, which does not happen and in any case I set a fixed ip on the config.g and even if the mac changes it should keep the IP assigned by code, if this is not the case then it is a bug in the code that does not keep IP, i.e. I have not enabled DHCP
-
@lamerhouse, I ran into that at one point. I don't recall during which specific upgrade but it likely was the upgrade to 3.4. During the upgrade, the MAC address of the printer changes. The router, when keeping track of IP's, links the MAC id to whatever the assigned (fixed) IP is. When the printer starts up, the fixed IP can not be assigned to the printer due to the changed MAC address.
If I recall correctly, when my updated printer started up, a new / different IP address was assigned by the router. My computer is set up with bookmarks to go to the appropriate IP for the printer DWC. Since the IP had changed, when I clicked on the bookmark to go to the printer DWC, I could no longer connect.to the printer since a new IP had been assigned.
I went to the new IP in my browser, and got reconnected. I then went into my router, deleted the old fixed ip assignment and then linked the new MAC address to the previously used fixed IP. Once that was done, my original bookmarks in my browser worked as it did before.
I use a specific IP assignment scheme so I had to assign the new MAC address to the old fixed IP address - if you don't use a specific scheme for your IP addresses, you can just go into the router and link the new MAC address to a new (different) fixed IP (you can't assign the same IP for two different MAC addresses) -
@jens55 OK thanks for the answer I'll give it a try
-
@jens55 @Phaedrux ok it worked, thanks to your observation I found out that my router which is an enterprise, assigns not only the MAC but also a card ID, and for him the MAC should not change every change is an attempt of unauthorised entry and since the mac changed it put it in bad list, now everything worked .. thanks again
-
undefined dc42 marked this topic as a question
-
undefined dc42 has marked this topic as solved
