¿ªÔÆÌåÓý

Date

Locked Re: Blocks not working properly

 

¿ªÔÆÌåÓý

Hello folks, I have a problem that I cannot seem to solve, perhaps one of you knowledgeable gentlemen can help, I have a N scale layout and I utilize BDL 168 for occupancy detection, I only use 12 detection blocks, when train is in 1 block that block does not light up occupied, instead another unoccupied block lights up, this only happens on the main oval tracks not the side tracks, I have checked all of my connections and found to be correct, I even went as for as completely deleting the panel pro and any thing associated with it in order to completely delete any prior info from previous panels and built a brand you layout, still no juice, any ideas as to the possible problem would be appreciated.

?

Thank you.

?

Sent from for Windows 10

?


Locked Re: BUG ? PanelPro: endlessly switching back and forth turnouts

 

Peter,

It would also be useful to know if any logix is/are active.

Wouter


On Sat, 5 Jan 2019 at 13:29, Peter Loth <peterloth@...> wrote:
Versions used:
- JAVA: 8 update 191,
- JMRI: 4.14
- Windows 10: Build 1809

Hardware used:
- Command station: Digitrax DCS240.
- Turnout decoders: Digitrax DS64 (Peco selenoid)
- Turnout decoder: Fleischmann 6915 (Fleischman 6154C)

JMRI Settings:
- Factory: Digitrax
- System connection: LocoNet PR3
- Serial port: COM3
- Command station type: DCS240 (Advanced Command Station)

Operating the turnouts with the DT500 and DT500D works perfectly.
When I switch a turnout via JMRI PanelPro, the turnout is endlessly back and forth. The same thing happens with the swing bridge of my Fleischmann turntable.

Peter Loth
the Netherlands


Locked Re: INFERNALS

 

¿ªÔÆÌåÓý

Don,

As a support person I completely agree that the 'Internal' setting bug was an 'infernal' bother.

As for your 'I' question the answer is pretty simple. Detectors, turnouts, etc. always require a 'System' name. The system name tells JMRI what connection is used to read and send any messages from/to that device. This shows up as a prefix like 'L' for LocoNet, 'N' for NCE, M for LCC etc. These examples are for actual hardware connections. However it is also possible to create an entry in JMRI that has no actual hardware connected. That JMRI only entry will have an 'I' for 'Internal' attached to it.

If you want to give random names to hardware be sure to use the 'User' name, not the 'System' name for your own definition. You are not allowed to simply make up 'System' names because they are the pointers to the actual hardware on your layout. 'PD03' sounds like it is your user name for some detector, so some 'helpful' programmer added an 'I' in front of it rather than warning you that you can't do that because there is no such thing as a 'PD' system device.

Dick :)

On 1/5/2019 9:55 AM, Don Weigt wrote:

Marc,

Sorry to "flog a dead horse", as the old saying here goes. Hope that's clear to everyone... I'm sorry if I took this all to seriously, but please understand what it's like for some of us just getting started with JMRI.

I wondered if INFERNALS was a joke, or real. I had seen other posts using INTERNALS, so thought there might be both in JMRI speak.

We're already dealing with JYTHON, which I understand is real, as is PYTHON in other places. So, when the gurus toss out terms, my first inclination is to think they are real. What's good fun for those who understand better, is just more uncertainty to those of us trying to wrap out heads around this big new thing.

I'm still wondering why Layout Editor is adding capital "i"s to the detector labels I have on my panel. For example, I enter PD03, it appears in the list as IPD03. Probably stands for INTERNAL PD03, but I've still not learned why some items get those added to their designators, while others, such as turnouts, don't. And I still don't grasp JMRI's distinction between internal and not internal. Might some be virtual in panels and others related to physical items on the layout? Not sure that's right, since detectors are on layouts.

JMRI is complicated enough without making it more confusing, however innocent the intent.

Stepping off the soapbox! (rant ends)

Don Weigt



Locked Re: Decoder Pro problems

 

¿ªÔÆÌåÓý

Likewise, "Read all from the decoder" instead of "Read changes on all sheets¡±?

Because that¡¯s not what it does. It only reads what was _changed_.

I always find this confusing - what has changed, the data on the sheet or has something changed in the decoder that I need to re-read it? (same with the similar message for a sheet).

?

I say again, when you learn another language, you don¡¯t complain that the foreign word means something different in English so you don¡¯t get it. You need to learn what it means in the language you are learning.

?

In JMRI, ¡°Read¡± means get data from the decoder and put it into the DecoderPro file. ¡°Write¡± means take data from the DecoderPro file and put it into the decoder. Once you learn that, everything makes sense.

