开云体育

After sending the reset value, doesn't power have to be removed from the decoder by tilting the engine?

David Klemm
Sent from my iPhone 7 Plus
________________________________
From: jmriusers@... <jmriusers@...> on behalf of terryintexas7@... [jmriusers] <jmriusers@...>
Sent: Thursday, July 27, 2017 2:02:14 PM
To: jmriusers@...
Subject: Re: [jmriusers] Re: Reset Fail



I have no problem programming other CVs
it just won't do a reset
The power pax is working fine Peter
I took the locos to my work bench where i have my old Zephyr DCS50
and used blast mode there to reset them

I can do speed curves ,momentum and sound levels
Any thing else

Jmri won't do a reset

Terry
Visit My Web site@


-----Original Message-----
From: ulvestad@... [jmriusers] <jmriusers@...>
To: jmriusers <jmriusers@...>
Sent: Thu, Jul 27, 2017 1:41 pm
Subject: [jmriusers] Re: Reset Fail

Does it work using JMRI with the zephyr in blast mode? Or in regular mode without the power pax?

Power Pax are unreliable, my club tried 2 with no luck and now we exclusively use Soundtraxx PTB-100s.

Peter



[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]

I have no problem programming other CVs
it just won't do a reset
The power pax is working fine Peter
I took the locos to my work bench where i have my old Zephyr DCS50
and used blast mode there to reset them

I can do speed curves ,momentum and sound levels
Any thing else

Jmri won't do a reset





Terry
Visit My Web site@

In a message written on Wed, Jul 26, 2017 at 05:34:22PM +0000, stevedavis@... [jmriusers] wrote:

Thank you. In my case, I'm using the LocoBuffer USB Rev-n so I'm afraid that's not my issue. Was worth a try though!

That's fascinating. I'm not saying it's impossible, but I beat one
up pretty bad and could never make it lock up. I suggest e-mailing
RR-CirKits support, they are good people and will want to replace
it if defective, and/or investigate if this is a new problem.

Note much of this is a timing issue on the loconet, so it's possible
your LocoBuffer is triggered by some other component on the LocoNet
I didn't have for testing.

--
Leo Bicknell - bicknell@...
PGP keys at

Does it work using JMRI with the zephyr in blast mode? Or in regular mode without the power pax?

Power Pax are unreliable, my club tried 2 with no luck and now we exclusively use Soundtraxx PTB-100s.

Peter

Billybob,


Thank you. I have spent a lot of time in vain searching through the JMRI documents to attempt to find a way to turn this functionality off. At least I don't need to keep searching!


I may be able to handle this by not defining these as "SE8c" signal heads, just generic 4-aspect heads, and then manually enter each address for each aspect of each head. I think that will work (as long as JMRI allows 2 turnout addresses per head, which as you know the SE8c requires).


Otherwise I might use virtual signals and have Logix generate the aspects.


At least I can stop searching for something that doesn't exist!


You have been extremely helpful through this, thank you.


Sincerely,


Steve
KCS 3rd Sub
Coweta, OK

JMRI will only bridge the events you place logic to connect them. Each
connection is treated as separate. So a Logix that watch a sensor on one
connection could then drive a turnout or sensor on the other connection.



But there are bridges available or look at the code from Robert Heller at
deepsoft.com. I seem to recall he has a number of tools like that for LCC.



-Ken Cameron, Member JMRI Dev Team

www.jmri.org

www.fingerlakeslivesteamers.org

www.cnymod.com

www.syracusemodelrr.org

Jeff,



Normally I find a finger across the rails will trip the detector, sometimes
needing to be slightly wet.



-Ken Cameron, Member JMRI Dev Team

www.jmri.org

www.fingerlakeslivesteamers.org

www.cnymod.com

www.syracusemodelrr.org

Steve,

This behavior is likely entirely consistent with JMRI's basic behavior for JMRI "signal heads" which are configured as controlled by an SE8c.

JMRI does not have support for any SE8c mode other than "fourth aspect dark".

When you change the SE8c mode to "fourth aspect flashing red", JMRI doesn't know that. It _assumes_ that it must "manually" flash the signal head. So JMRI alternately sends the turnout command for "RED" then the turnout command for the "Fourth Aspect", which it thinks is "dark". But the SE8c is _independently_ flashing the RED LED in the head, using its own timings. So you will get a JMRI phase of "RED" (from the "RED" turnout command) and then a JMRI phase of "Fourth Aspect". Exactly what you see at the LED depends on the SE8C flashing "phase", so you should expect to get odd patterns on the Red LED.

