¿ªÔÆÌåÓý

  1. Jmriusers
  2. Messages
Expanded Topics Messages Polls
Date
Locked Re: Possible roster problem #zimo

 

¿ªÔÆÌåÓý

Marc

Easydcc will not let you put "66" in the number AND in the Advance consist.

He is using a Lenz LE 103 - they do not like 128 peed steps - they are better with 28 or even 14.

Now, WiFi to JMRI to Easydcc - not sure what the commend station send to the decoder. Does the speed steps in JMRI go to CVP or does the setting in Easydcc override that and send its default? The cvp panel can be set to default to 14 - 28 or 128.

I threw out about 6 of these decoders a couple of months ago - still have one for testing.

I will not get time until Monday to "play" with it. My layout is on a layout Tour all day Sunday and I am off to an operating session today (Friday).

Gerry

On 20/09/2019 10:40 am, forfoum@... wrote:
Thomas, that is a good point.

Only problem is these LE103 of his work when he uses the EasyDCC throttle. So that throws the CV19 theory for a loop.
CV19 takes precedence over both CV1 and CV17/18. If CV19? was the root cause, then all throttles would have the same symptom.

Now what if he has CV1 = 66 and CV19 = 66.. Could it be JMRI and WiThrottle? using address 66 ends up on CV19 as a "Consist"? but his EasyDCC throttle
that might not support "Consist"? ends up on address 66? (CV1).? Not probable as CV19 is a decoder thing.

Marc 
-- 
Gerry Hopkins MMR #177 FNMRA
Great Northern Downunder




NMRA Australasian Region
Contest & AP Chairman
Web Administrator

Virus-free.

Locked Re: NCE PowerPro Connection Issues

 

Thanks for the responses, Dave and Dave! I'm tied up for the weekend, but will try your suggestions Monday.

-- Jeff

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Dave
Sand
Sent: Thursday, September 19, 2019 7:03 PM
To: [email protected]
Subject: Re: [jmriusers] NCE PowerPro Connection Issues

Jeff,

Since you are using Windows, a JMRI upgrade may leave some old stuff
behind depending on how old the previous version was.

I always do a clean install. This involves using the Control Panel to remove
the old JMRI version followed by manually deleting the residual JMRI
directory in C:\Program Files (x86).

Note: If you have placed custom components, such as icons, in the install
location instead of the user files location, be sure to back them up before
doing the cleanup steps.

The user data, such as rosters, panels, operations files, etc., are located at
C:\Users\<username>\JMRI.

Dave Sand



On Sep 19, 2019, at 5:30 PM, Jeff Mutter <jwmutter@...>
wrote:

I¡¯m not sure if it was the same set of errors but yes, I got several errors
about three times before I saved the last one.

I did upgrade Java yesterday, too. Could that be related?

-- Jeff

From: [email protected] [mailto:[email protected]] On Behalf Of
Dave Heap
Sent: Thursday, September 19, 2019 6:16 PM
To: [email protected]
Subject: Re: [jmriusers] NCE PowerPro Connection Issues

Jeff,

On 20 Sep 2019, at 3:12 AM, Jeff Mutter <jwmutter@...>
wrote:

Shorted the ¡°2¡± and ¡°3¡± pins on the serial adapter. Didn¡¯t see the
¡°timeout flushes receive buffer: AA¡± message, but got a bunch of ¡°ERROR¡±
messages (see log below). Does that mean the adapter is bad, or do the
error messages mean something else is wrong?
It looks more like a transient error in the JMRI or the Pure Java Comm
library we use. Or possibly a poor contact between pins 2 & 3.

Is it reproducible every time you start JMRI?

Dave in Australia
Locked Re: Turnouts work only in Edit mode

 

Thanks Dave. I will check when I get home. I forgot to mention all other turnouts work correctly. It is just the new ones added that do not.
Locked JythonAutomation and JythonSiglet use?

Randall Wood
 

¿ªÔÆÌåÓý

Does anyone use Jython scripts with the JythonAutomation and JythonSiglet classes?

