So after ordering and receiving a Duet Maestro V1 from Filastruder during their Duet Discount flash sale a few weeks back, I ran into a strange issue setting up the board yesterday. I generated a configuration from the RepRapFirmware Configuration webpage and put it on the SD card. Turned on the machine, it connected once for less than a minute and then wouldn't connect again.
Went back and forth changing small items in config.g and ended up with some strange behaviour that may be a minor bug in the settings.
On my (4) existing Duet 0.8.5 boards, each one had to use M540 to set unique mac addresses despite them having different static IP addresses. If I left M540 out of their config.g, as long as only (1) Duet 0.8.5 was online they would work fine, but the moment I turned on a second Duet 0.8.5 neither would communicate. So based on that experience, I assumed I would have to have the M540 on the Duet Maestro board with it's own unique identifier as well. This is where the bug begins.
I noticed the Duet Maestro board would power-up and the display on the Ender-5 worked, had menus, etc... so I could tell the board was functional. However, it would not load the DWC page nor would it respond to a ping from a network device. I could connect to it with the USB cable and user Pronterface to interface with the Duet Maestro. I went down various paths, using M552 to set IP addresses even to the point of setting it to 0.0.0.0 for DHCP. Using Pronterface over USB, M552 S1 P0.0.0.0 would indeed get an IP address from my network DHCP server, but still wouldn't respond to ping or connect to the DWC either. Everything within Pronterface over USB said the Ethernet card was enabled, working, had IP address, but nothing outside could connect to the Duet Maestro over Ethernet.
Re-reading the GCode section for M540, I noticed the comment about the default MAC address on a Duet 2 Ethernet is generated from the unique processor ID so there is normally no need to change it. That had me wondering about the Duet Maestro, so I removed my M540 from the config.g and rebooted the Duet Maestro.
Bang, everything worked like expected. It responded to ping on the network, it loaded the DWC page no problems.
It appears there may be a bug or issue with the latest firmware on the Duet Maestro not communicating properly if the config.g has something defined in M540. Without M540, it works no problem. With M540, the board thinks its working but nothing can connect to it from the outside. Had it not been for my experiences with the Duet 0.8.5 boards I probably would have left the M540 command out of my Duet Maestro config.g file, but it appears there may be a minor issue with it on the Duet Maestro.
I have not checked to see if the Duet Maestro has any issues online when the (4) Duet 0.8.5 boards are online too. It was rather late when I discovered the issue with M540 on the Duet Maestro. I'll continue the test with all (5) Duet boards on the same network later tonight.