Subject: Help! CS3+ seems to be changing my turnout addresses when I add mfx devices

Hi everyone,

I’m getting confused about how mfx and Motorola/MM addresses interact on the CS3+.
Here’s what happened:

I programmed all my turnouts manually on the CS3+ and noted their MM addresses.

Yesterday I added a batch of new signals and let the CS3+ search for mfx devices.

The search completed—but the CS3+ also “found” a bunch of my existing turnouts even though none of them were set up for mfx.

After that, several of those turnouts stopped responding to their original manual (MM) addresses. It looks like the CS3+ overwrote them with new mfx IDs.

Has anyone else run into this?
Clearly I’m misunderstanding something about how to configure mixed mfx/MM systems. Any tips on:

Preventing the CS3+ from re-identifying MM accessories as mfx

Restoring the original addresses without deleting and re-adding everything

Thanks in advance!

— Thorben

Hi Jean,

I appreciate your detailed explanation regarding the MFX protocol and its interaction with the CS3. Unfortunately, I learned the hard way about the implications of using the "Find MFX Accessory Decoders" function.

After setting up over 70 turnouts manually with specific addresses for integration with TrainController, I decided to experiment with a few signals using MFX. Activating the MFX discovery function resulted in the CS3 reassigning addresses to all my accessory decoders, including the turnouts. Consequently, TrainController no longer recognizes the turnouts, as their addresses have changed.

Now, I'm faced with the daunting task of manually identifying and reprogramming each turnout's address. This process requires two people: one to operate the CS3 and another to observe the physical turnout responses. It's a time-consuming endeavor that will take several days to complete.

While I understand the advantages of MFX's automatic address assignment, this experience has highlighted the importance of cautious use, especially when integrating with external control software like TrainController. In the future, I'll adhere strictly to manual address assignments and avoid using the MFX discovery function to prevent such disruptions.

Best regards,
Thorben

You make a good point that using other software can cause problems. I just use the CS3 and the decoders register themselves for turnouts etc with no problems.
Running our railways are as simple or as difficult as you want to make it and I just let Marklin work as it should and rarely have a problem. You can expand the hobby using other brands of software which in itself is a hobby and can be an added interest.

What if the dip switches on all the devices (where possible) are set to DCC? Would that preclude that the search for mfx articles could change anything on them?

It's too late. MFX have already reprogammed all turnouts. I got a solution from ChatGPT and it is to delete all the entries that MFX found, then it should go back to the old address. I will try that and let you know the result.

Regards Thorben