¿ªÔÆÌåÓý

Date

Locked Re: Dispatcher Collisions

 

Hi Stu,

Others could explain the _benefits_ of SignalHeads vs. SignalMasts better than I, but inside the Dispatcher code, there are some unavoidable differences in the logic. I use SignalMasts, so I can test/debug issues with those more easily than SignalHeads. The goal should be for these differences to be transparent to the regular user, but we're not there yet.


As for direction sensors, I only use internal sensors. Dispatcher SETS these when allocating a section. If I've included these sensors in my SignalMast logic, this prevents two trains from trying to allocate the same block, as only one will have a clear aspect.
Note: I only include the direction sensors in SM logic for blocks that may be used by opposing trains.


I've no experience with hardware direction sensors.


HTH,
SteveT


Locked Re: Contributing to the Engine Driver code on GitHub?

 

SteveT, I found a plugin to compare the Project that AndroidStudio imported to the original Eclipse Project. The import rearranged the folder structure and is telling me that the is over 1700 different files, so there is no hope I could manually workout and make the changes.


I have had several more attempts to get Eclipse to work, and everything I have googled about the problems I have, didn't help. In fact many things I have found suggest that it is simply not supported anymore.


I would appreciate any suggestions.


Peter


P.S.. A working APK is here...


Locked Re: Consist Settings

 

Setting up consists and decoder consist settings with NCE systems are quite different from any other brand of DCC system, due to special helper features in the NCE command station.

The correct way to set up consists and program decoders for proper consist operation with NCE systems is the subject of some documents I wrote and that are now available at the following link:
<>
--
Dave in Australia

On 20 Jun 2017, at 10:21 AM, znrauiufnjz2e6tsduf24xoihjbzwl5y3fdj7ebx@... [jmriusers] <jmriusers@...> wrote:

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?


Locked Re: Consist Settings

 

Are you using advanced consisting ? It should work there ......Mike

On Mon, Jun 19, 2017 at 10:51 PM, Roger Thomas rogert@...
[jmriusers] <jmriusers@...> wrote:




Not really what you want, but you can always set the whistle and bell
volume in the trailing loco to 0. Then, at least, only the lead loco
will respond with bell and whistle sounds.

Roger Thomas

On Monday 06/19/2017 at 10:36 pm,
znrauiufnjz2e6tsduf24xoihjbzwl5y3fdj7ebx@... jmriusers wrote:




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









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


Locked Re: Consist Settings

 

Not really what you want, but you can always set the whistle and bell
volume in the trailing loco to 0. Then, at least, only the lead loco
will respond with bell and whistle sounds.

Roger Thomas

On Monday 06/19/2017 at 10:36 pm,
znrauiufnjz2e6tsduf24xoihjbzwl5y3fdj7ebx@... jmriusers wrote:




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

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




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


Locked Re: New engine address

 

Sorry about that, I know that but old habits are hard to undo, maybe that dates me before JMRI time when it was called exactly that.
Al Babinsky

Sent from Alto

On Monday, June 19, 2017 at 17:42 Andrew Vandermolen skipvdmolen <jmriusers@...> wrote:

?

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]



