开云体育

That was it.

Thanks.


Roger T.

That makes sense. I'll give it a try. Thanks.

Roger T.

RJM,



On which should be 'Internal' and which should be 'LocoNet' (or other real
hardware).



When there is a real device that either is something you control or listen
to on the layout, those (usually sensors or turnouts) are the system things,
your case LocoNet. So the output bits on the Se8c which are either pairs of
turnouts to operate a signal or a turnout drive, those would be LT(digits)
things. The feedback or buttons on the board, those would be LS(digits)
things.



But a lot of things are not something you directly deal with on the layout,
you deal with some logical construction (signal mast) and that is an
'Internal'. So a block would be internal because you don't have a direct
device that is that block. You have other things, like sensors for occupancy
(LS) and turnouts that are part of the tracks in that block. Another is the
signal mast would be 'internal' because it is made up of signal heads. Those
heads are also internal because they are made up of two turnout addresses
(LT) which are real things.



Maybe this will help understand when one or the other. It isn't 100% but a
good starting point to know what to expect.



-Ken Cameron, Member JMRI Dev Team

www.jmri.org

www.fingerlakeslivesteamers.org

www.cnymod.com

www.syracusemodelrr.org

Roger, if you assign 151 to the engine you have to use 4 digit addressing and type in 151. 127 is the highest number for 2 digit addresses. I suspect the you used the 2 digit address and when you typed in 151 it went to highest number allowed which is 127.
Al Babinsky

Sent from my Verizon HTC Smartphone

----- Reply message -----
From: "'Roger Traviss. ' rogertra@... [jmriusers]" <jmriusers@...>
To: <jmriusers@...>
Subject: [jmriusers] New engine address
Date: Mon, Jun 19, 2017 15:03

I'm try to assign a new address to one of my engines but it keeps defaulting to 127 when I want it to be 151. I have swapped bodies so naturally want to assign the current body number. I have tried numerous times to readdress the decoder but it insists it is 127.



I've done this before on decoders but can't for my life figure out what I'm doing wrong.



Cheers.



Roger T.

I ran across something similar to this regarding 2 or 4 digit. In hex, 151
(dec) is 97 (hex) making it a 2 digit vice 4 digit engine number. I was
trying to call my train engine a 4 digit (more than 2 digit) and the
decoder wouldn't take right. I couldn't get a read back on the decoder.
Made it a 2 digit number instead of 4 and it took. Maybe that is your
problem? If it isn't that, Sorry....


On Mon, Jun 19, 2017 at 6:03 PM, 'Roger Traviss. '
rogertra@... [jmriusers] <jmriusers@...> wrote:

I'm try to assign a new address to one of my engines but it keeps
defaulting to 127 when I want it to be 151. I have swapped bodies so
naturally want to assign the current body number. I have tried numerous
times to readdress the decoder but it insists it is 127.

I've done this before on decoders but can't for my life figure out what
I'm doing wrong.

Cheers.

Roger T.

Sent from my iPhone

[Non-text portions of this message have been removed]

I'm try to assign a new address to one of my engines but it keeps defaulting to 127 when I want it to be 151. I have swapped bodies so naturally want to assign the current body number. I have tried numerous times to readdress the decoder but it insists it is 127.

I've done this before on decoders but can't for my life figure out what I'm doing wrong.

Cheers.

Roger T.

What ever you are going to use to sense the occupancy of block would be a stationary decoder. For the information to be available to JMRI it has to be sent to the computer. With a Loconet system that is accomplished by having an adapter between the loconet and the computer, I recommend a Locobuffer, others like the PR3.

Signing your name lets us address replies to your name.


Walt

Vince,

I tried another test using the same turnout and sensor names and still no blocks were created.

If you are willing, try uploading the panel XML file, or send it directly to me. Although the odds are small, there might be a clue in the file.

Dave Sand

