¿ªÔÆÌåÓý

  1. Jmriusers
  2. Messages
Expanded Topics Messages Polls
Date
Locked Re: Decoder Pro Errors out when Programming Functions on TSU-21PNEM #soundtraxx #tsunami

 

¿ªÔÆÌåÓý

Steve,

On 31 Aug 2019, at 10:03 AM, Breezlys via Groups.Io <livinthelife@...> wrote:

The Digitrax PR4 also works well with these (and most/all other) decoders and is a more economical alternative.

Agreed that there are other options (I did say "such as") but my reply is targeted at NCE users and in that case the Power Cab hardware can also be used in slave mode as a throttle with the main system, offsetting its cost.

There is a also CV128 'gotcha' when using the PR3/4 with non-Digtrax decoders:

Dave in Australia
Locked Re: Decoder Pro Errors out when Programming Functions on TSU-21PNEM #soundtraxx #tsunami

 

¿ªÔÆÌåÓý

pcgumshoe,

On 31 Aug 2019, at 9:53 AM, pcgumshoe <pcgumshoe@...> wrote:

I placed my loco on my portable programming track that has an NCE USB connection and a PowerCab.? I was able to program the function correctly, so I thought, I still can't get the F3 to turn on when the loco is moving forward or stopped.? In the "Function Map" tab, I selected "FX3 Effect" and changed it to "F0" and then I put check marks in the "Forward Driving" and "Forward Standing," spots, still no luck.

The NCE Power Cab doesn't have the CVs>256 issue, so is your ideal workaround for programming these decoders in Program Track mode.

Thinking out of the box earlier, I did think to do a program on the main, but I wasn't getting any feedback or notification that my programming was having any effect.? It may have been after the decoder was corrupted with bad CV data, I reset the decoder before placing it on my PowerCab track.

NCE command stations always report success for any CV write operation (main or program track), even if there is no loco on the track. These are called "blind writes" and are common for most systems when programming on main.

Dave in Australia
Locked Re: SSL heads fail to set properly after start .... JMRI 4.17.3

 

Looked at the Raspberry pi JMRI with that script of mine trying to get that script to run.? Got a system error saying it didnt like line 23 of InitLayout.py.? Reads "minPPwindow()

By the way, I do not use ANY DS64 boards.? I use the SE8C cards and a few Tam Valley servos.

Roger
Locked Re: Decoder Pro Errors out when Programming Functions on TSU-21PNEM #soundtraxx #tsunami

 

On Fri, Aug 30, 2019 at 04:29 PM, Dave Heap wrote:
?
?
If you have TSU2 decoders, your only choices are to use Program on Main or to get another programmer (such as a SPROG or an NCE Power Cab/NCE USB combination). JMRI can easily be configured to use two connections in the same session, with Program on Main, throttles, turnouts etc. being directed to the Power Pro and Program Track commands being directed to the SPROG/Power Cab.
The Digitrax PR4 also works well with these (and most/all other) decoders and is a more economical alternative.

Steve
"Breezlys"
Locked Re: Help with JMRI and Digitrax PR4

 

On Thu, Aug 29, 2019 at 08:51 AM, Rich S wrote:
Hi Steve,
?? Unplugging and plugging in the USB cable does not fix the issue. That is why I¡¯m wondering if the port settings are correct.
?
Cheers,
Rich S.
?
Rich,

To do the "reset" I've always unplugged *everything* that could supply power to the PR4: The USB cable, the external power, and the LocoNet if it's supplying railsync.

I also had a chance to peruse the layout computer. My COM port settings are as follows. I've never changed anything from when I first plugged in the PR4 and Windows discovered and installed it. I think the values in your JMRI preferences override these anyway:

In Device Manager:
Bits per second = 9600
Data bits = 8
Parity = None
Stop bits = 1
Flow Control = None?
FIFO buffers both set to high

JMRI preferences:
Baud rate = Fixed at 57,600
Serial connection uses = hardware flow control (recommended)
Packetizer type = Normal (recommended)
Transponding present = No
Turnout command handling = Normal


HTH,
Steve
Locked Re: Decoder Pro Errors out when Programming Functions on TSU-21PNEM #soundtraxx #tsunami

 

61 and 62, he had me try both number in CV 57 and CV 58.
Locked Re: Decoder Pro Errors out when Programming Functions on TSU-21PNEM #soundtraxx #tsunami

 