I am looking for sample scripts used with those classes as documented for automation (kind of) in??so I can write up sample uses for those classes.

Thank you,
Randall Wood
Locked VSD - Updated example.vsd #vsdecoder

 

Just found the updated VSD example file on github (3 days old).

All four locos run (3 diesel, 1 steam).? all sounds ?same? as previous release.? diesels good,
steam not so good (choppy chuff transitions).

not sure what changes were made.

HOWEVER, my thanks for all the JMRI and VSD work and contributions.??

Virtual Sound Decoder is a great asset for $$$$$ challenged model railroaders.

Conrad
Locked Re: Signal Mast Appearance definition file

 

I found a different way to view the signal system mast appearance files that will properly view the files and display all of the information even though the files don't "correctly" reference the JMRI web site. (At least it does on my computer!)

I did this by:
- opening PanelPro.
- Starting the "JMRI Web Browser" via Tools->Start JMRI Web Browser
- Used a web browser to open a page on the JMRI Web Browser. By default, the URL is your computer's IP address followed by ":12080". So a typical URL would be "192.168.1.5:12080" (without the quotes). Your computer's IP address is likely to be different, though.
- scroll to the bottom right of the page, in the "File Access" section of the page, and click on the "/xml/signals" link. This gives a list of the JMRI-defined "Signaling Systems". Click on the one you want, for example AAR-1946. Then click on one of the appearance files. This gives the complete output.

Regards,
Billybob
Locked Re: NCE PowerPro Connection Issues

 

Jeff,

Since you are using Windows, a JMRI upgrade may leave some old stuff behind depending on how old the previous version was.

I always do a clean install. This involves using the Control Panel to remove the old JMRI version followed by manually deleting the residual JMRI directory in C:\Program Files (x86).

Note: If you have placed custom components, such as icons, in the install location instead of the user files location, be sure to back them up before doing the cleanup steps.

The user data, such as rosters, panels, operations files, etc., are located at C:\Users\<username>\JMRI.

Dave Sand

On Sep 19, 2019, at 5:30 PM, Jeff Mutter <jwmutter@...> wrote:

I¡¯m not sure if it was the same set of errors but yes, I got several errors about three times before I saved the last one.

I did upgrade Java yesterday, too. Could that be related?

-- Jeff

From: [email protected] [mailto:[email protected]] On Behalf Of Dave Heap
Sent: Thursday, September 19, 2019 6:16 PM
To: [email protected]
Subject: Re: [jmriusers] NCE PowerPro Connection Issues

Jeff,

On 20 Sep 2019, at 3:12 AM, Jeff Mutter <jwmutter@...> wrote:

Shorted the ¡°2¡± and ¡°3¡± pins on the serial adapter. Didn¡¯t see the ¡°timeout flushes receive buffer: AA¡± message, but got a bunch of ¡°ERROR¡± messages (see log below). Does that mean the adapter is bad, or do the error messages mean something else is wrong?
It looks more like a transient error in the JMRI or the Pure Java Comm library we use. Or possibly a poor contact between pins 2 & 3.

Is it reproducible every time you start JMRI?

Dave in Australia
Locked Re: NCE PowerPro Connection Issues

 

¿ªÔÆÌåÓý

Jeff,


On 20 Sep 2019, at 8:30 AM, Jeff Mutter <jwmutter@...> wrote:

I¡¯m not sure if it was the same set of errors but yes, I got several errors about three times before I saved the last one.


Do you still get the same errors if you aren't trying the loopback mode but just have it:
1) Unplugged from the Power Pro end.
or
2) Plugged into the Power Pro.

?

I did upgrade Java yesterday, too.? Could that be related?


Unlikely.
Locked Re: NCE PowerPro Connection Issues

 

¿ªÔÆÌåÓý

I¡¯m not sure if it was the same set of errors but yes, I got several errors about three times before I saved the last one.

?

I did upgrade Java yesterday, too.? Could that be related?

?

-- Jeff

?

