We had a similar problem with my friends PS2 engine. It would run on his layout but could not be found on my layout. We needed to delete the engine on the DCS remote and add it back in. No problem after that, but it does the same thing every time he brings it over. Haven’t figured this one out yet
Ron
This I can easily explain. Because PS2 uses a battery (or yes, you can use a super capacitor replacement) the point is, understanding how a DCS PS2 or PS3 board stores the address when you add engine. The board is running a microcontroller that boots up and reads from permanent storage all the settings. One of those settings is DCS ID. But, a microprocessor runs in RAM (Random Access Memory) which is NON-permanent storage and is lost if power is lost. So when you add engine, the remote or DCS app on a tablet queries the engine through the TIU, and they negotiate a free ID address in your total list of DCS engines 1-98, then BOTH the remote (or app) and the engine store the new updated ID. But the catch22, that is in RAM because you are in a running state of the microcontroller. The firmware has a routine that only saves all the settings from RAM to more permanent storage at shutdown- meaning power loss on the track, and firmware completes an orderly shutdown sequence- all powered by the BCR (super cap(s)) or battery.
Again, whenever you see this where you can add an engine for a session, and it works and runs, but if power is lost to the track, and then you power back up the track and DCS cannot find that engine ID (not on track) but you add the engine again and it increments up and ID- then we begin to suspect this battery backup power system is not functioning (both charging and then later using the charged battery or super cap to power the electronics). This is because the new updated just added ID as part of the add engine process only happened in RAM and is lost when track power is dropped and the system fails to write that data and settings to storage. The next time it boots up, it keeps using the old previous ID that doesn't match the one saved in the remote.
In a nutshell, #1 inspect and know the state of your battery or BCR, and #2 perform the power loss sequence to see if sounds continue after power is dropped. If sounds cut off instantly- then your BCR or Battery subsystem is not properly functioning.