Signal pair conflict with turnout state? and auto train speed.?

#163351

Hi

Having problems with a signal pair that thinks the same turnout should be in different states.? Please see layout file here:
?/g/jmriusers/files/ProblemsBeingWorkedOn/Steve%20UK%20009

Signals? Hill - upprAppr(0008) and Uppr Brid - Uppr Loop (0009) are a pair but the latter thinks that turnout Chipping Dale (1012) should be closed and not thrown as it should be for correct signalling.??
I have a similar situation in the lower loop in which signals work fine.

Also auto train speeds seem to fluctuate and will occasionally? ignore red light for no apparent reason. Is there a way of tracking what speed setting is being invoked at any given time, the reason why that setting has been invoked and how this may be changed?
(using dispatcher and SML)

Has anyone any advice please?

Many thanks

Steve Lomax
--
Steve 009 in UK

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

#163350

Peter,

The log shows the known LocoBuffer empty speed setting in profile.xml which then defaults to 19200.  As Bob indicates, 4.17.3 resolves the issue.

Dave Sand

Show quoted text

On Aug 30, 2019, at 1:18 PM, Peter Ulvestad <ulvestad@...> wrote:

Tim's console

019-08-30 13:43:26,456 util.Log4JUtil                        INFO  - * JMRI log ** [main]
2019-08-30 13:43:26,456 util.Log4JUtil                        INFO  - This log is appended to file: C:\Users\Tim\JMRI\log\messages.log [main]
2019-08-30 13:43:26,456 util.Log4JUtil                        INFO  - This log is stored in file: C:\Users\Tim\JMRI\log\session.log [main]
2019-08-30 13:43:26,471 apps.Apps                             INFO  - PanelPro version 4.16+R6f9aced starts under Java 1.8.0_221 on Windows 7 amd64 v6.1 at Fri Aug 30 13:43:26 BST 2019 [main]
2019-08-30 13:43:26,623 apps.Apps                             INFO  - Starting with profile My_JMRI_Railroad.3ed9c7c2 [main]
2019-08-30 13:43:26,748 node.NodeIdentity                     INFO  - Using 01e2399b-7d56-421c-946b-9196045968e1 as the JMRI storage identity for profile id 3ed9c7c2 [AWT-EventQueue-0]
2019-08-30 13:43:26,826 xml.AbstractSerialConnectionConfigXml INFO  - Starting to connect for "LocoNet" [main]
2019-08-30 13:43:27,138 locobufferusb.LocoBufferUsbAdapter    INFO  - LocoBuffer-USB adapter set hardware flow control, mode=2 RTSCTS_OUT=2 RTSCTS_IN=1 [main]
2019-08-30 13:43:27,138 locobuffer.LocoBufferAdapter          INFO  - COM3 port opened at 19200 baud with DTR: true RTS: true DSR: true CTS: true  CD: false [main]
2019-08-30 13:43:27,184 loconet.LnPacketizer                  INFO  - lnPacketizer Started [main]
2019-08-30 13:43:27,530 loconet.LnPacketizer                  WARN  - LocoNet message with opCode: f8 ended early. Expected length: 197 seen length: 2 unexpected byte: c8 [LocoNet receive handler]
2019-08-30 13:43:28,969 util.FileUtilSupport                  INFO  - File path program: is C:\Program Files (x86)\JMRI\ [main]
2019-08-30 13:43:28,970 util.FileUtilSupport                  INFO  - File path preference: is C:\Users\Tim\JMRI\My_JMRI_Railroad.jmri\ [main]
2019-08-30 13:43:28,971 util.FileUtilSupport                  INFO  - File path profile: is C:\Users\Tim\JMRI\My_JMRI_Railroad.jmri\ [main]
2019-08-30 13:43:28,971 util.FileUtilSupport                  INFO  - File path settings: is C:\Users\Tim\JMRI\ [main]
2019-08-30 13:43:28,971 util.FileUtilSupport                  INFO  - File path home: is C:\Users\Tim\ [main]
2019-08-30 13:43:28,971 util.FileUtilSupport                  INFO  - File path scripts: is C:\Program Files (x86)\JMRI\jython\ [main]
2019-08-30 13:43:29,515 loconet.LnPacketizer                  WARN  - LocoNet message with opCode: c8 ended early. Expected length: 6 seen length: 3 unexpected byte: a0 [LocoNet receive handler]
2019-08-30 13:43:29,577 PanelPro.PanelPro                     INFO  - Main initialization done [main]
2019-08-30 13:43:29,858 loconet.LnPacketizer                  WARN  - LocoNet message with opCode: a0 ended early. Expected length: 4 seen length: 3 unexpected byte: fc [LocoNet receive handler]
2019-08-30 13:43:31,449 loconet.LnPacketizer                  WARN  - LocoNet message with opCode: fc ended early. Expected length: 160 seen length: 2 unexpected byte: fe [LocoNet receive handler]
2019-08-30 13:43:31,496 loconet.LnPacketizer                  WARN  - LocoNet message with opCode: fe ended early. Expected length: 32 seen length: 2 unexpected byte: ff [LocoNet receive handler]
2019-08-30 13:43:31,792 loconet.LnPacketizer                  WARN  - LocoNet message with opCode: ff ended early. Expected length: 32 seen length: 2 unexpected byte: ff [LocoNet receive handler]
2019-08-30 13:43:32,666 loconet.LnPacketizer                  WARN  - LocoNet message with opCode: ff ended early. Expected length: 160 seen length: 2 unexpected byte: ff [LocoNet receive handler]
2019-08-30 13:43:33,118 loconet.LnPacketizer                  WARN  - LocoNet message with opCode: ff ended early. Expected length: 32 seen length: 2 unexpected byte: ff [LocoNet receive handler]


