Part 2
I want to make sure that the grain hopper is being routed as I expect. In the last blog posting, I had the train pick the car up from the cassette and drop it off at the bakery. So, I run the train again and examine the generated manifest.
This looks good. The train picked up the now empty grain hopper and returned it to the cassette.
I notice that the grain hopper state was changed from loaded to empty. This is an automatic function when a car is dropped off on a spur track. If the car had been empty when it was dropped off, its state would have been changed to loaded.
I use the Move Action button in the Trains form to move the empty grain hopper to the cassette.
To make sure that all is working well, I schedule the train to run again and examine the manifest.
The train has no work! That’s not what I was expecting at all. So, I take a look at the Train Build Report:
One of the rules when using an interchange is that a car that was dropped off by one train may not be picked up by the same train. In other words, interchanges are used to exchange cars between trains.
So, it looks like I have a couple of choices:
- I could create a second train to operate on the same route.
- I could use something other than an interchange to model the cassette.
I don’t want to schedule another train for this simple bakery turn job. I don’t think that’s how a real railroad would do things. So, I look at my other options.
JMRI Operations supports 4 major track entities: spurs, interchanges, yards and staging.
I used a spur track at the bakery. Spur tracks accept picking and dropping cars and will toggle the car state between empty and loaded.
The interchange track is not doing what I want.
A yard track is used to hold cars until they have been assigned to trains. Yard tracks will not toggle the car state between empty and loaded.
A staging track is used to hold a complete train that has been assembled beyond the modeled layout. Staging tracks will also not toggle the car’s load state.
In the real world, car loads are generated at one industry and consumed at another. There is a cycle set up between the suppliers and consumers of goods or materials. In the bakery turn, I have only modeled half the cycle. I need to model the other half.
That is, I have modeled a loaded grain hopper being shipped to the bakery and the empty be taken from the bakery but I have not modeled the grain hopper being refilled with grain.
Since I want the grain hopper’s state to be reset to loaded, I will need to use a spur track.
So, I change the Cassette location from using interchange tracks to spur tracks. Also since spur tracks can accept both dropping off and picking up of cars, I should only need one spur track.
I make sure that the grain hopper is set onto this new spur track and that its state is set to loaded. I also make sure that the locomotive is set onto the new spur track.
I run the train again.
This looks good. I run the train for a couple more cycles. The grain hopper is being loaded at Cassette and emptied at Bakery. This is just what I wanted.
Now, let’s see what happens if I add another car to Cassette. I decide to add a tank car...
... and I run the train.
JMRI found the two loaded cars at Cassette and shipped them to Bakery. I run the train again.
It also found the empties at Bakery and shipped them to Cassette.
So, I add all the other cars to Cassette.
And I run the train again.
Wait a minute. I had 10 cars at Cassette, why did JMRI only move 6 of them? I look at the Train Build Report.
Aha! The train is able to handle 7 cars including the locomotives so, it can only handle 6 freight cars but Cassette is only allowing 5 pickups and Bakery is only allowing 5 set outs, so only 5 cars may be moved.
On the next train, the other loaded cars are shipped to the Bakery.
Hmmm… Why didn’t the train pick up the empties at the Bakery?
The clue is the line that reads “Train departs Bakery Westbound with 0 cars…”. The Cassette is East of the Bakery, so JMRI will not add the Eastbound empties to the Westbound train.
To fix this, I added another Location to the Bakery Turn route to say that the Bakery Eastbound is now part of the route.
Now the train picks up empties at the Bakery and returns them to Cassette.
The manifests are getting to be larger now. I wonder if JMRI can help me in reading them. Under the “Tools” menu is an entry named “Manifest Print Options”. Selecting this causes a form to be displayed which has a great many options for the format of the generated Manifests and Switch Lists.
For the moment, I select that pick ups are displayed in red and set outs are displayed in blue.
So, in this blog entry I have managed to create a cycle between Cassette and Bakery that is serviced by one train and moves cars between those two locations. I have also added the full complement of cars required by the Bakery location and have made the manifests a bit easier for me to read.