Happy to report that I was able to flash all six PanelDues (four V2s & two V3s), and I'll accept user error. Let me explain what I did as I know others will likely fall into the same trap I did. I installed BOSSA like normal which includes the baked-in CDC driver. The port doesn't show up in Device Manager just yet. Plug in the PanelDue and the BOSSA Driver still doesn't show up yet. The instructions say to press the erase button. Well, I hadn't held the button long enough apparently. Windows will eventually detect and then you will see the BOSSA driver appear in the device manager. I may have figured this out sooner had I left the PanelDue plugged into the screen, but since I'm using a 7" screen, I was concerned about power - there was nothing wrong with having it plugged in, and it went black as it states in the instructions. Now to plug back into the printers and see the fruits of my labor suffering.

@Sgt-G-294 Can't hurt to reflash. Now, it should be mentioned that I performed the incremental upgrade as noted which might be the issue here if you overlooked it.

Perhaps you need to reset the saved wifi profiles on the printer.

In my config.g, I have the following:

; Network
M552 S1                                            ; enable network
M586 P0 S1                                         ; enable HTTP
M586 P1 S0                                         ; disable FTP
M586 P2 S0                                         ; disable Telnet

I created the following macro files:

Wifi - Clear All (clears all saved profiles from memory)

M588 S"*"
G4 P1000
M587

Wifi - Set (creates a profile entry in memory)

M552 S0
G4 P5000
M587 S"myssid" P"mywifipassword"
G4 P1000
M587
M552 S1

Wifi - Cycle (when I'm having connectivity issues, I can cycle the wifi and reconnect)

M552 S0
G4 P5000
M587
M552 S1

Happy to report that I was able to flash all six PanelDues (four V2s & two V3s), and I'll accept user error. Let me explain what I did as I know others will likely fall into the same trap I did. I installed BOSSA like normal which includes the baked-in CDC driver. The port doesn't show up in Device Manager just yet. Plug in the PanelDue and the BOSSA Driver still doesn't show up yet. The instructions say to press the erase button. Well, I hadn't held the button long enough apparently. Windows will eventually detect and then you will see the BOSSA driver appear in the device manager. I may have figured this out sooner had I left the PanelDue plugged into the screen, but since I'm using a 7" screen, I was concerned about power - there was nothing wrong with having it plugged in, and it went black as it states in the instructions. Now to plug back into the printers and see the fruits of my labor suffering.

I have four PanelDue v2's. I'd like to still use them, but maybe I have to bite the bullet and upgrade them to v3's. I'm going to attempt upgrading through a Linux box and see if I can get anywhere with them. If that doesn't work, then maybe I'll try to put together a Win 7 box. I do wonder why the latest RRF broke the macro execution to start with. I could revert the four Duet boards firmware to a working version with the current firmware on the v2 PanelDues.

Time for normal maintenance of the machines with firmware, heatbreaks, fans, etc..., and I've noticed the macros don't work with the latest Duet firmware, so I thought maybe I should go through and update the firmware on the PDs. I have a mix of v2 and v3, no i's. I've since upgraded my PC and installed the latest BOSSA 1.9.1. CDC driver prompted for install; unfortunately, I don't see it in the Device Manager. I've tried the unsigned driver enable method, manual method - I've even tried 2 additional PCs to no avail on getting the BOSSA Program Port to start (Code 10). Anyone else run into this issue and resolve it?

I lowered my homing speed from 1800 to 1200 and that seemed to quiet down considerably. Perhaps some speed values cause some harmonics.

I picked up some .45 deg steppers for a delta printer upgrade. All seems to be fine keeping at 1/16 with interpolation enabled:

M350 X16 Y16 Z16 E16 I1;
M92 X320.00 Y320.00 Z320.00 E410.00;

I'm wondering if I should consider changing my settings, or even disabling interpolation given the resolution. Thoughts? They are a bit noisy when homing. I'm still calibrating and haven't tried printing anything yet.

So, my issue was the top mount I designed was too rigid causing noise. I've since modified the design and have it working on two of my machines now. Here's the writeup: https://www.thingiverse.com/thing:3192818

@peirof, what machine are you using?

@moriquendi I started with 2.02RC3, downgraded to 2.01 and then returned back to 2.02RC3 as it didn't seem to matter.