From: [email protected] [mailto:[email protected]] On Behalf Of Dave Heap
Sent: Thursday, September 19, 2019 6:16 PM
To: [email protected]
Subject: Re: [jmriusers] NCE PowerPro Connection Issues

?

Jeff,


On 20 Sep 2019, at 3:12 AM, Jeff Mutter <jwmutter@...> wrote:

Shorted the ¡°2¡± and ¡°3¡± pins on the serial adapter.? Didn¡¯t see the ¡°timeout flushes receive buffer: AA¡± message, but got a bunch of ¡°ERROR¡± messages (see log below).? Does that mean the adapter is bad, or do the error messages mean something else is wrong?

It looks more like a transient error in the JMRI or the Pure Java Comm library we use. Or possibly a poor contact between pins 2 & 3.

?

Is it reproducible every time you start JMRI?

?

Dave in Australia

?
Locked Re: NCE PowerPro Connection Issues

 

¿ªÔÆÌåÓý

Jeff,

On 20 Sep 2019, at 3:12 AM, Jeff Mutter <jwmutter@...> wrote:

Shorted the ¡°2¡± and ¡°3¡± pins on the serial adapter.? Didn¡¯t see the ¡°timeout flushes receive buffer: AA¡± message, but got a bunch of ¡°ERROR¡± messages (see log below).? Does that mean the adapter is bad, or do the error messages mean something else is wrong?

It looks more like a transient error in the JMRI or the Pure Java Comm library we use. Or possibly a poor contact between pins 2 & 3.

Is it reproducible every time you start JMRI?

Dave in Australia
Locked Re: Signal Mast Appearance definition file

 

Mike wrote:
"From what I can see in the reference below, and the links on its page, I believe that semaphores are not covered in any of the existing tables; that they are set up only for lights. Am I correct?"

"Yes and No" (one of my _favorite_ answers!).

- Most JMRI signaling system definitions do not _specifically_ call out masts with "semaphore-style" heads. Exceptions include "B&O-1980", "B&O-Semaphore" and "BR-2003".

- JMRI signaling system definitions are _not required_ to define _every_ style of signal head that a given railroad actually used. Depending on which head styles the JMRI developer was willing to create, given signaling system may or may not include "semaphore-shaped" icons. Some pre-defined JMRI signaling systems have defined masts with a greater variety of "head" types than others.

- It is important to note that many prototype railroad rule books define their signaling rules in a very simplified way. The rule book I have most easily available states "The aspects may be shown by color of lights and by the position of semaphore arms." That rule book does _not_ specify which types of signal heads present a "color of light". So a given signal aspect might be conveyed by any signal head type: semaphore, searchlight, color-light, color-position-light, position-light, etc.

- From the perspective of the icons on a JMRI panel, most users find that it does not matter what the icon looks like, so long as it correctly represents the "aspect" of the associated signal mast and so long as it is properly interpretable on the finished panel. So a layout might physically implement a combination of semaphore and position-light signals, but the panel might only show "searchlight" icons. This can be thought of as a simple matter of practicality, ease panel development, and/or ease of interpretation by a panel viewer.

One key thing to understand is how to map control of a given model of a physical signal to something that JMRI can control. In many cases, this is done via proper configuration of a JMRI "Signal Head" object which controls a given head on the physical signal, and in other cases it is via proper configuration of a JMRI "Signal Mast" object. Which of these two defines the hardware interactions between JMRI and the physical signal depends on exactly what signaling hardware you are using, and can be very layout-specific. If interested in that topic, I suggest that you investigate the hardware you are using and how it is proprerly controlled via JMRI, and relate that to the JMRI "Signal Heads" and "Signal Masts" documentation. If you need further help on that topic, feel free to start a new thread...

Regards,
Billybob
Locked Re: VSD CLASS 64 COASTING WEIRDNESS

 

Klaus,

"I did a test on my layout today. HALF_SPEED works, but there is one thing to keep in mind. If the assigned function key is pressed while driving, the loco decoder changes its status immediately. VSD, on the other hand, changes its status only when the speed changes."