I cannot envision any way to get around this problem without changes in JMRI's signal code.

Regards,
Billybob

I have hooked up a CT-detector ( RR-Cirkits ) to a watchman board. The detector is monitoring a power wire off the PSX to the track. Is there a way of testing the detector with a meter....????
Thanks
Jeff Zeleny

Ok Dave. Thanks.





Donald Dillaby

27 Palisade Dr

Nashua, NH 03062-2119

603-888-2766

603-305-5523







From: jmriusers@... [mailto:jmriusers@...]
Sent: Thursday, July 27, 2017 1:37 PM
To: jmriusers@...
Subject: [jmriusers] Re: JMRI 4.8 is available for download





Donald,

No. The file I modified for was an appearance file for SPTCO-1930 signal
system. Those changes are included in 4.8.


Dave Sand

Donald,

No. The file I modified for was an appearance file for SPTCO-1930 signal system. Those changes are included in 4.8.


Dave Sand

Hi


I upgraded to v4.8 but ever since have not been able to get my control panel to load without using TurnOffXmlValidation.py in the startup folder.


the error message says
Exception: org.jdom2.input.JDOMParseException: error on line 693: cvc-complex-type.3.2.2: Attribute 'firstTurnoutExit' is not allowed to appear in element 'slipturnouticon'.


the line of code is as follows:


<slipturnouticon turnoutType="threeWay" firstTurnoutExit="lower" x="0" y="0" level="7" forcecontroloff="false" hidden="no" positionable="true" showtooltip="true" editable="true" tristate="false" class="jmri.jmrit.display.configurexml.SlipTurnoutIconXml">



I have tried creating a new panel with just a three way point but get exactly the same error.
any help would be appreciated.


Brian

Hello,


I have experienced this "problem" in 4.5.x. I did some searching within this forum and read that this problem might be resolved in 4.7.1, so I upgraded to 4.7.1 Still getting errors (see below). No Routes have been created in Routes nor LRoutes tables within this panel. HOWEVER, the BLOCKS table IS populated. Running Win 7 in SIM mode. I can upload the entire panel entire file if needed, but am hoping these samples might provide a clue.


Is this a normal condition or does anyone have any suggestions as to what needs to be be done to stop messages? Am I required to build Routes? Or, is the fact that the BLOCKS table is populated, the "errors" are coming from that? If the BLOCKS table is causing these messages, can I delete the block assignments?


Thanks in advance,
Wain Schroeder


<<< Normal startup without panels loaded: >>>



2017-07-27 11:14:38,066 util.Log4JUtil INFO - * JMRI log ** [main]
2017-07-27 11:14:38,086 util.Log4JUtil INFO - This log is appended to file: C:&#92;Users&#92;WLS&#92;JMRI&#92;log&#92;messages.log [main]
2017-07-27 11:14:38,086 util.Log4JUtil INFO - This log is stored in file: C:&#92;Users&#92;WLS&#92;JMRI&#92;log&#92;session.log [main]
2017-07-27 11:14:38,106 apps.Apps INFO - PanelPro version 4.7.1-R1b7dd65 starts under Java 1.8.0_31 on Windows 7 amd64 v6.1 at Thu Jul 27 11:14:38 EDT 2017 [main]
2017-07-27 11:14:44,367 apps.Apps INFO - Starting with profile PanelPro.3f4800f9 [main]
2017-07-27 11:14:44,757 node.NodeIdentity INFO - Using jmri-3C4A924E5CC0-3f4800f9 as the JMRI Node identity [main]
2017-07-27 11:14:45,327 simulator.SimulatorAdapter INFO - NCE Simulator Started [Nce Simulator]
2017-07-27 11:14:45,397 nce.NceConnectionStatus INFO - NCE EPROM revision = 6.2.1 [AWT-EventQueue-0]
2017-07-27 11:14:46,137 hexfile.LnHexFilePort INFO - LocoNet Simulator Started [Thread-12]
2017-07-27 11:14:47,397 apps.PerformScriptModel INFO - Running script C:&#92;Program Files (x86)&#92;JMRI&#92;jython&#92;SetAllTurnoutsClosed.py [main]
2017-07-27 11:14:47,407 script.JmriScriptEngineManager INFO - ECMAScript ECMA - 262 Edition 5.1 is provided by Oracle Nashorn 1.8.0_31 [main]
2017-07-27 11:14:47,407 script.JmriScriptEngineManager INFO - python 2.7 is provided by jython 2.7.0 [main]
0 turnouts found, 0 changed to CLOSED
2017-07-27 11:14:52,548 util.FileUtilSupport INFO - File path program: is C:&#92;Program Files (x86)&#92;JMRI&#92; [main]
2017-07-27 11:14:52,548 util.FileUtilSupport INFO - File path preference: is C:&#92;Users&#92;WLS&#92;JMRI&#92; [main]
2017-07-27 11:14:52,548 util.FileUtilSupport INFO - File path profile: is C:&#92;Users&#92;WLS&#92;JMRI&#92;PanelPro&#92; [main]
2017-07-27 11:14:52,548 util.FileUtilSupport INFO - File path settings: is C:&#92;Users&#92;WLS&#92;JMRI&#92; [main]
2017-07-27 11:14:52,548 util.FileUtilSupport INFO - File path home: is C:&#92;Users&#92;WLS&#92; [main]
2017-07-27 11:14:52,548 util.FileUtilSupport INFO - File path scripts: is C:&#92;Program Files (x86)&#92;JMRI&#92;jython&#92; [main]