View Source




-- 
Peter Ulvestad

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

Re: XL Systems Inc.

#163349

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. Not sure if it’s just generic program or what. But someone probably could change listing I don’t know but I know I have no complaints with sound or install and if you email him thru eBay he will respond promptly for more info. Hopefully this helps.?

Show quoted text

On Thursday, August 29, 2019, 5:42 PM, jim green via Groups.Io <jimgreen150@...> wrote:

That I have not looked at yet. Just installed and tested on short track but didn’t set them up in decoderpro. If I get some time in the next day or so I’ll have to check and will post results. But they work fine and sound great. No complaints yet and plan on buying from again but 5 at 1 time still gets expensive when you have 4o locos to do.?

On Thursday, August 29, 2019, 10:14 AM, Ken Cameron <kcameron@...> wrote:
Jim,

So do they identify themselves as MRC or something else in DecoderPro?

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

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

#163348

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@...

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

#163347

Tim's console

019-08-30 13:43:26,456 util.Log4JUtil                        INFO  - * JMRI log ** [main]
2019-08-30 13:43:26,456 util.Log4JUtil                        INFO  - This log is appended to file: C:\Users\Tim\JMRI\log\messages.log [main]
2019-08-30 13:43:26,456 util.Log4JUtil                        INFO  - This log is stored in file: C:\Users\Tim\JMRI\log\session.log [main]
2019-08-30 13:43:26,471 apps.Apps                             INFO  - PanelPro version 4.16+R6f9aced starts under Java 1.8.0_221 on Windows 7 amd64 v6.1 at Fri Aug 30 13:43:26 BST 2019 [main]
2019-08-30 13:43:26,623 apps.Apps                             INFO  - Starting with profile My_JMRI_Railroad.3ed9c7c2 [main]
2019-08-30 13:43:26,748 node.NodeIdentity                     INFO  - Using 01e2399b-7d56-421c-946b-9196045968e1 as the JMRI storage identity for profile id 3ed9c7c2 [AWT-EventQueue-0]
2019-08-30 13:43:26,826 xml.AbstractSerialConnectionConfigXml INFO  - Starting to connect for "LocoNet" [main]
2019-08-30 13:43:27,138 locobufferusb.LocoBufferUsbAdapter    INFO  - LocoBuffer-USB adapter set hardware flow control, mode=2 RTSCTS_OUT=2 RTSCTS_IN=1 [main]
2019-08-30 13:43:27,138 locobuffer.LocoBufferAdapter          INFO  - COM3 port opened at 19200 baud with DTR: true RTS: true DSR: true CTS: true  CD: false [main]
2019-08-30 13:43:27,184 loconet.LnPacketizer                  INFO  - lnPacketizer Started [main]
2019-08-30 13:43:27,530 loconet.LnPacketizer                  WARN  - LocoNet message with opCode: f8 ended early. Expected length: 197 seen length: 2 unexpected byte: c8 [LocoNet receive handler]
2019-08-30 13:43:28,969 util.FileUtilSupport                  INFO  - File path program: is C:\Program Files (x86)\JMRI\ [main]
2019-08-30 13:43:28,970 util.FileUtilSupport                  INFO  - File path preference: is C:\Users\Tim\JMRI\My_JMRI_Railroad.jmri\ [main]
2019-08-30 13:43:28,971 util.FileUtilSupport                  INFO  - File path profile: is C:\Users\Tim\JMRI\My_JMRI_Railroad.jmri\ [main]
2019-08-30 13:43:28,971 util.FileUtilSupport                  INFO  - File path settings: is C:\Users\Tim\JMRI\ [main]
2019-08-30 13:43:28,971 util.FileUtilSupport                  INFO  - File path home: is C:\Users\Tim\ [main]
2019-08-30 13:43:28,971 util.FileUtilSupport                  INFO  - File path scripts: is C:\Program Files (x86)\JMRI\jython\ [main]
2019-08-30 13:43:29,515 loconet.LnPacketizer                  WARN  - LocoNet message with opCode: c8 ended early. Expected length: 6 seen length: 3 unexpected byte: a0 [LocoNet receive handler]
2019-08-30 13:43:29,577 PanelPro.PanelPro                     INFO  - Main initialization done [main]
2019-08-30 13:43:29,858 loconet.LnPacketizer                  WARN  - LocoNet message with opCode: a0 ended early. Expected length: 4 seen length: 3 unexpected byte: fc [LocoNet receive handler]
2019-08-30 13:43:31,449 loconet.LnPacketizer                  WARN  - LocoNet message with opCode: fc ended early. Expected length: 160 seen length: 2 unexpected byte: fe [LocoNet receive handler]
2019-08-30 13:43:31,496 loconet.LnPacketizer                  WARN  - LocoNet message with opCode: fe ended early. Expected length: 32 seen length: 2 unexpected byte: ff [LocoNet receive handler]
2019-08-30 13:43:31,792 loconet.LnPacketizer                  WARN  - LocoNet message with opCode: ff ended early. Expected length: 32 seen length: 2 unexpected byte: ff [LocoNet receive handler]
2019-08-30 13:43:32,666 loconet.LnPacketizer                  WARN  - LocoNet message with opCode: ff ended early. Expected length: 160 seen length: 2 unexpected byte: ff [LocoNet receive handler]
2019-08-30 13:43:33,118 loconet.LnPacketizer                  WARN  - LocoNet message with opCode: ff ended early. Expected length: 32 seen length: 2 unexpected byte: ff [LocoNet receive handler]
 

