¿ªÔÆÌåÓý

Date

Locked Re: New engine address

 

Try assigning it as a 4 digit number.

On Jun 19, 2017, at 6:10 PM, mt ler mtler1930@... [jmriusers] <jmriusers@...> wrote:

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]


Locked Consist Settings

 

Hey Guys,

I have a couple of questions on setting up a consist. I am using an NCE Pro Cab unit.

I have two BLI K4 Pacifics that I am running as a consist. It has been my assumption that in a consist the lead loco in forward motion, will be the only unit with a headlight and whistle, etc.. The rear loco would not respond to the horn or bell. Visa versa for reverse operation. I have both locos set in JMRI as to responding to the consist address (Functions 1 - 7). The locos run fine with these settings but both units respond to the functions horn, bell, etc. Is there a way to separate them out like I think they should be, or am I being to picky?

Thanks for any help or advice.

Ted


Locked Re: New engine address

 

The 2-digit and 4-digit terms for loco addresses are actually incorrect and misleading. These terms are never used in the the NMRA DCC Standards specifications.

That is why we have moved away from this incorrect terminology in JMRI and now use "Short" and "Long" terminology, both of which terms are used by the NMRA DCC Standards. (The NMRA also uses the terms "Primary" and "Extended" in some places).

For more information on DCC loco addresses, see:
<>
--
Dave in Australia

On 20 Jun 2017, at 8:10 AM, mt ler mtler1930@... [jmriusers] <jmriusers@...> wrote:

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....


Locked Re: Test release 4.7.6 available

 

Hi Leo, Couple of things to consider with the update you installed - very clearly the message stated that it was to be considered experimental due to the number of changes implemented.
I assume you made a complete backup of JMRI and its accompanying files before updating? Or another option is if you are windows based used a snapshot before the install or if mac based could wind back with time machine. As for Linux I am not sure how this is done? You are backing up right?
Also remember these developers are doing this for minuscule financial return - yep there will be glitches and some hiccups but given the speed at which they generally are able to resolve the issues I'd say they are better then the average software manufacturer - certainly more responsive and active at product development too. That and how good the product is for what we the users get for essentially free.
I'm sorry if this sounds harsh or you are having issues now - but please read the release notes and take heed before installing a test release on what sounds like an important MR setup you have. Remember the best backup you have is the one you never need.
Simon


Locked Re: Problems with LayoutEditor

 

Hi VInce IBn block names are created when place a piece of trackwork on a panel and the name for the block that you typed in does not exist. It creates the block with the name you typed in and a system name of IBnnn.
To avoid this only use a name that appear in the drop down box for "Block Name", and don't type the name in.
Steve G.


Locked Re: New engine address

 

Glad it worked,
Al

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:55

That was it.



Thanks.



Roger T.

On Jun 19, 2017, at 15:22, 'babinskya@...' babinskya@... [jmriusers] <jmriusers@...> wrote:
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.
Sent from my iPhone
------------------------------------
Posted by: "=?utf-8?B?YmFiaW5za3lhQGNvbWNhc3QubmV0?=" <babinskya@...>
------------------------------------
------------------------------------
Yahoo Groups Links


Locked Re: Getting last signal prior to fiddle yard to automatically cycle back to green (BR 4 Aspect)

 

Hi Steve,
If the signal logic is set up correctly then each signal sees the one ahead so if there is a single virtual signal ahead of the last signal on your layout then the virtual signal goes to red on a timer and the last signal then should change to single yellow. To get the last signal to go all the way to green (if you are using 4 aspects) then you will need three virtual signals on three timers to get the last real signal to show green.


---> layout ---> SM ---> virtual block 1 ---> VM1 ---> virtual block 2 ---> VM2 ---> virtual block 3 ---> VM3 ---> yard tracks


In my layout VM1 is triggered to red by a sensor that is delayed 30 seconds from the sensor at the last real signal. That sets the last real signal to yellow.


VM2 is triggered to red by a sensor that is delayed 60 seconds from the sensor at the last real signal. That sets VM1 to yellow and the last real signal to double yellow.


VM3 is triggered to red by a sensor that is delayed 90 seconds from the sensor at the last real signal. That sets VM2 to yellow, VM1 to double yellow and the last real signal to green.
Dave


Locked Re: New engine address

Roger Traviss.
 

That was it.

Thanks.


Roger T.

On Jun 19, 2017, at 15:22, 'babinskya@...' babinskya@... [jmriusers] <jmriusers@...> wrote:


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.



Sent from my iPhone














------------------------------------
Posted by: "=?utf-8?B?YmFiaW5za3lhQGNvbWNhc3QubmV0?=" <babinskya@...>
------------------------------------


------------------------------------

Yahoo Groups Links




Locked Re: New engine address

Roger Traviss.
 

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

Roger T.

On Jun 19, 2017, at 15:22, 'babinskya@...' babinskya@... [jmriusers] <jmriusers@...> wrote:


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.



Sent from my iPhone










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



------------------------------------
Posted by: "=?utf-8?B?YmFiaW5za3lhQGNvbWNhc3QubmV0?=" <babinskya@...>
------------------------------------


------------------------------------

Yahoo Groups Links




Locked Re: Why the choice of internal layouts and Loconet?

 

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


Locked Re: New engine address

 

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.


Locked Re: New engine address

 

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]


Locked New engine address

Roger Traviss.
 

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.


Locked Re: Why the choice of internal layouts and Loconet?

 

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


Locked Re: Problems with LayoutEditor

 

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


Locked Re: Dispatcher Collisions

 

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


Locked Re: Dispatcher Collisions

 

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


Locked Re: Why the choice of internal layouts and Loconet?

 

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


Locked Re: Test release 4.7.6 available

 

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]


Locked Re: Problems with LayoutEditor

Vincent Filardo
 

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

-----Original Message-----
From: jmriusers@... [mailto:jmriusers@...]
Sent: Sunday, June 18, 2017 4:52 PM
To: jmriusers@...
Subject: [jmriusers] Re: Problems with LayoutEditor

Vince,

I am not able to re-create your magic block problem. For now you should be able to go to the block table and delete the block.

The "Additional Name" field is used to assign the second turnout for "Single Slip" and "Double Slip" switches. These require two independent turnout controls.

Dave Sand


------------------------------------
Posted by: dave@...
------------------------------------


------------------------------------

Yahoo Groups Links