Since I don't have anything up and running yet. Let me start: I have a Zephyr/50 and some BLI locos. I have downloaded JAVA and JMRI. And have played a bit with JMRI. But. I keep reading about all these updates. Both to Java and to JMRI. Are these really important to the average user? Example: After one sets up the system and has figured out DecoderPro and has programmed some locos. Is there a good reason to keep updating? Once it's up and running as expected, why do we need all these updates/upgrades? I keep reading about all the problems people have after they upgrade. Usually JMRI. I suspect that JAVA MUST be updated. So can that be done without having to keep updating JMRI? Obviously, I'm a novice and hope this isn't a stupid question. Windows 10 updates automatically and I never see what it "upgrades". Can't JMRI do much the same thing? Or as with Windows, have it set auto or ask first? I suspect Windows vs JMRI is apples and oranges.
Morgan Bilbo, PRR fan/1952.

I feel the need to reiterate my problem again, as we are now on the second page of this thread, Also, I would appreciate it if you have a question not pertaining to my situation that you start your own thread, so as not to confuse me with questions and answers not pertaining to my Decoder Pro problem, Thanks!

I am using JMRI's decoder Pro on it's own separate Programming Track:? It is hooked up to my newer computer with Windows 10 as the operating system.? The programming track is hooked up to the computer with a Digitrax PR-4 which is the same as the older PR-3; but comes with its' own Power Supply.? Since I don't have a computer in my layout room, This is the best system I could come-up with.??Along with JMRI's Decoder Pro, I have downloaded Digitrax SoundLoader Program, which works as intended.?

I got started down this path, because my brand New DCS-51 Zephyr Xtra needs service as it will not allow any programming of any kind. However, the Digitrax Facility in Panama City received damage from Hurricane Michael in October of this year.? Digitrax will not take any repair work until February 2019.? Hence paragraph # 2 above.

Upon downloading JMRI's Decoder Pro, I have watched all the videos pertaining to the use of Decoder Pro that I can find, including Larry Puckett's (The DCC Guy who writes "DCC Corner" in Model Railroader Magazine) five videos where in he gives a very detailed look at Decoder Pro.

So far I have attempted to use Decoder Pro on 4 locomotives: A Stewart VO-1000, address 415, Two Life Like Proto 2000? GP-7s addresses 553 and 555 and a Life Like Proto 2000 SW1200 address 106.? All of these locomotives worked previous to my attempts to place them on the Decoder Pro roster and I have fixed all of them using the Digitrax SoundLoader.??

Tests Performed working with my test model, the LLP2K SW1200 and you can assume that the loco was operating correctly previous to my use of the Decoder Pro software:?
Place loco on Programming Track, going to the "BASIC" window and at the "NORMAL DIRECTION OF TRAVEL" change to "Reverse"? Place loco on the layout and nothing happens, no lights, no movement.? Attempt other changes and the same thing happens.? Use one of the other locomotives I've listed and the same thing happens.

Since it was suggested that Address 106 is actually a short address, I have changed this from a long address to short using Decoder Pro.? This caused the loco to not operate,?

I have found that Decoder Pro can read a loco's address and may read all other criteria that has been added or changed.

This post will be the only post I will make today, 1/1/2019 and I will refer everyone to this post when they ask questions about things that are included in this post.

Happy New Year to all!? Mark? ??

Thanks Bob,

It has been a long time since I worked on a signaling project. I was not aware of the ability to disable aspects. in masts. Since I have not worked with them , I wanted to sty with what I know. I will try aspects just for the fun of learning something new. I will give that a try and it sounds like that will solve my friend's problem with the dreaded Red X.

Thanks for the assist (again)

Nick Kulp

---

Unfortunately, I don’t think there’s much that can be done about that. It’s just the way Signal Heads work.

You said you don’t want to use Signal Masts, but they do provide that ability to disable an aspect.? Then you only see the ones you want (the ones that are not disabled)

Bob

