Large Scale Central

Airwire - Operating Question

I am slowly learning how to operate and program my new AirWire system that I installed into a USAT GP38.
I need help with this issue (and I cant find the answer in the 3-booklets that came with the system)

When I am operating the locomotive, the hand held remote has a automatic shut off time which can be adjusted (not a problem)
However, on my railway I am pretty much a set it and forget it runner. We just sit and watch our trains go in circles for hours on end.
The problem I have is when the hand held remote times out and shuts down, or, if I manually shut the controller down and power it back up, the locomotive will come to a stop.
Is there anyway to get the remote to remember the last controlled speed so this does not happen?

Thanks,
Vinny

I will be very interested in the answer to this question. I’ve had mine time out at just the wrong time at club meets!!!

JB?

I think it is a setting in the decoder, to keep running at last speed if no command is received.

DCC (which AirWire has pretty much cloned) was designed for track power, and as such, the “command station” constantly transmits the “speed command” to the loco at regular intervals.

In a battery powered system like AirWire, this would result in too much energy used, so the handhels shuts off, and thus the commands to “run at speed 60” stop.

I think there is a decoder setting though which says “keep running at last speed if you don’t hear another command”… this also has drawbacks, if you lose communication with the loco, you cannot control it, and it keeps going. Kind of like you took out the “dead mans switch” in the loco cab.

Greg

Greg, the locomotive will run at the speed I set it at even if the controller times out or I shut it off.
The problem is when you power the controller back up, it will automatically turn the locomotives speed to zero and stop the locomotive.

I cant find anything (at least not yet) that lets you avoid this from happening.

Greg, the AW is close to DCC but doesn’t have the constant memory of a DCC system. With AW you have to tell it to remember and to forget.

Vincent, first i apologize because i am terrible at describing this in text. I assume you are running the T5000? If so it all depends on how you want to operate your transmitter (TX). If to run a loco you use #LOCO# and just do direct operation then the loco is not in the memory bank and when the TX is shut down it loses what it was doing. You need to enter the loco in the memory of the TX.

Once you have your locos in the memory you bring them up with the loco memory button (blue top right corner). You scroll through the locos with the throttle knob and select the desired loco with the # enter/yes key (green bottom right corner).

Once your loco is chosen, operate as wanted. If you want to keep the loco doing the same thing while you change to another loco or just set the TX down, double click the loco/memory button. This locks the loco in in it’s current state. Turn the TX off, run another loco or 6 and the loco saved in memory will keep doing the same thing. I believe you can do this with up to 10 locos at a time.

READ THIS—> here’s the catch. When the loco is brought to a stop whenever you are done running it you make it remember that it is stopped by double clicking the loco/memory button when it is at zero speed steps. If not, when you bring the loco back up from memory it will remember the last thing you locked in. I found this out the hard way when I was programming sound. I set the loco on my workbench turned it on, then turned on the controller and the last program I set in it’s memory was speed step 40. Like a rocket it shot off the side…

If what i described doesn’t make sense PM me and we’ll exchange numbers and talk on the phone. Or, you can call Al at CVP and he’ll walk you through it. My description sounds overly complicated but it really isn’t.

Terry

Terry, thanks for the great info!
I need to read up in the manual about storing the locomotive in memory and that will correct my issue.

I kind of kept glancing at that in the manual but really didn’t pay to much attention to it because at the moment I only have the one locomotive that is battery powered.
I thought the controller would have saved / stored its last function before turning off, but apparently it does not do that.

I will figure it out now that I know what to read up on!
Thanks!

Great info Terry, I learned something more about this aspect of AW.

Thanks, Greg

Spot on Terry, Al could not have said it better.

The non memory part of the AW TX is about the only thing I really don’t care for about the system. Though, once you get the hang of it it’s simple and becomes a matter of habit.The only time it is really needed is if you are going to leave the loco to run on it’s own when you do other stuff like operate another loco or garden or enjoy a beverage. When we do ops I never use the feature because i never leave the loco or consist.

And Greg, yes there is a setting for the loco to shut down if it looses communication with the TX. If you don’t want it to shut down the setting is zero. However, if the controller shuts off the loco will do whatever it was last told to do, it wont shut down. So, when you turn the controller back on all speed steps that were not in memory are set to zero by default. By not saving the locos last functions the loco now thinks it should be stopped and will do so immediately. With heavy trains on a grade this is bad. Ask me how i know.

I am told that the TX and RX talk back and forth constantly. But a friend of mine who is far deeper into electronics than I ever want to be explained it more like this; The TX talks and the RX answers the RX never speaks on it’s own, if the TX quits talking the RX will just go on happily about its business until the TX tells it to do something else.

So, reread that last sentence and change TX to -wife- and RX to -husband- life by AW now makes perfect sense…

Terry

Steve Featherkile said:

I will be very interested in the answer to this question. I’ve had mine time out at just the wrong time at club meets!!!

JB?

Somehow, (And I forgot how) I set my Transmitter to never time out. It tells how in the down-loadable manual. I always carry a few extra AAA’s with me.

As to loco address; all mine are the same number. #1. I never rune more than one loco at a time so I’m comfortable with that. I’m still learning how to use the new AW Transmitter. I’m working a little on the Pheonix CV’s. (Changing sound with the motion of the loco, etc.)

John Bouck said:

Steve Featherkile said:

I will be very interested in the answer to this question. I’ve had mine time out at just the wrong time at club meets!!!

JB?

Somehow, (And I forgot how) I set my Transmitter to never time out. It tells how in the down-loadable manual. I always carry a few extra AAA’s with me.

As to loco address; all mine are the same number. #1. I never rune more than one loco at a time so I’m comfortable with that. I’m still learning how to use the new AW Transmitter. I’m working a little on the Pheonix CV’s. (Changing sound with the motion of the loco, etc.)

JB here is how you do it

AUTOSHUT OFF TIMER: This timer sets the duration
before the throttle automatically powers down. The timer range
is 1 minute to 9,999 minutes. The factory default is 15 minutes.
The throttle will not shut off if the active (not stored)
loco/consist speed is something other than zero. The timer is
paused until the speed is equal to zero. This prevents
inadvertent shut off while a train is in motion.
We recommend that the timer be set for a time that represents
the length of an average operating session.

Push MENU Twice than 5 set your min.

Aha! That’s how I did it. Thanks Richard.

At my age, I have to retrain myself every time I use the damn thing! :slight_smile:

Storing a loco in memory will not solve his problem. The transmitter will retain the speed step for a stored loco only as long as the transmitter is on. Once you turn it off and then back on and address the same stored loco the speed step will go to 0. If you address a ficticious loco before turning off the transmitter you can then turn it off and back on because at that point it will come up with the ficticious address. That would allow you to the start running another train but as soon as you bring up one that is still running it will go to speed 0 as before. I hope this wsan’t too confusing.

Paul, will the Tx time itself out if it looses link with the Rx? I think that is what happened to me. Distance was less than 75 ft.

Paul Burch said:

Storing a loco in memory will not solve his problem. The transmitter will retain the speed step for a stored loco only as long as the transmitter is on. Once you turn it off and then back on and address the same stored loco the speed step will go to 0. If you address a ficticious loco before turning off the transmitter you can then turn it off and back on because at that point it will come up with the ficticious address. That would allow you to the start running another train but as soon as you bring up one that is still running it will go to speed 0 as before. I hope this wsan’t too confusing.

This appears to be correct, it doesn’t seem there is anyway to avoid this besides setting the transmitter not to shut off.