Re: JUst a quick comment on this JMRI and decoder pro

#169439

What is the email address for donations?

Larry

On Wednesday, February 12, 2020, 10:02:40 PM EST, Breezlys via Groups.Io <livinthelife@...> wrote:

On Wed, Feb 12, 2020 at 08:22 PM, John wrote:

Donations are gratefully accepted too, helps to defray cost of hosting JMRI.

John

Here's the link, in case you missed it:

Steve
"Breezlys"
(A grateful long-time JMRI user)

Re: Unable to slow down an Athearn Genesis F7

#169438

Dave try this. Program CV5 to 0 (zero). ?After many hours of trying to program one of these I went on the MRC website and downloaded
instructions #0001922. ?These decoders have limits. ?For CV5 Top Voltage it gives a range 0-63 with the default of 63 but if you read the
Description "Top Voltage. 63=full speed, 0=half of the top speed". So the range should read 0 or 63.

Make sure CV21=0
Use programming on the main.

Hope that works for you, ?Mel

Re: Operations Feature Request #operationspro

#169437

开云体育

Hi Dennis,

I use Manifest Creator with my operations and worked with Dan Foltz to get a format that prints on a half sheet of paper to fit on small clipboards.? Very happy with all the formatting choices it gives me.? There are 4 versions as I recall.? You might want to look at each.

?

The format I use can be seen on page 29 of this PDF:

?

Take care,

Gary Ray

Magalia, CA

?

Show quoted text

From: [email protected] [mailto:[email protected]] On Behalf Of Dennis Drury
Sent: Thursday, February 13, 2020 7:38 AM
To: [email protected]
Subject: Re: [jmriusers] Operations Feature Request #operationspro

?

Hi Phil,

?

Thanks for sending this.? We don't use Manifest Creator in our op sessions but I might download it and give it a try.

Cheers, Dennis Drury
Dayton, NV

The miracle is this: the more we share the more we have.
Leonard Nimoy

?

On Wed, Feb 12, 2020 at 6:37 PM Phil in gorgeous Young Harris via Groups.Io <philabernathy=[email protected]> wrote:

Dennis, I have downloaded the latest Creators version and as a test, used it to make this from my csv file for Train 44 (which was run today in our postponed Op Session).? I had to just edit the preference file to hide the rows I did not want to print.? Here is a plain print version:

"Train Manifest #44 Page - 1 - 2/12/2020 21:06
Train departs Elizabeth Northbound 628 Tons 396 Feet Cars-9 (PULL-9)
TSMRI-L&N Old Line
MANIFEST for Train #44
Train departs Tate Northbound 603 Tons 352 Feet Cars-8 (DROP-1)
Train departs Ellijay Northbound 453 Tons 264 Feet Cars-6 (DROP-2)
Train departs Murphy Junction Northbound 252 Tons 176 Feet Cars-4 (PULL-1) (DROP-4)
Train departs Blue Ridge Northbound 531 Tons 308 Feet Cars-7 (PULL-4) (DROP-3)
Train departs Copperhill Northbound 0 Tons 0 Feet Cars-0 (DROP-4)
Train terminates at North Etowah
Created with MC3-4JMRI Version 6.02 06/23/19"

Since I do not use locos on my Operations, no loco information was available to print and I wanted to see how little I would need to change to get what I wanted. So, I did not go into the Visual Basic Code that drives this output from the csv file (other than to comment out a feature for tinting that my Excel 2000 did not like).? I also now see that I inadvertently deleted the departure time, but that may be in the preferences and should be easy to include.

This summary uses the csv file that uses the JMRI Car's information for length and adds it up.? I do not know but would assume that locos also have that kind of information, along with cabeese so an estimated length and tonnage can be calculated and printed by the program (although tonnage may not be needed for Dispatching since assigning motive power is probably not in that position's purview).

Do you use the Creators for Op Sessions?? I find that the improved formatting, straight columns, use of colors and cell lines make for an easier to use and to verify Manifest (and Switchlist for the Yard Crew).?? I have modified mine (the VBA as well as the preferences) to get a more tailored report, but there are several report formats available.? If you do use the Creators, this summary report/Manifest is the result of merely using "Hide" for rows that I don't want to see on the printout.? I hid the following rows: 17 (Header), 37 (Train Originates), 38 (Train Departs), 42 (Hold), 44 (Scheduled work for), 46 (Move), 49 (No work for; although I am torn on that), 50 (Pull) and 58 (Drop). I also left justified (rather than center justify) row 66 (Train departs) and row 75 (Train terminates).?? In our Op Session today, we did look up a train on the summaries I printed to see if it would be able to clear the main without fouling the end of a wye (and it did).

May be too much information, but thinking a little different has often worked for me.? Hopefully something along these lines will work.

Phil in gorgeous Young Harris, Georgia, USA

