Trains.com

Subscriber & Member Login

Login, or register today to interact in our online community, comment on articles, receive our newsletter, manage your account online and more!

DecoderPro Slot Monitoring

928 views
4 replies
1 rating 2 rating 3 rating 4 rating 5 rating
  • Member since
    January 2002
  • From: Canada, eh!
  • 737 posts
DecoderPro Slot Monitoring
Posted by Isambard on Saturday, June 13, 2009 6:03 PM

In monitoring slots, what is the practical difference between an Idle status
slot and a Common status slot after dispatching the address or a time out purge occurs? We
note that in some cases on dispatching a loco address the slot immediately goes
to Idle while in other cases it remains at Common e.g. if the loco sound is not
turned off, or if the loco was a top loco in a consist. Repeat dispatching of the address then usually causes the status to change from Common to Idle.


Our DCS200 has 120 slots available for loco addresses and status. We are
operating with 22 slots available, the factory default setting. We normally do
an OPSw39 purge before each session. We note activity in one or more of the
seven system slots from time to time, which appears to show to a phantom loco or
two. What do these system slots show? Should we be monitoring these slots during
routine operations and if so for what?

Comments appreciated

 Isambard

Isambard

Grizzly Northern history, Tales from the Grizzly and news on line at  isambard5935.blogspot.com 

  • Member since
    December 2001
  • From: Trois-Rivieres Quebec Canada
  • 1,063 posts
Posted by jalajoie on Sunday, June 14, 2009 10:34 AM

I did notice this however I didn't pay much attention to this matter. It is my understanding, if the I lights are still On or the motor speed not fully turned to zero, the command station still keep these decoders as active in its memory.

We operate our Super Chief with 120 slots so we never have to worry about how many are in use. I personally flush the internal memory of the system once a month.

Jack W.

  • Member since
    January 2002
  • From: Canada, eh!
  • 737 posts
Posted by Isambard on Monday, June 15, 2009 1:57 PM

Thanks Jack. Drop in and visit us if you're on the west island (www.wimrc.ca).

I'm waiting for others to comment too.

 Isambard

 

Isambard

Grizzly Northern history, Tales from the Grizzly and news on line at  isambard5935.blogspot.com 

  • Member since
    July 2006
  • From: Pittsburgh, PA
  • 1,796 posts
Posted by JoeinPA on Monday, June 15, 2009 5:22 PM

 I've noticed this too.  I've found that in most cases if you have dispatched your locos correctly exiting the program and re-entering "cures" the problem.  This would be a good question for the jmri users group on Yahoo (http://groups.yahoo.com/group/jmriusers/).

Joe

  • Member since
    February 2002
  • From: Reading, PA
  • 30,002 posts
Posted by rrinker on Tuesday, June 16, 2009 4:29 PM

 There is a file on either the Digitrax or JMRI Yahoo group which completely explains the various slot status conditions. This is invaluable for seeign jsut what all that stuff you see in JMRI actually means.

 The system slots are also explained. One is the fast clock, one is the dispatch slot (when you actually dispatch a loco or consist so that someone with another throttle can pick them up), others are for other internal functions.

 

                                 --Randy

 


Modeling the Reading Railroad in the 1950's

 

Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.

Subscriber & Member Login

Login, or register today to interact in our online community, comment on articles, receive our newsletter, manage your account online and more!

Users Online

Search the Community

ADVERTISEMENT
ADVERTISEMENT
ADVERTISEMENT
Model Railroader Newsletter See all
Sign up for our FREE e-newsletter and get model railroad news in your inbox!