Digitrax Status Editing

What is the Digitrax Status and how do we edit the status. We are all familiar, or should be,  with programming a decoder. Here we put the loco/decoder on a programming track, then we proceed to program CV values into the decoders memory.

A Digitrax system also has memory built into the command station. Part of the user programmable memory is called the Status. When we first enter a loco address to the system, the command station will store certain information about this address in an area of it's memory called a Slot. When we view or edit Status, it is part of the data in this memory slot that we are actually looking at. Typical current Digitrax systems allow 22 to 120 slots, this means 22 to 120 Loco's [decoder addresses] and/or throttles. This is in part why Digitrax offers such a balanced system.

So the first thing we need to keep in mind is, when we talk programming, we are programming the decoders memory on a programming track. When we say Status or Status Editing, we a talking about programming the command station's memory, not the decoders memory.

When ever we select a new or existing decoder address on a throttle, we see the status of this decoder. This is shown in one of two ways pending if short or long addressing is used. With 2 digit addressing [short] it will show as AD:xy, AD = decoder address, and xy = the actual status code. With 4 digit addressing [long] it will show as St:xy, on a rotating display. This Status will either be the default set by the system, or one that you have previously entered to the command station.

When ever you select a loco on a Digtrax throttle you do this by pressing the SEL/SET button.  Once you have the desired address on the display, if before you press the SEL/SET button again, you can now press the FUNC button. Doing this now enters you in to the Status Edit mode. You may now use either throttle knobs or the Up/Down buttons to change the status. Once you have the desired status, pressing the SEL/SET button will enter it into the command station.

What does the actual Status Code mean.

The Status code is in the form of 2 digits. The left digit tells what the actual status of this decoder is to the system. And the right digit tells what type of decoder it is.
 

A little on the actual terminology used here.  Refresh, this simply means is the command station sending packets with this decoder address or not. Selectable, this means can a throttle/computer select this address or not. In-Use, just as it implies, this address is currently being used by the system or another throttle. Common and Idle, these simply mean that this address is not in use, may be selected by another throttle/computer, etc. Only difference is are packets being sent by the command station to the rails or not. In other words Common = Refreshed, Idle = not Refreshed. New, again is as it implies, this address is currently not in the command stations memory so will enter as new. New, 128 speed step [0,3] is the factory default. Consist means that this address is Mu'ed with other locos as related to Digitrax UniVersal consisting. FX means this decoder supports Advanced consisting, this is how the command station, if it supports Advanced consisting will know that the decoder does also. Note that Digitrax systems such as the Chief also have what is called Unified consisting, meaning it will automatically select the type of consisting to use for you. If you want this to include Advanced consisting then the FX status must be set. If this is not set, then UniVersal consisting will be used. Which is by far the most common method used by Digitrax users.

NOTE: On the factory default. Digitirax sets the default to 128 SS, as this is the most common setup used by Digitrax users. You can always do a Status Edit to select another speed step if required. But the Digitrax DB150 and DCS100 command stations also allow the system defaults to be globally changed. These changes are made via OPSW#'s 21-22-23. Also note, these defaults can also be made on a throttle by throttle basis by changing the defaults on the DT100 throttles. As example this allows one throttle to enter new addresses as 28 SS, and yet another as 128 SS. This versatility is to allow the user to set a default that matches their most used decoders types, thus reducing or not requiring the user to do Status Edit, but allow the system to set it all up for them.

What is Status 'FF'

Sometimes users complain of getting a Status code of 'FF', and they can not enter a new loco address into the system. The first question they ask is what is going on, there is no code 'FF'. Next is what do I do about it. This is usually followed by how to I keep it from happening. So I hope to answer these and give an explanation of how and why it happens.

First note, please do not confuse Status Code 'FF' with the returned CV value of 'FF' on an service mode programmer like the Chief's or the PR1. Remember, when programming on a programming track we are programming the decoders memory. When doing a Status check or Edit, we are dealing with the command stations memory. When a programmer returns a CV value of 'FF', this means that it could not read back a valid CV value for this location in the decoders memory.

When the Status Code of 'FF' shows up, it simply means all the memory slots are filled up, and there is no place to enter a new address.

What to do about. You have several options to correct this, or free up some slots for new addresses. You can select an In-Use slot, zero speed it, and release/dispatch it to the system. Or if possible, you can do the same by stealing loco addresses. Then when the system purges this slot will be free. Another way with the DB150 and DCS100, is to set OPSW#36 to Closed. This will clear all loco address and consist info from all memory. Now all available slots will be free.

How to keep it from happening, is actually pretty simple and easy. But this is best shown by describing how the system works.