Nothing like success even if I didn't initially understand what was going on.

Test 1) Ran Kato Mikado 4-8-2 from idle to throttle 50 out of 100, chuffs rose to "level" 6.? Engaged HALF_SPEED (F8)?and loco speed dropped by maybe a half but chuffs stayed same at "level" 6.? Decreased throttle one step to 49 and chuffs slowly decreased to "level" 4.

Test 2) Ran Kato Mikado 4-8-2 from idle to throttle 50 out of 100, chuffs rose to "level" 6.? Engaged HALF_SPEED (F8)?and loco speed dropped by maybe a half but chuffs stayed same at "level" 6.? Increased throttle one step to 51 and chuffs slowly decreased to "level" 4.

Test 3) With HALF_SPEED engaged, ran Kato Mikado 4-8-2 from idle to throttle 50 out of 100? chuffs rose to "level" 4 with loco going slow.? Released HALF_SPEED (F8) and loco speed increased by maybe double but chuffs stayed a "level" 4.? Decreased throttle one step to 49 and chuffs rapidly increased to "level" 6.

Test 4) With HALF_SPEED engaged, ran Kato Mikado 4-8-2 from idle to throttle 50 out of 100? chuffs rose to "level" 4 with loco going slow.? Released HALF_SPEED (F8) and loco speed increased by maybe double but chuffs stayed a "level" 4.? Increased throttle one step to 51 and chuffs rapidly increased to "level" 6.