Hi Hubert/Steve,
I've been following this thread with interest as I'm just about to get in to automation & whilst I don't want to hijack this thread, I do have a couple of questions.I really don't mind if you want to leave the answers until you get the issue sorted to save any confusion, but I thought the questions might help others that are new to or thinking about using automation ..
Q1: What is the difference between using signal heads & signal masts??(I've seen these referred to in several threads so it obviously makes a difference between the types?).
Q2: What direction sensors are you using - or are aware of??(I was under the impression that JMRI would work out the direction of travel itself via two consecutive detectors (IR or other)).
Stu...
Sent from my Samsung Note3

Hi John,

My transits do include all the sections to make a circuit, and the first and last sections are the same. Trains loop around the layout very nicely.
Dispatcher allocates 3 sections ahead. You can see this as the yellow blocks in my youtube video.
So your loop must be more than 4 sections or I would expect the issue you describe. How many sections are in your transit?


SteveT

Thank You Walt. So if I develop the JMRI to use block sensors for signals and road crossings should I use the loconet? Have Digitrax DCS51 - SEC8C - BD4 to run on my layout. RJ

Wow. I cannot go back to 4.7.5, as NX and stored warrants are no longer
working.

First I just replaced the 4.7.6 .jar file to the 4.7.5. Nope.

I then re-installed 4.7.5 (on top of 4.7.6 as I cannot afford to d a
scratch re-install), same problem:

2017-06-19 10:32:42,985 util.Log4JUtil INFO -
* JMRI log ** [main]
2017-06-19 10:32:43,001 util.Log4JUtil INFO - This
log is appended to file: C:&#92;Users&#92;Railroad&#92;JMRI&#92;log&#92;messages.log [main]
2017-06-19 10:32:43,001 util.Log4JUtil INFO - This
log is stored in file: C:&#92;Users&#92;Railroad&#92;JMRI&#92;log&#92;session.log [main]
2017-06-19 10:32:43,001 apps.Apps INFO -
PanelPro version 4.7.5+R187bd9e starts under Java 1.8.0_111 on Windows 10
x86 v10.0 at Mon Jun 19 10:32:43 PDT 2017 [main]
2017-06-19 10:32:45,130 apps.Apps INFO -
Starting with profile My_JMRI_Railroad.3bb3dac2 [main]
2017-06-19 10:32:45,442 node.NodeIdentity INFO - Using
jmri-D4BED9D8AD87-3bb3dac2 as the JMRI Node identity [main]
2017-06-19 10:32:46,042 usbdriver.UsbDriverAdapter INFO - NCE
USB COM6 port opened at 9600 baud [main]
2017-06-19 10:32:46,121 gridconnect.GcSerialDriverAdapter INFO - COM3
port opened at 57600 baud, sees DTR: true RTS: true DSR: false CTS: false
CD: false [main]
2017-06-19 10:32:46,152 nce.NceConnectionStatus INFO - NCE
EPROM revision = 7.3.6 [AWT-EventQueue-0]
2017-06-19 10:32:46,386 locobuffer.LocoBufferAdapter INFO - COM5
port opened at 57600 baud with DTR: true RTS: true DSR: true CTS: true CD:
false [main]
2017-06-19 10:32:47,714 util.FileUtilSupport INFO - File
path program: is C:&#92;Program Files (x86)&#92;JMRI&#92; [main]
2017-06-19 10:32:47,730 util.FileUtilSupport INFO - File
path preference: is C:&#92;Users&#92;Railroad&#92;JMRI&#92;My_JMRI_Railroad&#92; [main]
2017-06-19 10:32:47,730 util.FileUtilSupport INFO - File
path profile: is C:&#92;Users&#92;Railroad&#92;JMRI&#92;My_JMRI_Railroad&#92; [main]
2017-06-19 10:32:47,730 util.FileUtilSupport INFO - File
path settings: is C:&#92;Users&#92;Railroad&#92;JMRI&#92; [main]
2017-06-19 10:32:47,730 util.FileUtilSupport INFO - File
path home: is C:&#92;Users&#92;Railroad&#92; [main]
2017-06-19 10:32:47,730 util.FileUtilSupport INFO - File
path scripts: is C:&#92;Program Files (x86)&#92;JMRI&#92;jython&#92; [main]
2017-06-19 10:40:37,247 audio.JoalAudioFactory INFO -
Initialised JOAL using OpenAL: vendor - OpenAL Community version - 1.1
ALSOFT 1.15.1 [Listed Table Generation]
2017-06-19 10:41:19,896 jmrit.Sound ERROR -
file:/C:/Program%20Files%20(x86)/JMRI/resources/sounds/phone_ring_old.wav
is not a recognised audio format [AWT-EventQueue-0]
2017-06-19 10:42:11,677 ptionhandler.UncaughtExceptionHandler ERROR -
Uncaught Exception caught by
jmri.util.exceptionhandler.UncaughtExceptionHandler [Thread-71]
java.lang.NullPointerException
at jmri.jmrit.logix.OBlock.getPortalByName(OBlock.java:729)
at jmri.jmrit.logix.RouteFinder.makeLevel(RouteFinder.java:125)
at jmri.jmrit.logix.RouteFinder.run(RouteFinder.java:97)
at java.lang.Thread.run(Unknown Source)
2017-06-19 10:42:44,609 logix.Engineer WARN -
RosterSpeedProfile not found. Using default ThrottleFactor 0.5
[AWT-EventQueue-0]

Apparently the java error reporting has been changed too. Never seen one
this short.

Leo P
[up a creek without a paddle ... or boat - now I have to restage 35 trains
manually ... UGH! what a way to start the week]

On Mon, Jun 19, 2017 at 10:18 AM, leo pesce <lpescester@...> wrote:

OK,

what a heck happened to the NX warrants?

I cannot even select an engine number. And all the other options which I
need to run different trains, they are gone too.

Going back to 4.7.5 ....

Leo P
[shaking my head, left and right, left and right, ....]

On Sat, Jun 17, 2017 at 3:24 AM, Bob Jacobsen rgj1927@...
[jmriusers] <jmriusers@...> wrote:

Test version 4.7.6 of JMRI/DecoderPro is available for download.

This is the next in a series of test releases that will culminate in a
production release, hopefully in June 2017.

There have been a lot of updates in this version, so it should be
considered experimental.

For more information on the issues, new features and bug fixes in 4.7.6
please see the release note:
<>

Note that JMRI is made available under the GNU General Public License.
For more information, please see our copyright and licensing page.
<>

The download links, along with lots of other information which we hope
you'll read, can be found on the release note page:
<>

Bob
--
Bob Jacobsen
rgj1927@...

[Non-text portions of this message have been removed]

Hi Dave
I have not created any block table, the only tables I created is Turnout Table with System Name IT5 and NT1 to NT4, User Name Turnout 1 to Turnout 5. Sensors Table with sensors IS801 to IS807 System Name, and Block 801 to Block 807 for User Name, plus IS901 to IS904 System Name and Interlock 901 to Interlock 904 for User Name. Also in Layout Editor I placed 5 single Turnouts L and R as per configuration of the JMRI Panel Tutorial by Bob Bucklew with no track line connection between turnouts. B. Bucklew doesn't use Block Table in this tutorial, I have done it in version 3.11... and 4.0 and works great, this new Layout Editor after save the panel, if open with an xml Editor shows IB1 to IB7 System Name and Block 1 to Block 7 user Name, I don't know where these blocks come from, and the <filehistory>at the bottom of the panel builds up for ever for each time save and open the panel I thought this was fixed after v 3.10...
Thank You for responding.
Vince

OK,

what a heck happened to the NX warrants?

I cannot even select an engine number. And all the other options which I
need to run different trains, they are gone too.

Going back to 4.7.5 ....

Leo P
[shaking my head, left and right, left and right, ....]

On Sat, Jun 17, 2017 at 3:24 AM, Bob Jacobsen rgj1927@...
[jmriusers] <jmriusers@...> wrote:

Test version 4.7.6 of JMRI/DecoderPro is available for download.

This is the next in a series of test releases that will culminate in a
production release, hopefully in June 2017.

There have been a lot of updates in this version, so it should be
considered experimental.

For more information on the issues, new features and bug fixes in 4.7.6
please see the release note:
<>

Note that JMRI is made available under the GNU General Public License. For
more information, please see our copyright and licensing page.
<>

The download links, along with lots of other information which we hope
you'll read, can be found on the release note page:
<>

Bob
--
Bob Jacobsen
rgj1927@...

[Non-text portions of this message have been removed]

Otto,
Look at the RTXINITIALIZER in LRoutes. It allows for a script to be run at startup.


I have used it for years in my client work for getting everything setup prior to Logix and other managers starting. Very useful for implementing CTC logix which sets the interlockings to Stop.


Chuck Catania
MRCS

Otto,



You can arrange to order of all the startup actions using the preferences
window. It will let you move one up or down in the order. That has been
around since 4.4 I think. So if you make the panel the first line and the
other actions like loading scripts later, that should also take care of it.



-Ken Cameron, Member JMRI Dev Team

www.jmri.org

www.fingerlakeslivesteamers.org

www.cnymod.com

www.syracusemodelrr.org

Thank you Randall; that fixed it up & now it is working without any error messages!

Hi Bob,

I fixed the error.

I wrote a script to load the panel and execute it on start up before the signal follower script.

the script:
import jmri
import java

jmri.InstanceManager.getDefault(jmri.ConfigureManager).load(java.io.File(jmri.util.FileUtil.getExternalFilename("preference:Inglenook_simulator.xml")))


Is this a sensible solution?

Regards
Otto

Hi Bob,

I got the signal mast follower to work (almost).

I set the SignalMastFollower script to run at startup, where it fails with:
AttributeError: 'NoneType' object has no attribute 'addPropertyChangeListener'

If I open the panel then execute the script again, the signal mast following works.

Have I missed something in the set up? - it seems the script is being run too early.

BTW: There's an error in the script. On the last line (the example) it should read SignalMastFollowerListener and not SignalFollowerListener.

Regards
Otto

Marshall,



After much debate we did add the 'normalizing' of names to remove leading
and trailing spaces. We had a history of finding and fixing users panels
where things didn't work right and it traced to where they had used a space
when entering the name one place and not the other, sometimes even 3
variants. But each would refer to a different object while the display would
barely show the space (trailing completely hidden by whitespace), making it
very unclear to the user why something didn't work right. And in the table
display, the sorting would usually not show them near each other so it was
very difficult to see.



-Ken Cameron, Member JMRI Dev Team

www.jmri.org

www.fingerlakeslivesteamers.org

www.cnymod.com

www.syracusemodelrr.org