Thanks Dave for that explanation.

I placed my loco on my portable programming track that has an NCE USB connection and a PowerCab.? I was able to program the function correctly, so I thought, I still can't get the F3 to turn on when the loco is moving forward or stopped.? In the "Function Map" tab, I selected "FX3 Effect" and changed it to "F0" and then I put check marks in the "Forward Driving" and "Forward Standing," spots, still no luck.

Thinking out of the box earlier, I did think to do a program on the main, but I wasn't getting any feedback or notification that my programming was having any effect.? It may have been after the decoder was corrupted with bad CV data, I reset the decoder before placing it on my PowerCab track.
Locked Re: XL Systems Inc.

 

Jim,

On 31 Aug 2019, at 7:57 AM, jim green via Groups.Io <jimgreen150@...> wrote:

I looked at my NCE program and it said manufacturer 143 and decoder version 0 I don¡¯t know if this makes a difference either.
ManufacturerID is MRC. (Model Rectifier Corporation)

Since you get multiple matches for version 0 it indicates that either:
- there is no MRC decoder with a VersionID of 0.
- there are multiple MRC decoders with a VersionID of 0.
- MRC hasn't made available enough information for us to make a unique VersionID to Model Name map.
- MRC doesn't use VersionID.
- The decoder you have isn't a genuine MRC decoder.

Dave in Australia
Locked Re: Decoder Pro Errors out when Programming Functions on TSU-21PNEM #soundtraxx #tsunami

 

Values of 253 for CV57 and 254 for CV58 appear to be default values from Soundtraxx.
What did "Tech" say they should be?

--
Peter Ulvestad

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

Locked Re: Decoder Pro Errors out when Programming Functions on TSU-21PNEM #soundtraxx #tsunami

 

¿ªÔÆÌåÓý

pcgumshoe,

On 31 Aug 2019, at 8:41 AM, pcgumshoe <pcgumshoe@...> wrote:

I'm using windows 10, Decoder pro works fine with NCE and LOCONet via PR3.? I can control locomotives, program them and do just about everything.

My problem is these new 21PNEM decoders, I've tried using the TSU-2200 file to program and the file that is detected by decoder pro.

The problem is caused by a Power Pro firmware issue that affects program track operations with both JMRI and the NCE throttle.

If you, by any means, attempt to write a value to any CV>256 in Program Track mode using an NCE Power Pro, the firmware will instead write to a CV<257, possibly corrupting ?your decoder.

For, example, if you use the NCE throttle to write a value to CV275, that value will be written to CV19 (the consist address) instead, making your decoder appear non-responsive to its normal address!

If you attempt use JMRI to write a value to CV275, JMRI intercepts that request (to protect your decoder) and instead throws an error (unfortunately not gracefully, but the error can be seen in the JMRI system console).

The DDE ?and other advanced panes in the TSU2 use CVs>256 so are affected.

The only workaround for these decoders is to read the decoder on the Program Track, then save and reopen in Program on Main mode. Attempting to use the NCE throttle as a workaround will simply corrupt other CVs in your decoder.