View Source




-- 
Peter Ulvestad

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

Re: CanExample.py

#163346

I have been in contact with Roco in the past months about their CAN protocol. They are using ZCAN20 (Zimo) protocol in the Z21.

If you read through ZCAN20 document Bob linked below () you will see references to Z21 CS and various Roco CAN accessories.

Rocrail has some of this protocol supported as part of their RCAN/CAN-GC* hardware combo,?, code available at?

For a pinout of the Z21 CAN port, you can refer to the Zimo MX10 rear CAN port??although I am not sure whether Roco pushes 30V through (like Zimo does) so the pinout is more precisely:

Pin 1 ... DCC-Signal (to booster)
Pin 2 ... DCC-Signal (to booster)

Pin 3 ... GND

Pin 4 ... CAN High

Pin 5 ... CAN Low

Pin 6 ... N/C

Pin 7 ... +12V (max 1A)

Pin 8 ... Short-circuit-signal (from Booster)

HTH!

A newbie with JMRI Completely stuck trying to get LocoNet to interface via LocoBuffer USB

#163345

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...

Re: Back and forth

#163344

Tim: The more I learn about what you've got the more I doubt I can help you. But I do think your answers to my questions will help others following this who have relevant experience and can jump in. So one more question...

Do you have all the NCE equipment installed and connected to JMRI and is it all working? If not, is that what you'd like help with? Or are you looking for help in setting up the back and forth scripts?