#AOLMsgPart_2_3f980178-6422-4a51-a4c0-53daee55f9b8 td{color: black;} .aolReplacedBody #aolmail_ygrp-mkp { border: 1px solid #d8d8d8; font-family: Arial; margin: 10px 0; padding: 0 10px;}.aolReplacedBody #aolmail_ygrp-mkp hr { border: 1px solid #d8d8d8;}.aolReplacedBody #aolmail_ygrp-mkp #aolmail_hd { color: #628c2a; font-size: 85%; font-weight: 700; line-height: 122%; margin: 10px 0;}.aolReplacedBody #aolmail_ygrp-mkp #aolmail_ads { margin-bottom: 10px;}.aolReplacedBody #aolmail_ygrp-mkp .aolmail_ad { padding: 0 0;}.aolReplacedBody #aolmail_ygrp-mkp .aolmail_ad p { margin: 0;}.aolReplacedBody #aolmail_ygrp-mkp .aolmail_ad a { color: #0000ff; text-decoration: none;} .aolReplacedBody #aolmail_ygrp-sponsor #aolmail_ygrp-lc { font-family: Arial;}.aolReplacedBody #aolmail_ygrp-sponsor #aolmail_ygrp-lc #aolmail_hd { margin: 10px 0px; font-weight: 700; font-size: 78%; line-height: 122%;}.aolReplacedBody #aolmail_ygrp-sponsor #aolmail_ygrp-lc .aolmail_ad { margin-bottom: 10px; padding: 0 0;} .aolReplacedBody #aolmail_actions { font-family: Verdana; font-size: 11px; padding: 10px 0; } .aolReplacedBody #aolmail_activity { background-color: #e0ecee; float: left; font-family: Verdana; font-size: 10px; padding: 10px; } .aolReplacedBody #aolmail_activity span { font-weight: 700; } .aolReplacedBody #aolmail_activity span:first-child { text-transform: uppercase; } .aolReplacedBody #aolmail_activity span a { color: #5085b6; text-decoration: none; } .aolReplacedBody #aolmail_activity span span { color: #ff7900; } .aolReplacedBody #aolmail_activity span .aolmail_underline { text-decoration: underline; } .aolReplacedBody .aolmail_attach { clear: both; display: table; font-family: Arial; font-size: 12px; padding: 10px 0; width: 400px; } .aolReplacedBody .aolmail_attach div a { text-decoration: none; } .aolReplacedBody .aolmail_attach img { border: none; padding-right: 5px; } .aolReplacedBody .aolmail_attach label { display: block; margin-bottom: 5px; } .aolReplacedBody .aolmail_attach label a { text-decoration: none; } .aolReplacedBody blockquote { margin: 0 0 0 4px; } .aolReplacedBody .aolmail_bold { font-family: Arial; font-size: 13px; font-weight: 700; } .aolReplacedBody .aolmail_bold a { text-decoration: none; } .aolReplacedBody dd.aolmail_last p a { font-family: Verdana; font-weight: 700; } .aolReplacedBody dd.aolmail_last p span { margin-right: 10px; font-family: Verdana; font-weight: 700; } .aolReplacedBody dd.aolmail_last p span.aolmail_yshortcuts { margin-right: 0; } .aolReplacedBody div.aolmail_attach-table div div a { text-decoration: none; } .aolReplacedBody div.aolmail_attach-table { width: 400px; } .aolReplacedBody div.aolmail_file-title a,.aolReplacedBody div.aolmail_file-title a:active,.aolReplacedBody div.aolmail_file-title a:hover,.aolReplacedBody div.aolmail_file-title a:visited { text-decoration: none; } .aolReplacedBody div.aolmail_photo-title a,.aolReplacedBody div.aolmail_photo-title a:active,.aolReplacedBody div.aolmail_photo-title a:hover,.aolReplacedBody div.aolmail_photo-title a:visited { text-decoration: none; } .aolReplacedBody div#aolmail_ygrp-mlmsg #aolmail_ygrp-msg p a span.aolmail_yshortcuts { font-family: Verdana; font-size: 10px; font-weight: normal; } .aolReplacedBody .aolmail_green { color: #628c2a; } .aolReplacedBody .aolmail_MsoNormal { margin: 0 0 0 0; } .aolReplacedBody o { font-size: 0; } .aolReplacedBody #aolmail_photos div { float: left; width: 72px; } .aolReplacedBody #aolmail_photos div div { border: 1px solid #666666; height: 62px; overflow: hidden; width: 62px; } .aolReplacedBody #aolmail_photos div label { color: #666666; font-size: 10px; overflow: hidden; text-align: center; white-space: nowrap; width: 64px; } .aolReplacedBody #aolmail_reco-category { font-size: 77%; } .aolReplacedBody #aolmail_reco-desc { font-size: 77%; } .aolReplacedBody .aolmail_replbq { margin: 4px; } .aolReplacedBody #aolmail_ygrp-actbar div a:first-child { margin-right: 2px; padding-right: 5px; } .aolReplacedBody #aolmail_ygrp-mlmsg { font-size: 13px; font-family: Arial, helvetica,clean, sans-serif; *font-size: small; *font: x-small; } .aolReplacedBody #aolmail_ygrp-mlmsg table { font-size: inherit; font: 100%; } .aolReplacedBody #aolmail_ygrp-mlmsg select,.aolReplacedBody input,.aolReplacedBody textarea { font: 99% Arial, Helvetica, clean, sans-serif; } .aolReplacedBody #aolmail_ygrp-mlmsg pre,.aolReplacedBody code { font:115% monospace; *font-size:100%; } .aolReplacedBody #aolmail_ygrp-mlmsg * { line-height: 1.22em; } .aolReplacedBody #aolmail_ygrp-mlmsg #aolmail_logo { padding-bottom: 10px; } .aolReplacedBody #aolmail_ygrp-msg p a { font-family: Verdana; } .aolReplacedBody #aolmail_ygrp-msg p#aolmail_attach-count span { color: #1E66AE; font-weight: 700; } .aolReplacedBody #aolmail_ygrp-reco #aolmail_reco-head { color: #ff7900; font-weight: 700; } .aolReplacedBody #aolmail_ygrp-reco { margin-bottom: 20px; padding: 0px; } .aolReplacedBody #aolmail_ygrp-sponsor #aolmail_ov li a { font-size: 130%; text-decoration: none; } .aolReplacedBody #aolmail_ygrp-sponsor #aolmail_ov li { font-size: 77%; list-style-type: square; padding: 6px 0; } .aolReplacedBody #aolmail_ygrp-sponsor #aolmail_ov ul { margin: 0; padding: 0 0 0 8px; } .aolReplacedBody #aolmail_ygrp-text { font-family: Georgia; } .aolReplacedBody #aolmail_ygrp-text p { margin: 0 0 1em 0; } .aolReplacedBody #aolmail_ygrp-text tt { font-size: 120%; } .aolReplacedBody #aolmail_ygrp-vital ul li:last-child { border-right: none !important; }



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


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