Locked
JMRI Not Identifying Locomotives Properly
I have many locomotives with proper road numbers that overlap with others. For example, I have a Kato NYC PA unit with the number of 4301, but I also have a Kato SD70ACE in MRL with the same number.? I have many instances of this same situation.? There must be a better way to assign the identity of a locomotive so that these miss-identities do not happen. I have 62 of these occurrences. This is where better indexing could keep this from happening.
|
Hi Morgan,
I'm new here too and had the same question (but only in my head). I discovered that one of my my new locos doesn't have it's decoder listed in the JMRI database yet so that right there is one reason to update- at least when there are production releases.
Best of luck.
Andy
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.
|
Locked
Re: Decoder Pro problems
Hello Mark (Deschane??),
First, let me apologize for hijacking (or at very least, misdirecting) your thread. I felt like we may have had similar issues but it now seems I have confused your discussion and potential problem solving. I'm sorry about that.
I will restate my issue in a new thread shortly and refrain from commenting on my issue here.
To follow up on something you've mentioned, I'm wondering what the problem is with your DCS51 and how you discovered it.?
Thanks,
Andy Roberts
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? ??
|
Locked
Re: PanelPro icon sets question
Hi Nick,
It sounds like the way you might want to go is defining your own (signalmast) signalling system. I know that sounds daunting, but even I was able to do that quite quickly; I derived a system from the 'basic' system that is much simpler even than the basic one itself. A few xml-files and a few icons was all it took, and if you can re-use some existing icons then you'll be done even faster.
If you like, I can send you that entire signal system as a zip or tar file so you can try it out. It's a one lamp dwarf, either red, yellow or green. And it works with the existing signal logic without any trouble. I was impressed at the ease of the process!
Wouter
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@...
|
Locked
Re: Trying to get on top of jython
Hi Bob,
Re 1) Not only did I think that was the way to do it, I was also (and am still) just building my 'library of tricks' to use in the proper, big script later on. This is one of the stages of learning! I have now removed the join, and made the spawned threads daemons, and that now works a *lot* better! Not only do I now get error messages when I need them (hurray!), the user interface no longer locks up, as you predicted (double hurray!).
Re 2) The line you mention is there. I'll see next what happens when I do not create that 'sensors' variable myself. IF it still goes wrong, at least I have an error message now to tell me where and how I goofed.
It's a lot better already, so thank you very much for the help so far. I'll let you know the result of the test once I get to it, which won't be today, but I hope to find time tomorrow.
Thanks again, Wouter
On Wed, 2 Jan 2019 at 20:03, Bob Jacobsen < rgj1927@...> wrote: 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@...
|
Locked
Re: PanelPro icon sets question
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@...
|
Locked
Re: Connect JMRI to Loconet through WIFI
Hi,
Trying a similar thing with RPI 3 running JMRI 4.12, Java 191 but using the Loconet simulator for testing purposes.? The client is a Pi zero wireless with same pieces of software on the same network. (The zero with a small touch screen is actually cheaper that iPads, etc.).?
Set up the server start action in preferences.? Restarted JMRI on the RPI.? ?Opened a Panel Editor panel.? Started JMRI on the zero.??
No joy with any of the JMRI client/server options: Simple server, Loconet 'direct', Loconet over IP...
The zero says cannot connect to the server and opens the preference dialog to update.? The Loconet tab is highlighted in red.
The RPI does not?seem to start the Loconet Server at init, even though I get INFO - lnPacketizer Started [main] in the console;
and starting it manually gives:
WARN - Could not Create RMI Registry, Attempting to locate existing Registry for: LoconetServer [AWT-Eventque-0]
Both systems can ping each other across the network.
Please advise, and thanks,
Martin Booker
BTW: the Web pages for client server configuration need an update as those screens are not the same in 4.12
|
Locked
Re: PanelPro icon sets question
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@...> 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@... 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@...
|
Locked
Re: Trying to get on top of jython
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@...
|
Hi Morgan,
There are definitely advantages to staying up to date as far as JMRI is concerned.
For one thing, if at one time, say in four years, you find you HAVE to upgade (for whatever reason; could be a solved bug, a new feature, or a new decoder on your layout) it will become a much more daunting task than the small updates once every half year. The chances of fouling up become a lot bigger.
Another reason is that, if you need support, there will be many more group members able to help if you are on a release that is current, or nearly current. Support requests for version 1 and 2 are now pretty unlikely to be resolved - knowledge slips away, but also interet in getting an old version back to life becomes very limited. And actual fixes on old releases, even if a bug is found, are highly unlikely to happen.
Once in a very big while, a new version of JMRI
might mean that you need to update Java as well. That is, however,
extremely rare.
Another factor is what other things you use your computer for. Nothing? Then that's very nice and easy. Don't even connect it to the internet, to prevent any automatic updates to, for instance, Windows which is many ases causes problems. It also makes antivirus software superfluous, which is something else that can muck up the installation process. If you *do*? use it for other things (or if your JMRI usage includes anything cloud based, like Dropbox) then you're prett much sunk and you need to keep OS and Java up to date anyway. And if you use a brower, then that, too.
Bottom line is, that only YOU can determine what's necessary - once you know the ins and outs of every choice you can make. Nobody can do it for you. From where I'm sitting, it sounds like a cheap, dedicated computer for just your trains sounds like the way to go. And I would advise keeping up to dte with production releases of JMRI, and of Java when JMRI says so. Yes, it's a bit more money that co-use of that computer with other applications. But it will give peace of mind.
Wouter
Wouter
On Wed, 2 Jan 2019 at 18:27, Mike Chamberlain < mikec6201@...> wrote: ?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
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.
|
?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
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.
|
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.
|
Locked
Re: MQTT Connection in JMRI
>> What I don¡¯t see (myself doing) is lots of MQTT diagnostics being built into JMRI: An address space browser, et al. There are lots of those around, and they¡¯re better than what we can do.
Sir,?
If we can create an "MQTT (traffic) monitor" to show the "incoming" and "outgoing" Topic and Message, we should have a good starting point.? I'd be willing to write some code to allow us to publish a message to a topic in another window.
Speed
|
I too did the same thing. Once I looked at the xml, I saw the format being
wrong. Remembering we ran into this a number of times before, the fix is
easy for us who edit xml files. What I don't recall is what we put into the
release documents to warn that if any panel file, using routes, from before
4.something, it was part of making standardized system names to insure
everything can identify them right. I guess one of the other things we might
consider is a test in the xml validator that would look for the R[0-9]*
pattern and flag that as an invalid name. I recall there was talk of a
conversion utility but this had not come up very often. Efforts like that
are not justified if we only run into it once every couple of months.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org
|
Locked
Re: Trying to get on top of jython
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@...
|
toggle quoted message
Show quoted text
On Jan 2, 2019, at 9:35 AM, Scott Rixon <scott@...> wrote:
Running 4.11.3+ is fine. But when I switch the install to either 4.12 or 4.14 I get the same error. So something has been changed and I'm missing an upgrade step?
|
Locked
Re: MQTT Connection in JMRI
Sensors and Reporters are the obvious things that need to subscribe, but even Turnouts and Lights should do it so that they learn if the state was changed remotely. (We don¡¯t do this for all things, i.e. signal heads, mostly for historical reasons) Broadly, there are two approaches: A) Require that everything be defined in JMRI first, and then JMRI just subscribes to what it knows about. This can be a lot of separate subscriptions; I don¡¯t know whether that¡¯s an issue or not. B) Define some address space (to keep types separate) and then use wildcards to subscribe to all of it. I.e. if the topic for Sensors always contained the word ¡°:sensors" and for turnouts ¡°turnouts¡±, JMRI could subscribe to #/sensors/# and #/turnouts/# which would allow it to automatically populate the tables. But it requires some sense of address space, so that JMRI can tell which MQTT item is of which type. Personally, I prefer (A). Digitrax does (B), and we get about a thread per month of ¡°how do I get rid of the items I don¡¯t want?¡± from people who have electronics installed with extra channels. It also is the most flexible, because it doesn¡¯t require anything specific in the topic name structure. What I don¡¯t see (myself doing) is lots of MQTT diagnostics being built into JMRI: An address space browser, et al. There are lots of those around, and they¡¯re better than what we can do. Bob On Jan 2, 2019, at 7:52 AM, Speed <gertmul@...> wrote:
The "subscription" to an MQTT broker is the harder part, since we would either need to subscribe to every topic in use individually or subscribe to all (which they discourage here: ) and then distribute it to the topics that exists in the table(s). Would all this need to be done in a separate thread, the JMRI gurus would need to help here?!? -- Bob Jacobsen rgj1927@...
|
Locked
Re: Layout Editor Turnout control definition
On Jan 1, 2019, at 10:30 PM, Don Weigt <dweigt47@...> wrote:
The little light bulb is beginning to turn on dimly! My script running in JMRI will need to take the data identified for the JMRI labeled device, and translate that into something I can use to map inputs and outputs into my computer's railroad I/O RAM space. Is that right? The data are identified in JMRI by the JMRI IDs I'm creating when I generate tables for sensors, turnouts, blocks, and so on? Right! I'm planning to use EasyDCC for only train control, not for controlling turnouts or other devices. I'd rather control turnouts and other things from facia mounted control panels or tablets or smart phone type throttles. I've been using EasyDCC plug in throttles. I have six. EasyDCC wireless costs more than I want to spend. Using tablets or smart phones and JMRI instead, seems very attractive.
Using a C/MRI protocol would reduce the amount of programing I'd need to do. I haven't paid much attention to it, I'd started my computer control project before C/MRI was published. I considered using C/MRI, but didn't because I thought its hardware was inefficient, with separate power and boards for each block. My hardware has (less) power control and occupancy detection for for blocks on each track board.I'm also multiplexing switch and detector inputs and LED driving outputs, not using static boards with separate hardware for each device. But, that doesn't mean the protocol won't work to transfer my data to and from JMRI and save me some work! Using JMRI for throttles makes it a bit more complicated. You want three things: Throttle control, turnout control, and sensor readback. Unfortunately, neither EasyDCC (no sensor support) nor C/MRI (no throttle support) can do all three. Maybe two serial links to your PC? Bob -- Bob Jacobsen rgj1927@...
|
Locked
Re: Trying to get on top of jython
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@...
|
Locked
Re: MQTT Connection in JMRI
Thank you Bob!
We should start with something simple, like using the Topic in the System Name (as Bob suggested) and then use, at first, the same Message or Payload as JMRI already does it, may that be Turnouts with "Closed/Thrown", Sensors with "Active/Inactive", Signals with "Red/Yellow/Flashing Green" and Masts with "Stop/Clear/Approach/Dark", for the publishing part.
And for the subscribing part, do the same, change a sensor when an "Active" or "Inactive" is published and JMRI receives it.?
The "subscription" to an MQTT broker is the harder part, since we would either need to subscribe to every topic in use individually?or?subscribe to all (which they discourage here: ) and then distribute it to the topics that exists in the table(s). Would all this need to be done in a separate thread, the JMRI gurus would need to help here?!?
I do not completely understand the use?of JSON, but most libraries for embedded systems have limits to the message size, the library I am using for example () has a 128 byte limit: "MQTT_MAX_PACKET_SIZE".? Sure, we could change that number, but where does that leave the 8-bit controllers with limited memory space?? I imagine JMRI would publish to a Broker, and the Broker would then send it directly to the described small devices. When we publish an 'ACTIVE' to a topic that contains 'sensor', is it worth unpacking the JSON string to find out that it is a sensor and the state is now active? Not saying there is no need for JSON, I just don't see the need in the end device receiving the MQTT message.
But, I am quite sure that once we have subscription up and running, we could expand it to publish JSON, why else would we have the next release?
Retention could be "active" at first, until we see the need to turn it off...not sure how much work it is to add columns in the tables.
For the Preferences->Connections, we should add Username and Password, and eventual the QOS (quality of service) settings, and maybe we could use the "MQTT channel" to enter the first part of the Topic, so we don't need to type "TxNamib/UpperLevel/BackCorner/" in front of every sensor in the sensor table's System Name. (note that they discourage use the leading '/' at the very front)
Then, when we have working subscription MQTT in JMRI, we could add options on what to publish on the different states, so that "Closed/Thrown" could maybe be "0/1" or "Normal/Reverse"?
Speed
|
Andrew Roberts
Bob Jacobsen
Ken Cameron