565 massively pre-dates any batch configuration tool, so there's no way it's going to respond to Mconfig. You'll struggle to batch process any config updates because it needs to be put into at least 3 configuration modes via the front panel and power switch before you can make the relevant settings - there's no global config receiving mode. It also has a rather restricted RS232 command set and no documentation as to the status of RS232 during any config mode, so it's going to be a bit of a lottery. That said, just hook it up and do the power switch thing and try using the MSR emulator in Mconfig just to see how far you get. If you're lucky it will respond to the right keys and give you screen feedback. I've not had a 565 for at least 10 years, but I don't remember config via the front panel as being more than a 10 minute job provided you had the planning worksheets in the manual filled in - at least in your head...
DSP3300, 3200 and DSW don't have any configuration settings at all, so there's no point in them having access to Mconfig. They have NV settings which are intended to be set by the SpeakerLink controller but which can be set via the terminal emulator in Mconfig. Hook one up and type NV? to get the status and make updates. Not sure about 5200 but there's no real reason for them to be different.
Julian
Lounge: G61RSL, DSP3200, DSP3300, DSW, HD621+Vertex2, SBT, Kef Ci160. Office: DSP33, D1500, SBT Archive: 568.2m, 562v3, 562v, DSP3100
|