Sometimes, but not usually, when starting with HALF_SPEED (F8) engaged and the running, the release of HALF_SPEED will result in increased chuff rate.? Note: this may be caused by unintended throttle movement by me:(

Thus, am I correct in understanding that VSD's engine code is only responding to LocoNet "Set speed of loco in slot 2 to xx" packets?? I say this because watching my JMRI LocoNet Monitor I see that toggling HALF_SPEED (F8) does not result in speed packets being sent.? This makes sense as HALF_SPEED?just tells the decoder to cut or increase the speed, say by half, independent of throttle setting.? So the code for HALF_SPEED goes to say F8, but is not linked to the engine functions.

As always, thank you for your sage advice.

Conrad
Locked Re: Signal Mast Appearance definition file

 

¿ªÔÆÌåÓý

From what I can see in the reference below, and the links on its page, I believe that semaphores are not covered in any of the existing tables; that they are set up only for lights. Am I correct?


Peace,

Mike G.

On 9/19/2019 10:57 AM, billybob experimenter wrote:

Assuming that you are working with a pre-defined JMRI "signal system", simply look at the JMRI web site page on "Aspect Signaling" and its list of available pre-defined Signal Systems (at  ).

Locked Re: Problem to reset slots with JMRI

 

Jacques,

Per the DCS240 manual section 5.1, changing OpSw 36 (or 37, 39, or 40) _requires_ interaction with the command station's front-panel switches. JMRI cannot do anything via a LocoNet message to get the DCS240 to do its internal housekeeping.

But, **I believe**, you can perform the OpSw change via JMRI and then manually interact with the command station front-panel switches, and you should get the desired effect. While I have not tried this, I believe it will work, but I cannot guarantee it...

Regards,
Billybob
Locked Re: Signal Mast Appearance definition file

 

Hal,

Ok - with a better understanding of what you are trying to do, here's a better answer.

Assuming that you are working with a pre-defined JMRI "signal system", simply look at the JMRI web site page on "Aspect Signaling" and its list of available pre-defined Signal Systems (at ). Click on the particular signal system you are interested in - AAR-1946, for example (at ).

Each page as a headling like "Signal Mast definitions:" followed by a list of links to the different mast types supported by the signaling system defintion. **Click on one of those listed mast types for a human-readable interpretation of the various XML files for that specific mast type.**

As an example, the AAR-1946 JMRI signalling system defines 12 different "mast" types. To see the appearance definition information for the "Double searchlight dwarf signal" mast type, select that mast type's link (at ).

That linked page is titled **JMRI ": Double head dwarf signal" Appearance Table** and shows:
- any descriptive text in the mast definition
- for each defined aspect, the colors displayed on each head, and the screen icon which can appear on a JMRI panel when the panel mast is giving a particular aspect, and any "reference text" provided with the aspect definition
- a table showing the "aspect mapping" for the mast.
- a table showing any "specific appearance mapping". Most importantly, this table will generally define a mapping between the JMRI generic term "Danger" - the most-restrictive aspect for the mast, and the aspect shown by the mast for that condition. In US signaling practice, this is typically the "Stop" aspect or the "Stop and Proceed" aspect.

While the content of these pages are missing some text (see below), the page contents which do appear is largely intact and still may be helpful for your purposes!

To interpret the aspect mapping table, consider a sequence of two signals: the signal being controlled and the next signal in advance of that signal. This is a "forward-looking" view, not a "backward-looking" view. The aspect to be displayed on "this" signal does not care what the aspect is or was on a signal which has already been passed. But it _does_ depend on the aspect of the signal which next will be encountered!

Consider a train approaching "the signal being controlled". It's possible aspects are constrained, in part, by the aspect of the next signal in advance (i.e. the second signal to be encountered by the train). The table's left column shows the "name" of the signal rule for the state of the signal in advance. The table's right column shows the possible states of the "signal being controlled" in the "Our Aspect" column of the table.

In the example above, if a train is approaching a signal, the possible aspects it can display depend on the aspect shown by the next signal in advance. If that next signal is displaying "Limited Clear", then the signal being approached may display either "Approach Medium" or implicitly, the mast's "Danger" aspect. Alternately, if if the next signal is displaying "Approach", then the signal being approached may display either "Advance Approach", Approach Medium", "Slow Approach", or, implicitly, the mast's "Danger" aspect.

FYI - The aspect mapping table will typically include one row for each possible aspect that can be displayed on a signal in advance of the one which is being defined. Since any one mast type can typically "protect" movement toward any other mast type (in a given signaling system definition), there is typically one row per possible unique aspect that can be displayed by _any_ mast type in the signaling system.

Unfortunately, it appears that some recent web page re-organization work is incomplete. This means that the individual mast-specific pages are not rendering correctly. This leaves these pages partially "broken", with some missing text. I have filed an issue with the JMRI development team.

Regards,
Billybob
Locked Re: VSD CLASS 64 COASTING WEIRDNESS

 

On Wed, Sep 18, 2019 at 08:57 PM, Klaus Killinger wrote:
Am 18.09.2019 um 15:55 schrieb conrad:
Yes, I did check that F8 was correct.? Program manager shows it and, more importantly, the loco slows when F8 is activated.? I'll switch all to F3 as a test though.
I'll check it out.
I did a test on my layout today. HALF_SPEED works, but there is one thing to keep in mind. If the assigned function key is pressed while driving, the loco decoder changes its status immediately. VSD, on the other hand, changes its status only when the speed changes.

Klaus
Locked Re: NCE PowerPro Connection Issues

 

¿ªÔÆÌåÓý

Thanks, Everyone!? Here¡¯s where I am:

?

I am careful to plug the USB end of the adapter into the same USB port on my computer.

All Default radio buttons are set to ¡°NCE¡±

?

Upgraded to 4.17.4.? No change.

Removed the screws/nuts on either side of the serial port. No change.

?

Shorted the ¡°2¡± and ¡°3¡± pins on the serial adapter.? Didn¡¯t see the ¡°timeout flushes receive buffer: AA¡± message, but got a bunch of ¡°ERROR¡± messages (see log below).? Does that mean the adapter is bad, or do the error messages mean something else is wrong?

?

Thanks again for your help!

Jeff

?

Latest log file:

?

2019-09-19 13:03:51,413 util.Log4JUtil??????????????????????? INFO? - * JMRI log ** [main]

2019-09-19 13:03:51,425 util.Log4JUtil??????????????????????? INFO? - This log is appended to file: C:\Users\Jeffrey Mutter\JMRI\log\messages.log [main]

2019-09-19 13:03:51,425 util.Log4JUtil??????????????????????? INFO? - This log is stored in file: C:\Users\Jeffrey Mutter\JMRI\log\session.log [main]

2019-09-19 13:03:51,433 apps.Apps? ???????????????????????????INFO? - PanelPro version 4.17.4+Rbf0d1af starts under Java 1.8.0_221 on Windows 10 x86 v10.0 at Thu Sep 19 13:03:51 EDT 2019 [main]

2019-09-19 13:03:53,738 apps.Apps???????????????????????????? INFO? - Starting with profile My_JMRI_Railroad.3ee7110a [main]

2019-09-19 13:03:54,060 node.NodeIdentity???????????????????? INFO? - Using 08fea99e-6b01-44fe-8e8b-1bbc47625414 as the JMRI storage identity for profile id 3ee7110a [AWT-EventQueue-0]

2019-09-19 13:03:54,191 xml.AbstractSerialConnectionConfigXml INFO? - Starting to connect for "NCE" [main]

2019-09-19 13:03:54,874 serialdriver.SerialDriverAdapter????? INFO? - NCE COM3 port opened at 9600 baud [main]

2019-09-19 13:03:55,260 util.FileUtilSupport????????????????? INFO? - File path program: is C:\Program Files (x86)\JMRI\ [main]

2019-09-19 13:03:55,261 util.FileUtilSupport????????????????? INFO? - File path preference: is C:\Users\Jeffrey Mutter\JMRI\My_JMRI_Railroad\ [main]

2019-09-19 13:03:55,261 util.FileUtilSupport????????????????? INFO? - File path profile: is C:\Users\Jeffrey Mutter\JMRI\My_JMRI_Railroad\ [main]

2019-09-19 13:03:55,262 util.FileUtilSupport????????????????? INFO? - File path settings: is C:\Users\Jeffrey Mutter\JMRI\ [main]

2019-09-19 13:03:55,262 util.FileUtilSupport????????????????? INFO? - File path home: is C:\Users\Jeffrey Mutter\ [main]

2019-09-19 13:03:55,262 util.FileUtilSupport????????????????? INFO? - File path scripts: is C:\Users\Jeffrey Mutter\JMRI\My_JMRI_Railroad\ [main]

2019-09-19 13:03:55,669 PanelPro.PanelPro???????????????????? INFO? - Main initialization done [main]

2019-09-19 13:04:04,986 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 0 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]