( The ESU decoders are not affected because ESU provides an in-decoder workaround that doesn't involve writing to CVs>256 so JMRI intercepts the write command and uses that workaround.)

If you have TSU2 decoders, your only choices are to use Program on Main or to get another programmer (such as a SPROG or an NCE Power Cab/NCE USB combination). JMRI can easily be configured to use two connections in the same session, with Program on Main, throttles, turnouts etc. being directed to the Power Pro and Program Track commands being directed to the SPROG/Power Cab.

Don't try other means to cheat around the firmware limitation in the Power Pro, it will inevitably lead to tears.

Dave in Australia
Locked Re: Problem with Lenz LE103 decoders #lenz

 

My problem just got bigger. I put a new Soundtraxx Econami Steam xxxPNEM sound decoder in one of my locos. DecoderPro didn't find the brand or model in CV 8 and 7. It reported both contained zeros. Yet, it identified a Lenz LE103 again...

When I set the decoder type, I was able to program it. I can run it with my EasyDCC plug in throttles, but not with WiThrottle through my RPi running Steve Todd's image, a serial connection, and my EasyDCC Command Station.

I have a SoundTraxx programming booster, but haven't tried it. I read it's not needed for the newer Econami decoders.

So, my problem isn't just with one old type decoder. It includes at least one modern sound decoder. There's a clue there, somewhere. But, for the moment, it's discouraging.

Don Weigt
Connecticut, USA
Locked Re: SSL heads fail to set properly after start .... JMRI 4.17.3

 

Bob,

? ? ?Found the source of my problem.? I had changed scripts to match what I was using in my Raspberry JMRI Pi.? I normally used "InitLayout.py" by Bill Dickerson's Cascade Western railroad.? This Python script not in your list of approved scripts.

? ? What happens when I use this script to initialize the layout is the PanelPro window shows up then the script starts running and you can see turnouts and sensors being cleared as it runs.?

? ? When that script cause the Rasbrian JMRI to lockup, I went and changed scripts.? Not noticing the change in my signals.? This was two weeks ago.? ?The new scripts that are in the Jython folder must have a bug in them or I put one int somehow.

Roger
Locked Re: Decoder Pro Errors out when Programming Functions on TSU-21PNEM #soundtraxx #tsunami

 

JMRI versions are the CURRENT version and 4.17 test versions were tried.
Locked Decoder Pro Errors out when Programming Functions on TSU-21PNEM #soundtraxx #tsunami

 

I'm using windows 10, Decoder pro works fine with NCE and LOCONet via PR3.? I can control locomotives, program them and do just about everything.

My problem is these new 21PNEM decoders, I've tried using the TSU-2200 file to program and the file that is detected by decoder pro.? I can program some things, but other things get messed up.? When I called Soundtraxx about the lights (thinking it might be the decoder) I was asked what the values were in cv 57 and cv 58.? These were over 200 each and the tech said "Where did you get those numbers?"? And I explained I let Decoder Pro program them.

Here is the log from the system console:

2019-08-30 15:32:25,838 util.Log4JUtil? ? ? ? ? ? ? ? ? ? ? ? INFO? - * JMRI log ** [main]

2019-08-30 15:32:25,848 util.Log4JUtil? ? ? ? ? ? ? ? ? ? ? ? INFO? - This log is appended to file: C:\Users\pcgum\JMRI\log\messages.log [main]

2019-08-30 15:32:25,849 util.Log4JUtil? ? ? ? ? ? ? ? ? ? ? ? INFO? - This log is stored in file: C:\Users\pcgum\JMRI\log\session.log [main]

2019-08-30 15:32:25,854 apps.AppsBase? ? ? ? ? ? ? ? ? ? ? ? ?INFO? - DecoderPro version 4.17.3+R12d2ded starts under Java 1.8.0_221 on Windows 10 x86 v10.0 at Fri Aug 30 15:32:25 PDT 2019 [main]

2019-08-30 15:32:26,044 gui3.Apps3? ? ? ? ? ? ? ? ? ? ? ? ? ? INFO? - Starting with profile My_JMRI_Railroad.3f60eef2 [main]

2019-08-30 15:32:26,585 node.NodeIdentity? ? ? ? ? ? ? ? ? ? ?INFO? - Using 7b5a555b-e311-40a3-8586-36ee772ee891 as the JMRI storage identity for profile id 3f60eef2 [AWT-EventQueue-0]

2019-08-30 15:32:26,676 xml.AbstractSerialConnectionConfigXml INFO? - Starting to connect for "NCE" [main]

2019-08-30 15:32:27,722 serialdriver.SerialDriverAdapter? ? ? INFO? - NCE COM4 port opened at 9600 baud [main]

2019-08-30 15:32:27,760 xml.AbstractSerialConnectionConfigXml INFO? - Starting to connect for "LocoNet" [main]

2019-08-30 15:32:27,879 nce.NceConnectionStatus? ? ? ? ? ? ? ?INFO? - NCE EPROM revision = 6.2.1 [AWT-EventQueue-0]

2019-08-30 15:32:27,881 locobufferusb.LocoBufferUsbAdapter? ? INFO? - LocoBuffer-USB adapter set hardware flow control, mode=2 RTSCTS_OUT=2 RTSCTS_IN=1 [main]

2019-08-30 15:32:27,882 locobuffer.LocoBufferAdapter? ? ? ? ? INFO? - COM5 port opened at 57600 baud with DTR: true RTS: true DSR: true CTS: true? CD: false [main]

2019-08-30 15:32:27,897 loconet.LnPacketizer? ? ? ? ? ? ? ? ? INFO? - lnPacketizer Started [main]

2019-08-30 15:32:28,076 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path program: is C:\Program Files (x86)\JMRI\ [main]

2019-08-30 15:32:28,076 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path preference: is C:\Users\pcgum\JMRI\My_JMRI_Railroad.jmri\ [main]

2019-08-30 15:32:28,076 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path profile: is C:\Users\pcgum\JMRI\My_JMRI_Railroad.jmri\ [main]

2019-08-30 15:32:28,076 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path settings: is C:\Users\pcgum\JMRI\ [main]

2019-08-30 15:32:28,076 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path home: is C:\Users\pcgum\ [main]

2019-08-30 15:32:28,077 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path scripts: is C:\Program Files (x86)\JMRI\jython\ [main]

2019-08-30 15:32:41,010 decoderdefn.IdentifyDecoder? ? ? ? ? ?INFO? - Decoder returns mfgID:141;modelID:71;productID:285 [AWT-EventQueue-0]

2019-08-30 15:33:14,926 ementation.MultiIndexProgrammerFacade ERROR - Exception doing final write [AWT-EventQueue-0]

jmri.ProgrammerException: CV number not supported

at jmri.jmrix.nce.NceProgrammer.writeCV(NceProgrammer.java:130)

at jmri.implementation.MultiIndexProgrammerFacade.programmingOpReply(MultiIndexProgrammerFacade.java:397)

at jmri.Programmer.notifyProgListenerEnd(Programmer.java:216)

at jmri.jmrix.nce.NceProgrammer.notifyProgListenerEnd(NceProgrammer.java:317)

at jmri.jmrix.nce.NceProgrammer.reply(NceProgrammer.java:268)

at jmri.jmrix.nce.NceTrafficController.forwardReply(NceTrafficController.java:110)

at jmri.jmrix.AbstractMRTrafficController.notifyReply(AbstractMRTrafficController.java:298)

at jmri.jmrix.AbstractMRTrafficController$RcvNotifier.run(AbstractMRTrafficController.java:1229)

at java.awt.event.InvocationEvent.dispatch(Unknown Source)

at java.awt.EventQueue.dispatchEventImpl(Unknown Source)

at java.awt.EventQueue.access$500(Unknown Source)

at java.awt.EventQueue$3.run(Unknown Source)

at java.awt.EventQueue$3.run(Unknown Source)

at java.security.AccessController.doPrivileged(Native Method)

at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)