The whole thing starts with System Purging, this is where the command station will free up un-used slots so new decoder addresses may be entered into a slot. The whole principle of purging is pretty simple, the command station has a count down timer, if the timer reaches '0' the slot is purged. As long as a throttle is holding a slot info, it will reset the timer every time a command is given, or every 100 seconds or so if no command is given. If a throttle is removed from the LocoNet, it will still keep slot info as long as it is not reset. And when plugged back in it will request an update on the slot info, if it matches, then things go as they were. If a throttle is removed from the LocoNet, and then reset or powered down, it no longer has the slot info stored, and will have to relog back on to the LocoNet. Thus it can not check the old slot info, nor send the slot an update every 100 seconds, so the command station timer will reach '0' and purge.

But there other requirements before the command station will purge. One is the speed has to be '00'. This is how the command station knows you want to purge this slot, and just not set this address in motion and let it run on the layout un-attended. Next it must not have an up-consisted flag, would not want to purge an address right out of the middle of a consist while running down a helix would we. These are all the norm, and how it works. There is one other point that happens from time to time, but fortunately not very often. That is the slot info get garaged in the command station, now the system has no idea what to do with it. This is just like computer memory, that is what it really is. And just like on your computer, voltage spikes, brownouts, etc. can cause problems here. When this happens all kinds of strange things can happen besides the 'FF', and the only cure I know is to do a rest via OPSW#36 and if that does not do it then OPSW#39 will.

The important part is the '00' speed. Even if a address is not dispatched, it should be purged if a throttle is no longer talking to it's slot. Read assigned another address or removed from the LocoNet. Dispatching is just a little more added insurance that it will get purged. But no matter what you do, if the speed is not '00' it will not get purged. Next is the consist issue. Addresses that are up-consisted, will not be purged. So if you want to purge addresses that are consisted, un-link the consist first. This applies to UniVersal consists only, not Advanced. Also being a club layout, if you are using a Chief then make sure OPSW# 44 is closed, this will expand the slot numbers from 22 to 120, so 120 will have to be filled before the 'FF' appears again. The biggest problem, especially with clubs, is removing the throttle, and going home, and not paying attention of what the actual state was when removing the throttle. Speed not '00' or running a consist. In either case, if the addresses are dispatched first, at least someone else can pick it up without having to steal it. Other wise, even if the speed is not '00' or is a consist, someone will have to steal it just to get the slot info so it can be properly taken care of. And even if the 'FF' shows up, usually you can steal a slot back and take care of it to allow it to be purged. But this is a one slot at a time deal and you need to find the addresses to steal. Thus OPSW#36 is a lot faster, but means all decoder Status needs to be taken care of, for those that do not match the default,  and Universal consist info.

Now you have basic understanding of how it all works, and why it does happen to some and not others. Here is are the simple basics to keep it from happening.

If you have more then 22 locos running, then you need more slots, or start using advanced consisting. But if you have less then 22 locos, no real reason for more slots. Read this as if you have less then 22 locos running on the layout at the same time, the answer is really not to increase the slots to 120. All this will do is increase the amount of time before the slots fill up again. The Digitrax Chief, the DCS100 command station supports 120 slots, 120 addresses, and 120 throttles. This is set by Closing OPSW# 44, this should be done if you have more then 22 locos on the layout or are running a club layout. Setting the slot number to 120 helps for clubs, and layouts that have different throttles and locos coming and going. Pulling a throttle with a consist and/or none '00' speed will cause it every time. Unless someone else steals it latter and properly handles it.

The system does a great job of trying to handle things for you behind the scenes, but it will only do what it thinks you want it to. If it sees an up-consist, it figures we do not want to purge this slot out. If it sees a loco running at any speed, other then '00' it figures we want to let this one run un-attended on the layout.

Now of course we can force the '00' speed if we like, the system will help out here also, that is closing OPSW#15, this will force a '00' speed at purge. It as has been pointed out, some of use do not want our un-attended locos to stop. So this has it's good and bad points, pending how we want to run the layout. This means an address that is purged will stop. But if there is a throttle sitting somewhere with this slot info, it will keep it from being purged. So it is possible to have OPSW#15 closed, but as long as there is also an un-attended throttle the purge timer will never reach zero so it will continue to run. This has the advantage if a throttle is ever removed from the layout, it will get purged because of the automatic '00' speed, as long is it is not part of a consist. But then again, there needs to be an un-attended throttle also to keep it running un-attended. But this all boils down again to how we want to run our layout, and how much do we want the system to do automatically or not. Best part is we have the choice to do it our way.

Keep in mind a Digitrax system has memory. It does not like to forget anything, unless we let it know we want it to forget. If a throttle is reset or removed from the layout, the command station still has the slot info in memory. When ever a throttle is going to be removed from the layout, or if battery powered, the battery removed. Any thing that will cause a throttle to be reset, and have to re-log on to the LocoNet. Before this happens make sure you '00' speed the loco. If it is consisted, un-link it from the consist. Doing this means at the proper time, the command station will purge the slot from an In-Use status so that now a new address can be entered in to this slot.

Top of Page