2019-09-19 13:04:05,090 nce.NceConnectionStatus?????????????? WARN? - Incorrect or no response from NCE command station [nce.NceTrafficController Transmit thread]

2019-09-19 13:04:05,096 jmrix.AbstractMRTrafficController???? ERROR - run: Exception: java.io.IOException in class jmri.jmrix.nce.NceTrafficController [nce.NceTrafficController Receive thread]

java.io.IOException

?????????????? at purejavacomm.PureJavaSerialPort$2.read(PureJavaSerialPort.java:887)

?????????????? at java.io.DataInputStream.read(Unknown Source)

?????????????? at jmri.jmrix.AbstractMRTrafficController.readByteProtected(AbstractMRTrafficController.java:946)

?????????????? at jmri.jmrix.AbstractMRTrafficController.loadChars(AbstractMRTrafficController.java:977)

?????????????? at jmri.jmrix.AbstractMRTrafficController.handleOneIncomingReply(AbstractMRTrafficController.java:1049)

?????????????? at jmri.jmrix.AbstractMRTrafficController.receiveLoop(AbstractMRTrafficController.java:870)

?????????????? at jmri.jmrix.AbstractMRTrafficController$2.run(AbstractMRTrafficController.java:794)

?????????????? at java.lang.Thread.run(Unknown Source)