Jan

Re: Windows 4.17 download caught by Malware

#163343

OK thanks Cliff and James.

I think it is a false positive with Avast, I cross-checked with Malwarebytes and it sees no problem.

Re: Windows 4.17 download caught by Malware

#163342

Avast claimed the same thing about my copy too. On this machine that version had been in use every day since the release notice or a day after. Because windows kept telling me that "JMRI is already running." every time I started PanelPro with either version 4.17.3 or 4.16 I decided to try uninstalling both of them and clean out the Program Files (x86) folders and reinstall them.

Version 4.16 reinstalled as expected but Avast got in the way and moved the 4.17.3 file to what it calls the Virus Chest. Even though I requested a review of that action, in fact twice, I have received no response. After two an a half days, I simply clicked, or maybe right clicked(?) on the Virus Chest link and instructed it to execute anyway.

No problems since then. By the way, the erroneous windows message about already running still reappears from time to time, but not always.

Cliff in Baja SoCal

Re: Windows 4.17 download caught by Malware

#163341

开云体育

You have to turn off antivirus software to install on windows.?

Jim

Show quoted text

On Aug 30, 2019, at 11:21, Dave Barraza <dave@...> wrote:

My Avast Antivirus is flagging the JMRI.4.17.3+R12d2ded.exe as containing "FileRepMalware"

Is anyone else having this problem?

Dave

Windows 4.17 download caught by Malware

#163340

My Avast Antivirus is flagging the JMRI.4.17.3+R12d2ded.exe as containing "FileRepMalware"

Is anyone else having this problem?

Dave

Re: Virtual Sound Decoder - Clicks on looped sound files

#163339

Conrad,

You can upload to the VSD section in files at:

/g/jmriusers/files/VSD

Hope that helps.

Oh, and I'll come back with some thoughts surrounding the 'clicking' etc. a bit later.

Best regards,

Matt H

Re: CanExample.py

#163338

Bob, Paul,

I feel obliged to specify a point I was referring to as being unclear to me.

As I see, for me it suffices what Roco did publish.

If you remember, I wanted to send a CAN message to my CAN reporter in a script, i.e. purely within my computer, even within JMRI not involving my command station Z21. To be more specific, just this array of bytes:
[0x0E, 0x00, 0xC4, 0x00, 0x00, 0x00, 0x00, 0x00, 0x06, 0x11, 0x,13, 0x11, 0x14, 0x11].
According to Roco's "Z21 LAN Protocol Specification", if I am not mistaken, my CAN reporter "ZRD6AA:6" should interpret this as two messages
Orientation B Address 19(S), having system name RD19 and
Orientation B Address 20(S), having system name RD20.

Now, if I understand you, Bob, correctly then there is a standard way of sending such a message, independent of Roco. I can think of two methods for doing so:
Using the function reporter.reply(<message>), except that I don't know what the Z21Reply type variable would be in my case, or
Sending it as a frame similarly to but definitely somewhat differently from CanMessage.py.

I could probably figure out how to do it from your link, Paul, if I knew Java but even in Python I am compelled to rely on recipes I get from you as many times in the past.

Gabor

Re: Virtual Sound Decoder - Clicks on looped sound files

#163337