<<< sample errors after panels loaded (same heading as above): >>>



2017-07-27 11:20:13,332 layoutEditor.LayoutEditor INFO - Font size: 9.0 [AWT-EventQueue-0]
2017-07-27 11:20:16,308 layoutEditor.LayoutEditor INFO - Font size: 9.0 [AWT-EventQueue-0]
2017-07-27 11:20:23,937 layoutEditor.LayoutBlock INFO - From LS125, no routes returned for getRouteByNeighbour(LS124) [AWT-EventQueue-0]
2017-07-27 11:20:23,939 layoutEditor.LayoutBlock INFO - From LS121, no routes returned for getRouteByNeighbour(LS124) [AWT-EventQueue-0]
2017-07-27 11:20:23,940 layoutEditor.LayoutBlock INFO - From LS128, no routes returned for getRouteByNeighbour(LS124) [AWT-EventQueue-0]
2017-07-27 11:20:23,940 layoutEditor.LayoutBlock INFO - From LS128, no routes returned for getRouteByNeighbour(LS124) [AWT-EventQueue-0]
2017-07-27 11:20:23,941 layoutEditor.LayoutBlock INFO - From LS125, no routes returned for getRouteByNeighbour(LS124) [AWT-EventQueue-0]
2017-07-27 11:20:23,955 layoutEditor.LayoutBlock INFO - From LS128, no routes returned for getRouteByNeighbour(LS124) [AWT-EventQueue-0]
2017-07-27 11:20:23,956 layoutEditor.LayoutBlock INFO - From LS121, no routes returned for getRouteByNeighbour(LS124) [AWT-EventQueue-0]
2017-07-27 11:20:23,956 layoutEditor.LayoutBlock INFO - From LS115, no routes returned for getRouteByNeighbour(LS124) [AWT-EventQueue-0]
2017-07-27 11:20:24,098 layoutEditor.LayoutBlock INFO - From LS93, no routes returned for getRouteByNeighbour(LS96) [AWT-EventQueue-0]
2017-07-27 11:20:24,098 layoutEditor.LayoutBlock INFO - From LS93, no routes returned for getRouteByNeighbour(LS96) [AWT-EventQueue-0]
2017-07-27 11:20:24,306 layoutEditor.LayoutBlock INFO - From CY-WB-5, no routes returned for getRouteByNeighbour(CY-Wst-Ldr) [AWT-EventQueue-0]
2017-07-27 11:20:24,307 layoutEditor.LayoutBlock INFO - From CY-WB-4, no routes returned for getRouteByNeighbour(CY-Wst-Ldr) [AWT-EventQueue-0]
2017-07-27 11:20:24,308 layoutEditor.LayoutBlock INFO - From Block CY-WB-3, no routes returned for getRouteByNeighbour(CY-Wst-Ldr) [AWT-EventQueue-0]
2017-07-27 11:20:24,308 layoutEditor.LayoutBlock INFO - From CY-EB-1, no routes returned for getRouteByNeighbour(CY-Wst-Ldr) [AWT-EventQueue-0]
2017-07-27 11:20:24,309 layoutEditor.LayoutBlock INFO - From CY-WB-5, no routes returned for getRouteByNeighbour(CY-Wst-Ldr) [AWT-EventQueue-0]
2017-07-27 11:20:24,309 layoutEditor.LayoutBlock INFO - From CY-EB-1, no routes returned for getRouteByNeighbour(CY-Wst-Ldr) [AWT-EventQueue-0]
2017-07-27 11:20:24,310 layoutEditor.LayoutBlock INFO - From Block CY-WB-3, no routes returned for getRouteByNeighbour(CY-Wst-Ldr) [AWT-EventQueue-0]
2017-07-27 11:20:24,310 layoutEditor.LayoutBlock INFO - From CY-WB-4, no routes returned for getRouteByNeighbour(CY-Wst-Ldr) [AWT-EventQueue-0]
2017-07-27 11:20:24,343 layoutEditor.LayoutBlock INFO - From LS87, no routes returned for getRouteByNeighbour(LS84) [AWT-EventQueue-0]
2017-07-27 11:20:24,356 layoutEditor.LayoutBlock INFO - From CY-WB-5, no routes returned for getRouteByNeighbour(CY-Wst-Ldr) [AWT-EventQueue-0]
2017-07-27 11:20:24,356 layoutEditor.LayoutBlock INFO - From CY-WB-4, no routes returned for getRouteByNeighbour(CY-Wst-Ldr) [AWT-EventQueue-0]
2017-07-27 11:20:24,357 layoutEditor.LayoutBlock INFO - From Block CY-WB-3, no routes returned for getRouteByNeighbour(CY-Wst-Ldr) [AWT-EventQueue-0]
2017-07-27 11:20:24,357 layoutEditor.LayoutBlock INFO - From CY-EB-1, no routes returned for getRouteByNeighbour(CY-Wst-Ldr) [AWT-EventQueue-0]



