ESU Automatic Horns With No Movement Until Done Sounding

Even with the plethora of Horn sound slot file tutorials on this blog, the most common request this author receives is to change them so the engine does not move until the horn is finished playing (that's prototypical). Apoorva (The IndianRail Modeler) and I have been working on this together and with his help and input on both the stop signal and some selections within sound files that the author was unfamiliar with, we have it working. This is one of the more complicated projects presented in this blog but it works and it's a relief to have it working. The core of this project lies in the Starting Delay sound slot usually slot #26 shown in figure 1.

Figure 1 Sound Slot #26 Starting Delay

It is recommended that you run this with the simulator to see how it actually works. The Start, Reverse and Stop horn sounds will be added directly into this slot but there are several things you have to know for it to work properly. They will be discussed. The stumper for the author was getting the Stop signal to function. He was all over the place and none of the tries worked. Then Apoorva demonstrated how easy it was. The author just never looked at it this way.

Let's start with the completed project (figure 2) and we'll break it down into parts as we go.

Figure 2 The completed project

We'll start with the Forward and Reverse signals. First, be certain that with the original Starting delay slot in the Sound Slot properties you have the Unlimited checkbox checked and there is a constant variable of Speed 1 = 0.

The Forward Signal

Add a container named Forward Signal between the two Drivelock states. The entry conditions are Requested Speed > Speed 1 and Reverse = false. The exit actions are tmr1 = SV13. So we are setting timer 1 to the value in SoundCV 13. SoundCV 13 can be viewed on the Sound Slot settings sheet of the Decoder pane. In most (if not all) sound files 13 is a default value. The contents of the Forward Signal container are shown in figure 3.

Figure 3 The Forward Signal

Notice how timer 2 controls not only the length of time the horn sounds (in 1/4 secs. so 2=.5 secs) but also the length of time of the pause between horn blasts (in this case a hard coded value of 6, change it if you like). The select value is entered and changed on the Sound slot settings sheet of the decoder pane (it's the Sound configuration variable). The statement in the comment about mapping all horn states to sound slot #3 is in the author's opinion a stroke of genius by Apoorva. This is done in the State Properties as shown in figure 4.

Figure 4 Tying another sound slot to this one

What this does is tie the horn to sound slot 3 so in the event you change the selected horn by changing SoundCV 9, all of the horn states in this sound slot change with it. You don't have to do anything extra!

The Reverse Signal

More of the same here except the entry conditions have the Reverse = false changed to Reverse = true. See figure 5.

Figure 5 The reverse signal

The Stop Signal

Now for the item that caused the author a lot of grief. We'll not get into that but the fact is if the engine got as far as the Drivelock Timer Before Release then it moved and sounded the horn so now you have to sound the stop signal when spd=0. We also have to take into account the Function mapping being still in effect. So to differentiate these two we'll implement a user variable. A value of 1 means the function is still active so when spd=0, sound the stop horn. Shown in figure 6.

Figure 6 The stop signal

Again, nothing new. Prior to the stop horn sounding there is a delay state that allows for a short delay until the stop horn actually sounds. It consists of playing the silence.wav file a number of times. Look at the state properties in figure 7.

Figure 7 The delay state properties

Adjust the delay by changing the Min and Max numbers equally up or down.

Summation

• You do not have to worry about mapping this in the Function Mapping sheet of the Decoder pane. Since it is already mapped with 'Stop, F8, not F15' you're good there.

• Do not uncheck the Starting Delay on the Driving characteristics sheet of the Decoder pane. That will prevent this sound slot file from working properly. If it is unchecked, check it.

• The unlimited checkbox MUST be checked. A quote from Apoorva,

  "The unlimited check box signals to the decoder what to do if a soundslot is interrupted while it’s playing. Interruption could be due to loss of power, hierarchy when too many sounds are simultaneously playing or conditions within the soundslot. If the box is not checked, the user will need to toggle the function button to re-start the soundslot. If it is checked, the decoder will automatically restart the sound".

• Every horn state must be mapped to sound slot 3 or whatever sound slot you have moved the horn pack to, if you have.

Recommendations

• If, and for some sound files that's a big IF, you have an extra soundCV available use it to set and change the values where tmr2 is hard coded to a value of 6 as shown in figures 5 and 6. Say you have SoundCV 14 free. Set it to a value of 6 on the Sound settings sheet. Then change the appropriate transition action lines from tmr2 = 6 to tmr2 = SoundCV14. With this in place you just write decoder data when you change SoundCV 14 (less than 10 secs.).  As is, if you change this value you will have to re-burn the sound file (30 minutes!!).

• As an experiment you could substitute the start, reverse and stop horn files that I detailed here in place of the ones in this article. The author would be interested to know if these work and if they work properly. There's no reason they shouldn't. The only issue with this is if you change the horn you will have to revisit the file and update the horns manually. Mapping the horns to the sound slot will not work in this case.

• If the delay between the start horn finishing and the engine starting to move is more than you prefer, just reduce the value of SoundCV 13 on the Sound slot setting sheet.

I hope you learn a lot from this sound slot, THIS AUTHOR DID! It somewhat changes the way you think about how sound slots work and how to connect them to other slots and sounds.

Thanks Apoorva for pointing me in the right direction!

Good luck with this everyone but most importantly, have fun!

---

If you have an idea for a blog post here, let me know. If I can comment on it, I will or I'll see if someone else can and post it.

Digitrax Track Status Light - Which Color Is It Anyway, And When?

The following is from BillyBob Experimenter on the Digitrax-Users groups.io forum and was written about a year ago.

---

When address 0 is being used and it is "stopped", the lamp should look about the same as when address 0 is not being used.

When address 0 is being used and it is "moving forward", as the speed increases, the track status "gets more redish" (or gets more-greenish), with the most-redish (or most-greenish) when Address 0 is at a speed of 99.

When address 0 is being used and it is "moving reverse", as the speed increases, the track status "gets more-greenish" (or gets more-redish), with the most-greenish (or most-redish) when Address 0 is at a speed of 99.

When the "Address 0" feature is disabled, the track status lamp will show as "Amber".  And please note, I LocoNet devices do not support the "address 0" ("Analog loco") feature, and actually turn the command station's feature "off" if they see it turned on!  The OpSw which controls this is typically command station OpSw20; OpSw20=Thrown seems to allow Analog operation via address0;  opSw20=Closed seems to disallow Analog operation.

Be aware that the DCC track signal does not know which direction the loco is going!  If the loco is placed on the rails one way, the loco will run forward when the Track Status is more-greenish, and run reverse when the Track Status is more-redish .  But when put on the rails in the opposite direction, the loco will run reverse when the Track Status is more-greenish and run forward when the Track Status  lamp is more-redish! That's why I said "more-greenish (or more red-ish)" above...

And some DCC command stations display the Track Status in such a way as to be harder to determine the Analog usage.  This is because some command stations and boosters do not have a great "amount of greenishness" and "amount of redishness" for the effect of the "Address 0" speed.  In my experience, the DCS52, DCS210, DCS210+, DCS240, and DCS240+ command stations seem to have this "lower" variance.  This may affect DB210, DB220, DB220Opto boosters, too.

---

If you have an idea for a blog post here, let me know. If I can comment on it, I will or I'll see if someone else can and post it.  

ESU 5 Single Sound Slot Auto Horn

This is a move in creating a more efficient automatic horn sound slot that combines two slots into one. Eventually this will become a part of a project that will also allow the horn to complete playing before the engine starts to move. There have been many questions to the author about getting this to work so he has finally taken this on and it's a complicated one.

A single start, stop and reverse sound slot file was first mentioned here. The cons, as detailed in that post were taken care of in this new version. Figure 1 shows the general flow of the logic and it's quite simple. The key is everytime the engine starts in motion it will eventually have to stop so tie the stop horn to the start horns and it becomes simpler. 

Figure 1 The general flow

For those of you that have already implemented the auto horns which were detailed here. The forward and reverse horns and also the stop horn (shown in figures 2, 3 and 4) can be merely copied and pasted into the new diagram containers respectively. For those that haven't implemented the horns, it is recommended you do. You'll learn a lot about creating containers and states and saving the finished product to your templates.

Figure 2 The forward horn signal

Figure 3 The reverse signal

Figure 4 The stop signal

Once you have this complete, save it to your templates. The next project up is utilizing it in a slot that plays the horn sounds completely before the engines moves.

---

If you have an idea for a blog post here, let me know. If I can comment on it, I will or I'll see if someone else can and post it. 

ESU Autobell WIth Start, Loop and End Files Employed

Originally, this author posted how to employ an auto bell for locomotive starts and stops. That post is here. This is a rather simplistic way of getting the bell to work automatically. It only employs the Loop sound WAV file but it does work. He had every intention of employing all three files (start, loop, end) sometime in the future. Well, we all know how that "future intention" works and here we are three years in the future.

Recently, a reader of this blog who has employed several of the other methologies presented in this blog sent the author an email showing where he could not get the file to work after adding the start and end sound files. So it looks like that time is now.

First of all if you have not followed and implemented the original method mentioned above, it is recommended you do. You will learn a lot of manipulations that you need to know and you will have a basis for building this more advanced form of the auto bell. The really good thing about this exercise is that it can be built completely utilizing the Simulator and not have to be burned to the decoder until we have it correct.

The original project was simple. If the speed was greater than zero, spd > 0, and less than the max speed we selected, spd < SV16, then ring the bell using the loop WAV, otherwise stop ringing. Now the logic gets more complicated. Whereas the bell ringing happened in a simple State located in a Container, that State now expands to multiple states in the Container to hold the additional logic and sound WAVs. The starting container is shown in figure 1.

Figure 1 The starting container

  

The complete contents of the container is shown in Fig.2. The Decision state and wait for function are both states. 

 

Figure 2 Autobell with start and stop sound WAVs added

The logic of which sound file to play is determined by using the user1 variable and setting it to either 1 or 0. Anytime it is 1 indicates the start sound should play. Otherwise, depending on the speed which is determined by the spd register obviously and the sound CV SV16, play either the loop sound or the end sound.

Don't forget to check the loop checkbox in the Repeat Playback section for both the Decision State and the Wait for Function state or you will get an error.

Have fun with this one.

---

If you have an idea for a blog post here, let me know. If I can comment on it, I will or I'll see if someone else can and post it. 

CowCatcher Magazine's Article on Model Railroad Tariffs

Updated from the May/June 2025 Cowcatcher Magazine this article discusses the effects of the newly imposed tariffs on the hobby.

---

If you have an idea for a blog post here, let me know. If I can comment on it, I will or I'll see if someone else can and post it. 

The Hobby Industry Coalition

This is a forward posting of an email from Atlas Insider. It is meant to help protect the future of toys and hobbies in America. It appears things are heating up and they had better do that or this hobby may not survive the next four years.

Read about it here.

---

If you have an idea for a blog post here, let me know. If I can comment on it, I will or I'll see if someone else can and post it.  

A Message From The Model Train Industry

This is something that everyone needs to watch and listen to concerning the tariffs. It is a statement  from most of the prominent model railroad manufacturers today and an important eye opener for all of us who love the model railroading hobby.

---

If you have an idea for a blog post here, let me know. If I can comment on it, I will or I'll see if someone else can and post it- 

Loksound Equipped Engine Refuses To Move But Sound Is Fine Final Update 2025-04-17

This problem has plagued users for a long while now and is almost constantly an issue brought up on the LokSound groups.io forum. Guaranteed you'll see it brought up about every two or three days.

There are several reasons this could happen and the majority of them are easily remedied. There is a list of things that need to be checked and these are mentioned whenever the problem pops up. 

• Make sure Drive Hold is not on
• Ensure the Independent Brake is not on
• Ensure the Automatic (Train) Brake is not on
• To learn how to implement the Train brake read this
• Make sure CV19 is set to 0 (not in advanced consist)
• By default, the sound files have a 3 second delay before they allow the engine to move
• Allows the engine sound to spool up before moving (because that's how prototypes work, read this) 
• If you haven't turned off this delay, give it a little time to start moving
• A comment was left by a reader with a common sense check I should have mentioned. After checking the easy stuff, check the motor contacts (or wiring) make sure they are clean (in the case of contacts) or wired correctly (for wiring). Problems with wiring includes a wire where half or more of the individual threads of wiring have been cut through or broken or have a bad (cold) solder joint. Thanks to the reader whoever you are.

If group members think of other things that need to be checked, email the author and he'll add them to this list. 

Recently, the author came across this problem in a couple of his locomotives and it always occurred when initially programming the decoder. It didn't matter if the engine was programmed from scratch or was a copy of a previously programmed engine with just the engine number changed. It happened in both instances and was always for a v5 decoder (that's what the author has) so, both 21 pin and micro decoders developed the problem.

Definition of Terms

Just to be clear, the following was done with a LokProgrammer and not JMRI. Also, with a LokProgrammer there are some terms used in this discussion that may be confusing for those used to JMRI - Panes, Sheets and Driver's Cab. 

• Panes are the columnar selections on the left side of the LokProgrammer window. They start with Driver's Cab at the top and end with Sound at the bottom. Directly to the right of the Panes are the Sheets starting with Address. See figure 1. 
• Sheets give you access to the individual CV settings of the decoder but they can also give you access to other things such as the individual sound slots on the Sound Pane. It depends on which Pane you select. It  takes a little getting used to.
• Driver's Cab is a built in throttle which allows you to immediately test the changes you have made to CVs after Writing Decoder Data. It does not allow you to test any changes you have made to the Sound Pane though. Some changes there have to be burned to the decoder to hear them (the Simulator in the sound pane will allow hearing some changes but not all of them and that is beyond the scope of this discussion).
  
  
  

Fig 1 Panes, Sheets and CV access

Now For The Insidious One
Re-burning the unchanged original downloaded file from ESU (pure factory reset not a reset to previously programmed values) would clear up the problem so what did the author change that caused this? 

Today it was decided he was going to take the time and trace the cause. One sheet at a time utilizing the Driver's Cab to test if the engine is running or not after changes and then go changed setting by changed setting on the particular sheet if the problem occurred.

This took some time. Brake Settings, Driving Characteristics, the various Function Sheets, all were fine. Motor Settings, WAIT!!! the engine refused to move!!! Now change by change until the author got to Motor Overload Protection. Long story short finally, checking the Enable motor current limiter would prevent the engine from moving!  See figure 2.

 

Fig 2 Motor current limiter

Think! Why? This was an older HO KATO AC4400CW purchased at a swap meet and it had the same changes made as to a new one that was working. This makes perfect sense. The older motor needs more current than the new model and the protection wouldn't let it move because it was above the set limit.

Uncheck the Enable motor current limiter box, test, engine moves! Problem solved. Perhaps in the future (when there's time) some experimentation with this setting will show what's going on.

Don't forget this one after checking Drive Hold and all the different brakes don't fix the problem. Also remember that if after all of these checks are done and the engine still does not move, you probably have a blown drive circuit in the decoder and it requires a trip to Colorado for a fix. Remember that the ESU office has moved. It's no longer in Pennsylvania. 

I hope this helps and I know it demonstrates what lengths you sometimes have to go through to isolate problems. Good luck!

<Update 2025-02-19>
Interesting development concerning these settings happened today. The author obtained a brand new CSX GP38-2 Atlas Master (new old stock) with the the older DCC/DC mother board controlled by a slide switch. The motherboard was removed and replaced by the new Athearn G67140 Genesis DC-21 Pin Motherboard for LEDs. A new ESU 21 pin v5 decoder was added and programmed.

Now for the fun!  During the BEMF auto-calibrate (CV54=0, press F1) procedure, the author noticed that the engine was extremely sluggish although it did move. Testing the results, no matter how much the throttle speed was increased the engine refused to move at more than a crawl speedwise. The author went as far as re-burning the soundfile to the decoder, no joy. After some thought he remembered he had checked the Motor-overload-protection and also the Current-limiter-protection so, he unchecked them just to see if it had any effect and yes, you guessed it, the engine returned to normal running. 

This one is a stumper!! These settings seem to have a lot more to do with the running of an engine than would be expected from their names and the experience discussed from the beginning of this post.

<Final Update 2025-04-17>
The author was finally able to reach ESU tech support and talked to Lee about these problems caused by Enable motor overload protection and Enable motor current limiter. According to Lee these two settings should be ignored. They were originally put into the programmer to help Rapido with some decoders they thought were having problems. Turns out it was the wonderful Chinese motors that were put into the engines (yeah, wonderful). So, accordingly, these settings are no longer needed. Lee stated (and I quote), "Frankly, I don't understand why ESU just doesn't remove these settings from the software".

So there you have it, leave these settings alone!

---

If you have an idea for a blog post here, let me know. If I can comment on it, I will or I'll see if someone else can and post it-

Microsoft Offering a Minimum 3 Year Windows 10 Extended Security Support

Microsoft is offering extended security support for Windows 10 computers. This programm will last for at least 3 years. You can read about it here.

If you think this is not a model railroading topic, talk to a person who is familiar with JMRI. 

---

If you have an idea for a blog post here, let me know. If I can comment on it, I will or I'll see if someone else can and post it

Tony's Train Exchange Response Concerning Tariffs

To all of our Tony's customers:

We hope you’re doing well. We wanted to take a moment to update you about some changes that will affect the pricing of our products & services in the near future. As you may know, recent changes in trade policy have resulted in increased tariffs (import taxes) on certain products and materials that are essential to our model train offerings. These changes are beyond our control, but we want to be upfront with you about what’s happening and how we’re handling it.

This is a dynamic and evolving situation. We're closely monitoring updates from our suppliers and adjusting accordingly to the most current information available. Our goal is to minimize the impact on you—our valued customers—while continuing to deliver the quality and craftsmanship you expect from us.

Why are prices increasing?

The increase in tariffs on materials and products imported to the USA has led to higher costs for us in manufacturing and importing. Unfortunately, these higher costs now need to be reflected in our pricing. This change will help us maintain the quality of our products and services, which we’ve always worked hard to deliver at the best value.

What are we doing to minimize the impact on you?

We understand that price increases can be challenging, and we’re committed to keeping our prices as fair as possible. Here’s what we’ve been doing to minimize the impact:

• We’ve been working closely with our suppliers to find cost-saving measures.
• We’ve reviewed our operations and made efficiency improvements where possible to offset some of the increased costs.
• We’ve done everything we can to keep our prices reasonable while ensuring the same high-quality products and services you’ve come to expect.

How will this affect you?

When necessary there will be a price adjustment noted on your invoice.  This will affect many imported model railroading items. Please know we are still committed to providing the best value and service. We remain focused on ensuring that you continue to receive the quality you expect.

Your Support Means the World

We deeply value your loyalty and trust in Tony's Train Exchange. We’re here to help answer any questions you may have about this change. If you have any concerns or would like more details, please don’t hesitate to reach out to us. We want to make this transition as smooth as possible for you.

Thank you for your understanding and continued support as we navigate these changes. We look forward to continuing to serve you.

Warm regards,

Erik Fiske

Owner

---

If you have an idea for a blog post here, let me know. If I can comment on it, I will or I'll see if someone else can and post it

Walthers Update Concerning Tariffs

Dear Valued Partner,

As you may be aware, ongoing tariff increases and fluctuations are impacting pricing across many product categories both inside and outside of our hobby. At Walthers, we are actively working with our industry partners—and the broader toy industry—to advocate for tariff relief (exclusion or reduction) on model trains. At the same time, we are collaborating closely with our suppliers to absorb as much of the added cost as possible.

The recent tariff changes scheduled to take effect have further impacted pricing on many products within our hobby. As a result, effective immediately, we will no longer be able to honor backorders and advanced reservations at their original pricing. This policy will apply to all products we distribute, including Walthers-branded items and those from our vendor partners. Updated pricing will be provided prior to shipping new products.  We will continue to monitor the situation and communicate actively with you should anything change.

Please rest assured that our commitment to delivering the highest quality and value remains unchanged. We are doing everything we can to minimize the impact on you, and we sincerely appreciate your understanding as we navigate these challenges. If you are concerned about the tariff situation and its impact on our hobby, consider communicating actively with your own elected representatives about your concerns so your voice can be heard.

Your continued support means the world to us and we remain proud to serve you as we have for almost 93 years. Thank you for your loyalty, patience, and partnership in supporting this wonderful hobby.

 

Warm regards,
The Walthers Team

---

If you have an idea for a blog post here, let me know. If I can comment on it, I will or I'll see if someone else can and post it

DC Engines on a DCS52 Controlled Track

In reply to a question on the Digitrax groups.io forum of whether or not a DC engine could run on a DCC track whose command station is a DCS52 Carl Hilinski said this...

"I have a couple of Marklin engines that  are DC. They can run on my DCS52 if I select 0 as the engine number.  ALL DC engines will be controlled by the 0 selection. The problem is that you shouldn't leave the engine on the track even if it's not controlled because it is still getting power and hums and vibrates. Also all DC locos on the track will run the same speed and direction just like a normal DC operation".

This was what the author knew on the subject because he does this all the time for testing and has never had a problem. The interesting reply to this statement was from the "Hostler" named Bob who said...

That's only part of the problem.  It turns out that SOME Digitrax LocoNet devices do not work well with "DC loco" operation,  They work so poorly that they will go to the effort of changing the Command Station's "Analog (DC) operation" OpSw to disable it!

So, if you happen to use any of those Digitrax devices (which ones were not mentioned), the "analog" operation feature may not be available to you.

Interesting, this is the first the author has heard of this.

---

If you have an idea for a blog post here, let me know. If I can comment on it, I will or I'll see if someone else can and post it

ESU Mobile Control Pro And Docking Station

ESU advertises their new Mobile Control Pro.

The Mobile Control Pro is ESU's latest answer to the question of how to combine the advantages of smartphone technology with the needs of model railway control. The Mobile Control Pro is essentially a compact Android-based tablet equipped with controls for controlling your locomotives and accessories. The connection to the digital command station is established exclusively wirelessly via Wi-Fi. A specially designed app by ESU can communicate directly with a variety of digital command stations. The Mobile Control Pro is therefore not limited to use with ESU command stations.

MC-Pro will not be available in the US until July. It replaces the MCII which is no longer in production. 

You can read about it here.

The Docking Station

The docking station is the perfect companion for your ESU Mobile Control II or Mobile Control Pro Wi-Fi radio throttle. The docking station fulfills two tasks: Firstly, it ensures safe storage of the throttle when it is not in use. Secondly, the controller can be charged directly in the docking station. No cables need to be connected: For charging, the docking station connects to the charging points provided on the underside of every Mobile Control II or Mobile Control Pro and charges the device.

The charging cradle does not have a US release date yet. 

Read about it here.

---

If you have an idea for a blog post here, let me know. If I can comment on it, I will or I'll see if someone else can and post it

Athearn's Response To Tariffs

 

Important Notice Regarding Upcoming Price Adjustments At Athearn, we value transparency and open communication with our customers. We’d like to inform you of an important update regarding our pricing structure. For over 20 years, Athearn has produced our Roundhouse, Athearn, and Genesis HO and N scale models at factories in China. During that time, we’ve faced increased costs from raw materials and shipping but have largely been able to absorb those expenses without significant changes to pricing. However, recent tariffs imposed on all imports from China have created new challenges. Unlike previous increases, these tariffs have had a substantial impact, and unfortunately, we are no longer able to absorb the added costs. Effective Monday, March 24th   we will implement a price increase to help offset the effects of these tariffs. This adjustment will apply to: All current open pre-orders Items in the April 2025 pre-order packet and beyond In-stock items shipping from Horizon Hobby We understand this may come as disappointing news, and this was not an easy decision. Our hope is that this is a temporary measure. Athearn and Horizon Hobby will continue to closely monitor the situation and make adjustments as necessary. We truly appreciate your continued support and understanding. -The Athearn Team <Author's Note> Here we go! If you have an idea for a blog post here, let me know. If I can comment on it, I will or I'll see if someone else can and post it

From Walthers: Important Notice About Tariffs

Dear Valued Customer:

As you may be aware, the recent tariff changes are affecting many products within our hobby. While we've worked diligently to absorb as much of the impact as possible, some of these increased costs were incorporated into our pricing going forward. Rest assured, all backorders and advanced reservations placed before this date will be honored at the original price. Our commitment to maintaining high quality and offering great value remains unchanged, and we truly appreciate your understanding and continued support as we navigate these challenges together. Thank you for being an important part of our hobby community!

---

If you have an idea for a blog post here, let me know. If I can comment on it, I will or I'll see if someone else can and post it

Bob The Train Guy's Last Weekend! Updated 2025-03-24

Bob the Train Guy is finally calling it quits!

From Bob:

 

Store will close in a day or so!

 

The new owner is taking the last truckload of inventory today!

 

A very sad day for me!

 

The new owner will be in contact with all of you. I assured him most of my customers are real model railroaders with a lot of patience!

 

I would like to Thank the thousands of valued customers who have bought from me! My current health status is slightly better but I will never be able to hit it like I did in the past. I cannot do many shows due to my balance and overall strength.

 

Please contact me if you need your order in a timely manner, I will try to move your order to the top. I will continue to be around and will honor and special orders and reservations. Please review the website and see you find something you would like to get while still in stock!

 

The inventory is being shipped out shortly. Please order anything NOW if you want it!

Bob's inventory is moving to A and S Trains

A and S Trains

It's a shame to see him go as this author has bought quite a bit of merchandise from him in the past. At least his inventory was bought out and will, hopefully, continue to be available to the Model Railroad community.

---

If you have an idea for a blog post here, let me know. If I can comment on it, I will or I'll see if someone else can and post it