2019-09-19 13:04:05,096 jmrix.AbstractMRTrafficController???? WARN? - sendMessage: Exception: In jmri.jmrix.nce.NceTrafficController port warn:? [nce.NceTrafficController Transmit thread]

java.io.IOException

?????????????? at purejavacomm.PureJavaSerialPort$1.write(PureJavaSerialPort.java:642)

?????????????? at java.io.DataOutputStream.write(Unknown Source)

?????????????? at java.io.FilterOutputStream.write(Unknown Source)

?????????????? at jmri.jmrix.AbstractMRTrafficController.forwardToPort(AbstractMRTrafficController.java:689)

?????????????? at jmri.jmrix.nce.NceTrafficController.forwardToPort(NceTrafficController.java:494)

?????????????? at jmri.jmrix.AbstractMRTrafficController.transmitLoop(AbstractMRTrafficController.java:474)

?????????????? at jmri.jmrix.AbstractMRTrafficController$1.run(AbstractMRTrafficController.java:770)

?????????????? at java.lang.Thread.run(Unknown Source)

2019-09-19 13:04:05,105 jmrix.AbstractMRTrafficController???? ERROR - Exit from rcv loop in class jmri.jmrix.nce.NceTrafficController [nce.NceTrafficController Receive thread]

2019-09-19 13:04:15,104 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 1 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]

2019-09-19 13:04:15,206 jmrix.AbstractMRTrafficController???? ERROR - Transmit thread terminated prematurely by: java.lang.NullPointerException [nce.NceTrafficController Transmit thread]

java.lang.NullPointerException

?????????????? at jmri.jmrix.AbstractMRTrafficController.getPortName(AbstractMRTrafficController.java:818)

?????????????? at jmri.jmrix.nce.NceConnectionStatus.nceEpromPoll(NceConnectionStatus.java:132)

?????????????? at jmri.jmrix.nce.NceTrafficController.pollMessage(NceTrafficController.java:430)

?????????????? at jmri.jmrix.AbstractMRTrafficController.transmitLoop(AbstractMRTrafficController.java:469)

?????????????? at jmri.jmrix.AbstractMRTrafficController$1.run(AbstractMRTrafficController.java:770)

?????????????? at java.lang.Thread.run(Unknown Source)

?

-- Jeff

?

From: [email protected] [mailto:[email protected]] On Behalf Of Marcus Ammann
Sent: Wednesday, September 18, 2019 10:33 PM
To: [email protected]
Subject: Re: [jmriusers] NCE PowerPro Connection Issues

?

Hi Jeff

?

You said the USB to Serial cable worked in your mate¡¯s computer, that confirms the Cable is okay.

From your Console Log, it shows COM 3.

Make sure you are using the SAME USB Port on your computer each time.

?

With Decoder Pro showing the Roster page:

Select the Edit Tab, then

Select the Preferences Tab, then

Select Defaults on the Drop Down window.

?

Make sure ALL selections are ¡°ticked¡± for NCE and not Internal.

?

If you made any changes, make sure you select SAVE at the L/H bottom.

?

As others have said, maybe you need to upgrade from 4.16

?

If it still does not work, check your ¡°Serial¡± connection using this page:

?

?

Regards

Marcus

??
Locked Re: NX Routing

 

Thanks both

Good to see that the problem is being progressed, and that I can continue testing using internal turnouts. I will monitor 7431 to see the progress.

Bill
Locked Re: Signal Mast Appearance definition file

 

David¡¯s explanation is right, but should be prefixed.

If you¡¯re just _using_ signal masts, you don¡¯t need to worry about any of this. Look at the various signal systems linked on this page: Pick the one you want, then select it when creating your signal masts. That¡¯s all that¡¯s needed. Each of those systems is defined by multiple files. The help pages describes how it works, because some people want to know that. That¡¯s fine. But the existing systems _do_ work, and those web pages show what they do. All you have to do is pick one.

Bob


On Sep 19, 2019, at 5:58 PM, Dave Sand <ds@...> wrote:

Hal,

In order to understand the internals of signal mast logic does require looking at xml files.

