As a C & C++ programmer from around 1976 I'd love to see the Kernighan and Ritchie style with { } syntax. I hate Python indention style.
Just my opinion since you asked.

Well I found my issue but I'm not sure how I did it. There was, indeed, a typo in the PanelDueFirmware.bin. Somehow I managed to get a leading space or some unprintable character before the P. I can't reproduce adding a leading space as both RRF and Windows will remove a leading space. I didn't notice it in the DWC but when I looked at the card in Windows the filename was shifted one position right.

Sorry for the false alarm.

Is it possible for the DWC to ask for confirmation for some buttons while the printer is printing? I just shot myself in the foot. I now have both printers running on Duets so I have two web pages open to control them. While one printer was 3 hours into a print I got distracted and clicked home all on the wrong page and screwed up the print. It was my fault but if the DWC can know the printer is printing a "Are you sure?" prompt would be helpful.

@Joel I've got the same issue with V5 being able to only run on one PC at a time. The "must uninstall" message is very misleading.
You do not need to uninstall but "Deactivate Product" under the Help menu. You can then run V5 on the otherPC. When you have two PCs for printing on two different levels in the house and forget to deactivate one it's a pain.

They offer a floating license for $199.00 that will allow you to just quit the application and restart on another PC but still one at a time. To me it's ludicrous for them to charge $199 for what I already had in V4.

I've got a few more days to decide to get a refund and I may do it just because of this licensing change.

Thanks again. Coming from Marlin I'm still getting used to all this run time flexibility. I should have moved from Marlin long ago.

OK, I have not yet tried to move back down to 3.1.1 but since I saw that 3.2.0-beta2 was released I thought I'd try it. Mixed results.
Here's the results with various browsers

Chrome 64 bit 85.0.4183.121
Still does not automatically update the graphic when you click on heightmap. If you manually reload the page you now see the updated map. I no longer get the "cannot read..." error message. So, an improvement.

Firefox 64 bit 71.0
When you click heightmap you see a flash of the graphic and then nothing. If you click on the "invert z coordinates" the map graph is then displayed. You still need to reload the page to see the updated graphic.

Brave 64 bit 1.18.84 Basically the same as Firefox.

Edge 64 bit 85.0.564.68 Basically the same as Chrome

Internet Explorer 64 bit 11.508.19041.0
This is interesting in that it never shows any DWC page. All you see is a blank page.

This is all on Windows Pro version 2004 64 bit with all updates as of this afternoon.

I'll try 3.1 but I don't expect any change.

@fcwilt Yeah, I can agree with you on C++. I'd rather stick with straight C as most of my experience was with windows device drivers. In any case, it's better than Python.

@fcwilt I don't know what the status of Shapeways is but I've been using https://www.jawstec.com/ for some SLA parts.

Got both my cartesian (Maestro) and delta(Duet Ethernet) running on 3.0RC1 with no issues other than those that were self inflicted. I don't have any specific printing requirements right now so I've just been printing calibration stuff and Benchys but all is working well. Thanks guys for all the work.

OK, if the checkbox in S3D is unchecked is it not going to produce absolute extruder moves and if there is an M83 in config,g is the printer not going to expect relative moves?
Maybe this doesn't work as I thought.

Answered my own question. I didn't realize that S3D would output the M82 as a result of the checkbox. Learned something new.

@fcwilt I don't know what the status of Shapeways is but I've been using https://www.jawstec.com/ for some SLA parts.

@dc42 For what it's worth the two prints that gave me the Code 2 error printed just fine with this firmware, Thanks.

@T3P3Tony I updated to the most recent +3 and on my first print it failed with a message on the console.
Error: Code 2 move error: info=-0.00195, seg: s=2467229762 t=11130 d=-29.00 u=-3.1414e-3 a=9.6290e-8 f=09

M122 included
console (1).txt

Edited to add a second attempt to print:
Error: Code 2 move error: info=-0.00195, seg: s=2255125801 t=11176 d=-25.00 u=-2.6995e-3 a=8.2784e-8 f=08

Edited to add that I reverted back to 3.60beta3+1 and the Code 2 errors have gone away.

@timschneider
Is it possible you have a variation of my problem which has been solver?

https://forum.duet3d.com/topic/37329/3-6-0-beta-3-duet-2-issues-lost-communication/3

@dc42
Bingo! DWC comm is back. I had to pull the printer apart to get to the Duet so I can't try a print for a while. Thank you for the quick response.

@droftarts
Here is the beta 2 M122
Beta2M122.txt

@droftarts
I'd like to include the M122 output but I can't. When I issue M122 I get no text on TeraTerm for about 15 seconds then the board reboots.
If I issue M115 I immediately get the board name and firmware version.
So something is running.

@dc42
Here's the config file. Last changed on 8/24.

config.g

@droftarts

New results. With beta.3 I can get results from M115 but M122 just hangs for maybe 15 seconds then the Duet reboots. I did have a recent Duet2_SDiap32_WiFiEth.bin but I noticed that the 3.54 release area had a few hours old version so I put it on the SD card. No change. I'm hardwired so no wifi in use. I'm back to beta.2 via bossa and M122 works fine.

Are there known instances of stand alone duet2 boards working with this release?

@droftarts

A little more info. I pulled the SD card and copied 3.6.0-beta.2 into the firmware directory. No matter how many time I ran M997 S0 on reboot it aways reported 3.6.0-beta.3 when I entered M115 and there is no DWC connection. I did an erase and used bossa to write the beta.2. file. On boot M115 reports 3.6.0-beta.2 and I have a DWC connection. I then used the system update from DWC to update again to beta.3. Same results with no DWC connection.

So something is awry with either the duet2combinedfirmware.bin file or my system. I didn't see anything obvious in the release notes that I need to update anything else first.

I'm away for some time but I'll try any tests later today.