PS2 Premier Santa Fe GP30 will operate in conventional mode but not DCS

tiu n remote should be 6.1 software version. try it again on layout with 6.10 ! did the sounds last 7 to 10 seconds after power off maybe battery issue outherwise baatery problem with ps 2

Alan Mancus posted:

tiu n remote should be 6.1 software version. try it again on layout with 6.10 ! did the sounds last 7 to 10 seconds after power off maybe battery issue outherwise baatery problem with ps 2

Both the remote and the TIU 6.10 at  The one club.  At the one I am today both are 5.00. 

 I don’t think it could be the battery,  7 to 10 seconds after power off, the sounds shutdown normally.

If you try to add it and it can't be found, try the "Recover Lost Engine" function and see if that finds it.

gunrunnerjohn posted:

If you try to add it and it can't be found, try the "Recover Lost Engine" function and see if that finds it.

I tried it with the 5.00 system, I will try the 6.10 Recover engine function next time i’m at that club

that was a bug in the 5.0 version.

Tim,

Be aware that if you try to recover the engine, it must be while connected to TIU #1 only.

SDIV Tim posted:

20-2777-1 PS2 GP 30 Santa Fe Road Number 3233.

I ran it weeks ago on a club layout with 6.10. It ran normal. Today I took it to another club that has 5.00. The engine would power up normal conventionally, but when I tried to add it, “No Engine to add!” Came up. 

Runs normal in conventional mode but won’t respond or add to DCS. I had another PS3 engine and PS2 engine and they added without an issue. The sounds shut down normal and power up normal.

What can be causing this?

Sometimes, the remote thinks that the engine is already loaded. When I get this message, I place the engine back on the rails and power up. I then press the read. It will come up under a different name and I press start-up. If the engine starts, then I know what happened.

 I think a lot of times it's posted that the remote or the board scrambled the address, when in reality, it just that it's already in there!

Club type systems, should have specific rules for adding engines and keeping things straight. Otherwise, all sorts of issues can creep in.

As Joe mentioned you could have an engine  ID conflict. Engine ID s stick with the engine so it's possible the remote that  you used already had that ID taken...The fix,, Use a programming track with no other engines receiving power anywhere on the layout and a new ID should be created for the engine while adding.

Gregg posted:

As Joe mentioned you could have an engine  ID conflict. Engine ID s stick with the engine so it's possible the remote that  you used already had that ID taken...The fix,, Use a programming track with no other engines receiving power anywhere on the layout and a new ID should be created for the engine while adding.

maybe also keep addresses #1 thru 10 open for guest engines? or something like that?

When the user goes back home he'll need to delete and re-add the engine. So it could be cool to ID the address of any engine at a club before changing it. Then, at the end of the session, the ID could be returned so the user doesn't have to do anything later on.

 Maybe keep a chalk board chart of guest engines and addresses???