Thanks for the inputs.? ?My wife and I are off to watch the grandkids so I will be working on a response maybe this weekend or next week.? I'm old (75) and it's been a few months since I modified the VSD files, so I need to refresh my memory (what's left of it).? I have been using and enjoying the sounds all summer with my layout.

One question - how do I send files to this site?? or where are the instructions to do it?

conrad

PS I have electrics - ACELA HHP8, Alpine Express, AEM7, DB401, GG1 and Shinkansen? (all made by me without any notching)

Re: Virtual Sound Decoder - Clicks on looped sound files

#163336

Conrad,

Welcome to VSD!

Thanks for your report and for your offer. Yes, I'm interested in your method and some details. But I use Audacity instead of WavePad.

Roberto and Jim, many thanks for the good advice. Very helpful to repair the root cause for the "pops or clicks".

Just to give an example of a click: lets take EMD_645_Turbo.vsd - notch1 (idle sound) sounds pretty good for me, but there is a click in notch2.
Conrad, do you have clicks in all notch or idle sounds?

Another cause might be restarts of the VSD player. They sound different, because there is a short sound gap associated. Easy to hear on Diesel sounds, more difficult in Steam sounds. For example, I noticed such restarts the first time I run VSD on a "Raspberry Pi 3 B+". But it turns out that it was a configuration issue concerning my sound card. Restarts are reported in JMRI session.log.

VSD right now doesn't support Electric engine sound. I have no experience here. Should VSD support Electric engines?

Regards,
Klaus

Re: Problem with Lenz LE103 decoders #lenz

#163335

Mike, I'm having this problem with an EasyDCC system. I'd be interested in your idea when you have access to something with a keyboard.

Gerry, I look forward to your test results! I've thought about using the Lenz LE103s for lighting controls or my turntable. Of course, the turntable won't work if a loco won't. But, I've not even been able to control the lights on the four locos that have them. So far, I have control of lights and motor, or neither.

It's worth mentioning that when I bought these decoders, one consideration was that the complied with the NMRA DCC Standard. So, I expected them to remain compatible with newer DCC equipment.

Don Weigt
Connecticut, USA

Re: Web Server, Panel Update for feedback #layouteditor #webserver

#163334

Thanks Randall and Steve, understand... The ultimate plan is to have the operators use a native panel.

Re: Problem with Lenz LE103 decoders #lenz

#163333

开云体育

Don

I will test tomorrow - I removed these decoders form locos years ago - some are now in cabooses (cabeese) to control the lights.

Gerry

On 30/08/2019 10:37 am, Don Weigt wrote:

I seem to have narrowed my problem with locos that program OK, run with EasyDCC throttles, but not with WiThrottle.

Every one so far has the same brand and model decoder: an early Lenz LE103 unit. They were my choice when I got started with DCC, reasonable size, price, and current rating. Most of my locos have Lenz LE103 decoders, and NONE tested so far works with WiThrottle! DecoderPro identifies them, programs all the CVs, they run with EasyDCC throttles set to those addresses, but don't run with WiThrottle. Given I have ten or more locos with LE103 decoders, I sure wish WiThrottle could control them!

The two locos that are working are using other decoders, one an inexpensive NCE bought a month ago, the other an older Zimo, probably an MX-61N. DecoderPro identified the NCE and its model correctly. It couldn't identify the Zimo, even by brand, yet could program and control it.

Has anyone else had problems using Lenz LE103s or other older decoders with JMRI? Does anyone know why this should be happening, or better still, have a fix?

Don Weigt
Connecticut, USA

-- 
Gerry Hopkins MMR #177 FNMRA
Great Northern Downunder




NMRA Australasian Region
Contest & AP Chairman
Web Administrator

Virus-free.

Re: Back and forth

#163332

Jan
Yes when you lock it out yes means you can’t have trains pass there. 
Yes I have blocks set up and using nce bd20’s which are put into the sensors table and turnouts are wired into nce switch 8 which will be put onto the turnout table in jmri.