开云体育

Barry,

You sure of that last date? I recall traffic in January on CATS. Yahoo
doesn't keep track anymore, but is still a list server.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org

Thanks Tony,

That’s good to know, However, the loco I have is a recently purchased new Hornby 4-4-0 that came with an 8 pin socket, but my decoder is an old Arnold/Rivarossi unit (mfr #173, version #021) which I seem to recall was actually made for them by Lenz. My NCE was able to read the decoder info and also read back the decoders short address during the programming process, my SPROG3/DecoderPro setup could not. You may be right about not being able to use a long address with this decoder, it is very old. I got two of them back in 2005 when I was working for Model Expo, who was the US distributor for Rivarossi & Arnold at the time, and the decoder wasn’t a recent release even then. I also got the NCE/TTX DH102EU decoder at about the same time, it was made for Tony’s Trains by NCE. They all had 8 pin plug & play plugs attached from the factory, and as soon as I can find the box containing most of my HO locos I will have my Atlas DCC-ready U36c chassis that I used for a DCC testbed, so I'll be able to experiment more with the two remaining decoders, which I am sure were working when they were put in the spare parts box. I got my first DCC system (an original Digitrax Challenger - I still have it) back in 1993 and also still have a few locos with decoders from that era. Decoders have come a long way since then and have gotten a lot less expensive as well, those old very basic decoders sold for $40-$50 at the time!

Thanks,
Bill in FtL?

I am no JMRI expert but have spent a lot of time on the site. ?The ethos here is you must demonstrate you have spent time trying to resolve your issue by (a) exploring the site and (b) describing how you used the knowledge acquired to attempt to resolve your issue. Just announcing a problem won't get you responses. Personally I find that Googling with"JMRI" and the specific issue in my search string gets me to the pertinent parts of this site the fastest. ?Look for hits referencing the JRMI site.?

THANK YOU. EXCELLENT. I am going to try it this coming week.?

Hi All,

I think I have it working now ...
No need for any action ...

Hi All,

I have created a panel in PanelPro layout editor.

I have placed it in the problem files area DaveS directory.

I am finding that some of the signal masts? have the 'Active' box unchecked?when I look at the mast's signal logic in the panel.

These masts just sit at red.

If I delete the logic for that mast and use Discover to recreate it?- the mast logic is then shown as active and the mast functions correctly.
But next time I open Panelpro the mast is again not active.

Can anyone help me to resolve this problem please.

Panelpro is 4.12. Java is 1.8.0_221

Many Thanks

Dave

Thanks George, looks good.
Andy

Bill,

On 2 Feb 2020, at 3:22 PM, Bill Nielsen <wrangler@...> wrote:

Thanks for the reply. I didn’t realize that having two engines on the track would disable the programming attempt,

It doesn't disable "programming attempts". It disables "program track reads". Huge difference.

I thought that more than one engine on the program track would reprogram them all.

That is correct, as far as "program track writes" are concerned. Both NCE and SPROG do "blind writes" - they don't listen while writing and don't care what happens on the track.

Having more than one loco on the program track when doing "program track reads" is like asking a group of people a question and having them all reply equally loudly at the same time. The result is you hear nothing intelligible.

but realistically, the Hornby loco, even though brand new, is still pretty old tech with its ringfield motor & tender drive, so I’m not sure it would be worth the expense of the latest decoder version.

If it's that old with a ringfield motor it's highly likely to have "suppressors" across the motor and/and/or in the track leads and that may be the problem.

I’m pretty sure my problem is not the the DP is too old to see the decoders, probably more likely that the decoders are what’s too old! It’s good to know that the Asus convertible should still work with the newer DecoderPro, since I really like that little computer, though I don’t much care for Windows. I thought I had read that the Java version on it was too old for the newer DP.

All Windows versions back to XP are capable of having a Java version that runs the latest JMRI.

(nstalling the correct Java version for XP is messy, but quite possible
<>

The HP/“HackIntosh” Netbook uses an early version of Mac OSX that was current right after Apple switched over away from Motorola chips, It uses a third party software to allow the HP Netbook to run an Apple OS, a door which Apple closed pretty quickly.

You don't need to be secretive about macOS versions here. Many of the developers speak Mac. DecoderPro and JMRI started life on Mac and still is the platform of choice for many of the developers.

It figures that the DecoderPro V2 graphics would be obsolete, that’s the one I’m more comfortable using!

You can actually make DecoderPro V3 and V4 look like V2 if you really want to!

Dave in Australia

Hi Dave,

Thanks for the reply. I didn’t realize that having two engines on the track would disable the programming attempt, I thought that more than one engine on the program track would reprogram them all. I am using DecoderPro with the SPROG3, the NCE PowerCab is my stand alone System. The program/test track is setup using Kato’s UniTrack and also uses their mini Molex connectors, so I can easily swap between DP/SPROG3, the PowerCab, or even an analog MRC 9500. Both of the decoders in question are quite old (I think I’ve had them for going on 15 years now), and the NCE PowerCab System was able to see, read, and write to at least the Arnold/Rivarossi decoder after a while. I’m pretty sure it’ll be the same with the NCE/TTX decoder too, but I haven’t tried yet because I had gotten sidetracked trying to get DecoderPro to work. Like I said, they are the only decoders I had on hand that were thin enough to fit in the loco, All my other on-hand decoders are too thick to fit, mostly because they all have JST connectors and shrink wrap, which makes them just a bit too thick. Since the engine in question has no lighting, there’s no need for the extra functions found on newer decoders. I would like to have a better motor control with bemf, and possibly an anti-stall capacitor, but realistically, the Hornby loco, even though brand new, is still pretty old tech with its ringfield motor & tender drive, so I’m not sure it would be worth the expense of the latest decoder version.

I’m pretty sure my problem is not the the DP is too old to see the decoders, probably more likely that the decoders are what’s too old! It’s good to know that the Asus convertible should still work with the newer DecoderPro, since I really like that little computer, though I don’t much care for Windows. I thought I had read that the Java version on it was too old for the newer DP. The HP/“HackIntosh” Netbook uses an early version of Mac OSX that was current right after Apple switched over away from Motorola chips, It uses a third party software to allow the HP Netbook to run an Apple OS, a door which Apple closed pretty quickly. My limited computer experience has been limited to mostly Apple, but I really liked the size of the HP Netbook. The software conversion was done for me by a guy in the IT department at the university where my wife worked. At the time, he said that he had converted a lot of MS computers over to the Mac OS, because Macs were very popular with both instructors and students at the school, but by then, Apple had made any future upgrades to their OS running on a PC impossible. It figures that the DecoderPro V2 graphics would be obsolete, that’s the one I’m more comfortable using!

Thanks,
Bill in FtL

There was a Yahoo Group called CATS-users@... The last message was late November, and Yahoo now has deleted all user messages as of December 14. So it would appear the only place to request help on the CATS software is here on the JMRI group, if the owners will permit such off-topic threads. Not sure if CATS is still available or being developed. Would be sad to lose it.

Barry Draper

________________________________________
From: [email protected] <[email protected]> on behalf of Ken Cameron <kcameron@...>
Sent: Saturday, February 1, 2020 6:37 AM
To: [email protected]
Subject: Re: [jmriusers] CATS: Where is new CATS Group? Was Moving objects on the designer panel #cats

AFAIK, there is still the CATS group on Yahoo. It didn't make the move that
I remember.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org

If SoundLoader is working, try to make sure that JMRI is using the same
settings (Port). Make sure you try exiting SoundLoader and restarting it
too. If the issue is down at the driver level, that would also hang.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org

Bill,

On 2 Feb 2020, at 11:33 AM, Bill Nielsen <wrangler@...> wrote:

i have been using DecoderPro for programming my DCC loco decoders (in all scales) for several years now, because the graphic interface is a lot easier to operate the trying to do programming adjustments with my NCE PowerCab. Recently however, I have come up against an issue that has me stumped trying to program a Hornby 4-4-0. Because this loco has an eight pin NMRA socket, but is also a tender-drive model, there is very little space inside the tender for a decoder. In fact, the only decoders I have on hand that could fit, both are used and refugees from my spare parts box, one is an Arnold/Rivarossi unit identified as mfg #173, decoder version #021. The other decoder is an old NCE/TTX DH102EU neither of which are able to be seen or communicate with DecoderPro when I try them on the program track.

They'll only be seen if fitted to a loco (or a motor across the motor terminals).

They are possibly defective, or there is a wiring problem in the loco. Quite likely interference suppression components connected to the motor or even the track wiring. They can cause havoc with reading/using decoders.

I have two computers set up with DecoderPro, an old HP Netbook with a Mac OS (a “HackIntosh”) running DecoderPro 2.14,

A very old version of JMRI that won't know about many modern decoders.

What macOS version are you running on the HackIntosh?

and a slightly newer Asus tablet/ notebook convertible running Windows 8 and DecoderPro version 3.

A very old version of JMRI that won't know about many modern decoders.

Windows 8 can certainly run the latest version of JMRI.

Neither computer can see either decoder. Yet, if I put a known working DCC loco (Walthers Plymouth ML8) on the programming track everything works fine as expected.

Good.

If I then add the Hornby loco equipped with the Arnold/Rivarossi decoder to the program track along with the working ML8 loco, all of a sudden DecoderPro can not see either loco.

That's expected. If you have more than one decoder on the program track you won't be able to see either (unless you've implemented CV15/16 decoder locking in both locos and they have different lock keys).

As soon as I remove the Hornby loco, DecoderPro immediately sees the Walthers loco again just fine. It’s as if the Hornby loco isn’t just unable to be seen, it prevents the other loco from being seen as well.

See above.

I was able to set the short address on the Hornby loco using the NCE PowerCab with the instruction book in hand, but it took many attempts before I could get the new address to actually work. For a test, I just today took the loco down to my LHS, where they have a demo layout using an MRC Prodigy Squared System, and using that system, I was able to select the address of the Hornby 4-4-0 and it operated fine.

That doesn't prove that it read the loco.

Since the Hornby loco has no lights, the only feature needed from the decoder is motor control. I realize this is an old decoder, but it is the first time I have had trouble with DecoderPro detecting a loco. My question is, is there something wrong with my DecoderPro, my SPROG 3 interface, computers, decoders or what?

You are confusing me. Is your Program Track (and JMRI) connected to the Power Cab or to a SPROG 3?

I believe the Java on my two computers are probably limiting me to the JMRI versions they are using, and I can’t foresee buying a new laptop and trying to learn how to work the latest version of DecoderPro.

If you have a laptop with Windows 8, that's more than adequate for the latest JMRI version.

I still use Windows 7 and even Windows XP with the latest JMRI.

I have enough trouble trying to figure out the differences between DecoderPro v2 & V3!

Big user-interface changes between DecoderPro V2 and V3. V4 has basically the same user interface as V3.

Dave in Australia

i have been using DecoderPro for programming my DCC loco decoders (in all scales) for several years now, because the graphic interface is a lot easier to operate the trying to do programming adjustments with my NCE PowerCab. Recently however, I have come up against an issue that has me stumped trying to program a Hornby 4-4-0. Because this loco has an eight pin NMRA socket, but is also a tender-drive model, there is very little space inside the tender for a decoder. In fact, the only decoders I have on hand that could fit, both are used and refugees from my spare parts box, one is an Arnold/Rivarossi unit identified as mfg #173, decoder version #021. The other decoder is an old NCE/TTX DH102EU neither of which are able to be seen or communicate with DecoderPro when I try them on the program track. I have two computers set up with DecoderPro, an old HP Netbook with a Mac OS (a “HackIntosh”) running DecoderPro 2.14, and a slightly newer Asus tablet/ notebook convertible running Windows 8 and DecoderPro version 3. Neither computer can see either decoder. Yet, if I put a known working DCC loco (Walthers Plymouth ML8) on the programming track everything works fine as expected. If I then add the Hornby loco equipped with the Arnold/Rivarossi decoder to the program track along with the working ML8 loco, all of a sudden DecoderPro can not see either loco. As soon as I remove the Hornby loco, DecoderPro immediately sees the Walthers loco again just fine. It’s as if the Hornby loco isn’t just unable to be seen, it prevents the other loco from being seen as well. I was able to set the short address on the Hornby loco using the NCE PowerCab with the instruction book in hand, but it took many attempts before I could get the new address to actually work. For a test, ?I just today took the loco down to my LHS, where they have a demo layout using an MRC Prodigy Squared System, and using that system, I was able to select the address of the Hornby 4-4-0 and it operated fine. Since the Hornby loco has no lights, the only feature needed from the decoder is motor control. I realize this is an old decoder, but it is the first time I have had trouble with DecoderPro detecting a loco. My question is, is there something wrong with my DecoderPro, my SPROG 3 interface, computers, decoders or what? I believe the Java on my two computers are probably limiting me to the JMRI versions they are using, and I can’t foresee buying a new laptop and trying to learn how to work the latest version of DecoderPro. I have enough trouble trying to figure out the differences between DecoderPro v2 & V3!

Thanks,
Bill in FtL

Just finished creating and placing signal heads for 10 turnouts, complete with very basic SSL for each head. All turnouts were working properly from the panel and the heads were responding appropriately. I saved the panel from the My Panel window and from the signal head tools/table window. I powered the system down and then returned about 4 hours later and powered up. The signal heads for one turnout were completely missing from the panel and the signal heads for five of the turnouts had lost their respective SSL; the fields in the SSL window for these five turnouts were completely blank.

Every time I power the system I get different results. This current situation is the most annoying due to the work involved. But sometimes the two SE8C boards being used for occ sensors will not boot properly; sometimes the turnouts will not respond to mouse clicks on the panel, and sometimes everything works fine.

I am using a PC with win 8, a Digitrax DCS52, LocoNet, two SE8Cs, and one Azatrax IR MRD8 board. I have tried a PC with win 7. I have tried both JMRI 14 and 18 on each of the PCs with similar results. I have tried using one SE8C instead of two. I have tried with and without the MRD8. The lack of consistantcy is very frustrating.

I must be missing something, but have yet to figure out what. Any ideas?

Thanks,

John

I have joined the group again after a hiatus of a couple of years.? I've still be putzing with JMRI and have progressed (ish).

I am stuck on a couple of things.? I am having trouble with the Palette.? When I pull in signal heads from the Palette, all I get is an "X" on the Panel Editor.? When I try to fix it by editing the icon, I get a warning popping?up that says "Family name 'RJE_SHicon_Searchlight' is the name of a different icon set for SignalHeads in the Catalog.? Please change the name."? This happens even though that is the name of the icon set I pulled from in the Palette.? 'RJE_SHicon_Searchlight' is a name I assigned to the icon set, and when I choose a new name it shows up on the next pop-up along with 'RJE_SHicon_Searchlight' , but it does not show up on the?Palette.

I can go into the Layout xml file and manually correct this to make the signal show up correctly.? I can also copy a signal head in the panel editor and it works fine, put pulling it from the Palette is a problem.? I have mucked around with Layout file (as noted above), and also the? "catalogTrees.xml" file? - probably to the point of no return.

The same thing happens when I start a brand new layout, so I'm guessing it is not in the layout files I have created.

I have obviously screwed up somewhere, but not sure how to fix it.

Any help would be greatly appreciated.

BobE

HI
I got JMRI going onn my laptop with windows 10 and I made a roster but now how do I get connected to my dcc program track to program with decoder pro? I have a new Digitrax DCS Zepher Express connected.
If there is a description somewhere let me know
Thanks?

bill

Larry,

For the timed script you can run it from DP or PP. Using the timed script, you will find the loco drifts one way or the other over time.

Using optical sensors, you need the additional hardware to connect to LocoNet.

--
Peter Ulvestad

JMRI Users Group Moderator - ( )
Tam Valley Group Moderator - ( )
Sprog-DCC Group Moderator - ( )
Edmonton Model Railroad Association -