When a signal mast is defined in the JMRI Signal Mast table, the Signal System and Mast Type are selected. The same Signal System is used for all of the masts.

Each mast type has an appearance-??????.xml file in the signal system directory. The <name> element has the user friendly name that is shown in JMRI.

The <appearances> section defines what the mast looks like, including the icons to be displayed on a JMRI panel.

The <aspectMappings> section defines what aspect should be displayed based on the current aspect of the next signal mast. A <aspectMapping> set is defined for each possible aspect as defined in aspects.xml. The next aspect name is defined using <advancedAspect>. This is followed by one or more <ourAspect> entries using one of the appearances listed in the <appearances> section.

If more than one <ourAspect> is listed, then the route and speed values in the aspects.xml file are used to determine the correct aspect for the mast.

The speed is based on the Path Speed as shown in the Signaling Mast Pairs SML window. This is based on block and turnout speeds.

The route is Normal if all turnouts are normal and Diverging if any turnout is diverging.

I hope I have not made things more confusing.

Dave Sand



On Sep 19, 2019, at 7:40 AM, haltz@... wrote:

Thanks, Billybob, vey helpful. I was just trying to figure out what the logic is as described in the "JMRI Signal Mast Logic" page. There it says (italics mine):

"Which Aspect our source Signal Mast displays after being released from "Danger" is firstly determined by the Aspect mapping that has been defined in the Signal Mast Appearance definition file. If there is only one Aspect that could be displayed, then the Signal Mast will be set to that Aspect.
However if multiple Aspects could potentially be displayed then the logic looks at two areas to determine the resulting Aspect to be displayed:"...Diverging Route...Block/Signal Speed..."

That's why I was trying to look at a definition fie, but didn't know which one to look at nor how to look at it (short of reading xml, which is fine as a last resort)
I'll look closer at all you wrote and maybe understand better. Thanks again, Hal.
--
Bob Jacobsen
rgj1927@...
Locked Re: Signal Mast Appearance definition file

 

Hal,

In order to understand the internals of signal mast logic does require looking at xml files.

When a signal mast is defined in the JMRI Signal Mast table, the?Signal System and Mast Type are selected. ?The same Signal System is used for all of the masts.

Each mast type has an appearance-??????.xml file in the signal system directory. ?The <name> element has the user friendly name that is shown in JMRI.

The <appearances> section defines what the mast looks like, including the icons to be displayed on a JMRI panel.

The <aspectMappings> section defines what aspect should be displayed based on the current aspect of the next signal mast. ?A <aspectMapping> set is defined for each possible aspect as defined in aspects.xml. ?The next aspect name is defined using <advancedAspect>. ?This is followed by one or more <ourAspect> entries using one of the appearances listed in the <appearances> section.

If more than one <ourAspect> is listed, then the route and speed values in the aspects.xml file are used to determine the correct aspect for the mast.

The speed is based on the Path Speed as shown in the Signaling Mast Pairs SML window. ?This is based on block and turnout speeds.

The route is Normal if all turnouts are normal and Diverging if any turnout is diverging.

I hope I have not made things more confusing.

Dave Sand



On Sep 19, 2019, at 7:40 AM, haltz@... wrote:

Thanks, Billybob, vey helpful. I was just trying to figure out what the logic is as described in the "JMRI Signal Mast Logic" page. There it says (italics?mine):

"Which Aspect our source Signal Mast displays after being released from "Danger" is firstly determined by the?Aspect mapping that has been defined in?the Signal Mast Appearance definition file.?If there is only one Aspect that could be displayed, then the Signal Mast will be set to that Aspect.
However if multiple Aspects could potentially be displayed then the logic looks at two areas to determine the resulting Aspect to be?displayed:"...Diverging Route...Block/Signal Speed..."

That's why I was trying to look at a definition fie, but didn't know which one to look at nor how to look at it (short of reading xml, which is fine as a last?resort)
I'll look closer at all you wrote and maybe understand better. Thanks again, Hal.
76741 - 76760 of 240292