¿ªÔÆÌåÓý

  1. Jmriusers
  2. Messages
Expanded Topics Messages Polls
Date
Locked Z21 Users Please test

 

Hello Z21 Users,

As I mentioned in an e-mail a few weeks ago, I was acquiring a Roco Z21. That unit arrived, and I've had a little time to work on some of the issues reported in JMRI's Z21 support.

Here's what I've made sure works with my unit:
1) Programming on the programming track. This worked with no issues.
2) Using a throttle to control a locomotive. This required a minor change (The short reason for the change is that Roco has chosen to send an XPressNet message that doesn't have the XPressNet message length set correctly. Since the JMRI throttle used on the Z21 is an XPressNet throttle, this caused an exception that stopped all XPressNet traffic)

I also made some minor corrections to the Z21 configuration tool and the Z21 monitor code, but these really only impact readability, not functionality.

If you're using a Z21, please go to:



And download a daily build. Any build after #1614 has the changes noted above included (this includes the build marked as the latest build, from the link above).

I've tested all this with a real live Z21 (with firmware 1.24 installed) and it seems to work for me, but I want to know it works for you too.

Thanks,
Paul
Locked Trouble with JMRI throttle

 

Greetings.


I have the current production release of JMRI, I have windows 10 and the current update of JAVA.I have Digitrax loconet via RRcirkits locobuffer. The layout has been running fine for months. I have been laying new track but nothing seems to be a problem. My layout has stopped responding to the throttles. It was running perfectly with 6 engines active last evening.. I closed all throttles and cleared all slots. To-day I opened the panel-pro program, I opened my profile, I powered up the layout (no problem), I opened a new throttle window, I selected one of the engine numbers. It pulled the file from my roster. The number of the engine is in the box, the drop-down says"no engine selected" and I can't change anything on the selector box. The function buttons and the speed buttons are all inoperable. Happens with all engines on the layout. I can't get any engine to work. Loconet and locobuffer seem to be all active.I'm sure I haven't done anything major to screw up the system but I have no idea what to do now?


HELP????please....


Thanks.




Jim
Locked Re: Panel Pro For Hire

Scott J. Meller
 

Hi Keith,

The layout is built. I just need someone to do the JMRI integration. I am
located in Los Angeles, so this would have to be done remotely. A JPG of
my layout is attached.

Thank you and best regards,

On Tue, Jun 20, 2017 at 10:56 AM, kwilliams@... [jmriusers] <
jmriusers@...> wrote:



Scott,

Are you looking to have someone build your layout, or your control panel,
or both? Having spent the last 5 years or so building and refining my
layout panel, I might want to give yours a try. Can you send me some
information, such as a pdf of your track plan?

Where are you located?

What is your timing to get this done?

I am located in Bowling Green KY at the moment, but live in Atlanta, GA.

Keith Williams
kwilliams@...

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




--
Thank you and best regards,

SCOTT J. MELLER
Locked Re: Panel Pro For Hire

[email protected]
 

Scott,

Are you looking to have someone build your layout, or your control panel, or both? Having spent the last 5 years or so building and refining my layout panel, I might want to give yours a try. Can you send me some information, such as a pdf of your track plan?

Where are you located?

What is your timing to get this done?

I am located in Bowling Green KY at the moment, but live in Atlanta, GA.

Keith Williams
kwilliams@...
Locked Re: Consist Settings

 

When using advance consisting with NCE, what you say is usually true, sometimes you have to adjust, I think, CV21 and CV22 to get the lights right. However, with NCE you run the consist with the lead engine number as the address, NOT the consist address. If you use the consist address the same information will be sent to every loco in the consist.

Wil
Locked Re: Test release 4.7.6 available

 

Perhaps the documentation would be far better if we as model railroaders were to
pay the volunteer developers what JMRI was actually worth, but then it would not
be as far advanced as it is now.

Considering the mount of money I have laid out for JMRI I consider these points
of confusion a good opportunity to keep my brain active, any hick-ups between
versions are soon fixed anyway.

Great job JMRI developers...

John

---------- Original Message ----------
From: "leo pesce lpescester@... [jmriusers]" <jmriusers@...>
Date: June 20, 2017 at 11:39 AM


up_sbrown, thank you for the nice words.

Yes, I know all that. I do read the release notes. I do know these are
experimental test releases.

I wish there was a better attention to detail when it comes to "whatever"
releases, ie. releasing versions that "break" a lot of stuff, in the
attempt to fix or improve something else.

LOL, at least that has been a "constant" through the history of JMRI.

I realize the value the developers are doing. I lived a long while in the
high tech industry to know that. Harsh? Please. This here is cupcakes.

As for the issue at hand, I am assuming no-one has had a chance to see that
the java error means?

Backups. Yes. I do have backups. And I hope a lot of people out there
should have too.

Am I to assume this will constitute a ban from the list? again?

Cheers
Leo P

PS. I do love JMRI and cannot do without it, and I do thank the devs for
what they do.

On Mon, Jun 19, 2017 at 4:29 PM, up_sbrown@... [jmriusers] <
jmriusers@...> wrote:



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: Test release 4.7.6 available

 

up_sbrown, thank you for the nice words.

Yes, I know all that. I do read the release notes. I do know these are
experimental test releases.

I wish there was a better attention to detail when it comes to "whatever"
releases, ie. releasing versions that "break" a lot of stuff, in the
attempt to fix or improve something else.

LOL, at least that has been a "constant" through the history of JMRI.

I realize the value the developers are doing. I lived a long while in the
high tech industry to know that. Harsh? Please. This here is cupcakes.

As for the issue at hand, I am assuming no-one has had a chance to see that
the java error means?

Backups. Yes. I do have backups. And I hope a lot of people out there
should have too.

Am I to assume this will constitute a ban from the list? again?

Cheers
Leo P

PS. I do love JMRI and cannot do without it, and I do thank the devs for
what they do.

On Mon, Jun 19, 2017 at 4:29 PM, up_sbrown@... [jmriusers] <
jmriusers@...> wrote:



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: Contributing to the Engine Driver code on GitHub?

 

Hi Peter,

Sorry I haven't responded sooner, been covered up and out of town.


Do you remember what files you actually changed code in? If so, here's my suggestion to make your changes visible.


1) Fork the project on GitHub.
2) Make the changes (again) to that fork (cut and paste from your code should be fine.)
3) Compare the fork with the JMRI/EngineDriver to insure it clearly shows your actual changes and nothing else.