?

I find the JMRI lingo quite logical and easy to understand. I wouldn¡¯t change it.

?

Mark Granville


Locked Re: Sensors not working

 

I've used Arduinos in conjunction with JMRI, but some more information would be useful to help diagnose the problem. ?E.g. what software are you running on the Arduino and how is it connected to JMRI? ?You've just upgraded to 4.14 - what from and was it working satisfactorily on that version? ?If sensors are not showing as Active are they showing as Inactive or Unknown? ?Is there a pattern to which sensors appear to work e.g. is it a range of system names that are effected? ?I think that there are differing versions of IRDOTs with direct (open collector) outputs or relays. ?Are yours electrically isolated from the Arduino by relays or are they directly connected?

Regards

Paul


Locked Re: XpressNet Session Log errors

 

Link worked for me.

--
Peter Ulvestad

JMRI Users Group Moderator - ( )
Tam Valley Group Moderator - ( )
Sprog-DCC Group Moderator - ( )
Edmonton Model Railroad Association -


Locked Re: Decoder Pro problems

 

Hi
Does anyone read the tooltips?
Steve G.


Locked Another new user with Mac to MRC Prodigy issues

David S
 

Hello everyone! ?This is my first post.

I've got a Mac running the latest OS with?the latest JMRI & Java software installed. ?I have ?a MRC Prodigy Advanced2 system and the MRC computer interface cable (#1516).

I've setup a connection in DecoderPro for the MRC using a serial connection and cab# 7.

How do I know if I have a connection? ?Obviously, I am at the bottom of the learning tree for JMRI so please bear with me. ? I use WiThrottle on my iPhone and have a full roster along with function labels set up via the phone. ? As I understand, the labels are all stored on the MRC 1530 WiFI device.

Once connected, can I access this roster or do I need to set it up again in DecoderPro/PanelPro?

More questions to follow once I have a connection, obviously.

Thanks,
Dave S


Locked Re: XpressNet Session Log errors

 

¿ªÔÆÌåÓý

Paul,

As you were. Slight hitch in link. Clicked it and noted that (.) missing ...jmri.tagadab....in URL address bar in browser.

Sorted. Will look at it a little later and let you know.

Cheers

Tom

On 05/01/2019 14:21, Paul Bender wrote:

Tom,

I think I have this fixed, at least I no longer see the error with an Atlas Commander connected to JMRI.

When you get a chance, please download a daily build from


To confirm you no longer see it either.

Thanks!

Paul


On Dec 28, 2018, at 3:43 AM, Tom Busza via Groups.Io <tombee50@...> wrote:

Many thanks Paul, I look forward to the fix.

Meantime Happy New Year to one and all.

Tom

On 28/12/2018 07:08, Paul Bender wrote:

On Dec 25, 2018, at 3:25 PM, Tom Busza via Groups.Io <tombee50@...> wrote:

I am just intrigued why this is happening.

The annoying part is that when I open JMRI, I have to wait for JMRI to check things, give me an error message:

System connection XpressNet provides a null manager for interface CommandStation Unable to to run startup due to earlier failures.?? Please check logs for more details. The Preferences window will open so this can be fixed.

This happens because you are using a Compact which doesn¡¯t provide support for sending raw packets to the rails.

BUT you shouldn¡¯t get this Error message because the command station option should be disabled when the compact is connected.

I¡¯ll pull out an Atlas Commander (rebadged Compact ) so I can replicate the issue and fix it. ?This might take me a few days however.

Paul


Virus-free.


Locked Re: INFERNALS

 

Marc,

Sorry to "flog a dead horse", as the old saying here goes. Hope that's clear to everyone... I'm sorry if I took this all to seriously, but please understand what it's like for some of us just getting started with JMRI.

I wondered if INFERNALS was a joke, or real. I had seen other posts using INTERNALS, so thought there might be both in JMRI speak.

We're already dealing with JYTHON, which I understand is real, as is PYTHON in other places. So, when the gurus toss out terms, my first inclination is to think they are real. What's good fun for those who understand better, is just more uncertainty to those of us trying to wrap out heads around this big new thing.

I'm still wondering why Layout Editor is adding capital "i"s to the detector labels I have on my panel. For example, I enter PD03, it appears in the list as IPD03. Probably stands for INTERNAL PD03, but I've still not learned why some items get those added to their designators, while others, such as turnouts, don't. And I still don't grasp JMRI's distinction between internal and not internal. Might some be virtual in panels and others related to physical items on the layout? Not sure that's right, since detectors are on layouts.

