开云体育

On Nov 23, 2018, at 9:22 AM, paul@... wrote:

Dave,

I've now downloaded 4.14.5. Thanks for the inclusion of N148 and the example script. I'm looking forward to setting up the timetable. I'd been wondering how I could easily set this sort of data up but this solves the problem brilliantly and I can now start experimenting with a script to do the integration with dispatcher.

A minor point - it appears that the 'Route Duration' field is not being set on the train display. This seems to be the case for new trains and trains migrated from the 4.14.4 version. The timings appear correct on the relevant segment's Train Graph. Also if you're considering any enhancements, a function to duplicate a train would be really useful, allowing for the situation where there a several trains with the same basic itinerary but at different times in the schedule.

Paul

On Dec 4, 2018, at 2:41 AM, John Pearson <pearsonjohn99@...> wrote:

Dick
Thanks you for the EXCELLENT reply dated Dec 2nd it has opened my eyes to the differences in the different JMRI design systems. I agree with Alan B Pearce’s comments “ it should be in FAQ” As a newby JMRI bless it is akin to drinking from a full bore fire hydrant !

To your note it is apparent that I should be using (CPE ). Control Panel Editor
My layout is quite small and caters around an interlocking controlled by a CTC machine. there are several back to back crossovers and a flat crossing with 4 90 degree diamonds, many of the signals are eye candy with of stage virtuals.
I have no room for ABS or long stretches of track.

Signal Masts are obviously the way to go ( thanks again for the explanation )

What I need now more than anything is a JMRI tutorial covering CPE & SML

BTW I have some of your SM LEDs ( RR-CirKits ) the Colors are excellent
Many thanks
John Pearson


On 3 Dec 2018, at 11:55, Alan B. Pearce <alan.b.pearce@...> wrote:

This needs to be in an FAQ somewhere. Thanks to Dick for a clear definition of the differences.

From: [email protected] <[email protected]> On Behalf Of dick bronson
Sent: 02 December 2018 23:47
To: [email protected]
Subject: Re: [jmriusers] Panel Pro - Layout Editor - looking for up to date Tutorial

John,

I'll make some (many) comments based on my personal opinions.

a) Layout editor (LE) is a vector view of your layout. I.e. the toe bone connects to the foot bone, the foot bone, connects to the ankle bone, .... It is designed to document and edit the connectedness of the layout. It only allow for one definition of each chunk of the layout. (vector) As soon as you have two turnouts that operate as one (e.g. crossover) or two detectors that operate as one you need to fight the system to figure out how to defeat its basic nature. (typically by making an internal shadow to define the duplicate item) It was never designed to make a CTC panel drawing in the first place. Doing so is sort of like trying to use a CAD program to paint a landscape.

b) The Control Panel Editor (CPE) is designed to create a pictorial CTC machine (Control Panel) view of your layout. It consists of various icons and images that allow you to recreate either a classic or modern CTC panel with surprising fidelity. It neither knows nor cares how one image or icon connects to another. The disadvantage of that of course is that you need to manual define the items and how they fit together or what they control. The advantage of that is that it will not try to force you into its own way of doing things.

c) The Panel Editor (PE) is the original JMRI panel editor which has been superseded by the Control Panel Editor which has many new features and ease of use advantages over the original. PE should have been depreciated years ago, but JMRI seldom does that for anything.

d) Signal heads refers to the class of hardware that can only control a signal one set of lights at a time. Typically it controls R, Y, and G lamps.

e) Signal Masts refers to an entire signal, be it one head or many heads, 3 lights per head or 7, etc. Typically it operates by sending aspect messages, not individual light commands. However if your hardware doesn't understand aspects, then JMRI can create signal aspects out of multiple heads.

f) SSL stands for Simple Signal Logic. Think 'Simple' as in 'Simple minded', not simple as in 'Easy'. It does basic ABS on single track fairly well. However as soon as you add a crossover or anything more complex you need to cross your eyes and stand on one leg to figure out how to make it work correctly. (mostly done by adding invisible signals and calling them 'distant')

g) SML Signal Mast Logic. IMHO This is the way signal logic should always be done. It treats signaling as aspects (per the prototype). It calculates aspects as they relate to pairs of signals, i.e. the signal you are facing paired with the next signal along the path you will be taking. It has built in rules for a growing number of prototype railroads. This saves you a lot of research into how signaling should be done on your railroad. It takes the most complex trackage in its stride. For each signal pair you simply list the correct turnout positions along that route and list all the blocks between this signal and the next.

h) NEVER mix SSL and SML unless you enjoy cat fights and detective mysteries. They do not play at all nicely with one another and you will be left wondering just why in the world your signals behave the way they do.

i) Crossovers in CTC territory are two blocks. When calculating any block requirements always think about how many different trains can occupy any given area at the same time. That is the number of block detectors required. For single track it is one, unless the track is long, then it may be several so one train can follow another. For a single turnout it is one. For a crossover it is two, one on each side if they are passing. For a yard ladder it is ........ one. (unless you can switch two parts of the ladder at the same time somehow) Of course a yard ladder is not usually signaled, but it makes a nice example. <G>

Dick :)

._,_._,_