at java.awt.EventQueue.dispatchEvent(Unknown Source)

at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

?
Locked Re: SSL heads fail to set properly after start .... JMRI 4.17.3

 

Bob,

? ? Took out the two scripts that clear turnouts and clears unknown sensors.? Did that on the Raspberry Pi.? All that did was leave all signals red.??

? ? Trying to find my loconet checker.? It's a mess here.

? ? ?Will load up the laptop and delete all logix next.

Roger
Locked Re: XL Systems Inc.

 

I looked at my NCE program and it said manufacturer 143 and decoder version 0 I don¡¯t know if this makes a difference either.?




On Friday, August 30, 2019, 5:13 PM, Dave Heap <dgheap@...> wrote:

Jim,

> On 31 Aug 2019, at 4:36 AM, jim green via Groups.Io <jimgreen150=[email protected]> wrote:
>
> Well looked at it today and it does list mrc but I do n scale and I read decoder from decoder pro and it came up as HO decoder ALCO and EMD locos probably 10 different kinds which is strange to me. I¡¯m not savvy with pro yet but when I brought up and selected mrc and read decoder it went back to HO decoder and listed those locos again.

Many decoder manufacturers do not provide enough CV-accessible information to enable DecoderPro to uniquely identify a decoder, so JMRI has no option but to try to narrow the list and let the user make the final choice.

If the decoder definitions in JMRI don't have an N scale option it may mean that the there is no programming difference between the HO and N versions (but in this case it would be normal to omit any reference to scale in the name.

Dave in Australia
Locked Re: SSL heads fail to set properly after start .... JMRI 4.17.3

 

Are you running any scripts at startup?

It sounds like something it deliberately going through and setting those signals. Now we just have to figure out what.

Two strong candidates are a script you¡¯re running, or Logix that you¡¯ve defined to do something.

Bob