> On Dec 31, 2018, at 10:46 AM, Nick via Groups.Io <cornwall9=[email protected]> wrote:
>
> Spuds,
>
> Thanks for the response. My REAL question is how do I get rid of it ? I do not use Logix or signal masts . All I want is to create a simple model railroad signal set like the on in signal masts . It only has 4 icons. I do not want 8, or 10 "selections" that need to be "scrolled" through until I can get to the one I want on the panel. When I try to create a set, the only "choices" I get provide 8-10 blanks with red X's to place my icons into. Any unused box will bring up the red X if not changed. All I want is a set with 4 boxes so I can use the 3 basic aspects, Red, Yellow, Green, period.
>
> Is there any way I can accomplish that in signal heads ?
>
> Thanks,
> Nick Kulp
>
> "Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes...Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than to prevent homicides, for an unarmed man may be attacked with greater confidence than an armed man."
>
> -Thomas Jefferson
>
>
>
> From: Spuds McCat <spudsmccat@...>
> To: [email protected]
> Sent: Monday, December 31, 2018 12:21 PM
> Subject: Re: [jmriusers] PanelPro icon sets question
>
> The red x is caused by lack of logic. It's telling you that that head has no clue what it should be displaying.
>
> On Sun, Dec 30, 2018, 10:48 Nick via Groups.Io <cornwall9=[email protected] wrote:
> Friends,
>
> After being away from panel creation for a LONG time, I have been helping a friend prep his layout for signaling. Getting signals set up is not a problem. I can actually still do that. I like some of the changes in the way things work but I have a question about Panel Editor.
>
> He uses Digitrax, Windows 7 64-bit PRO, Locobuffer USB, and it has worked a long time without problems.
>
> In one location, he has a simple signal set up that his dispatcher can "clear" for train movement by clicking on the signal on the panel and it will return to Red when the train trips a sensor past the yard entrance. It is simple and uncomplicated.
>
> Previously, he was using a very old version of JMRI, (Version 3.11 I think) Before the new JAVA update. Since I was using a later version that offered more options and a better CMRI interface, I suggested that he update his to the newest 4.15 just released. He had to update JAVA, then update JMRI. Naturally, this created havoc. The new file system completely bollixed his panel and that took a little time to repair. After we solved that problem (error messages about turnouts out of range LT3005 which didn't exist) , we started to experiment with creating CMRI signal heads. He will be using PRR Position lights with only ONE head and 3 aspects .
>
> To keep things simple, all signal HEADS will be the same configuration. Triple Output, Steady, with the signal lit.
>
> Our problem is that when we try to create an icon set with limited icons (He HATES the RED X when the panel comes up), I cannot figure out how to eliminate the "fancy" settings like flashing or dark so that only the icons we want are in the set. Currently when we want to add signals, there are 8-10 icons needed. We don't want to build signal masts. The signals will be ultra simple, ABS. The dispatcher only controls routes, not signals. This might change in the distant future, but for now. the KISS method will be what we want.
>
> How can we eliminate the extra aspects when we create our icon set ? I apologize for the lengthy question but this is the first time I have been unable to keep abreast of simple signaling problems. Any help will be appreciated.
>
> Regards and Happy New Year,
> Nick Kulp
>
>
>

--
Bob Jacobsen
rgj1927@...

1) Why make the main thread wait with a join?? What does that do for you?

2) I’m not a Bash expert, but that looks like it should work.? Somehow, Jython isn’t initializing properly for you.? Are you getting a line like this in the log?

2019-01-02 11:58:29,512 script.JmriScriptEngineManager? ? ? ? INFO? - python 2.7 is provided by jython 2.7.0 [AWT-EventQueue-0]

When I force an error, I get output that starts like:

2019-01-02 11:58:41,099 jython.InputWindow? ? ? ? ? ? ? ? ? ? ERROR - Error executing script [AWT-EventQueue-0]
javax.script.ScriptException: NameError: name 'xo' is not defined in <script> at line number 1
? ? ? ? at org.python.jsr223.PyScriptEngine.scriptException(PyScriptEngine.java:202)
? ? ? ? at org.python.jsr223.PyScriptEngine.eval(PyScriptEngine.java:42)
? ? ? ? at org.python.jsr223.PyScriptEngine.eval(PyScriptEngine.java:31)
? ? ? ? at javax.script.AbstractScriptEngine.eval(AbstractScriptEngine.java:264)

Bob