<<< many more lines similar to the above, only different
No actual ERROR is indicated, just INFO. Is this normal?

Bob,


At the NMMRC, I upgraded our 2 PCs last night to 4.8. Initial test last night show all is well.


PC1 is our programming track PC where we just use decoder pro. That one had 4.5.2 prior to the upgrade. No issues after the upgrade.


PC2 is our panel PC. That one was on 4.7.7 prior to the upgrade to 4.8. We will leave that running for a couple weeks to make sure all is well before taking a test release.


I take all updates on my home laptop running the club panel as an initial test prior to updating the club PCs. In other words my laptop is the QA environment to the club PCs.


Thanks for all the hard work the JMRI developers are doing to improve and add to JMRI.


Club layout stats


DCS240 qty 1 (Command Station Only)
DB100/200's qty 7

LNRP's qty 14 (Limiting 8 Quads per leg. The 35+ UP-5's are divided into 3 groups across 3 legs.)
UP-5's qty 35
LocoBuffer qty 1
UR-91's qty 2
UR-92's qty 4
BDL168's qty 6
TAM Valley Super Quads w/Signal qty 11
TAM Valley Super Quads turnouts qty 50



David

________________________________
From: jmriusers@... <jmriusers@...> on behalf of Bob Jacobsen rgj1927@... [jmriusers] <jmriusers@...>
Sent: Monday, July 24, 2017 9:40 AM
To: mopacmike@... [jmriusers]
Subject: [jmriusers] JMRI 4.8 is available for download



We are very pleased to announce that the 4.7 series of JMRI test
releases has resulted in a version that's good enough to be
recommended for general use, including by new users. We're therefore
making that version, "Production release 4.8", available for download
today.

Note: this version of JMRI, along with future ones, will require that
you have Java 1.8 or later.

There have been hundreds of updates, new features and bug fixes since
version 4.6 came out six months ago. For more information,
please see the release note:

<>

The release note also contains the download links for Mac OS X, Linux
and Windows. (That's our subtle way of trying to get you to read the
note).

--
Bob Jacobsen
rgj1927@...

Dave:



Is that the file you modified for me for use with JMRI 4.6? I have yet to
download version 4.8.





Donald Dillaby

27 Palisade Dr

Nashua, NH 03062-2119

603-888-2766

603-305-5523







From: jmriusers@... [mailto:jmriusers@...]
Sent: Thursday, July 27, 2017 10:54 AM
To: jmriusers@...
Subject: [jmriusers] Re: JMRI 4.8 is available for download





Fraser,

With 4.8 installed, search your ENTIRE machine for file name
signalmasts-2.9.6.xsd


