Locked
Re: Decoder pro version
On Sat, Jan 5, 2019 at 07:32 PM, James LeFevre wrote:
I just went to source forge. All versions are listed. I do not see anything
about any version being recommended over any other.
Jim
Version 4.10 was listed on the Jmri.sourceforge.net main page as current, the download page is correct. I'm sure Bob will correct. -- Peter Ulvestad JMRI Users Group Moderator - ( ) Tam Valley Group Moderator - ( ) Sprog-DCC Group Moderator - ( ) Edmonton Model Railroad Association -
|
Thank you all. I have always gone to sourceforge as someone mentioned. I will go to jmri.org. I figured it was something like a new website...great responsiveness in the group...and kind.?
Mike Shockley?
|
Locked
Re: Decoder pro version
I just went to source forge. All versions are listed. I do not see anything about any version being recommended over any other.
Jim
toggle quoted message
Show quoted text
On Jan 5, 2019, at 19:41, Tom Wilson < thomasthetrainengine@...> wrote: Bob,
is still up and alive and showing 4.10 as current production version.
I saw that posted a few days ago on another forum.
Tom Wilson
Colorado Springs, CO On Sat, Jan 5, 2019, 6:03 PM Bob Jacobsen < rgj1927@... wrote: As Peter mentions, 4.14 is current and available at
If you¡¯re seeing an earlier version at some URL, could you let me know where?? I¡¯d like to get that fixed.
Bob
> On Jan 5, 2019, at 1:22 PM, Michael Shockley via Groups.Io <docshock31=[email protected]> wrote:
>
> I am using decoder pro 4.10xxxx. The website says that is the current production version.? Some people tell me they are using 4.14xxx as a production release.
> My concern is the my new locomotive isn¡¯t listed as a choice¡ªTsunami2 OEM Athearn Genesis. I think the list is GP7 and GP38-2. I have an SD60E.
> Just trying to understand.
--
Bob Jacobsen
rgj1927@...
|
Locked
Re: Running JMRI From A MacBook Pro
Sort of going backwards now....
The name of my CU. connection is, as I said earlier, 'cu.usbserial-A9KJ71D9'. The 'A9KJ71D9' is thr serial number of that device.
I upgraded my JMRI to 4.14, replacing the earlier?installation?completely. ?I tried to set up a connection but I get this error message...
Unable to create connection 'MRC' (M)
Serial port cu.usbserial-A9KJ71D9 is in use.
System connection MRC provides a null manager for interface jmri.ThrottleManager.
Unable to run startup features becuase of earlier errors.
Please?check the logs for more details.
|
Locked
Re: Decoder pro version
Bob,
is still up and alive and showing 4.10 as current production version.
I saw that posted a few days ago on another forum.
Tom Wilson
Colorado Springs, CO
On Sat, Jan 5, 2019, 6:03 PM Bob Jacobsen < rgj1927@... wrote: As Peter mentions, 4.14 is current and available at
If you¡¯re seeing an earlier version at some URL, could you let me know where?? I¡¯d like to get that fixed.
Bob
> On Jan 5, 2019, at 1:22 PM, Michael Shockley via Groups.Io <docshock31=[email protected]> wrote:
>
> I am using decoder pro 4.10xxxx. The website says that is the current production version.? Some people tell me they are using 4.14xxx as a production release.
> My concern is the my new locomotive isn¡¯t listed as a choice¡ªTsunami2 OEM Athearn Genesis. I think the list is GP7 and GP38-2. I have an SD60E.
> Just trying to understand.
--
Bob Jacobsen
rgj1927@...
|
Locked
Re: Another new user with Mac to MRC Prodigy issues
On 6 Jan 2019, at 12:02 PM, David S <docdata3d@...> wrote:
Loaded the FTDI USB drivers and tried again.
Found an instance of this error message for each time I tried to start DecoderPro. No error message were displayed on screen.
2019-01-05 19:54:31,524 ptionhandler.UncaughtExceptionHandler ERROR - Uncaught Exception caught by jmri.util.exceptionhandler.UncaughtExceptionHandler [AWT-EventQueue-0]
java.lang.NullPointerException: Required nonnull default for jmri.ThrottleManager does not exist. Go to Preferences->Defaults and make sure everything is set to MRC and nothing to Internal. Also please make sure you are running JMRI V4.14 or V4.15.1 or the "Internal" problems may occur again in the future. Dave in Australia
|
Locked
Re: Running JMRI From A MacBook Pro
I have a 'cu.usbserial-A9KJ71D9' and this is a selection in the 'serial port' option for a connection setup.
Still nothing.
|
Locked
Re: Decoder pro version
As Peter mentions, 4.14 is current and available at If you¡¯re seeing an earlier version at some URL, could you let me know where? I¡¯d like to get that fixed. Bob On Jan 5, 2019, at 1:22 PM, Michael Shockley via Groups.Io <docshock31@...> wrote:
I am using decoder pro 4.10xxxx. The website says that is the current production version. Some people tell me they are using 4.14xxx as a production release.
My concern is the my new locomotive isn¡¯t listed as a choice¡ªTsunami2 OEM Athearn Genesis. I think the list is GP7 and GP38-2. I have an SD60E.
Just trying to understand. -- Bob Jacobsen rgj1927@...
|
Locked
Re: Another new user with Mac to MRC Prodigy issues
Loaded the FTDI USB drivers and tried again. Found an instance of this error message for each time I tried to start DecoderPro. ?No error message were displayed on screen. ?
2019-01-05 19:54:31,524 ptionhandler.UncaughtExceptionHandler ERROR - Uncaught Exception caught by jmri.util.exceptionhandler.UncaughtExceptionHandler [AWT-EventQueue-0]
java.lang.NullPointerException: Required nonnull default for jmri.ThrottleManager does not exist.
Dave S
|
Locked
Re: Unable to use power button on JMRI throttle
On 6 Jan 2019, at 11:14 AM, Ken Cameron <kcameron@...> wrote:
I just took a look and the PowerCab doesn't have the concept of track power
being on/off. At least the notes I have don't identify any command for track
power. If that is true, JMRI shouldn't even bother you with the option of an
on/off if it can't work. But I'd want somebody else to verify this. The NCE DCC systems don't actually support Power OFF/ON commands: - With the Power Pro system we fudge it by using the ENTER PROG TRACK MODE and EXIT PROG TRACK MODE commands. This works with the Power Pro because there are two outputs (Track and Program Track) and one or other is always active (but never both at the same time). - The Power Cab system has a single shared output and it is never off. ENTER PROG TRACK MODE switches it to power-limited mode. EXIT PROG TRACK MODE switches it to full power mode. So we can't use the fudge above. Dave in Australia
|
Locked
Re: Digitrax PR4 Stand Alone Programming Track Issues
Congratulations Steve, glad to hear it. Maybe you can help my friend John Umberger, also posting in this thread, to get his PR4 to work. We have tried everything, we tjink. Maybe you can point out something that we missed.
Stefan
--
Stefan Bartelski
Home layout: The Blue Ridge Line, an HO representation of the L&N Etowah Old Line from Etowah to Elizabeth, set in 1986 9under construction)
Modular Layout: Shoofly module of the Country RRoads Modular group
|
Locked
Re: Digitrax PR4 Stand Alone Programming Track Issues
Marc,
I am using a DCS 200.
John
|
Locked
Re: Decoder pro version
Guys
The update window that I use shows ALL production versions and
ALL test versions. Shown down the left side of screen.
Gerry
On 6/01/2019 11:12 am, Ken Cameron
wrote:
Mike S,
What website was saying 4.10.xxx as the current JMRI version?
Jmri.org is the official site for JMRI. And right now, 4.14 is the official
production version. We've already started on the next set and 4.15.1 is the
first of those development versions.
-Ken Cameron, Member JMRI Dev Team
--
Gerry Hopkins MMR #177 FNMRA
Great Northern Downunder
NMRA Australasian Region
Contest & AP Chairman
Web Administrator
|
Locked
Re: Running JMRI From A MacBook Pro
Hi Steve,
Am I OK to copy / paste your advice for use on the JMRI MERG CBUS Hardware Support page?
I'm presuming a CANUSB4?
Thanks,
Steve.
|
Locked
Re: Unable to use power button on JMRI throttle
I just took a look and the PowerCab doesn't have the concept of track power
being on/off. At least the notes I have don't identify any command for track
power. If that is true, JMRI shouldn't even bother you with the option of an
on/off if it can't work. But I'd want somebody else to verify this.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org
|
Locked
Re: Decoder pro version
Mike S,
What website was saying 4.10.xxx as the current JMRI version?
Jmri.org is the official site for JMRI. And right now, 4.14 is the official
production version. We've already started on the next set and 4.15.1 is the
first of those development versions.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org
|
Locked
Re: Digitrax PR4 Stand Alone Programming Track Issues
On Sat, Jan 5, 2019 at 03:35 PM, Marc wrote:
The PR3 /PR4? were made for DIGITRAX decoders..They were not developed with ALL decoders in mind.
While that may be true for the PR3 (I haven't checked, and I have no inclination to do so), it certainly isn't true for the PR4. Direct from the PR4 product page on the Digitrax Web site: <quote> Programs CV¡¯s for most DCC decoders. </quote> Not most Digitrax decoders... Not most non-sound decoders... Just..."most DCC decoders". Source: Steve "Breezlys"
|
Locked
Re: Running JMRI From A MacBook Pro
On 6 Jan 2019, at 10:28 AM, David S <docdata3d@...> wrote:
Can you provide the link(s) for this driver? <> Irrespective of DCC system, there are some basic rules for troubleshooting any USB-attached device to a Mac. Plug your device into your Mac. Go to "System Information" from Apple Menu->About This Mac->More Info->System information. Look in the USB section, expand all sections under controllers and hubs and see what devices are present. Unplug your device, select Refresh from the System Information menus and see what device has disappeared. Plug your device back in, refresh again and see what reappears. Repeat until you see what is changing. If there is no change, there must be a hardware problem external to your Mac, such as a faulty USB cable, connector or device and there is no point going any further until your Mac can see the physical device. Once you have seen the device in System Information, (it should report the Manufacturer name so you know where to go to get drivers) you will quite likely have to install Mac drivers for it (although some do not need extra drivers, see your documentation). If unsure, try the next step anyway. In High Sierra and above, you must open System Preferences->Privacy and Security and allow the kernel extensions (drivers) you installed to be loaded, or they will not be used. Unplug your device. Open a window of the Terminal utility (from /Applications/Utilities), copy and paste the following command in EXACTLY (including spaces and punctuation) then press Enter. while : ;do clear;ls -lt /dev|head;i=$((i+1));echo $i;sleep 1;done This command should show about 10 lines of output and then sit looping, with a counter incrementing every second. Plug your device back in and wait a few seconds. Two new items with names like cu.xxx and tty.xxx should appear in the list. They should disappear if you unplug your device. If this does not happen, you do not have the correct drivers installed for your device and you will need to solve that before proceeding further. Once you have found your device, write down the name you see.You want the cu.xxx version not the tty.xxx version. If you have got this far you know your device is be being seen by the Mac, that it has a matching driver installed and the name of the connection port "cu.xxx" you need to select in JMRI. If you cannot get this far, there's no way JMRI can find your device until the driver issue is resolved. Dave in Australia
|
Locked
Re: Digitrax PR4 Stand Alone Programming Track Issues
On Sat, Jan 5, 2019 at 01:26 PM, Stefan ` Bartelski wrote:
There are some who claim that it DOES work, although I suspect they may be using it in the connected mode and programming through a DCS base station.
Yeah, I'm one of those who claims the PR4 works, because mine Just Does. And no, I don't use it in "connected mode" through a command station for programming. As a matter of fact, the programming outputs on my DCS100 haven't been connected to anything since back when the PR3 was first introduced. I have two JMRI profiles. My preferences are set so Decoder Pro launches using the profile with the PR4 as a stand-alone programmer, and Panel Pro launches using the profile with the PR4 as a LocoNet pass-thru device. So depending on what task I want to do, I just launch one or the other as appropriate, and away I go. Oh, and as far as all the gibberish about needing a different power supply with the PR4 - That's one (of several) of the differences between it and the PR3. Using only the included PS14, my PR4 easily and reliably reads and writes CV's to Tsunami's, Tsunami 2's, Econami's, Sound Value's, TCS WOW (V3 and V4), Soundtraxx LC's, ESU Loksound, and of course Digitrax sound decoders. And it does it a lot faster than my PR3 (powered by an 18VDC regulated supply) ever did! Steve "Breezlys"? ?
|
Don W,
If you are building panels using Internal devices because you don't know
which real system you will use, then assigning 'usernames' to each item will
save you a lot of effort later. If all the panels use the usernames from the
tables (for turnouts and sensors) then later when you start getting real
hardware, there is a step to 'move' the username from one systemName to
another. All the places using the username won't notice the change. Keep in
mind that many panels do have logical things that use Internal for their
system. These are virtual items sometimes used in control panels or
maintaining logic states.
Now the normal default for a CMRI connection is 'C', EasyDCC seems to user
'E'.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org
|
Peter Ulvestad
Michael Shockley
Bob Jacobsen
Ken Cameron