Re: Problem seeing all of the panel - can't scroll down

#169436

Opened it up on the connected layout, did the zoom to fit and now I can scroll around and get to all of it (and resize it). That? fixed it (there's probably still an issue in the code though).

Scott

Re: Problem seeing all of the panel - can't scroll down

#169435

Did that, but I see no change in the panel (still can't scroll down). But now I can zoom out and see it! Perhaps that gives a work-around. That was with current code. I'll try on the real railroad with 4.19.3.

Scott

Re: Getting started with Dispatcher - getting an NPE when creating a new Train #dispatcher

#169434

That was the Dispatcher Options that fixed it! It's now working. I fixed the options (and updated to 4.19.3) and was able to run around the railroad. Now I have some signal masts to debug.

Thanks all!

Scott Walton

Re: Panel behavior beginning with 4.19.2 - can't see all of the panel

#169433

Bob,

JMRI issue #8126 has been created.

Dave Sand

Show quoted text

----- Original message -----
From: Dave Sand <ds@...>
To: "[email protected]" <[email protected]>
Subject: Re: [jmriusers] Panel behavior beginning with 4.19.2 - can't see all of the panel
Date: Thursday, February 13, 2020 1:06 AM

Bob,

It is a layout editor panel.  I have a clue as to what is happening but more research is required.

Dave Sand

----- Original message -----
From: Bob Jacobsen <rgj1927@...>
To: [email protected]
Subject: Re: [jmriusers] Panel behavior beginning with 4.19.2 - can't see all of the panel
Date: Wednesday, February 12, 2020 9:25 PM

Which kind of panel?

On Feb 6, 2020, at 5:22 AM, Scott Walton <jscottwalton@...> wrote:

Starting with 4.19.2 (it wasn't a problem in 4.19.1), I can't see the bottom of my panels, and I can't zoom out, nor scroll down. This is also present in current code (as of 8:15 AM, EST). The environment is Windows (both 8 and 10), Java 1.8.0_231, Digitrax, both with DCS 100 and standalone with Loconet simulator. It could be something I'm doing, but most likely not, since the behavior changed between 4.19.1 and 4.19.2

Scott Walton
--
Bob Jacobsen
rgj1927@...

Re: Problem seeing all of the panel - can't scroll down

#169432

Scott,

JMRI issue #8126 has been created.

Dave Sand

Show quoted text

----- Original message -----

From: Dave Sand <ds@...>

To: "[email protected]" <[email protected]>

Subject: Re: [jmriusers] Problem seeing all of the panel - can't scroll down

Date: Thursday, February 13, 2020 9:15 AM

Scott,

Try putting a sensor icon(select any sensor) near the upper left corner of the panel and then move it to the upper left grid box. ?The move is important.

When you right click the icon, the context menu should show a "Set Location" of x:0, y:0.

Dave Sand

----- Original message -----

From: Scott Walton <jscottwalton@...>

To: [email protected]

Subject: [jmriusers] Problem seeing all of the panel - can't scroll down

Date: Thursday, February 13, 2020 1:51 AM

The panel ("Pennsy West Main") can be found in the ProblemsBeingWorkedOn, in the Scott_Walton folder. The environment is Windows, JMRI 4.19.2 (and current code), Java 1.8_181, Digitrax or LocoNet Simulator. The problem did not exist in JMRI 4.19.1. The issue is that this panel extends down (there is a loop coming off the main section across the top). Though the panel extends down, even when I "Zoom to Fit", I can't scroll down to see the rest of the panel. This is a problem because there is a tournout there and I can't set the turnout except through the turnout table.

Scott Walton

Re: Operations Feature Request #operationspro

#169431

Hi Phil,

Thanks for sending this.? We don't use Manifest Creator in our op sessions but I might download it and give it a try.

Cheers, Dennis Drury
Dayton, NV

The miracle is this: the more we share the more we have.
Leonard Nimoy

On Wed, Feb 12, 2020 at 6:37 PM Phil in gorgeous Young Harris via Groups.Io <philabernathy=[email protected]> wrote:

Show quoted text

Dennis, I have downloaded the latest Creators version and as a test, used it to make this from my csv file for Train 44 (which was run today in our postponed Op Session).? I had to just edit the preference file to hide the rows I did not want to print.? Here is a plain print version:

"Train Manifest #44 Page - 1 - 2/12/2020 21:06
Train departs Elizabeth Northbound 628 Tons 396 Feet Cars-9 (PULL-9)
TSMRI-L&N Old Line
MANIFEST for Train #44
Train departs Tate Northbound 603 Tons 352 Feet Cars-8 (DROP-1)
Train departs Ellijay Northbound 453 Tons 264 Feet Cars-6 (DROP-2)
Train departs Murphy Junction Northbound 252 Tons 176 Feet Cars-4 (PULL-1) (DROP-4)
Train departs Blue Ridge Northbound 531 Tons 308 Feet Cars-7 (PULL-4) (DROP-3)
Train departs Copperhill Northbound 0 Tons 0 Feet Cars-0 (DROP-4)
Train terminates at North Etowah
Created with MC3-4JMRI Version 6.02 06/23/19"

Since I do not use locos on my Operations, no loco information was available to print and I wanted to see how little I would need to change to get what I wanted. So, I did not go into the Visual Basic Code that drives this output from the csv file (other than to comment out a feature for tinting that my Excel 2000 did not like).? I also now see that I inadvertently deleted the departure time, but that may be in the preferences and should be easy to include.

This summary uses the csv file that uses the JMRI Car's information for length and adds it up.? I do not know but would assume that locos also have that kind of information, along with cabeese so an estimated length and tonnage can be calculated and printed by the program (although tonnage may not be needed for Dispatching since assigning motive power is probably not in that position's purview).

Do you use the Creators for Op Sessions?? I find that the improved formatting, straight columns, use of colors and cell lines make for an easier to use and to verify Manifest (and Switchlist for the Yard Crew).?? I have modified mine (the VBA as well as the preferences) to get a more tailored report, but there are several report formats available.? If you do use the Creators, this summary report/Manifest is the result of merely using "Hide" for rows that I don't want to see on the printout.? I hid the following rows: 17 (Header), 37 (Train Originates), 38 (Train Departs), 42 (Hold), 44 (Scheduled work for), 46 (Move), 49 (No work for; although I am torn on that), 50 (Pull) and 58 (Drop). I also left justified (rather than center justify) row 66 (Train departs) and row 75 (Train terminates).?? In our Op Session today, we did look up a train on the summaries I printed to see if it would be able to clear the main without fouling the end of a wye (and it did).

May be too much information, but thinking a little different has often worked for me.? Hopefully something along these lines will work.

Phil in gorgeous Young Harris, Georgia, USA

Re: Unable to slow down an Athearn Genuseesis F7

#169430

开云体育

Dave,

?

Perhaps this decoder requires 28 speed-step operation for speed table use.? This was very common with early decoders.

?

IIRC, your DCC system is Digitrax; try ‘Status Editing” the address for 28 speed-step operation and see if you can control the top speed with appropriate CV settings.

?

HTH

Ross

?

Show quoted text

From: [email protected] <[email protected]> On Behalf Of inspectordave
Sent: Thursday, February 13, 2020 9:29 AM
To: [email protected]
Subject: [jmriusers] Unable to slow down an Athearn Genesis F7

?

Has anybody had any luck trying to slow down an Athearn Genesis F7 with a MRC dual mode decoder? I can read the model number, 31, but there are no 31's listed in DecoderPro for an MRC decoder. I can program any and everything else but I cannot slow it down. This unit does warp 8 with full throttle. Any suggestions are welcome and thanks.

Later

Dave
Trempealeau WI.

Re: Problem seeing all of the panel - can't scroll down

#169429

Scott,

Try putting a sensor icon(select any sensor) near the upper left corner of the panel and then move it to the upper left grid box. ?The move is important.

When you right click the icon, the context menu should show a "Set Location" of x:0, y:0.

Dave Sand

Show quoted text

----- Original message -----

From: Scott Walton <jscottwalton@...>

To: [email protected]

Subject: [jmriusers] Problem seeing all of the panel - can't scroll down

Date: Thursday, February 13, 2020 1:51 AM

The panel ("Pennsy West Main") can be found in the ProblemsBeingWorkedOn, in the Scott_Walton folder. The environment is Windows, JMRI 4.19.2 (and current code), Java 1.8_181, Digitrax or LocoNet Simulator. The problem did not exist in JMRI 4.19.1. The issue is that this panel extends down (there is a loop coming off the main section across the top). Though the panel extends down, even when I "Zoom to Fit", I can't scroll down to see the rest of the panel. This is a problem because there is a tournout there and I can't set the turnout except through the turnout table.

Scott Walton

Unable to slow down an Athearn Genesis F7

#169428

Has anybody had any luck trying to slow down an Athearn Genesis F7 with a MRC dual mode decoder? I can read the model number, 31, but there are no 31's listed in DecoderPro for an MRC decoder. I can program any and everything else but I cannot slow it down. This unit does warp 8 with full throttle. Any suggestions are welcome and thanks.

Later

Dave
Trempealeau WI.

Re: Getting started with Dispatcher - getting an NPE when creating a new Train #dispatcher

#169427

Scott,
Do you have "SignalHeads/SSL" or "SignalMasts" selected in your Dispatcher Options panel?
I would think you want "SignalMasts", but that crash is coming from code related to "SignalHeads".
--SteveT

Re: LCC Buffer in Linux

#169426

Guys:?
Without doing the chmod 666 /dev/ttyUSB0,? JMRI would error out on start up with "/dev/ttyUSB0 is already in use".?? There was no lock files in /var/log either.

I'll run the two scenarios tonight with and without the chmod, with restarts after each, and send the necessary system logs.?? I understand and appreciate what you have said about persistence across reboots, but that was the only thing that would allow JMRI to run.?? This was a plain vanilla new install of Mint, the connection is Digitrax/DB150 using Loconet-Locobuffer II for the USB-Serial connection.

I also offer to assist in the updating of the Ubuntu install pages (which could be renamed:? Debian based Linux Install pages). There are so many Ubuntu derivative distros out there that the renaming might be appropriate.??

Bob

Problem seeing all of the panel - can't scroll down

#169425

The panel ("Pennsy West Main") can be found in the ProblemsBeingWorkedOn, in the Scott_Walton folder. The environment is Windows, JMRI 4.19.2 (and current code), Java 1.8_181, Digitrax or LocoNet Simulator. The problem did not exist in JMRI 4.19.1. The issue is that this panel extends down (there is a loop coming off the main section across the top). Though the panel extends down, even when I "Zoom to Fit", I can't scroll down to see the rest of the panel. This is a problem because there is a tournout there and I can't set the turnout except through the turnout table.

Scott Walton

Re: Getting started with Dispatcher - getting an NPE when creating a new Train #dispatcher

#169424

I'll try again on the real railroad -- I tried it on a different machine (with the current JMRI code) with LocoNet Simulator and can run the trains (using the AutoActiveTrainsSimulator script). It (and most of my transits) run fine there. It's either Dispatcher options, or something about the way the signals are setting.

Scott

Re: track lineup in staging #operationspro

#169423

Hey Dan,
In my staging town my tracks are as follows, track 01, track 02 and so on till track 99. So if I manually pick my tracks they should line up and stay that way or will that be too much to ask for? The first time I built my database the tracks lined up this must have been a fluke. I was backing up my database to my computer now it is backed up to a thumb drive. I had a massive computer failure I luckily had a paper copy of my car list been working on the rebuild for three years ?and getting close to done. I am trying a few things new that I didn't the first time.
Matt Greenwood
Cascade Rwy

Re: Panel behavior beginning with 4.19.2 - can't see all of the panel

#169422

Bob,

It is a layout editor panel.  I have a clue as to what is happening but more research is required.

Dave Sand

Show quoted text

----- Original message -----
From: Bob Jacobsen <rgj1927@...>
To: [email protected]
Subject: Re: [jmriusers] Panel behavior beginning with 4.19.2 - can't see all of the panel
Date: Wednesday, February 12, 2020 9:25 PM

Which kind of panel?

On Feb 6, 2020, at 5:22 AM, Scott Walton <jscottwalton@...> wrote:

Starting with 4.19.2 (it wasn't a problem in 4.19.1), I can't see the bottom of my panels, and I can't zoom out, nor scroll down. This is also present in current code (as of 8:15 AM, EST). The environment is Windows (both 8 and 10), Java 1.8.0_231, Digitrax, both with DCS 100 and standalone with Loconet simulator. It could be something I'm doing, but most likely not, since the behavior changed between 4.19.1 and 4.19.2

Scott Walton
--
Bob Jacobsen
rgj1927@...

Re: Getting started with Dispatcher - getting an NPE when creating a new Train #dispatcher

#169421

The Transit that gave me the error was B24_Loop. I've also uploaded the script to the same folder ("crossing_signals.py").

Scott Walton

Test version 4.19.3 of JMRI/DecoderPro is available for download

#169420

Test version 4.19.3 of JMRI/DecoderPro is available for download.

This is the next in a series of test releases that will culminate in a production release, hopefully in early summer 2020. It’s really helpful when people download, install and use these test versions so we can find and fix any inadvertent new problems early.

If you are currently using JMRI 4.9.6 or earlier, we strongly recommend that you first update to JMRI 4.12 and make sure that's running OK before updating to this test release. There have been a number of changes in serial port support, panel file format and configuration options since those earlier releases, and moving to the stable JMRI 4.12 release is a good way to work through any possible problems.
<>

If you use JMRI on Linux or Mac and are updating from JMRI 4.7.3 or earlier, there’s a necessary migration step. (Not needed on Windows) Please see the JMRI 4.12 release note for details: <>

For more information on the issues, new features and bug fixes in 4.19.3 please see the release note:   
<>

Note that JMRI is made available under the GNU General Public License. For more information, please see our copyright and licensing page.
<>

The download links, along with lots of other information which we hope you'll read, can be found on the release note page:
<>

--
Bob Jacobsen
rgj1927@...