Thanks to everyone who has followed my initial conversation with F4f and offered helpful advice and suggestions, and encouragement. It is much appreciated.
I think IRM have done a great job supplying us with the A Class loco and the decoders. I'm relatively new to DCC but not to the hobby as a whole. I expect some of you are experienced DCC operators. As a new DCC operator, my requirements are for an A Class loco with configurable motor performance, sound palette, and lighting. A few pennies have dropped overnight and I now realise that I don't want to hear the engine sound immediately after track power up, or see lights coming on. That is not realistic. I want to have a start up sequence, initiated using a function key. I want to have control of brake sound, horn, lights etc. I expect some of you have already done this and are wondering why I'm stuck "at the beginning". We'll it's usually a very good place to start. I'm learning as I go.
I will continue to experiment with my Digitrax DCS52. I will purchase a Lokprogrammer in the near future, and install DecoderPro software.
Regarding the A Class sound decoder, from a technical perspective - my understanding is that the IRM 1123 sound decoder uses the ESU LokSound 5 platform, which is a "Leerdecoder ohne Sound", meaning an empty decoder without sound. The 1123 package includes a "sound project" for a Crossley engine. As far as I know, the 1123 is not supplied with any user instructions regarding how to use the sound project audio in a user application. So perhaps this is where the experienced DCC operator comes in, or an experienced DCC programmer. Perhaps there are some Youtube videos on this subject. For me this is an interesting area to get into. As I've already said, I want to have a start up sequence, a shut down sequence, initiated using function keys. I want to have control of brake sound, horn, lights etc.
From a technical perspective - if I was to attempt a reset of a 1123 decoder, I think I would need to make a back up copy of the sound project, which I could probably do if I had produced it myself. Doing a reset will return the decoder back to ESU factory default values, and.....unless the sound project is protected, the reset could result in the decoder defaulting to a generic sound project. Perhaps the Lokprogrammer can safeguard against this happening. If anyone can confirm this, I would appreciate their input. I think this is an important point.