On Aug 30, 2019, at 2:12 PM, Roger Merritt <merritt_roger@...> wrote:

Bob,

Went back to 4.15.9 and problem is there too.

What I am seeing is as JMRI is loading all signals go RED. Then I see signals go green if occupancy is inactive and the occupied signal for occupied blocks stay red. Then at the end all go green! Weird.

My memory is just terrible. There was something done to the setup and it involved my Dispatcher running AUTO trains. Sometimes it would miss throwing the first turnout and that would cause a derailment. Cant remember who, but he advised making a change somewhere. I think in the preferrances.

Maybe I need to check my loconet. Missing packets? I did try the test at another PR3 and it failed also. I have two of them.

Roger
--
Bob Jacobsen
rgj1927@...
Locked Re: XL Systems Inc.

 

Jim,

On 31 Aug 2019, at 4:36 AM, jim green via Groups.Io <jimgreen150@...> wrote:

Well looked at it today and it does list mrc but I do n scale and I read decoder from decoder pro and it came up as HO decoder ALCO and EMD locos probably 10 different kinds which is strange to me. I¡¯m not savvy with pro yet but when I brought up and selected mrc and read decoder it went back to HO decoder and listed those locos again.
Many decoder manufacturers do not provide enough CV-accessible information to enable DecoderPro to uniquely identify a decoder, so JMRI has no option but to try to narrow the list and let the user make the final choice.

If the decoder definitions in JMRI don't have an N scale option it may mean that the there is no programming difference between the HO and N versions (but in this case it would be normal to omit any reference to scale in the name.

Dave in Australia
Locked Re: SSL heads fail to set properly after start .... JMRI 4.17.3

 

Bob,

? ? Went back to 4.15.9 and problem is there too.

? ? What I am seeing is as JMRI is loading all signals go RED.? Then I see signals go green if occupancy is inactive and the occupied signal for occupied blocks stay red.? Then at the end all go green!? Weird.

? ? ?My memory is just terrible.? There was something done to the setup and it involved my Dispatcher running AUTO trains.? Sometimes it would miss throwing the first turnout and that would cause a derailment.? Cant remember who, but he advised making a change somewhere.? I think in the preferrances.??

? ? ?Maybe I need to check my loconet.? Missing packets?? I did try the test at another PR3 and it failed also.? I have two of them.

Roger
Locked Re: A newbie with JMRI Completely stuck trying to get LocoNet to interface via LocoBuffer USB

 

¿ªÔÆÌåÓý

Dick, Bob, Peter & Dave

Many thanks yes 4.17.3 fixed it phew, and Dick I meant to say LocoBufferUSB not LocoBuffer II so in fact it was fine.

Best Wishes to All

Tim
(from the Highlands of Scotland taking 20 minutes off grand child caring duties)




On 30 Aug 2019, at 20:34, dick bronson via Groups.Io <dick@...> wrote:

Tim,

Also after switching up to 4.17.3 be sure to get rid of that LocoBuffer-II option. That is a completely different item and will not work for you. You have a LocoBuffer-USB (Rev-n) and must select 'LocoBuffer-USB' in your preferences. What happened is that you got nabbed by a bug in JMRI 4.16. You are not being an idiot, so no apologies are required nor expected.

Dick :)

On 8/30/2019 2:21 PM, Bob Jacobsen wrote:
Please download and try JMRI 4.17.3

Bob

On Aug 30, 2019, at 4:19 AM, timj@... wrote:

Newbie here - and to JMRI completely stuck apologies in advance if I am being an idiot.

I have a LocoNet system (DCS100) with a load of devices attached. All working well and has been for years but I just can't get JMRI to respond to it.

Initially I tried with a pi4 running buster and a LocoBuffer-USB 'n' but it just didn't see any traffic - so then I swapped to a Loconet-II with same result. Then I swapped to a windows 7 Intel computer that I know can see LocoNet (as e.g. it runs traincontroller ok) via the LocoBuffer-II and again seeing nothing.

The setup seems ok, it picks up the right port but just see nothing at all on the traffic monitor - I note if i look at JMRI LocoNet-stats it says "raw-data" which i read elsewhere is indicative of problems but I don't know where to go next. Any suggestions very gratefully received as I feel like I am banging head against brick wall...

--
Bob Jacobsen
rgj1927@...
76781 - 76800 of 239666