Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Jmriusers
- Messages
Search
|
Locked
Re: Panel pro window does not appear un an upgraded linux mint system
Dave,
toggle quoted message
Show quoted text
What version of JMRI are you running? Are there any error messages in ~/.jmri/log/session.log? Does PanelPro start when using a new profile? Does PanelPro start after removing the startup actions? Dave Sand On Mar 10, 2018, at 9:40 AM, dap@... [jmriusers] <jmriusers@...> wrote: |
|
Locked
Re: Problemconnecting 2 crossovers with track segments
Ken,
toggle quoted message
Show quoted text
I have created a GitHub issue so hopefully someday it will be fixed. I am currently working on other things but it is on my mental list. Dave Sand On Mar 10, 2018, at 11:43 AM, Ken boomer17@... [jmriusers] <jmriusers@...> wrote: |
|
Locked
error message
For some reason I'm now getting an unrecoverable error message when I try to open Decoder or Panel Pro I've uninstalled and reinstalled the software but no change. every thing was OK one day and not the next. I keep my files are on a USB stick and every thing works normal on a second computer.
Gerry |
|
Locked
Re: Problemconnecting 2 crossovers with track segments
Thanks Dave, I would never thought to try that. Works great. Will that
toggle quoted message
Show quoted text
bug be fixed? Ken On 3/10/2018 12:13 PM, Dave Sand dave@... [jmriusers] wrote:
There is a way to get around the bug. |
|
Locked
How to use Decoder Pro
New to Decoder Pro. Three questions:
What is the proper procedure to read an address, change an address, and access programming values for: 1. A BLI Loco ? 2. A BLI Blueline Loco that has the sound decoder installed and another decoder added? 3. A loco with a DCC decoder and a Soundtrack decoder ? Thank you for your response. Ed Woz. |
|
Locked
Re: Problemconnecting 2 crossovers with track segments
Yes, this is a bug.
toggle quoted message
Show quoted text
There is a way to get around the bug. The 4 connection points on a cross-over are labeled A-D with A being the upper left point (purple or blue), going clockwise. If a track segment is attached to point B (upper right) you cannot attach a track segment to point C (lower right). Make the connection to point C first and then the connection for point B. Dave Sand On Mar 10, 2018, at 10:49 AM, boomer17@... [jmriusers] <jmriusers@...> wrote: |
|
Locked
Problemconnecting 2 crossovers with track segments
Using Panel Editor 4.11.4ish in Loconet simulator mode I can not seem to attach a track segment to the crossovers as shown. Could this be a bug?
CROSSOVER TEST.XML has been uploaded. |
|
Locked
New file uploaded to jmriusers
Hello,
This email message is a notification to let you know that a file has been uploaded to the Files area of the jmriusers group. File : /ProblemsBeingWorkedOn/Ken's crossover problem/CROSSOVER TEST.xml Uploaded by : boomer535 <boomer17@...> Description : Problem connecting track segments You can access this file at the URL: To learn more about file sharing for your group, please visit: Regards, boomer535 <boomer17@...> |
|
Locked
Re: Decoderpro sound issue
I use the programming tack to set the address of the decoder. and to read the decoder,if needed.
All other programming is done on the main (Ops mode). That way I can see and hear the results of the changes. Walt |
|
Locked
Panel pro window does not appear un an upgraded linux mint system
Dear All,
I am having problens with the main PanelPro interface window not appearing. Any ideas folks? We have upgraded from Linux Mint 17 to Linux Mint t0 18.2 on a PC used for JMRI by completely reinstalling a Linux Mint image (one we use on many other computers just fine). The railway itself is controlled by DCC++. I then copied on the exact copy of JMRI I had before and my .jmri directory. When I now start PanepPro it connects to DCC++, various jython scripts runfine (to initialise turnouts etc) a layout panel I had been experimenting with shows but the main PanelPro window never appears. Our new Linux Mint image, as well as being Mint 18.2 (rather than 17) we will also have lots of other new applications, java updates and many more... Any bright ideas anyone? Any suggestions of things that can stop the PanelPro main window appearing? I'll be doing more proper debugging on Monday morning.... We had hoped to have our railway shunting yard with auto shunting scripts and part of a new student project working as part of our 'annual science week' whuch we have to set up Monday afternoon. Dave Price |
|
Locked
Re: Decoder Pro is exceptionally sluggish
Hi Dave,
toggle quoted message
Show quoted text
So with all av's turned off and everything removed from the system, just to why it is locking up on the completion of the install - is this why it won't talk to the command unit? It recognises that it is there, but can't access. Something somewhere is stopping this installation process completing - I've not had this with any other software installed on the PC. Regards, GeoffB On Saturday, 10 March 2018, 06:57:54 GMT, Dave Heap dgheap@... [jmriusers] <jmriusers@...> wrote:
? I suspect the registry entries would have all been related to the installer. JMRI runs on multiple platforms (Mac, Linux and Windows). The first two have no concept of a registry, so JMRI doesn't use any registry entries. As long as you've got a clean install of whatever you wanted. I just fixed another user's V4.11.3 installation lockup by getting him to temporarily disable virus protection. -- Dave in Australia The New England Convention 2018 On 10 Mar 2018, at 12:49 PM, Geoff Byman gbrails@... [jmriusers] <jmriusers@...> wrote:[Non-text portions of this message have been removed] #yiv8295315233 #yiv8295315233 -- #yiv8295315233ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv8295315233 #yiv8295315233ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv8295315233 #yiv8295315233ygrp-mkp #yiv8295315233hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv8295315233 #yiv8295315233ygrp-mkp #yiv8295315233ads {margin-bottom:10px;}#yiv8295315233 #yiv8295315233ygrp-mkp .yiv8295315233ad {padding:0 0;}#yiv8295315233 #yiv8295315233ygrp-mkp .yiv8295315233ad p {margin:0;}#yiv8295315233 #yiv8295315233ygrp-mkp .yiv8295315233ad a {color:#0000ff;text-decoration:none;}#yiv8295315233 #yiv8295315233ygrp-sponsor #yiv8295315233ygrp-lc {font-family:Arial;}#yiv8295315233 #yiv8295315233ygrp-sponsor #yiv8295315233ygrp-lc #yiv8295315233hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv8295315233 #yiv8295315233ygrp-sponsor #yiv8295315233ygrp-lc .yiv8295315233ad {margin-bottom:10px;padding:0 0;}#yiv8295315233 #yiv8295315233actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv8295315233 #yiv8295315233activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv8295315233 #yiv8295315233activity span {font-weight:700;}#yiv8295315233 #yiv8295315233activity span:first-child {text-transform:uppercase;}#yiv8295315233 #yiv8295315233activity span a {color:#5085b6;text-decoration:none;}#yiv8295315233 #yiv8295315233activity span span {color:#ff7900;}#yiv8295315233 #yiv8295315233activity span .yiv8295315233underline {text-decoration:underline;}#yiv8295315233 .yiv8295315233attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv8295315233 .yiv8295315233attach div a {text-decoration:none;}#yiv8295315233 .yiv8295315233attach img {border:none;padding-right:5px;}#yiv8295315233 .yiv8295315233attach label {display:block;margin-bottom:5px;}#yiv8295315233 .yiv8295315233attach label a {text-decoration:none;}#yiv8295315233 blockquote {margin:0 0 0 4px;}#yiv8295315233 .yiv8295315233bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv8295315233 .yiv8295315233bold a {text-decoration:none;}#yiv8295315233 dd.yiv8295315233last p a {font-family:Verdana;font-weight:700;}#yiv8295315233 dd.yiv8295315233last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv8295315233 dd.yiv8295315233last p span.yiv8295315233yshortcuts {margin-right:0;}#yiv8295315233 div.yiv8295315233attach-table div div a {text-decoration:none;}#yiv8295315233 div.yiv8295315233attach-table {width:400px;}#yiv8295315233 div.yiv8295315233file-title a, #yiv8295315233 div.yiv8295315233file-title a:active, #yiv8295315233 div.yiv8295315233file-title a:hover, #yiv8295315233 div.yiv8295315233file-title a:visited {text-decoration:none;}#yiv8295315233 div.yiv8295315233photo-title a, #yiv8295315233 div.yiv8295315233photo-title a:active, #yiv8295315233 div.yiv8295315233photo-title a:hover, #yiv8295315233 div.yiv8295315233photo-title a:visited {text-decoration:none;}#yiv8295315233 div#yiv8295315233ygrp-mlmsg #yiv8295315233ygrp-msg p a span.yiv8295315233yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv8295315233 .yiv8295315233green {color:#628c2a;}#yiv8295315233 .yiv8295315233MsoNormal {margin:0 0 0 0;}#yiv8295315233 o {font-size:0;}#yiv8295315233 #yiv8295315233photos div {float:left;width:72px;}#yiv8295315233 #yiv8295315233photos div div {border:1px solid #666666;min-height:62px;overflow:hidden;width:62px;}#yiv8295315233 #yiv8295315233photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv8295315233 #yiv8295315233reco-category {font-size:77%;}#yiv8295315233 #yiv8295315233reco-desc {font-size:77%;}#yiv8295315233 .yiv8295315233replbq {margin:4px;}#yiv8295315233 #yiv8295315233ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv8295315233 #yiv8295315233ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv8295315233 #yiv8295315233ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv8295315233 #yiv8295315233ygrp-mlmsg select, #yiv8295315233 input, #yiv8295315233 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv8295315233 #yiv8295315233ygrp-mlmsg pre, #yiv8295315233 code {font:115% monospace;}#yiv8295315233 #yiv8295315233ygrp-mlmsg * {line-height:1.22em;}#yiv8295315233 #yiv8295315233ygrp-mlmsg #yiv8295315233logo {padding-bottom:10px;}#yiv8295315233 #yiv8295315233ygrp-msg p a {font-family:Verdana;}#yiv8295315233 #yiv8295315233ygrp-msg p#yiv8295315233attach-count span {color:#1E66AE;font-weight:700;}#yiv8295315233 #yiv8295315233ygrp-reco #yiv8295315233reco-head {color:#ff7900;font-weight:700;}#yiv8295315233 #yiv8295315233ygrp-reco {margin-bottom:20px;padding:0px;}#yiv8295315233 #yiv8295315233ygrp-sponsor #yiv8295315233ov li a {font-size:130%;text-decoration:none;}#yiv8295315233 #yiv8295315233ygrp-sponsor #yiv8295315233ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv8295315233 #yiv8295315233ygrp-sponsor #yiv8295315233ov ul {margin:0;padding:0 0 0 8px;}#yiv8295315233 #yiv8295315233ygrp-text {font-family:Georgia;}#yiv8295315233 #yiv8295315233ygrp-text p {margin:0 0 1em 0;}#yiv8295315233 #yiv8295315233ygrp-text tt {font-size:120%;}#yiv8295315233 #yiv8295315233ygrp-vital ul li:last-child {border-right:none !important;}#yiv8295315233 [Non-text portions of this message have been removed] |
|
Locked
Re: WiThrottle viewing turnouts
Brian, please send me your session.log file and your panel file. Sounds like something in the data is messed up and needs fixing.
SteveT |
|
Locked
Re: Upgrading JMRI from 4.10 to 4.11.3 caused major issue
I find that the first time I try the install, it is rejected by the AV. The
second time I try, it gives dire warnings, but I say install anyway and it works fine. One has to read the AV pop ups carefully to know which 'other option' to pick to get it to do the install on fresh new code. -Ken Cameron, Member JMRI Dev Team www.jmri.org www.fingerlakeslivesteamers.org www.cnymod.com www.syracusemodelrr.org |
|
Locked
Re: WiThrottle viewing turnouts
Hi, David you are not alone with this problem.
I am using JMRI 4.10 and was happy with WiThrottle and as the layout developed I really liked the facility of switching turnouts from the throttle. The problem arrived when I added 2 more turnouts. They did not show on the WiThrottle list. All my turnouts have user names and I was already using the filter feature to display only relevant turnouts on WiThrottle. I tried to reuse the filter buttons to find my 2 missing turnouts and lost them all! Now all I have is 'User TO' which if selected gives me a numeric keypad 0-9,T,C which does nothing. I have tried all sorts but cannot include any of my turnouts to display on WiThrottle. On the JMRI WiThrottle window they are all there in Sytem Name and User Name columns. On the end of my list is a Sytem name XT1017 which is not one of mine and does not appear in the xml file. This sounds similar to your problem. Fingers crossed for a solution. Rgds Brian |
|
Locked
Re: Issues with Win 10 & PR4
Hi Jay,
You won't get much response with so little information. - Which command station? - Boosters? - What JMRI version? (*) - What Java version? (*) - What does the console log say when things go wrong? - Can youp operate trains? That sort of thing. WIth the proper information this group is remarkable in getting problems solved. Wouter (*) 'LATEST' is NOT a version On 9 March 2018 at 23:18, [email protected] [jmriusers] < jmriusers@...> wrote:
[Non-text portions of this message have been removed] |
|
Locked
Re: Upgrading JMRI from 4.10 to 4.11.3 caused major issue
Duncan took his installation issue offline and I solved it by getting him to temporarily disable his Trend Micro virus protection.
toggle quoted message
Show quoted text
Some antivirus programs automatically reject a new JMRI version for a while and then accept it later. -- Dave in Australia The New England Convention 2018 On 10 Mar 2018, at 2:53 PM, ira_alan@... [jmriusers] <jmriusers@...> wrote: |
|
Locked
Re: Decoder Pro is exceptionally sluggish
I suspect the registry entries would have all been related to the installer.
toggle quoted message
Show quoted text
JMRI runs on multiple platforms (Mac, Linux and Windows). The first two have no concept of a registry, so JMRI doesn't use any registry entries. As long as you've got a clean install of whatever you wanted. I just fixed another user's V4.11.3 installation lockup by getting him to temporarily disable virus protection. -- Dave in Australia The New England Convention 2018 On 10 Mar 2018, at 12:49 PM, Geoff Byman gbrails@... [jmriusers] <jmriusers@...> wrote: |
|
Locked
Re: Lockup of JMRI
The command station locks up, not JMRI.
toggle quoted message
Show quoted text
We have a similar situation sometimes with a decoder "Read All Sheets" and it can be unlocked by power-cycling the NCE command station WITHOUT touching or quitting JMRI. Try that when you get a lockup to see if it frees things up. For a long time we believed the "Read All Sheets" lockup was an NCE command station issue, but we then discovered an as-yet-unresolved circumstance where JMRI can send overlapping CV read commands. So at this stage we could not make a call on your issue. Please try the command station power cycle, report back and then please raise an issue at <> so we have some background information and can get back to you for testing if needed. -- Dave in Australia The New England Convention 2018 On 10 Mar 2018, at 12:38 PM, Ted Smith tfsmith365@... [jmriusers] <jmriusers@...> wrote: |
|
Locked
Re: Upgrading JMRI from 4.10 to 4.11.3 caused major issue
I went to 4.8 directly because I had other issues with 4.10. This worked for me
|
|
Locked
Re: Decoderpro sound issue
Tim,
As a long-time and successful PR3 user, I have two suggestions for you: 1) Don't try to run your Soundtraxx-equipped locos on the PR3's programming track. When you do that, the PR3's firmware sets a CV (CV128, I believe) in the decoder. That puts Digitrax sound decoders into "neutral" so you can run up the sounds without the loco moving. But on Soundtraxx decoders, it kills the sound (as you have discovered). So program them on the program track, and run them on the layout. 2) Throw away the PTB-100 and instead power your PR3 with a good DC power supply in the 16-18VDC range. I use an 18VDC regulated supply with my PR3 and it'll program anything, no booster needed. HTH, Steve "Breezlys" ---In jmriusers@..., <tgallagh@...> wrote : Hello, I I am having a sound issue with decoder pro. I¡¯m using Windows 7, the very latest version of JM all right to go to pro, DigiTrax PR3, & a Ptb100. I¡¯ve tried this with three brand new locomotives. To Walters Proto 2000 and an athearn genesis engine. All three are F7 units. All three also have soundtraxx tsunami decoders. All three had some levels appropriate and adequate one placed on the programming track and up they were powered up. However, when I selected new logo name of the locomotive and put in the address and click save. When I powered up the programming track again the volume level had dropped to almost nothing. This happened with all three engines. Does anyone have any clue as to what¡¯s happening? Am I missing the setting? I open the comprehensive program and page and click the sound page everything was set appropriately. Then I moved the sound levels page and increased the volumes for the locomotive the belt and the horn to 255. Wrote the page, and the same thing, virtually no sound at all. Help... |
Ken Cameron
to navigate to use esc to dismiss