Tried it today but failed to learn what I wanted
I have PAw connected to the Audio Panel via 3.5mm audio cable. SD connected to headset via Bluetooth (it should also connect to the Bluetooth Audio Panel, but I couldn't confirm that that worked)
Check PAw WiFi connect and Audio OK. Goto 192.168.1.1/configure and press 'Test' if you don't hear 'Pilotaware' (Audio Panel didn't have 'Music' selected (the PAw channel)). So no PAw sound.
Check SD Bluetooth connection successful, select new voice in SD (it then speaks so you can check setup) and make sure you hear it (My Bluetooth volume on headset was on minimum / 0). So no SD intelligent sound.
Mk1 eyeball still works! Conflict, 300ft above on climb out, flying 50 ft above ATZ on the runway track... I saw it later on the .trk file / aircrew.co.uk
Get someone else to operate aircraft while I operate the test
.trk file (from PAw) was useful. I saw what it picked up. Also saw most targets that were of interest were Mode C/S, therefore bearingless at the moment. SD wouldn't have warned for my 300ft conflict opposite direction overhead. That's not a criticism of SD, too early to tell, reduced warnings are a potentially great benefit. Other bearingless targets were dubious (echos?) or in the circuit (too many to be useful, Mk1 eyeball preferred)
Not what I intended to learn, but learning. I hope that's helpful to someone.