Hi Dave & Cliff
Tried to understand Dave's scripts... but I'm not a programmer so scripts are not of much use.
First off.. Connection Prefix is "L" for Digitrax on both computers.
I have modified both computers to have only the default settings by completely uninstalling 4.12, deleting all JMRI folders "everywhere" except registry and then reinstalling the program on both. (I did keep my 'layout'.xml files and selected the c:\program files directory on the Win7 to keep that variable the same.)
The application works perfectly using simulate on both. I have not connected the LocoBuffer-USB at all.
The file D:\Layouts JMRI\Roberts Layout31.xml loads on the Win7 without errors [debug xml reports OK too]. The Signal Table is fully populated.
I noticed one signal head was missing in the table so I added it. I used the correct user name [D Main B CCW], SEC8 4 Aspect and the correct turnout codes for the aspects [919 & 920]. Then I saved the entry. It was correctly processed.
I then closed the table and saved the configuration & panel. Shut down the program to restart PanelPro. I came up OK. When I loaded the layout again, the program reported an error and when I clicked on OK, it closed down.
Here is the log:
2018-12-03 17:16:33,135 util.Log4JUtil??????????????????????? INFO? - * JMRI log ** [main]
2018-12-03 17:16:33,166 util.Log4JUtil??????????????????????? INFO? - This log is appended to file: C:\Users\Robert\JMRI\log\messages.log [main]
2018-12-03 17:16:33,166 util.Log4JUtil??????????????????????? INFO? - This log is stored in file: C:\Users\Robert\JMRI\log\session.log [main]
2018-12-03 17:16:33,198 apps.Apps???????????????????????????? INFO? - PanelPro version 4.12+Rb6a9bb1 starts under Java 1.8.0_151 on Windows 7 amd64 v6.1 at Mon Dec 03 17:16:33 SGT 2018 [main]
2018-12-03 17:16:34,088 apps.Apps???????????????????????????? INFO? - Starting with profile My_JMRI_Railroad.3f2ad5f8 [main]
2018-12-03 17:16:34,713 node.NodeIdentity???????????????????? INFO? - Using jmri-flM1ndZMrhNiaa5aGQeR91-3f2ad5f8 as the JMRI Node identity [AWT-EventQueue-0]
2018-12-03 17:16:36,432 loconet.LnPacketizer????????????????? INFO? - lnPacketizer Started [main]
2018-12-03 17:16:36,573 hexfile.LnHexFilePort???????????????? INFO? - LocoNet Simulator Started [LocoNet HexFileFrame]
2018-12-03 17:16:37,083 util.FileUtilSupport????????????????? INFO? - File path program: is C:\Program Files\JMRI\ [main]
2018-12-03 17:16:37,085 util.FileUtilSupport????????????????? INFO? - File path preference: is D:\Layouts JMRI\ [main]
2018-12-03 17:16:37,086 util.FileUtilSupport????????????????? INFO? - File path profile: is C:\Users\Robert\JMRI\My_JMRI_Railroad\ [main]
2018-12-03 17:16:37,086 util.FileUtilSupport????????????????? INFO? - File path settings: is C:\Users\Robert\JMRI\ [main]
2018-12-03 17:16:37,087 util.FileUtilSupport????????????????? INFO? - File path home: is C:\Users\Robert\ [main]
2018-12-03 17:16:37,087 util.FileUtilSupport????????????????? INFO? - File path scripts: is C:\Program Files\JMRI\jython\ [main]
2018-12-03 17:16:39,133 PanelPro.PanelPro???????????????????? INFO? - Main initialization done [main]
2018-12-03 17:16:53,181 configurexml.ErrorHandler???????????? ERROR - Parse error while parsing file /D:/Layouts%20JMRI/Roberts%20Layout31.xml Exception: org.jdom2.input.JDOMParseException: Error on line 2801: cvc-identity-constraint.4.2.2: Duplicate key value [LT11 DS TR] declared for identity constraint "signalElementName" of element "signalelements".
See for possibly more information. [AWT-EventQueue-0]
org.jdom2.input.JDOMParseException: Error on line 2801: cvc-identity-constraint.4.2.2: Duplicate key value [LT11 DS TR] declared for identity constraint "signalElementName" of element "signalelements".
?at org.jdom2.input.sax.SAXBuilderEngine.build(SAXBuilderEngine.java:232)
?at org.jdom2.input.sax.SAXBuilderEngine.build(SAXBuilderEngine.java:253)
?at org.jdom2.input.SAXBuilder.build(SAXBuilder.java:1091)
?at jmri.jmrit.XmlFile.getRoot(XmlFile.java:197)
?at jmri.jmrit.XmlFile.rootFromURL(XmlFile.java:182)
?at jmri.configurexml.ConfigXmlManager.loadOnSwingThread(ConfigXmlManager.java:646)
?at jmri.configurexml.ConfigXmlManager.lambda$1(ConfigXmlManager.java:604)
?at jmri.util.ThreadingUtil.runOnGUIwithReturn(ThreadingUtil.java:152)
?at jmri.configurexml.ConfigXmlManager.load(ConfigXmlManager.java:602)
?at jmri.implementation.JmriConfigurationManager.load(JmriConfigurationManager.java:231)
?at jmri.implementation.JmriConfigurationManager.load(JmriConfigurationManager.java:170)
?at jmri.implementation.JmriConfigurationManager.load(JmriConfigurationManager.java:160)
?at jmri.configurexml.LoadXmlConfigAction.loadFile(LoadXmlConfigAction.java:52)
?at jmri.configurexml.LoadXmlUserAction.actionPerformed(LoadXmlUserAction.java:44)
?at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
?at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
?at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
?at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
?at javax.swing.AbstractButton.doClick(Unknown Source)
?at javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown Source)
?at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(Unknown Source)
?at java.awt.Component.processMouseEvent(Unknown Source)
?at javax.swing.JComponent.processMouseEvent(Unknown Source)
?at java.awt.Component.processEvent(Unknown Source)
?at java.awt.Container.processEvent(Unknown Source)
?at java.awt.Component.dispatchEventImpl(Unknown Source)
?at java.awt.Container.dispatchEventImpl(Unknown Source)
?at java.awt.Component.dispatchEvent(Unknown Source)
?at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
?at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
?at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
?at java.awt.Container.dispatchEventImpl(Unknown Source)
?at java.awt.Window.dispatchEventImpl(Unknown Source)
?at java.awt.Component.dispatchEvent(Unknown Source)
?at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
?at java.awt.EventQueue.access$500(Unknown Source)
?at java.awt.EventQueue$3.run(Unknown Source)
?at java.awt.EventQueue$3.run(Unknown Source)
?at java.security.AccessController.doPrivileged(Native Method)
?at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
?at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
?at java.awt.EventQueue$4.run(Unknown Source)
?at java.awt.EventQueue$4.run(Unknown Source)
?at java.security.AccessController.doPrivileged(Native Method)
?at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
?at java.awt.EventQueue.dispatchEvent(Unknown Source)
?at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
?at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
?at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
?at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
?at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
?at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: org.xml.sax.SAXParseException; lineNumber: 2801; columnNumber: 249; cvc-identity-constraint.4.2.2:
Layout 31 is a copy of layout 11 which I have not opened or modified so to have a clean file to copy from.
Working on signing up and downloading Dropbox.
Robert
|
Locked
Defining a Departure Track
This is my first go at JMRI. I have loaded all my cars, locations, made 2 train and 2 routes. The build works just fine. I have departure and arrival tracks at 3 of my main terminals. I am wondering how I define them in the program. The switch list has my train switching at those teminals also. I live in Bloomington Mn.
|
Locked
Re: Can't edit crossovers. Right click not working
Perfect Dave.? Thanks so much.
|
Locked
Massoth mobile decoder definition files
hi there
is there a decoder pro definition file for massoth decoders
thanks?
keith
|
Locked
Re: Double crossover needed in Control Panel Editor
Paul,
You can flip between PE and CPE. So flip to PE mode and add your double
crossover. Then flip back to CPE.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org
|
Locked
Re: Panel Pro - Layout Editor - looking for up to date Tutorial
This needs to be in an FAQ somewhere. Thanks to Dick for a clear definition of the differences.
?
?
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 :)
|
Hi Paul,
Like the others have said the way you propose will work. I would like to offer a second way to experiment with which will save you?some time, be simpler,?and?will better suit your future needs.
You can?do all that you listed in your first post by just building Train-B?and no others. This uses JMRI_OPS Manifests and Switchlists.?
For clarity; Manifests are the switching documents that accompany the Train as it goes around the layout.? Switchlists?show the cars that are switched out at a location.?
Here's what you can do:
First off all you will need to change your setup slightly
A.?- Remove the Siding-S from your Route-B?for Train-B and replace it with City-C (same location)
B - In Route-B there?is a Comment section for each location.? Put a Comment in such as "Train to drop/pickup?all cars to/from City-C on Siding-S"
C - Check your Spurs in City-C to make sure there are no restrictions preventing Train-B from picking up or dropping off cars.
Create a Manifest for Train-B
1? - Build only Train-B
2? - Print?the Manifest
3 -?Go to the bottom of the "Trains" page and click "Switch Lists"
4. -?Check off the location (City-C) for that the Switchlist, and print it out.
You will see that the Switchlist shows all the pickups and drop offs for Train-B at City-C
Give this Switchlist to Train-A.? He can?use this list to gather all the cars from the Spurs and?put them on Siding-S for Train-B to pickup.
Once Train-B pickups up the cars and drops the?others.? Train-A can use the same?Switchlist to deliver the new cars to the Spurs.
This is all accomplished with just 1 Build (Train-B). In fact you don't even need to have Train-A (or Train-C) in your JMRI-OPs setup.
When all the switching is done you can Terminate Train-B.
Where this suggestion really shines is it can handle multiple trains that pickup and drop off at a location.?Build all your Trains then print a Switchlist for?the locations you have a local switch crew at..? The Switchlist will have all the?cars which are picked up and dropped off at that location, grouped by the Train they are associated with.?
This works very well in Yards too.? I have an Arrival/Departure track in my yard that I use the same as your Siding-S.???
Before doing any changes to your existing setup,?try this with a new train (Train-D for instance) and see if this works for you.
Hope this helps
-Scott-
(aardtechus)
|
Based on recent discussion items in this forum, I¡¯ve added some more ¡°how to¡¯¡± and ¡°what-where¡¯s¡± as well as continued with reorganizing the scripting web and help pages. ?These are?now on the JMRI web site at: ?.??They will also become part of the Help system in the next JMRI release 4.13.6.
While example scripts should remain your primary source of information on how to create JMRI scripts (learn by doing!), I know that I benefit from written explanations as well (learn by reading). ?If you do too and would like to help other users, I¡¯m volunteering to collect and edit additional content you send my way and to incorporate them into an appropriate part of the scripting section.
Again, a hearty ¡°thank you¡± to our developers and other experts who make this forum and JMRI so useful to model railroading.
Jerry
___________________________________ jerryg2003@...
|
Check the preferences/defaults in JMRI and make sure it shows connection to LocoNet not Internal. I had the same issue that I got figured out today.
|
Locked
Re: Can't edit crossovers. Right click not working
toggle quoted message
Show quoted text
On Dec 2, 2018, at 7:16 PM, Jack Basiago <jbasiago@...> wrote:
It's being a real bugger. You can't just remove the references to the blocks in <layoutturnout> elements. You have to change them to another block that is recognized. But if you reassign the block to the block that it was assigned to in the panel dialog, it looks like it will take it, but it throws the exception again when you reload the file. This is a total mess. It will be easier to start from scratch again. I just don't know what I did to get in such a mess. How do you stay out of trouble when you're building layout panels. Looks like you have to define everything, particularly blocks, before you use them. The create options in the edit dialogs must be broken somehow. Any insights? When I look at the XML, there are lots of elements with different ID's that use the same system name.
Thanks for your help.
Jack
|
Locked
Double crossover needed in Control Panel Editor
I have a working panel in Layout Editor for my layout and now I want to build one in CPE but CPE does not have the double crossover track segment icons I need to do my layout. I know that PE has a double crossover but I want to use CPE.? I tried to replicate the functionality of a double crossover in CPE by using left and right single crossovers back to back but it does not replicate how the flow through a double crossover actually works. I even tried using various combinations of left and right turnouts but that became a mess and did not appear that it could produce anything workable.
Are there any plans to add a double crossover icon to the CPE track set?
|
I am try to install a LocoBuffer-USB connection on my new laptop (Windows 10). The driver install goes OK but I end up with no connection to the Loconet. Both green led's on the LocoBuffer (version 2.040) are lit and the red led will flash when I send commands from my Digitrak throttles. I have reloaded the drivers several times with no luck. What am I missing? The command? station is a DCS 210.
Thanks
Don McGovern
|
Locked
Re: Can't edit crossovers. Right click not working
It's being a real bugger.? You can't just remove the references to the blocks in <layoutturnout> elements.? You have to change them to another block that is recognized.? But if you reassign the block to the block that it was assigned to in the panel dialog, it looks like it will take it, but it throws the exception again when you reload the file.? This is a total mess.? It will be easier to start from scratch again.? I just don't know what I did to get in such a mess.? How do you stay out of trouble when you're building layout panels.? Looks like you have to define everything, particularly blocks, before you use them.? The create options in the edit dialogs must be broken somehow.? Any insights?? When I look at the XML, there are lots of elements with different ID's that use the same system name.
Thanks for your help.
Jack
?
|
Locked
Re: Can't edit crossovers. Right click not working
Jack,
I do some development in my areas of interest. The layout block issue is on my todo list. I plan to work on it during the next development cycle.
Dave Sand
toggle quoted message
Show quoted text
On Dec 2, 2018, at 5:58 PM, Jack Basiago <jbasiago@...> wrote:
Dave, are you a developer? I appreciate your quick response to this.
|
Locked
Re: Can't edit crossovers. Right click not working
Dave, are you a developer?? I appreciate your quick response to this.?
|
Locked
Re: Can't edit crossovers. Right click not working
Yea, I've got an editor.? I'll take care of it.? Is this a bug or expected behavior?? Is there anything I need to do to describe what happened here for others to possibly fix it?
|
Locked
Re: Can't edit crossovers. Right click not working
Jack,
Do you have access to a programing editor? Since you are using a Mac, TextEdit may work.
Basically you need to remove the blockname entries from the affected layout turnout items.
If you want, I can cleanup the XML file for you, but I have not been able to figure our OLCB simulation yet so I won¡¯t be able make sure the changes are correct.
Dave Sand
toggle quoted message
Show quoted text
On Dec 2, 2018, at 5:41 PM, Jack Basiago <jbasiago@...> wrote:
I did not do any renaming of blocks. After submitting the topic, I did find the errors in the debug window. I created the blocks while in the crossover editor. I see now that all the blocks that are un-editable are the ones with the errors. Any suggestions on fixing this issue. I've done a Delete Paths, but that hasn't fixed anything. Working with this application has been a little frustrating. I've run across these kinds of issues a lot. It's like I have to figure out how to navigate through the software so that it doesn't break.
Thanks,
Jack
|
Locked
Re: 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 :)
On 12/2/2018 5:21 PM, John Pearson
wrote:
toggle quoted message
Show quoted text
Dave?
Quick response appreciated, thank you.
a few comments / observations / Questions?
1) your listed order of actions easy to follow, I'll try it
out tomorrow on a simple test diag?
2) Found Quaker valley ok lots of writing but they sem to
be persuing my objective ,? Not sure at this stage what the
difference between Sig Heads and SSL &? Sig Masts + Signal
Mast logic? might be, I'll think about and reasearch.? ? ?(
SSL ? please,? ?Single Signal Lamp ?)?
3) Also your warning about turnouts becoming "blocks" is
significant as I was lumping them in with track segments /
bigger blocks..... A crossover between two main lines would
become a block in its own right? Or does it split in the
centre between the two parallel tracks ?
No doubt the reason that Interlocking drawings label
turnouts with an OS number and detect vehicles on the OS..? ?
Is joining two turnouts throat to throat acceptable as one OS
item ? ( Guess it becomes a double slip ).
Many?thanks for your assistance??
John Pearson
?
On Sun, Dec 2, 2018 at 6:01 PM Dave Sand < ds@...>
wrote:
John,
Take a look at?
The signaling section is based on signal heads and SSL
rather than signal masts and signal mast logic.
Listed below are the steps that I use for a new Layout
Editor Panel.? The steps are based on using the
appropriate simulation mode for the hardware.? I also use
signal masts and signal mast logic for all of my designs.
?
- Place turnout icons on the panel and connect them
with track segments.
- Create turnouts in the turnout table.? Use default
feedback settings. ?
- Assign turnouts to the turnout icons.? Clicking on
the turnout icons should change the turnout state and
the icon.
- Turnout context menu: ?Edit item.
- Create occupancy sensors in the sensor table.
- Assign blocks to the turnout icons and track
segments.? Set the occupancy sensor for each layout
block.
- Context menu: ?Edit item.
- Set Block
- Select Create/Edit
- Select Sensor tab and select sensor name.
- Verify that the panel is valid using the Tools
>> Check items.
- Add sensor icons to the panel to simulated train
movements.? Verify that the correct tracks show
occupied.
- Create signal masts in the signal mast table.
- Assign the signal masts to the appropriate block
boundaries.
- Context menu: ?Set Signal Masts...
- Use the Signal Mast Logic table to generate the
signal mast logic.
- Verify the SML works by setting blocks occupied and
setting turnout positions.
Obviously there are a lot of details missing, but it
provides a general flow.
Step 5 is very important.? Since you are talking about
interlocking plants, the block topology must be correct.?
The basic rule is that each turnout or turnout group must
be its own block.? This provides the necessary block
boundaries for placing signal masts which protect the
interlocking.
Dave Sand
On Dec 2, 2018, at 4:29 AM, John
Pearson <pearsonjohn99@...>
wrote:
Hello JMRI group, I¡¯m new to the group and looking for
Help.
Intro ?I¡¯ve dabbled with Panel Pro over the last 2 years
to the extent of creating a plausible US&S CTC panel
with layout model board across the top.??The board has
NO working logic.
Now?at the stage of needing to design the signaling
system to work I¡¯ve started LAYOUT EDITOR, ?but having
great difficulty getting in.....? The only?tutorial I
can find is by Dave Duchamp¡¯s NMRA presentation dated
2008 does not cover the current version of Panel Pro,
4.12?
Any guidance appreciated, starting from scratch. ?
MY INITIAL OBJECTIVE IS A WORKING LOGIC INTERLOCKING
PLANT USING LAYOUT EDITOR?
Eventual ambition Merging LAYOUT EDITOR drawing with
WORKING CTC PANEL AND LAYOUT SIGNALS controlled by MRCS
/CMRI logic
At the moment I cannot get past drawing a turnout, track
segment and Tools-Tables-Turnouts, without them fighting
each other !!!!!
My current set up?
a) lap top Samsung - Windows 7
b) Panel Pro ?4.12+Rb6a9bb1
c) Java 1.8.0_191
Previous set up - CTC panel?
a) lap top Samsung - Windows 7
b) Panel Pro ?4.10
c) Java 1.6?
Guidance appreciated?
John pearson?
|
Locked
Re: Can't edit crossovers. Right click not working
I did not do any renaming of blocks.? After submitting the topic, I did find the errors in the debug window.? I created the blocks while in the crossover editor.? I see now that all the blocks that are un-editable are the ones with the errors.? Any suggestions on fixing this issue.? I've done a Delete Paths, but that hasn't fixed anything.? Working with this application has been a little frustrating.? I've run across these kinds of issues a lot.? It's like I have to figure out how to navigate through the software so that it doesn't break.
Thanks,
Jack
|
Locked
Re: Can't edit crossovers. Right click not working
Jack,
If you look at the system console (Help >> System Console) you will see a lot of errors.
What you are seeing on the panel is a result of the errors. By any chance, did you try renaming a block table entry after assigning blocks to the cross-overs?
Dave Sand
toggle quoted message
Show quoted text
On Dec 2, 2018, at 4:53 PM, Jack Basiago <jbasiago@...> wrote:
JMRI version: 4.13.4
Java version: 1.8.0_171
MacOS: Version 10.13
I've been working on a layout that includes 6 crossovers, 3 left hand and 3 right hand. I've uploaded my layout to Full Yard. When I open this panel, I can no longer right click on the 4 upper crossovers to edit them. The lower two crossovers still work. Also, why are my track lines not showing the main line width on these crossovers. Is there anything I can do to make the layout look more consistent. It seems that there is a problem when you have one crossover connected directly to another.
Thanks for all your help.
Jack Basiago
|
Jack Basiago
Ken Cameron
Ken Glover
Paul Davidson