Hi. I just joined the group because I am new to JMRI (and model railroading) and have questions about the program.

I have a location with one spur long enough to hold two flatcars. All my trains (so far) stop at this location. I have the move count set to two at this location and pick-up and drop off are enabled. The spur only accepts loaded flatcars. Also, random is set to off. However, the program creates switch lists which only have one move at that location when two are possible.?
The only thing I can think of is it has something to do with the fact that the train length in settings is set to the length of trains I will want to run when the layout is finished and I have all the rolling stock I will need (right now I probably have less than half). Does the program prioritize train length (that is to say try to keep the staging tracks being used full) over car movement?

I would love to hear any ideas any of you have about why this happens. Thanks

Paul

Thanks, Nick. I now understand the naming a bit better. But I'm unable to find the xml files for the tutorials. I see no reference to them on the mentioned site, and on?http://www.quaker-valley.com/CTC/JMRI_Panel_Tutorial.html there is a link to download each of the three tutorial xml files, but when I click on it, either on my Windows PC or on my iPhone, I get a blank screen and nothing downloads. How can I contact you off-list? Thanks.

Marc,

On 21 Sep 2019, at 1:37 AM, forfoum@... wrote:

You are a tad confusing. " CV1 and CV 66 are both short addresses " But I do follow what you are getting at and I had stated same as you in earlier response to thread.

Sorry, what I should have said is that "the numbers stored in CV1 and CV19 are both short addresses".

Dave in Australia

开云体育

Hal,

Do not be fooled into thinking that SSL is simpler than aspect based signaling. It most definitely is not. The 'Simple' in the name means Simplistic, not easy. You wind up having to do strange things and add invisible signals to do even easy things like crossovers properly. It was all that was originally available in JMRI until things got advanced enough so that JMRI could follow actual prototype rules. Now that JMRI can use actual signal rules for different railroads, using SSL is sort of like filling out your taxes with quill pen and abacus instead of getting a copy of Quicken because you want to keep things 'simple'.

There is no more reason to understand the details of the aspect based signaling control files than there is a need to understand your ECU in order to drive to work.

Dick :)

The program calculates how many lines should fit.? Could you try printing to a pdf file and see if all of the lines are there?? Seems like a printer issue.

Dan

I have my Manifests ready to print. ?First I want to print my CAR FILE. ?When I do print the car file (or my manifests) the page layout is larger than a normal page of printing and I lose the last line which should be printed. ?I am using the latest release 4.17.4?

How do I control the number of lines that will be printed PER PAGE on a multiple page document. ?I have selected the 4.5 - 11 option. ?I need to increase the space of the borders so I do not lose data to be printed. ?When I print the MANIFESTS I do not print the last line to be printed and it DOES NOT carry over to the next page,

THANK YOU....FRank in Houston

Jacques,

The same OpSw 36 problem has been around since DCS 100/200 and our club has been working on that issue for several years. With a lot of help from Billybob and several other members on this group, we have come to the conclusion that a combined script and manual activity is mandatory. The script is automatically run in the Start Up sequence.

Most of script code deals with a GUI that provides a dialog window that instructs the person to flip a toggle switch on the front of the command station, and to some extent also detects that the person has probably completed that activity.

Since both a jython subfolder and a resources subfolder that cumulatively contain three files are involved a zip file has been uploaded for your review.

Without any experience using a DCS 240, it is impossible for me to believe that these could be used without serious modification. However, at least some of this information may provide you with some clues.

Cliff in Baja SoCal

Thanks all for the clarifications. I'll try to digest it all (with a Tums or two), but for now, since I'm just starting with signalling, I think I'm gong back to SSL and signal heads. Thanks again! Hal

Hello all. I'm trying to figure out how to use signal heads and SSL and am finding Robert Bucklew's tutorial 3 () very helpful. But I have two questions:

1. does anyone know where I can find a panel file (xml) for the finished product of this tutorial?

2. I'm confused about the naming of the signal heads. On page 3 are instructions for adding 4 heads:
4 East Upper, 4 East Lower, 4 West main, and 4 West Siding.
On subsequent pages these signals are all placed in the northWEST corner of the layout, if I'm not mistaken. I'm puzzled why the upper and lower are called East since they are placed in the west portion of the layout. What am I missing?

Thanks, Hal.

On Thu, Sep 19, 2019 at 07:55 PM, billybob experimenter wrote:

Unfortunately, it appears that some recent web page re-organization work is incomplete. This means that the individual mast-specific pages are not rendering correctly. This leaves these pages partially "broken", with some missing text. I have filed an issue with the JMRI development team.

Regards,
Billybob

Billybob,

This issue should now be fixed.