> On Jan 2, 2019, at 8:24 AM, whmvd <vandoornw@...> wrote:
>
> Hi Bob ,
>
> Thanks for the quick reaction.
> Re 1: I actually do that in a separate thread - but then the first thread waits while 'join'ing the subthread, so that remains the same problem, really. Do I need to make the subthread a daemon one and let the main thread just go? That would seem to make sense?
>
> Re 2: I use 'Run script...' from the Tables menu. If it helps, this is the script I use to start jmri (which should be good enough):
> =============================
> #!/bin/bash
>
> cd $HOME/JMRI
> nohup ./PanelPro >>$HOME/Desktop/.PanelPro.log 2>&1 &
> =============================
> Everything I log neatly shows up in the file on the desktop. The install is squeaky-clean; everything I do is in the user files area, nothing in the installation directory. VERY interesting that 'sensors' and 'turnouts' should have been predefined...
>
> Wouter
>
>
>
> On Wed, 2 Jan 2019 at 15:52, Bob Jacobsen <rgj1927@...> wrote:
> 1) There are ways to do this. They start off looking complicated, but you have to remember that asking the program to sleep _actually_ _works_: If you do that in the main program, the main program sleeps so that you can’t click, etc.? Instead, you have to hive your turnout activity into a little separate item (called a “thread”) which can run and sleep independently.
>
>
>
> 2) How are you running your scripts?? When I run something (i.e. while debugging) from a Script Entry window, the syntax error and runtime error messages show up nicely on JMRI System console window. Perhaps you’re running them a different way or there’s something else wrong?
>
> Another clue that something is wrong is not seeing “turnouts” and “sensors” predefined.? They _definitely_ should be.
>
> Bob
>
> > On Jan 2, 2019, at 7:42 AM, whmvd <vandoornw@...> wrote:
> >
> > Hello scripting-gurus,
> >
> > For quite a while now, I've been fighting python/jython rather than using it, and frustration is building up. I want to like it, I want to work with it - but it's not making it easy. For now, I'd like to focus on two things that make life very hard:
> >
> > 1) A small test script that looks up a turnout (successfully) checks its status (thrown or closed), logs it and sleeps for 0.2 seconds before checking again until it is what I want it to be does not allow me to operate any of my four panels (3x Panel Editor, 1x Layout Editor). The only things that can be operated are the resize buttons on the window and the positioning. So I can't throw the turnout to let the test program complete (the log line appears every 0.2 seconds, so it sort of seems to work). I would have thought that the time.sleep(200/1000.0) would allow me to do things instead of the whole interface being locked up? (BTW: specifically not looking for different ways to do this; I know I should add a listener and make that react, and I will end up doing that anyway - I am trying to understand why the simple thing I'd like to do cannot work)
> >
> > 2) When I make one of my frequent coding errors, the result is the same as described above - interface locked up except for the sizing/positioning of windows). I get no error logged. Nothing on standard output or standard error,? and nothing in the console. Zilch. This leaves me having to guess where I could have gone wrong, instead of being able to look at a stack dump. For instance: I thought in my optimism that the variables 'turnouts' and 'sensors' where predefined when importing jmri, so I was happily using them. That caused the lock-up with no message at all. Finding the cause of that took me several frustrating days. I hope to turn this back into a hobby!
> >
> > Any help will be greatly appreciated.
> >
> > Wouter
> >
> > PS: using JMRI 4.14 on Linux Mint 18.3.
> >
>
> --
> Bob Jacobsen
> rgj1927@...
>
>
>
>
>
>
>

--
Bob Jacobsen
rgj1927@...

?Don't worry too much about the small test updates . I just update when an official Production release comes up . We are now on production release 4.14 . There is a test release of 4.15.1 now , but I wont update till the next production release is available . Keeping up with the production updates keeps the decoder definations up to date and also covers any new decoders that may come out between production releases.....Mike

On Wed, Jan 2, 2019 at 12:42 PM PennsyNut <pennsynut@...> wrote:

Since I don't have anything up and running yet. Let me start: I have a Zephyr/50 and some BLI locos. I have downloaded JAVA and JMRI. And have played a bit with JMRI. But. I keep reading about all these updates. Both to Java and to JMRI. Are these really important to the average user? Example: After one sets up the system and has figured out DecoderPro and has programmed some locos. Is there a good reason to keep updating? Once it's up and running as expected, why do we need all these updates/upgrades? I keep reading about all the problems people have after they upgrade. Usually JMRI. I suspect that JAVA MUST be updated. So can that be done without having to keep updating JMRI? Obviously, I'm a novice and hope this isn't a stupid question. Windows 10 updates automatically and I never see what it "upgrades". Can't JMRI do much the same thing? Or as with Windows, have it set auto or ask first? I suspect Windows vs JMRI is apples and oranges.
Morgan Bilbo, PRR fan/1952.