JMRI is complicated enough without making it more confusing, however innocent the intent.

Stepping off the soapbox! (rant ends)

Don Weigt



Locked Re: XpressNet Session Log errors

 

¿ªÔÆÌåÓý

Paul,

Thanks, but cannot open link. I just get "Server not found" message.

Thanks

Tom

On 05/01/2019 14:21, Paul Bender wrote:

Tom,

I think I have this fixed, at least I no longer see the error with an Atlas Commander connected to JMRI.

When you get a chance, please download a daily build from


To confirm you no longer see it either.

Thanks!

Paul


On Dec 28, 2018, at 3:43 AM, Tom Busza via Groups.Io <tombee50@...> wrote:

Many thanks Paul, I look forward to the fix.

Meantime Happy New Year to one and all.

Tom

On 28/12/2018 07:08, Paul Bender wrote:

On Dec 25, 2018, at 3:25 PM, Tom Busza via Groups.Io <tombee50@...> wrote:

I am just intrigued why this is happening.

The annoying part is that when I open JMRI, I have to wait for JMRI to check things, give me an error message:

System connection XpressNet provides a null manager for interface CommandStation Unable to to run startup due to earlier failures.?? Please check logs for more details. The Preferences window will open so this can be fixed.

This happens because you are using a Compact which doesn¡¯t provide support for sending raw packets to the rails.

BUT you shouldn¡¯t get this Error message because the command station option should be disabled when the compact is connected.

I¡¯ll pull out an Atlas Commander (rebadged Compact ) so I can replicate the issue and fix it. ?This might take me a few days however.

Paul


Virus-free.


Locked Re: BUG ? PanelPro: endlessly switching back and forth turnouts

 

Peter,

The questions I have are:
1. What is the configuration of the DS-64?
2. Did you wire any sort of 'feedback' for the turnout?
3. What 'mode' is the turnout in the turnout table? Direct, Monitor, etc...

That last one is the most likely suspect. Need to know the other answers to
try figuring this out.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org


Locked Re: XpressNet Session Log errors

 

¿ªÔÆÌåÓý

Tom,

I think I have this fixed, at least I no longer see the error with an Atlas Commander connected to JMRI.

When you get a chance, please download a daily build from


To confirm you no longer see it either.

Thanks!

Paul


On Dec 28, 2018, at 3:43 AM, Tom Busza via Groups.Io <tombee50@...> wrote:

Many thanks Paul, I look forward to the fix.

Meantime Happy New Year to one and all.

Tom

On 28/12/2018 07:08, Paul Bender wrote:

On Dec 25, 2018, at 3:25 PM, Tom Busza via Groups.Io <tombee50@...> wrote:

I am just intrigued why this is happening.

The annoying part is that when I open JMRI, I have to wait for JMRI to check things, give me an error message:

System connection XpressNet provides a null manager for interface CommandStation Unable to to run startup due to earlier failures.?? Please check logs for more details. The Preferences window will open so this can be fixed.

This happens because you are using a Compact which doesn¡¯t provide support for sending raw packets to the rails.

BUT you shouldn¡¯t get this Error message because the command station option should be disabled when the compact is connected.

I¡¯ll pull out an Atlas Commander (rebadged Compact ) so I can replicate the issue and fix it. ?This might take me a few days however.

Paul


Virus-free.


Locked Re: Roster Images Upside Down

 

¿ªÔÆÌåÓý

We need to stop blaming cameras/iPhones etc. and look into how to code JMRI so it makes use of the worldwide EXIF Orientation tag standard.

?

Why blame the end user? Maybe EXIF is just an unneeded complication. What do we care about the camera orientation? All we want is a picture where up is up. If we are an artist who wants a sideways picture, we can use photo editing software. Instead of adopting EXIF, the software coders for cameras etc. could have just made the camera always store an image in its right-side-up orientation so all software that imported it would get a properly oriented picture without additional coding in the end user software needed to make use of the EXIF.

?

I¡¯ve noticed this problem with videos taken with a smart phone. If the phone was rotated, the video plays rotated in Windows Media player but plays right-side-up using QuickTime. They automatically rotate the screen display to look correct. Why not store it that way?

?

However, since the cat is out of the bag, I suppose JMRI coders will eventually have to add to the code. Did I say complication that probably shouldn¡¯t have been introduced to begin with? Just another case of data overload?

?

Mark Granville


Locked Re: BUG ? PanelPro: endlessly switching back and forth turnouts

 

¿ªÔÆÌåÓý