Thanks for raising it.

Best regards,

Matt H

Petr,

This issue should now be resolved - can you verify?

Thanks.

Best regards,

Matt H

14 -> 27 and 28 -> 55 were Ugly Hacks built into some early command stations. Basically, the command station would rapidly switch back and forth between step N and N+1 to _effectively_ have step N+0.5. Putting a 0.5 in between all 14 steps gives you 27 total steps.

Once 128 existed, there was little need.

Bob

On Sep 20, 2019, at 8:17 PM, whmvd <vandoornw@...> wrote:

55?? That's a new one on me!

On Fri, 20 Sep 2019 at 18:14, <forfoum@...> wrote:
As per the LE103 doc I found on Yumpu, These did not support 128.

They supported 14/27 or 28/55 Speed Steps.

So if the Command Station default for Speed Steps is 28. No issue. But you would need to check how the decoder address is REGISTERED with
your EASYDCC for speed steps, might have been changed inadvertently.

Your CV7 = 0. If that is correct, that is some very old decoder. Values should be 41 thru 43 for the LE103.

Marc

--
Bob Jacobsen
rgj1927@...

开云体育

wouter,

No, I haven't checked the JMRI speed table for this decoder recently. With EasyDCC I do normally have a start voltage set, and mid and full speed, often evenly divided with full speed at 100%. On a few of my faster locos, full speed is reduced. Momentum is set for 4 or 5 accelerating and braking. It seems the JMRI roster info needs to be checked for that.

In 28 speed step mode, wouldn't the JMRI be sending "speed step nn", and the decoder using its value for that speed step to control the motor? I don't think there is a way JMRI could tell these decoders the actual duty cycle the decoder should be setting.

If the number of speed steps is mismatched, or the JMRI speeds are 0 for start, mid, and full, wouldn't F0 still control the lights? I can't even do that on LE103s with JMRI, but can with EasyDCC plug in throttles. The speed table values seem more likely to be the source of trouble with the Zimo decoder, where I could control F1, but not train speed.

The recent discussions of what may be wrong are interesting and educational. Thanks for helping me, guys! I have always set these decoders up in EasyDCC as Class 2, which supports 28 speed steps. Even in the late 1990s, the decoders I used supported that. There was no reason to use the coarser 14 speed steps on any of my locos. Notice 1477 read back showed it is configured for 28/128 speed steps. I believe all my roster entries are set for 28 speed steps, so that should match, but I will confirm that.

Don Weigt
Connecticut

Marc,

On 20 Sep 2019, at 1:44 PM, forfoum@... wrote:

Not what I said. I asked what would occur if CV1 = 66 and CV19 = 66. And I tested it and the decoder accepts this. Now the Command Station sends out commands to Address 66... So which will it be ? the Standard address or the Consist address ? CV19 takes precedence over others and I do not see the Command Station changing this based on which throttle.

CV1 and CV 66 are both short addresses. With that configuration, the only way to make the loco move is to send short address 66 speed packets. Having a non-zero CV19 overrides anything in CVs 1, 29, 17 or 18 as far as speed packet receptivity is concerned.

<>

Dave in Australia

This is thought to be an unwanted side-effect of migrating the JMRI site to https:



Bob

On Sep 20, 2019, at 11:32 AM, Petr ?ídlo via Groups.Io <sidlo64@...> wrote:

Lately there is a strange message in the Apperance table
for example

Error: This appearance does not appear in the aspect table. Check spelling and upper / lower case.

In the Aspect table, the respective aspects are
for example

I did not observe this error before.

--
Bob Jacobsen
rgj1927@...

Conrad,

I think that the loco decoder and VSD are in sync when the HALF_SPEED key is switched and the loco is not running.

Prerequisite: the basic acceleration and deceleration times of the loco decoder and VSD are in sync.

If the HALF_SPEED key is changed while the loco is running, things are not fully synchronized.

I admit I haven't read the NMRA recommendations on half-speed.

Thus, am I correct in understanding that VSD's engine code is only responding to LocoNet "Set speed of loco in slot 2 to xx" packets?? I say this because watching my JMRI LocoNet Monitor I see that toggling HALF_SPEED (F8) does not result in speed packets being sent.? This makes sense as HALF_SPEED?just tells the decoder to cut or increase the speed, say by half, independent of throttle setting.? So the code for HALF_SPEED goes to say F8, but is not linked to the engine functions.

The answer to your question is yes. JMRI provides a speed value between 0 and 1. If HALF_SPEED is active, VSD divides the value by 2. That's it. There are no speed setting packages on the LocoNet. VSD then uses momentum to adjust the speed. And it looks like the loco decoder doesn't do this.

Klaus