This time I'm stumped!

The problem is if I run a member engine of the lashup on its own,  and then make it inactive and once again make the lashup active, all settings including the volumes, etc revert back to the factory settings

By any chance, are you starting up the member engine before shutting down the lashup? if so, that's a no-no.

You don't mention what engines your using in the lashup. Regardless, in beta testing and after, the way I successfully altered lashup settings in the member engines is as follows:

• Startup the lashup
• Locate each of the lashup's member engines and ensure that they are all in the Active Engine List
• Bring the member engine whose settings you want to modify into the remote's window. Do not press startup!
• Modify whatever settings you like
• Repeat for any other member engines whose lashup settings you want to modify
• Reselect the lashup, making sure that all member engines are in the Active Engine list, not the Inactive Engine List
• Press the lashup's FSV soft key
• Shut down the lashup. This should lock-in the changed lashup settings. Just to be sure, you could also turn off track power.

Do not intentionally make either the lashup or any of its member engines Inactive. Let DCS decide what engines should be made inactive, as well as when they should be made so.

Barry,  thank you for the quick reply.  FYI per your reply,  My lashup consists of one proto 2 dash 8and one  proto 3 dash 9 and one proto 3 SD70ACE.  I will follow the steps you outlined and give it another try.  Once again thanks for taking the time to quickly answer. 

Have a blessed  day...

N S Scale

Barry, I tried each step that you listed, but the settings still change upon shutting down the lashup, then starting a member engine on its on, shutting that particular member engine down and restarting the lashup with that member engine now on board.  In fact to make things less complicated, I created a lashup using two Mth PS2 Gensets and I was met with the same results. This new version seems to be acting no different than 4.20.  I was wondering  if there could possibly be problems with the remote, although all other functions appear to work just fine. I will continue to test and maybe reload the remote with the new upgrade.  Thanks again.

Dave...

NS Scale

This has consistently worked for me throughout the beta test and with the final 2.30 release. The rules are as follows:

• When you change a member engines settings while the lashup is active and without starting up the member engine, those settings should remain with the lashup and not be in place for the member engine when it is subsequently started up after the lashup has been shut down.
• Conversely, any changes to the member engine that are made after it has been started up remain with the member engine and do not transfer to the lashup. 

Two questions:

• Which of the above isn't behaving for you? Be specific as regards how each member engine and  the lashup itself are being affected.
• Is the battery in the PS2 engine fully charged?

In answer to your question, both.  In other words,  neither as lashup or single member engine are the saved(?) settings being retained.  Two of the engines in the first lashup I mentioned were PS3 engines so or course no batteries involved.  All PS2 engine batteries check OK per remote info screen.  To make myself more clear, if I set up a lashup, the lashup settings are retained,  that is, as long as it stays as a lashup.  When a member engine is brought out of the lashup to run as a single engine its original single engine settings are lost.  When placed back into the lashup,  all the settings in all of those lashup engines are lost, and revert back to vol 100, bell 100 horn 100 etc.  Fyi, I usually set the master volume on the remote to 100, and then adjust each individual engine down to a more scale sounding volume.  Just thought I would mention that in case it may have some effect on the toggling action being produced from the memory of the remote.

Dave...

NS Scale

When a member engine is brought out of the lashup to run as a single engine its original single engine settings are lost

Two questions:

• Are you doing this while the lashup is still active, i.e., started up and not shut down?
• Are you deleting the lashup and then rebuilding it?

I am monitoring this post closely as i have identical symptoms with my MU's..although i did not know you should leave member engines in the active list to maintain settings in MU. I tried this after several days away from my trains and MU settings stayed. I am still 4.2.

The answer would be "no" in both instances.  Barry I shut down the lashup, then select a member engine, which by this time DCS has placed on the inactive list.  Upon starting the single member engine all volumes on the single member engine are back to 100, ditch light settings have changed, etc.  Even when making sure all engines are in the active list, and upon selecting the lashup, once again.  all settings that I made for all lashup members have changed.  As I said before,  it is performing as 4.20 which did not have the new FSV soft key and the ability per MTH instructions to send and save those lashup settings.  I thought perhaps one day when I can get my hands on another remote I will see if the one I have may have a problem, as when I depress the FSV softkey the remote displays that it is indeed saving lashup settings for the particular lashup.  At this point in time I just have to  re-enter the lashup settings and the single member settings if  I decide to temporarily  pull that member engine out of lashup service.

Dave....

NS SCALE

Dave,

Try the following two tests and post your results.

Test #1

Barry, I tried the above steps, without success.  I did notice one time when switching back to each member engine the two volumes were like 31 and 32 instead of the normal setting of 30 and 30 respectively.  this may be an issue in the remote. For right now I am going to live with it, but do really appreciate all the time you spent trying to help.

Maybe if others report this problem MTH may find a fix, or like I said before it just may be a hardware problem on my system.  I will probably reload 4.30 again on the remote, just in case something funky happened to all those electrons when they were parking themselves.

Thanks again,

Dave.....

NS SCALE

Dave,

Maybe if others report this problem MTH may find a fix, or like I said before it just may be a hardware problem on my system

It's not you. I've duplicated it with the 4.31 beta. It'll be worked until resolved. However, I can't say exactly when that will be. It all depends on how soon MTH's developer can figure out what to correct, and then correct it.