Is it accurate that we're supposed to wait some time ~ after initial powering up ~ before hitting start-up on a PS3.0 engine. Something about capacitors charging? There's nothing mentioned in the brief instructions that came with the engines. If so, how long is that time?
Replies sorted oldest to newest
The first time out of the box it sometimes takes a few seconds, but once its run a bit, they seem pretty instantaneous. The caps need to charge up, but it doesnt take that long. It seems to me that the locomotive just wont respond to the start up command until its charged and ready anyways.
Paul,
Under conventional mode, wait about 20-30 seconds or until it starts making sounds.
Under DCS, there's no wait time at all. Just apply power and press Startup.
 | This and a whole lot more is all in “The DCS Companion 3rd Edition!" This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at OGR’s web store! |
My PS-3 diesel engine starts right up under DCS like Barry B. mentions.
Lee Fritz
I notice some PS/3 engines running command have low volume if you start them up within a few seconds of powering on, then it comes up full shortly.
Isn't the startup sequence longer in PS3 engines just for this reason. Waiting for the cap to fully charge? At least that's what I've noticed with my PS3 vs PS2.
I have noticed I have some ps2 3 volt steam engines that I have upgraded to bcr's and wait for the bcr to charge a minute or even longer and they startup just fine but sometimes the volume comes on low but the second startup is just fine so I don't worry about it never had any issues other then that !
works great I installed one in A mth challenger great running engine
Alan
The reason I ask is because 3 of the 4 PS3.0 engines I own will come up in conventional mode after about 20-30 seconds upon powering up on FXD channels - thus even though they should be seeing the DCS signal they're defaulting to conventional after 20-30 seconds. To avoid this, I have been addressing with remote before that happens ~ within 10 seconds. (all three that come up in conventional mode were purchased this year so they're probably the latest from MTH, fwiw, the only one that doesn't was purchased last year). I am running on FXD channels to mainlines, version 4.3.
I am guessing I'll have to live with this once my yard is finished, but since my yard tracks will be toggled I guess its not a big deal.
Could it be my TIU's are ready for the retirement home? I think I bought them 2004 to 2005.
The common reason for them coming up in conventional is you provide power to them after the TIU watchdog signal has expired. That signal is output when a channel of the TIU is first powered, and it last around 7-8 seconds. If you just switch a yard track onto an already powered TIU channel, you'll come up in conventional mode every time.
Hey Paul, did you ever you determine if the engines starting in conventional happens on all channels? We did mention a fix with a master toggle between the power and var channel . (set to fxd) It not your tiu (s).
John,
That signal is output when a channel of the TIU is first powered, and it last around 7-8 seconds
Just to be clear...
The watchdog signal issued every time that the voltage at the output of a TIU channel changes from 0 to any other value, and it is present for 5 seconds effective with DCS 4.0 or later.
Prior to DCS 4.0 it was only present for 1/2 second.
| This and a whole lot more is all in “The DCS Companion 3rd Edition!" This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at OGR’s web store! |
Out of curiosity, is there a technical reason, with DCS's two way communication being a major bullet point of the system, that DCS engines couldn't be programed to send out a "I'm here!" signal when they are powered on. The TIU could then be watching for this signal and if received send out a watchdog signal?
In other words, assuming an update to the TIU software, to provide for this capability, and an update to the software running on newly produced engines to provide for the "I'm here" signal, would the system allow for this without a redesign?
JGL
Barry and John, I think the watchdog signal is there and A-Okay - since the PS2.0 engines are staying quiet until addressed.
Gregg - all my engines (PS2.0 and PS3.0) come up in conventional on the VAR channels set to Fixed. Its these latest PS3.0 engines coming up pre-maturely on both FXD channels that is puzzling. Does anyone have MTH's latest batch of PS3.0 steamers to try out to verify?
All my new ps 3 engines do this to. There is a problem with these new PS3 that mth needs to address. I will not buy any more PS3 until fixed
I typically run my test tracks on the variable channels in fixed mode so I can test conventional or command without rewiring anything. I don't have any issue with PS/3 stuff coming up in conventional mode when I power up a channel. This is not a typical PS/3 issue, at least not in my experience.
Barry Broskowitz posted:John,
That signal is output when a channel of the TIU is first powered, and it last around 7-8 seconds
Just to be clear...
The watchdog signal issued every time that the voltage at the output of a TIU channel changes from 0 to any other value, and it is present for 5 seconds effective with DCS 4.0 or later.
Prior to DCS 4.0 it was only present for 1/2 second.
This and a whole lot more is all in “The DCS Companion 3rd Edition!"
This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at OGR’s web store!
Barry,
I recently had a conversation with Jason,and he said the watchdog signal is only present less than a second. Was he mistaken?
Dave
Dave,
I recently had a conversation with Jason,and he said the watchdog signal is only present less than a second. Was he mistaken?
Unless something changed in DCS 5.0 of which I'm not aware, I think you and he might have miscommunicated. Regardless, I've sent Jason an E-mail requesting clarification.
Dave,
I recently had a conversation with Jason, and he said the watchdog signal is only present less than a second. Was he mistaken?
I communicated with Jason a little while ago and it turns out that we were both mistaken, and that the issuing of the watchdog signal is a little more complicated than one might suspect.
The watchdog signal is a command that is sent repeatedly when a channel output goes from zero to some other voltage, until one of the following occurs:
The way I intend to state the duration of the watchdog signal going forward is:
"The watchdog signal persists for the lesser of 44 seconds or until a command is issued on that TIU channel."
That pretty much sums it up. 
FWIW, almost all of my engines are PS3 and I am having no problems with any of them and there are quite a few. All come up silent in command mode as they are supposed to waiting to be told to start.
Also nice to learn of Barry's new found information above on the watchdog signal.
Barry Broskowitz posted:Dave,
I recently had a conversation with Jason, and he said the watchdog signal is only present less than a second. Was he mistaken?
I communicated with Jason a little while ago and it turns out that we were both mistaken, and that the issuing of the watchdog signal is a little more complicated than one might suspect.
The watchdog signal is a command that is sent repeatedly when a channel output goes from zero to some other voltage, until one of the following occurs:
- 44 seconds elapses (this may have been stated to you by Jason as 1/2 a minute or less than 1/2 a minute). Note that this duration is subject to change in future DCS release if the number of dat packets in the command changes the time required to send the command there requisite number of times.
- Another command, such as Startup, is issued on that channel.
The way I intend to state the duration of the watchdog signal going forward is:
"The watchdog signal persists for the lessor of 44 seconds or until a command is issued on that TIU channel."
That pretty much sums it up.
Huh? Now I'm really confused. If that's the case(44 seconds) why are engines starting in conventional . No commands are given.
Gregg,
If that's the case(44 seconds) why are engines starting in conventional . No commands are given.
They shouldn't. Obviously, something in Bob's layout, TIU and/or engines isn't quite right. Regardless, there's nothing "confusing" about this at all.
5 seconds is an eternity in terms of the speed of electronic components. For the purposes of the watchdog signal, the difference between 5 seconds and 44 seconds is of no consequence.
Barry Broskowitz posted:Dave,
I recently had a conversation with Jason, and he said the watchdog signal is only present less than a second. Was he mistaken?
I communicated with Jason a little while ago and it turns out that we were both mistaken, and that the issuing of the watchdog signal is a little more complicated than one might suspect.
The watchdog signal is a command that is sent repeatedly when a channel output goes from zero to some other voltage, until one of the following occurs:
- 44 seconds elapses (this may have been stated to you by Jason as 1/2 a minute or less than 1/2 a minute). Note that this duration is subject to change in future DCS release if the number of data packets in the command changes the time required to send the command there requisite number of times.
- Another command, such as Startup, is issued on that channel.
The way I intend to state the duration of the watchdog signal going forward is:
"The watchdog signal persists for the lesser of 44 seconds or until a command is issued on that TIU channel."
That pretty much sums it up.
I was just getting ready to post this question..had some pre draft text ready. The DCS knowledge on this forum is incredible
I can hear the data packets (watch dog) going out on my AM radio when plugged into the same wall outlet as a spare tiu (using an aux power supply)
I'm guessing 3 seconds max on fixed 1 when the voltage is raised above 0 , Pretty much the same as it has been . I suppose it doesn't really matter how long if everything is working as it should. I'm still a little concerned about Proto-3 missing the WS.( some do some don't).
I don't know about it being his layout I have PS3 that start normal on my layout and a new PS3 that starts as stated in discussion. I truly think there is a problem. What the problem is that is the question that needs to be answered.
Gregg posted:I'm still a little concerned about Proto-3 missing the WS.( some do some don't).
MTH knows about this. It is not that they miss the signal due to not being able to see it. It is a power up vs time issue.
Dave
Has anyone actually charged up a proto-3 and then shut down the layout. Immediately power up again. Does the engine that misses the WD the first time miss it a second time?
Gregg posted:Has anyone actually charged up a proto-3 and then shut down the layout. Immediately power up again. Does the engine that misses the WD the first time miss it a second time?
Yes to above. TIU on >DCS remote on>eng all and start. Occasionally 1 of my PS3 engines in a 5 engine MU will miss the "wd". Repeat my previous procedure immediately and all good. I am a violator of dirty track though. 
Gregg posted:Has anyone actually charged up a proto-3 and then shut down the layout. Immediately power up again. Does the engine that misses the WD the first time miss it a second time?
yup all the time on one ps3 engine but did noticed that if I run for long time say hour and shut down. Then it seems to start up just fine.
Access to this requires an OGR Forum Supporting Membership