The number of lines in the file should be around 406.


If you have more than 1 file, you have another JMRI install somewhere. The
4.6 version of that file has 253 lines. If JMRI happens to use an old
version of the file, that would explain the validation errors.


If you only have one occurrence of the file, but the size is wrong, maybe
the Synology is replacing it.


Dave Sand

Fraser,

With 4.8 installed, search your ENTIRE machine for file name signalmasts-2.9.6.xsd


The number of lines in the file should be around 406.


If you have more than 1 file, you have another JMRI install somewhere. The 4.6 version of that file has 253 lines. If JMRI happens to use an old version of the file, that would explain the validation errors.


If you only have one occurrence of the file, but the size is wrong, maybe the Synology is replacing it.


Dave Sand

Just upgraded to Production Version 4.8 all works ok except as in the past i still can't do a reset on a TCS Wow Decoder

I tried a Wow version 2 on my programing track Using my DC51 Zephyr and my Power Pax Booster
and get a Unknown error 307 message
So i tried another loco and got the same message

I was able to reset both decoders by using Blast Mode on my Zephyr and writing a value of 2 to CV 8

I was told in the past that perhaps the write was too fast

Has this problem ever been addressed ?

I have no problems doing other programming writes
I haven't tried any Reads



Terry
Visit My Web site@

Rodney,


I realize you're the author of CATS and not JMRI, but I have to admit I'm stumped here. I don't have any of the Software Flash boxes checked within CATS, and I can't figure out where in JMRI I can go to turn software flashing off (or on for that matter). Even when adding a new signal head, in the "Add New" dialog, there is nothing about software flashing.


Right now if I set my SE8c to 4th aspect = Flashing Red, I get a weird result: a "flash" between red and flashing red - so ostensibly in place of dark the software - whether CATS or JMRI I don't know - is sending the flashing red aspect. Looks really strange and still eats up the bandwidth because the commands are sent frequently.


Any advice - from you or any other Se8c/JMRI gurus out there?


Thank you all in advance,


Steve
KCS 3rd Sub

Hi Egbert

That "MT " that you found is exactly the same as that found by Dave Sand a couple of days ago. I removed it then and that changed the line number of the "Outputs" error when loading. I didn't understand where it came from before but the fact that it has come back again could be due to one of two things: 1) JMRI is introducing it for some reason or 2) it is possible that I have reintroduced it when I downloaded the one that I uploaded and with all that's going on forgot to remove it again. Probably the latter. It is/was the very first entry in the turnouts section.

I have another computer in the loft that I will stop the Synology synchronisation on and attempt the complete removal of JMRI from and do as clean an install as I can of 4.8 and then try making up the "straight" panel again and see how that behaves.

Cheers

Fraser

Sorry to reply to my own, but I just had another thought. This may be a misunderstanding of the C/MRI protocol.

The NS (number of bytes of board configuration, e.g. ceiling(n_boards/4)) is sent as a raw integer, not an ASCII character. As such, it can have values that looks like protocol characters. In that case, a DLE (a.k.a. DL or 0x10) character is sent before that.

When NS is 3, that’s the case. It’ll be sent as x10 0x03, i.e. DL 03. That’s completely normal and correct AFAIK.

Unfortunately, the C/MRI monitor doesn’t understand that when decoding the message. So get lines like this:

[41 49 58 00 00 10 03 A5 5A 09] Init ua=0 type=X DL=0 NS=16 CT: 3 a5 5a 9

That’s the right raw data, but the wrong interpretation of it.

I’ll fix this.

But, unfortunately, that means this isn’t the cause of your problem. I’m not sure what’s going wrong there.

Bob

On Jul 26, 2017, at 12:26 AM, scott.rose@... [jmriusers] <jmriusers@...> wrote:

The SUSIC is set up with 24 bit cards in the following format:-


OOOO OOII IIII


My interpretation of the initialisation sequenece is ua=0, Type= N, NS=3, CT = aa 5a 55


I have checked via the CMRI monitor for this sequence and have found that for 4.6, 4.7.4 & 4.8 the sequence is ua=0, Type=N, NS=16, DL=10, CT= 3 aa 5a 55 ????? I would have expected NS to be 3. It appears to have added the correct NS to the CT sequence. The baud rate on the SUSIC matches the preferences entry and there is only one entry for the CMRI.

--
Bob Jacobsen
rgj1927@...