¿ªÔÆÌåÓý

  1. Jmriusers
  2. Messages
Expanded Topics Messages Polls
Date
Locked Re: WiThrottle crash? #withrottleserver

 

Restarted the Mac and started JMRI (WiThrottle set to start with app). During JMRI start there was an iPhone running withrottle. This phone showed up as "unknown" (mac address was same one as when phone was connected earlier with proper name). When I see "Unknown" in the device name it means that its time for some buggy operation. Sometimes unknown and "Daves iPhone" appear together, but the iPhone throttle doesn't actually work.

Here's the short log:?
2020-02-03 20:23:56,147 util.Log4JUtil? ? ? ? ? ? ? ? ? ? ? ? INFO? - * JMRI log ** [main]
2020-02-03 20:23:57,418 util.Log4JUtil? ? ? ? ? ? ? ? ? ? ? ? INFO? - This log is appended to file: /Users/davebarraza/Library/Preferences/JMRI/log/messages.log [main]
2020-02-03 20:23:57,418 util.Log4JUtil? ? ? ? ? ? ? ? ? ? ? ? INFO? - This log is stored in file: /Users/davebarraza/Library/Preferences/JMRI/log/session.log [main]
2020-02-03 20:23:57,427 apps.Apps? ? ? ? ? ? ? ? ? ? ? ? ? ? ?INFO? - PanelPro version 4.19.2+R846b684 starts under Java 1.8.0_231 on Mac OS X x86_64 v10.15.3 at Mon Feb 03 20:23:57 EST 2020 [main]
2020-02-03 20:23:57,639 apps.Apps? ? ? ? ? ? ? ? ? ? ? ? ? ? ?INFO? - Starting with profile My_JMRI_Railroad.3e80976d [main]
2020-02-03 20:23:57,723 node.NodeIdentity? ? ? ? ? ? ? ? ? ? ?INFO? - Using c6f7c494-1590-4edf-83b6-fe19a3b8d450 as the JMRI storage identity for profile id 3e80976d [AWT-EventQueue-0]
2020-02-03 20:23:57,789 xml.AbstractSerialConnectionConfigXml INFO? - Starting to connect for "CAN" [main]
2020-02-03 20:24:00,157 gridconnect.GcSerialDriverAdapter? ? ?INFO? - cu.usbmodem1461301 port opened at 57600 baud, sees? DTR: true RTS: true DSR: false CTS: false? CD: false [main]
2020-02-03 20:24:00,218 xml.AbstractSerialConnectionConfigXml INFO? - Starting to connect for "SPROG Programmer" [main]
2020-02-03 20:24:00,237 serialdriver.SerialDriverAdapter? ? ? INFO? - cu.usbserial-feedcode port opened at 9600 baud, sees? DTR: true RTS: true DSR: true CTS: true? CD: false [main]
2020-02-03 20:24:00,252 xml.AbstractSerialConnectionConfigXml INFO? - Starting to connect for "LocoNet" [main]
2020-02-03 20:24:00,270 locobufferusb.LocoBufferUsbAdapter? ? INFO? - LocoBuffer-USB adapter set hardware flow control, mode=2 RTSCTS_OUT=2 RTSCTS_IN=1 [main]
2020-02-03 20:24:00,270 locobuffer.LocoBufferAdapter? ? ? ? ? INFO? - cu.usbserial-FTXPTBL0 port opened at 57600 baud with DTR: true RTS: true DSR: true CTS: true? CD: false [main]
2020-02-03 20:24:00,289 loconet.LnPacketizer? ? ? ? ? ? ? ? ? INFO? - lnPacketizer Started [main]
2020-02-03 20:24:00,290 xml.AbstractSerialConnectionConfigXml INFO? - Starting to connect for "LocoNet" [main]
2020-02-03 20:24:00,308 locobufferusb.LocoBufferUsbAdapter? ? INFO? - LocoBuffer-USB adapter set hardware flow control, mode=2 RTSCTS_OUT=2 RTSCTS_IN=1 [main]
2020-02-03 20:24:00,309 locobuffer.LocoBufferAdapter? ? ? ? ? INFO? - cu.usbserial-FTOYEDZV port opened at 57600 baud with DTR: true RTS: true DSR: true CTS: true? CD: false [main]
2020-02-03 20:24:00,310 loconet.LnPacketizer? ? ? ? ? ? ? ? ? INFO? - lnPacketizer Started [main]
2020-02-03 20:24:00,747 withrottle.FacelessServer? ? ? ? ? ? ?DEBUG - WiThrottle listening on TCP port: 12090 [WiThrottleServer]
2020-02-03 20:24:00,804 withrottle.FacelessServer? ? ? ? ? ? ?INFO? - Published ZeroConf service for 'new york and atlantic._withrottle._tcp.local.' on fe80:0:0:0:f81f:26a0:e5d0:778f%utun1:12090 [WiThrottleServer]
2020-02-03 20:24:00,804 withrottle.FacelessServer? ? ? ? ? ? ?INFO? - Published ZeroConf service for 'new york and atlantic._withrottle._tcp.local.' on fe80:0:0:0:b727:325d:9a87:7eb1%utun0:12090 [WiThrottleServer]
2020-02-03 20:24:00,806 withrottle.FacelessServer? ? ? ? ? ? ?INFO? - Published ZeroConf service for 'new york and atlantic._withrottle._tcp.local.' on fe80:0:0:0:4c67:9eff:fe2e:f985%awdl0:12090 [WiThrottleServer]
2020-02-03 20:24:00,806 withrottle.FacelessServer? ? ? ? ? ? ?INFO? - Published ZeroConf service for 'new york and atlantic._withrottle._tcp.local.' on fe80:0:0:0:0:0:0:1%lo0:12090 [WiThrottleServer]
2020-02-03 20:24:00,807 withrottle.FacelessServer? ? ? ? ? ? ?INFO? - Published ZeroConf service for 'new york and atlantic._withrottle._tcp.local.' on fe80:0:0:0:1494:f9da:15e4:6394%en1:12090 [WiThrottleServer]
2020-02-03 20:24:00,807 withrottle.FacelessServer? ? ? ? ? ? ?INFO? - Published ZeroConf service for 'new york and atlantic._withrottle._tcp.local.' on 192.168.1.102:12090 [WiThrottleServer]
2020-02-03 20:24:00,808 withrottle.FacelessServer? ? ? ? ? ? ?INFO? - Published ZeroConf service for 'new york and atlantic._withrottle._tcp.local.' on fe80:0:0:0:aede:48ff:fe00:1122%en6:12090 [WiThrottleServer]
2020-02-03 20:24:00,808 withrottle.FacelessServer? ? ? ? ? ? ?INFO? - Creating new WiThrottle DeviceServer(socket) on port 12090, waiting for incoming connection... [WiThrottleServer]
2020-02-03 20:24:06,247 withrottle.DeviceServer? ? ? ? ? ? ? ?DEBUG - Creating input? stream reader for /fe80:0:0:0:835:6d53:56b4:41dc%7:52404 [WiThrottleServer]
2020-02-03 20:24:06,251 withrottle.DeviceServer? ? ? ? ? ? ? ?DEBUG - Creating output stream writer for /fe80:0:0:0:835:6d53:56b4:41dc%7:52404 [WiThrottleServer]
2020-02-03 20:24:06,255 withrottle.DeviceServer? ? ? ? ? ? ? ?DEBUG - Sent: VN2.0? ? ? ? ? ? ? ? ?to? Unknown/fe80:0:0:0:835:6d53:56b4:41dc%7:52404 [WiThrottleServer]
2020-02-03 20:24:06,257 withrottle.DeviceServer? ? ? ? ? ? ? ?DEBUG - Sent: RL78]\[BA 67}|{67}|{S]\[BA 78}|{78}|{S]\[BR 1338}|{1338}|{L]\[BR 1350}|{1350}|{L]\[CP 5723}|{5723}|{L]\[CP 5726}|{5726}|{L]\[CSX 1303}|{1303}|{L]\[CSX 1304}|{1304}|{L]\[CSX 8058}|{8058}|{L]\[CSX 8199}|{8199}|{L]\[CSX_4042}|{4042}|{L]\[CSX_4049}|{4049}|{L]\[DCR 31452}|{1452}|{L]\[DH 7414}|{7414}|{L]\[DH 7418}|{7418}|{L]\[EMD 779}|{779}|{L]\[Korea Brass 7566}|{7566}|{L]\[LI 1500 old baseline}|{1500}|{L]\[LI 1501}|{1501}|{L]\[LI 151}|{151}|{L]\[LI 1558}|{1558}|{L]\[LI 158}|{158}|{L]\[LI 164}|{164}|{L]\[LI 172}|{172}|{L]\[LI 172 backup}|{172}|{L]\[LI 2007}|{2007}|{L]\[LI 202}|{202}|{L]\[LI 222}|{222}|{L]\[LI 224}|{224}|{L]\[LI 225}|{225}|{L]\[LI 226}|{226}|{L]\[LI 229}|{229}|{L]\[LI 254}|{254}|{L]\[LI 256}|{256}|{L]\[LI 276}|{276}|{L]\[LI 3101}|{3101}|{L]\[LI 3121}|{3121}|{L]\[LI 4137}|{4137}|{L]\[LI 4137 blowedup}|{3}|{S]\[LI 4145 New}|{4145}|{L]\[LI 4145 old baseline}|{4145}|{L]\[LI 464}|{464}|{L]\[LI 466}|{466}|{L]\[MW-418}|{628}|{L]\[MW-628}|{628}|{L]\[NJT 4428}|{4428}|{L]\[NJT 7001}|{7001}|{L]\[NYA 151}|{151}|{L]\[NYA 156}|{156}|{L]\[NYA 159}|{159}|{L]\[NYA 261}|{261}|{L]\[NYA 261(spare)}|{261}|{L]\[NYA 268}|{268}|{L]\[NYA 270}|{270}|{L]\[NYA 271}|{271}|{L]\[PKP 1028}|{1028}|{L]\[PNCX 3634}|{3634}|{L]\[PRR 88030}|{8030}|{L]\[PSX-AR 1125T}|{988}|{L]\[PW 2009}|{2009}|{L]\[PW 3902}|{3902}|{L]\[PW 4005}|{4005}|{L]\[PW 4301}|{4301}|{L]\[PW 4302}|{4302}|{L]\[QLN11004}|{11004}|{L]\[QLN11004v2}|{11004}|{L]\[QLN11005}|{11005}|{L]\[QLN11006}|{11006}|{L]\[QLN11007}|{11007}|{L]\[S057ML}|{12023}|{L]\[S079ML}|{12101}|{L]\[SignalMan Default}|{9999}|{L]\[SignalMan in Test Lab 11101}|{11101}|{L]\[SLRG 8542}|{8542}|{L]\[SNC 8524}|{8524}|{L]\[SP 4809}|{4809}|{L]\[Vaughan Black Porter}|{1001}|{L]\[William Penn}|{6}|{S? to? Unknown/fe80:0:0:0:835:6d53:56b4:41dc%7:52404 [WiThrottleServer]
2020-02-03 20:24:06,258 withrottle.DeviceServer? ? ? ? ? ? ? ?DEBUG - Track Power valid. [WiThrottleServer]
2020-02-03 20:24:06,259 withrottle.DeviceServer? ? ? ? ? ? ? ?DEBUG - Sent: PPA2? ? ? ? ? ? ? ? ? to? Unknown/fe80:0:0:0:835:6d53:56b4:41dc%7:52404 [WiThrottleServer]
2020-02-03 20:24:06,259 withrottle.DeviceServer? ? ? ? ? ? ? ?DEBUG - Turnout Controller valid. [WiThrottleServer]
2020-02-03 20:24:06,263 withrottle.DeviceServer? ? ? ? ? ? ? ?DEBUG - Sent: PTT]\[Turnouts}|{Turnout]\[Closed}|{2]\[Thrown}|{4? to? Unknown/fe80:0:0:0:835:6d53:56b4:41dc%7:52404 [WiThrottleServer]
2020-02-03 20:24:06,267 withrottle.DeviceServer? ? ? ? ? ? ? ?DEBUG - Route Controller valid. [WiThrottleServer]
2020-02-03 20:24:06,268 withrottle.DeviceServer? ? ? ? ? ? ? ?DEBUG - Sent: PRT]\[Routes}|{Route]\[Active}|{2]\[Inactive}|{4? to? Unknown/fe80:0:0:0:835:6d53:56b4:41dc%7:52404 [WiThrottleServer]
2020-02-03 20:24:06,269 withrottle.ConsistController? ? ? ? ? DEBUG - Using JMRIConsisting [WiThrottleServer]
2020-02-03 20:24:06,270 consisttool.ConsistFile? ? ? ? ? ? ? ?INFO? - Consist file does not exist.? One will be created if necessary. [WiThrottleServer]
2020-02-03 20:24:06,270 withrottle.DeviceServer? ? ? ? ? ? ? ?DEBUG - Consist Controller valid. [WiThrottleServer]
2020-02-03 20:24:06,271 withrottle.ConsistController? ? ? ? ? DEBUG - 0 consists found. [WiThrottleServer]
2020-02-03 20:24:06,271 withrottle.DeviceServer? ? ? ? ? ? ? ?DEBUG - Sent: RCC0? ? ? ? ? ? ? ? ? to? Unknown/fe80:0:0:0:835:6d53:56b4:41dc%7:52404 [WiThrottleServer]
2020-02-03 20:24:06,272 withrottle.DeviceServer? ? ? ? ? ? ? ?DEBUG - Fast Clock Controller valid. [WiThrottleServer]
2020-02-03 20:24:06,272 withrottle.DeviceServer? ? ? ? ? ? ? ?DEBUG - Sent: PFT1580761446<;>1.0? ?to? Unknown/fe80:0:0:0:835:6d53:56b4:41dc%7:52404 [WiThrottleServer]
2020-02-03 20:24:06,272 withrottle.DeviceServer? ? ? ? ? ? ? ?DEBUG - Sent: PW12080? ? ? ? ? ? ? ?to? Unknown/fe80:0:0:0:835:6d53:56b4:41dc%7:52404 [WiThrottleServer]
2020-02-03 20:24:06,273 withrottle.FacelessServer? ? ? ? ? ? ?DEBUG - Starting thread 'DeviceServer-1' [WiThrottleServer]
2020-02-03 20:24:06,273 withrottle.FacelessServer? ? ? ? ? ? ?INFO? - Creating new WiThrottle DeviceServer(socket) on port 12090, waiting for incoming connection... [WiThrottleServer]
2020-02-03 20:24:06,273 withrottle.DeviceServer? ? ? ? ? ? ? ?DEBUG - Notify Device Add [DeviceServer-1]
2020-02-03 20:24:06,274 ptionhandler.UncaughtExceptionHandler ERROR - Uncaught Exception caught by jmri.util.exceptionhandler.UncaughtExceptionHandler [DeviceServer-1]
java.lang.NullPointerException
at jmri.jmrit.withrottle.UserInterface.notifyDeviceConnected(UserInterface.java:265)
at jmri.jmrit.withrottle.DeviceServer.run(DeviceServer.java:170)
at java.lang.Thread.run(Thread.java:748)
2020-02-03 20:24:31,097 withrottle.DeviceServer? ? ? ? ? ? ? ?DEBUG - Sent: PPA1? ? ? ? ? ? ? ? ? to? Unknown/fe80:0:0:0:835:6d53:56b4:41dc%7:52404 [AWT-EventQueue-0]
2020-02-03 20:24:31,213 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path program: is /Applications/JMRI/ [main]
2020-02-03 20:24:31,214 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path preference: is /Users/davebarraza/Dropbox/JMRI/NY&A Model Railroad/ [main]
2020-02-03 20:24:31,214 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path profile: is /Users/davebarraza/Dropbox/JMRI/NY&A Model Railroad/ [main]
2020-02-03 20:24:31,214 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path settings: is /Users/davebarraza/Library/Preferences/JMRI/ [main]
2020-02-03 20:24:31,214 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path home: is /Users/davebarraza/ [main]
2020-02-03 20:24:31,214 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path scripts: is /Users/davebarraza/Dropbox/JMRI/Jython/ [main]
2020-02-03 20:24:31,544 server.WebServer? ? ? ? ? ? ? ? ? ? ? INFO? - Starting Web Server on port 12080 [WebServer]
2020-02-03 20:24:31,735 PanelPro.PanelPro? ? ? ? ? ? ? ? ? ? ?INFO? - Main initialization done [main]
2020-02-03 20:24:32,195 server.WebServer? ? ? ? ? ? ? ? ? ? ? INFO? - Starting ZeroConfService _http._tcp.local for Web Server with properties {path=/, json=5.3.0} [WebServer]
2020-02-03 20:25:00,382 withrottle.DeviceServer? ? ? ? ? ? ? ?DEBUG - Sent: PFT1580761500<;>1.0? ?to? Unknown/fe80:0:0:0:835:6d53:56b4:41dc%7:52404 [AWT-EventQueue-0]
2020-02-03 20:25:00,382 withrottle.DeviceServer? ? ? ? ? ? ? ?DEBUG - Sent: PFT1580761500<;>1.0? ?to? Unknown/fe80:0:0:0:835:6d53:56b4:41dc%7:52404 [AWT-EventQueue-0]
Locked Re: Some questions about signaling and the best way to debug the layout

 

Bob, Andy,

A typical signal mast logic xml entry consists of only the source mast and its destination masts. If the SML is manually created or modified, the user supplied blocks, turnouts, sensors and other masts will be included. The path speed is not included.

For generated SML, the blocks and turnouts are identified during start up using block routing.

The path speed is calculated using the block speeds and turnout leg speeds (based on turnout position).


Dave Sand

----- Original message -----
From: Bob Jacobsen <rgj1927@...>
To: [email protected]
Subject: Re: [jmriusers] Some questions about signaling and the best way to debug the layout
Date: Monday, February 03, 2020 5:13 PM

Thanks! I think I¡¯ve fixed the first three now.

I don¡¯t see a ¡°Max Speed¡± value in the signal mast logic stored values. Could you provide a file that has it as an example?

Bob

On Feb 3, 2020, at 2:51 PM, Andy Brown <andy.badshot@...> wrote:

Bob
A couple of things I've noticed so far:

? Blocks section is a bit messed up. The body of the table is shifted right compared to headings (system name under username etc), and there is no Username displayed.
? Routes have no user name shown
? "Memories" used as title rather than "Memory Variables", as used in tables
? No Max Speed value shown in Signal Mast Logic

Hope that helps
Andy
--
Bob Jacobsen
rgj1927@...
Locked Re: Some questions about signaling and the best way to debug the layout

 

Thanks! I think I¡¯ve fixed the first three now.

I don¡¯t see a ¡°Max Speed¡± value in the signal mast logic stored values. Could you provide a file that has it as an example?

Bob

On Feb 3, 2020, at 2:51 PM, Andy Brown <andy.badshot@...> wrote:

Bob
A couple of things I've noticed so far:

? Blocks section is a bit messed up. The body of the table is shifted right compared to headings (system name under username etc), and there is no Username displayed.
? Routes have no user name shown
? "Memories" used as title rather than "Memory Variables", as used in tables
? No Max Speed value shown in Signal Mast Logic

Hope that helps
Andy
--
Bob Jacobsen
rgj1927@...
Locked Re: Some questions about signaling and the best way to debug the layout

 

Bob
A couple of things I've noticed so far:

  • Blocks section is a bit messed up. The body of the table is shifted right compared to headings (system name under username etc), and there is no Username displayed.
  • Routes have no user name shown
  • "Memories" used as title rather than "Memory Variables", as used in tables
  • No Max Speed value shown in Signal Mast Logic

Hope that helps
Andy
Locked Re: New JMRI Version breaks my panels #4-18

 

? ? The JMRI versions you downloaded would be in the download folder.

Roger
Locked Re: New JMRI Version breaks my panels #4-18

 

The bottom of panel files says what version of JMRI was used to write them.

Bob

On Feb 3, 2020, at 1:05 PM, rzeollaorcl <robert.zeolla@...> wrote:

I do not know what version I upgraded from. And cannot find out unless I restore the backups. Is there another way to locate that information?
--
Bob Jacobsen
rgj1927@...
Locked Re: Some questions about signaling and the best way to debug the layout

 

Thanks! (That¡¯s the same version as the mail I just sent, sorry for the confusion)

It was originally created to be a printable form, for people who wanted to pop something in a notebook.

Let me know if you notice any issues, missing parts, etc.

Bob

On Feb 3, 2020, at 1:01 PM, Andy Brown <andy.badshot@...> wrote:

Bob
I've tried it in JMRI.4.19.3ish+jenkins+20200203T1929Z+Rb4f477330b and my panel xml displays fine now.

I think having a more readable format will encourage me to add comments against some of the items. That should help me and others understand it better when looking at in the future.

Thanks for the quick fix!
Andy
--
Bob Jacobsen
rgj1927@...
Locked Re: Some questions about signaling and the best way to debug the layout

 

Could you try this one please?



Bob

On Feb 3, 2020, at 7:47 AM, Andy Brown <andy.badshot@...> wrote:

Bob
Unfortunately the work-around didn't work for me. When used on the 'test' file (v29) it yielded the same error. On my latest panel (v36) it produced 'gibberish' - no formatting at all, just a long list of the items. Here's an excerpt from the start of what was produced:

4 19 3 ish MS+2020 RS-X-XoverStraight MS+2021 RS-X-XoverLoopAB MS+2022 RS-X-XoverLoopCD MS+2023 RS-X-XoverInnerSwap MS+2024 RS-X-XoverOuterSwap MS+2031 RS-1-MainA Route Set MS+2032 RS-1-MainB MS+2033 RS-2-MainC MS+2034 RS-2-MainD MS+2100 KL-1-All MS+2101 KL-1-1 Keypad LED MS+2102 KL-1-2 MS+2103 KL-1-3 MS+2104 KL-1-4 MS+2105 KL-1-5 MS+2106 KL-1-6 MS+2107 KL-1-7.......

I'm not in a hurry for this, so I'll give it another try when the new JMRI version is available.

Thanks for quick response
Andy
--
Bob Jacobsen
rgj1927@...
Locked Re: New JMRI Version breaks my panels #4-18

 

I do not know what version I upgraded from.? And cannot find out unless I restore the backups.? Is there another way to locate that information?
Locked Re: Some questions about signaling and the best way to debug the layout

 

Bob
I've tried it in JMRI.4.19.3ish+jenkins+20200203T1929Z+Rb4f477330b and my panel xml displays fine now.

I think having a more readable format will encourage me to add comments against some of the items. That should help me and others understand it better when looking at in the future.

Thanks for the quick fix!
Andy
Locked Re: Signal heads losing SSL during power down and up

John
 

Ken,
Thanks for the information. I have Panel Pro set up to ask for a file selection when it is booted. I had the file name issue earlier and found that forcing me to make the selection each time eliminated that problem. Plus, I use simulator for offline programming and configuration so when I boot Panel Pro, I have to make at selection to be sure I get into the correct file.

I think the original problem was related to signal heads. I had programmed some of them incorrectly and was not able to delete them from the signal head table. They were SE8C 4 aspect heads and would not go away. I first tried to block them out by removing the user name and then re-entered new heads. I had hoped this method would work as the set signals at turnout function uses the user names and not the system names. However, that was when the problems started. I eventually went into the XML file and deleted the heads manually and that seems to have fixed the problem.

I am not sure why the delete button in the signal head table did not work.

I appreciate your time,

John


On Mon, Feb 3, 2020 at 9:16 AM KEN <boomer17@...> wrote:
John,
I think Ken meant to say Store instead of save. Some how, for whatever reason, the save command has been changed back to Store.




On 2/2/2020 12:31 PM, Ken Cameron wrote:
John,

The most frequent issue is you make a change on the panel and either fail to
save it before shutting down or you save it to (usually a new) one filename
but don't update the startup and load the old filename instead. Either way
next time you run; you don't have those last changes.

-Ken Cameron, Member JMRI Dev Team

Locked Re: Cannot connect a second time, Decoder Pro

[email protected]
 

On Mon, Feb 3, 2020 at 01:44 AM, <gjs1010@...> wrote:
Actually I downloaded Digi-IPL some time ago. ?I get COM port errors when I try to use it and like all COM errors in this project, I am unable to find a solution.

I think I'm done. I've easily spent 10+ hours trying to get computers talking to the PR3. I can't get the Mac or the PC to talk to it. ?I just don't have the knowledge to debug this.I am a computer user not a computer expert and the later is needed. I'll revisit if I can locate a local expert in COM issues, as Decoder Pro is most impressive when it can be accessed. Thanks again, sorry to use so much time for no result. ?
As you are encountering issues with both Soundloader AND DiGIIPL, I think it is a safe bet to call Digitrax for help. It works, then it does not work points to a PR3 or USB cable fault. Cable could be intermittent connection. Not a device driver issue since it did work for a time. Drivers are not in the habit of being temperamental.? Hardware can be temperamental.?

Suggesting a SPROG ??? ?? How does one Ioad SPJ files to a? Digitrax Sound decoders with a SPROG ?? You could suggest a SPROG to all those ESU users to replace there LokProgrammer.?
SPROG is not the " fix all " solution. depends on the case.

Current and updated WIn10 installs do not require you source device drivers for the PR3/PR4,? Windows 10 now has them included.? If WIn 10 can not find a proper driver, then you go to Digitrax.? But you certainly need to look at updating your Win10 Install.

Marc
Locked Re: New JMRI Version breaks my panels #4-18

 

It would be better to copy and paste the system console here.

What version did you update from?

--
Peter Ulvestad

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

Locked Re: Cannot connect a second time, Decoder Pro

 

¿ªÔÆÌåÓý

How about considering just getting a Sprog and start fresh ? I know nothing about A PR anything but I do Know I have been using sprog and decoder pro for about fifteen years and have upgraded many times as computers and operating systems either give up or become non supported. Currently windows 10 64 bit and thankfully working fine with all my roster intact. The sprog comes with everything you need to get up and running. Rick.


On 2/3/2020 1:44 AM, gjs1010@... wrote:

Actually I downloaded Digi-IPL some time ago. ?I get COM port errors when I try to use it and like all COM errors in this project, I am unable to find a solution.

I think I'm done. I've easily spent 10+ hours trying to get computers talking to the PR3. I can't get the Mac or the PC to talk to it. ?I just don't have the knowledge to debug this.I am a computer user not a computer expert and the later is needed. I'll revisit if I can locate a local expert in COM issues, as Decoder Pro is most impressive when it can be accessed. Thanks again, sorry to use so much time for no result. ??
Locked Re: Some questions about signaling and the best way to debug the layout

 

Bob
Unfortunately the work-around didn't work for me. When used on the 'test' file (v29) it yielded the same error. On my latest panel (v36) it produced 'gibberish' - no formatting at all, just a long list of the items. Here's an excerpt from the start of what was produced:

4 19 3 ish MS+2020 RS-X-XoverStraight MS+2021 RS-X-XoverLoopAB MS+2022 RS-X-XoverLoopCD MS+2023 RS-X-XoverInnerSwap MS+2024 RS-X-XoverOuterSwap MS+2031 RS-1-MainA Route Set MS+2032 RS-1-MainB MS+2033 RS-2-MainC MS+2034 RS-2-MainD MS+2100 KL-1-All MS+2101 KL-1-1 Keypad LED MS+2102 KL-1-2 MS+2103 KL-1-3 MS+2104 KL-1-4 MS+2105 KL-1-5 MS+2106 KL-1-6 MS+2107 KL-1-7.......

I'm not in a hurry for this, so I'll give it another try when the new JMRI version is available.

Thanks for quick response
Andy
Locked Re: Signal heads losing SSL during power down and up

 

¿ªÔÆÌåÓý

John,
I think Ken meant to say Store instead of save. Some how, for whatever reason, the save command has been changed back to Store.




On 2/2/2020 12:31 PM, Ken Cameron wrote:

John,

The most frequent issue is you make a change on the panel and either fail to
save it before shutting down or you save it to (usually a new) one filename
but don't update the startup and load the old filename instead. Either way
next time you run; you don't have those last changes.

-Ken Cameron, Member JMRI Dev Team

Locked Re: Some questions about signaling and the best way to debug the layout

 

Sorry for the problem, thanks for the file to confirm. There will be a fix later today.

In the meantime, if you change this line near the top of the file from

<?xml-stylesheet href="/xml/XSLT/panelfile-2-9-6.xsl" type="text/xsl¡±?>

I hope it will bypass the problem.

Debugging depends a lot on what you¡¯re using for a browser, as the formatting is done right in the browser.

Bob



On Feb 3, 2020, at 12:34 AM, Andy Brown <andy.badshot@...> wrote:

Hi Bob
This looks very useful and I hadn't realised it was built in.

Is there an easy way to debug it when it fails? I have a panel that simply returns "Error loading stylesheet: Parsing an XSLT stylesheet failed."

An example failing panel can be found in /g/jmriusers/files/ProblemsBeingWorkedOn/Andy%20Brown%20-%20161045/MavinsHillsSMFailure.jmri.zip

I tried to view it using a recent dev release JMRI.4.19.3ish+jenkins+20200203T0523Z+Rfc1deeba0 on Ubuntu 19.04 using Firefox 72.02 with java 11.0.6 (en).

--
Bob Jacobsen
rgj1927@...
Locked Re: back up to another comuter #backup

 

Dave,
Is this what your asking for?

User Files Location: C:\Users\Mike Swederska\Dropbox\JMRI\
Roster Location: C:\Users\Mike Swederska\Dropbox\JMRI\
Profile Location: C:\Users\Mike Swederska\JMRI\Meramec_Valley_Lines.jmri\
Settings Location: C:\Users\Mike Swederska\JMRI\
Current Config file:C:\Users\Mike Swederska\JMRI\Meramec_Valley_Lines.jmri\ProfileConfig.xml
Scripts Location: C:\Program Files (x86)\JMRI\jython\
Program Location: C:\Program Files (x86)\JMRI
Temp Files Location:C:\Users\MIKESW~1\AppData\Local\Temp\
Log Files Location: C:\Users\Mike Swederska\JMRI\log\
? C:\Users\Mike Swederska\JMRI\log\messages.log
? C:\Users\Mike Swederska\JMRI\log\messages.log.1
? C:\Users\Mike Swederska\JMRI\log\messages.log.2
? C:\Users\Mike Swederska\JMRI\log\session.log


Mike Swederska
Locked Re: Decoder Pro Not Seeing my Locomotive

 

Hi Bill.

Glad you were able to program the decoder so leave well alone.
Do you have a catalogue number for the Thomas loco in question as a matter of interest ?

Regards.
Tony.
Locked Re: Cannot connect a second time, Decoder Pro

 

¿ªÔÆÌåÓý

This means you don¡¯t have the PR3 software installed so that the computers see it on the Com port. Look in device manager to see this.?

David Klemm
11 PRO Max

From: [email protected] <[email protected]> on behalf of gjs1010@... <gjs1010@...>
Sent: Monday, February 3, 2020 12:44:18 AM
To: [email protected] <[email protected]>
Subject: Re: [jmriusers] Cannot connect a second time, Decoder Pro
?
Actually I downloaded Digi-IPL some time ago. ?I get COM port errors when I try to use it and like all COM errors in this project, I am unable to find a solution.

I think I'm done. I've easily spent 10+ hours trying to get computers talking to the PR3. I can't get the Mac or the PC to talk to it. ?I just don't have the knowledge to debug this.I am a computer user not a computer expert and the later is needed. I'll revisit if I can locate a local expert in COM issues, as Decoder Pro is most impressive when it can be accessed. Thanks again, sorry to use so much time for no result. ??
72241 - 72260 of 240577