Item 2 can be done on GitHub (using the online Edit) button, or you can pull the code down and edit it using a text editor and then commit them back to GitHub.


I can then view the changes on GitHub, create a patch from them, pull them down to my computer to compile, etc.


If you'd like, and the changes can be separated out, do one of your items and I'll take a look before you spend time on the others.


Regards,
SteveT
Locked Re: Panel Pro For Hire

Scott J. Meller
 

Hi Ichi,

Thanks for the feedback.

Thank you,

On Tue, Jun 20, 2017 at 7:13 AM, one2beros@... [jmriusers] <
jmriusers@...> wrote:



Scott,

Here's a few tips.

Ensure that the designer is in your area.
Ensure that he provides you with the supporting documentation.
Ensure that the deliverables are understood and noted.
Ensure that there is fair equity in the job for both.

Converting Anyrail to JMRI is 5% of the task. The other 95% is making
sure that everything works or will work when its installed. Bring all the
pieces together
the wiring, the DCC system, track, switch controls and supporting
components
as well as the display takes a lot of planning.

Ichi

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




--
Thank you and best regards,

SCOTT J. MELLER
Locked Re: Problems with LayoutEditor

Vincent Filardo
 

Thanks Dave for much appreciated response

I opened the file with an xml Editor and fix the problem, now everything works fine shows the right Tables and creates no IBs Blocks.
I'll continue with the Tutorial and hope it all goes fine.
Thank you again.
Vince

-----Original Message-----
From: jmriusers@... [mailto:jmriusers@...]
Sent: Monday, June 19, 2017 3:49 PM
To: jmriusers@...
Subject: [jmriusers] 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

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


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

Yahoo Groups Links
Locked Re: Problem with leading spaces in a sensor "username".

 

Ken,

Thanks for the explanation. I now know how to fix the issue without using a text editor.
Did I miss this change in the Release notes?

Marshall

From: mailto:jmriusers@...
Sent: Monday, June 19, 2017 7:23 AM
To: jmriusers@...
Subject: RE: [jmriusers] Re: Problem with leading spaces in a sensor "username".


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

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





[Non-text portions of this message have been removed]
Locked Re: Panel Pro For Hire

 

Scott,

Here's a few tips.

Ensure that the designer is in your area.
Ensure that he provides you with the supporting documentation.
Ensure that the deliverables are understood and noted.
Ensure that there is fair equity in the job for both.

Converting Anyrail to JMRI is 5% of the task. The other 95% is making
sure that everything works or will work when its installed. Bring all the pieces together
the wiring, the DCC system, track, switch controls and supporting components
as well as the display takes a lot of planning.

Ichi
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

[email protected]
 

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
102801 - 102820 of 240675