Sorry, Peter, I cannot comment on your issue.

But I am replying on the conciseness and organization of your statement of the issue.?

I hope other posters take note.
--
Bruce Petrarca

On Jan 5, 2019, at 6:29 AM, Peter Loth <peterloth@...> wrote:

Versions used:
- JAVA: 8 update 191,
- JMRI: 4.14
- Windows 10: Build 1809

Hardware used:
- Command station: Digitrax DCS240.
- Turnout decoders: Digitrax DS64 (Peco selenoid)
- Turnout decoder: Fleischmann 6915 (Fleischman 6154C)

JMRI Settings:
- Factory: Digitrax
- System connection: LocoNet PR3
- Serial port: COM3
- Command station type: DCS240 (Advanced Command Station)

Operating the turnouts with the DT500 and DT500D works perfectly.
When I switch a turnout via JMRI PanelPro, the turnout is endlessly back and forth. The same thing happens with the swing bridge of my Fleischmann turntable.

Peter Loth
the Netherlands


Locked BUG ? PanelPro: endlessly switching back and forth turnouts

 

Versions used:
- JAVA: 8 update 191,
- JMRI: 4.14
- Windows 10: Build 1809

Hardware used:
- Command station: Digitrax DCS240.
- Turnout decoders: Digitrax DS64 (Peco selenoid)
- Turnout decoder: Fleischmann 6915 (Fleischman 6154C)

JMRI Settings:
- Factory: Digitrax
- System connection: LocoNet PR3
- Serial port: COM3
- Command station type: DCS240 (Advanced Command Station)

Operating the turnouts with the DT500 and DT500D works perfectly.
When I switch a turnout via JMRI PanelPro, the turnout is endlessly back and forth. The same thing happens with the swing bridge of my Fleischmann turntable.

Peter Loth
the Netherlands


Locked Re: Decoder Pro problems

 

Likewise, "Read all from the decoder" instead of "Read changes on all sheets¡±?
Because that¡¯s not what it does. It only reads what was _changed_.
I always find this confusing - what has changed, the data on the sheet or has something changed in the decoder that I need to re-read it? (same with the similar message for a sheet).


Locked Re: Decoder Pro problems

 

So (within the limitations of this text format), we could have (note preamble to each row of buttons):
"For CVs on this pane only: Recover values from decoder/Write changes to decoder/Read all from decoder/Write all to decoder."
"For the entire range of CVs: Recover values from decoder/Write changes to decoder/Read all from decoder/Write all to decoder."
To me these are better messages, they at least reference the decoder, and the direction the data is going, which makes them more intelligible to the non-technical user.

While the messages are slightly longer I believe the readability will increase a lot. Are we really that tight for screen space we can't have slightly larger buttons?

If need be there could have a 'beginners mode' with a pop-up text box that has a verbose explanation with 'proceed' and 'cancel' buttons. Somewhere there could be a tick box marked 'expert mode' to turn off beginners mode pop-ups.


Locked Re: JMRI Not Identifying Locomotives Properly

 

Hi Thomas,

That's an intresting notion, but as they are user defined values, it means that you can't trust them to remain constant. Someone might be using them, say, as the date of the last maintenance done to the engine, after which DecoderPro would no longer find it when identifying. Pity, because I like the idea. Maybe, just maybe, it would work with an option in the preferences to turn it on (default: off).

Wouter


On Fri, 4 Jan 2019 at 22:20, thomasmclae <thomas_applink@...> wrote:
That would be the railcom that I turn off in all my Loksound decoders.
Only a small subset of decoders have that feature, and older decoders of the same brand may not work the same..And we never throw out a working decoder, right?
You are asking for a feature that cannot be retrofitted, and that the Decoder makers see no profit in providing.

At the Club ( with hundreds of roster entries) we make use of the Owner data field. If you get duplicate matches, look at the owner.
And if you have more than one copy of a Lok learn how to renumber the thing. (I have about 6 duplicates on that list).

Someone years ago suggested using CV 105 & 106 as extra match fields. Most NMRA decoders have those. (more than have RailCom) Did that fall out?
The user would have to put data in those CVs, but they are right there on the basic sheet. Maybe too easy?

Thomas
DeSoto, TX


Locked Re: Decoder Pro problems

Peter Ross
 

Maybe it is because I only see the digest, Dave, but I'm still lost. I just searched for SwissChris and only found four messages none of which was relevant.
I used to get every message but there was too little of relevance to my situation.
Maybe you could cut and paste what SwissChris said into your reply? It would be interesting to know what it said.
Regards
Peter