jmriusers@groups.io

Hi Bob

Thanks for looking at this but having looked at the schema for matrix signal mast and checked which line it was that was causing the problem it is the bit I've copied that is where the problem is. It definitely says matrixsignalmastxml for the class in the first line and the order of the sections within ny quoted bit matches the requirements of the schema.

Line 3107 is the problem and that is the sixth line of my excerpt

        <output matrixCol="output1">CW12 Ch1</output>

I've searched through the file and the only places where output or outputs occurs is within my matrix signal mast definition section. I've dumped my complete layout editor xml file at

By the way I'm not in a hurry for the answer so you can dedicate your time to other more serious problems.

Thanks

Fraser

Re: JMRI 4.8 is available for download

[email protected]

#138680

I can't find your email.  

You can email me at mikeca@... or  let me to get the file to you.

Thanks,
Michael Carney
www.papacarney.com

PR3 not communicating after 4.8 upgrade

#138708

Hi, I am new to the group, and unfortunately have a problem I am hoping others may have solved or at least get advice from those more computer literate than myself. I did not see a similar issue in recent posts.
I have used Decoder Pro solely for programming locomotives on a standalone track since I converted to DCC in 2013. I have a Digitrax system and hence use the PR3 as a standalone programmer, and successfully used it as recently as this past weekend. Today I downloaded version 4.8 release after reading the release notes, and now serial port COM3 which is where my PR3 connects is not recognized, and Decoder Pro says no programmer is connected. I use a windows 7 operating system so thought none of the warnings noted for Linux or Mac should apply.
Did I miss something? Any advice would be appreciated. Thank you

Tim

Re: JMRI 4.8 is available for download

[email protected]

#138679

Hi Dave,

For some reason my file upload button is not on the file screen.  It was there earlier but it is not there now.  Any suggestions on how to get it back.

I will try and emailing you my config file.

Michael Carney

Re: JMRI 4.8 is available for download

#138678

I don’t think that particular element is the problem. For one thing, it’s a regular mast:  Matrix masts are (I think) stored as <matrixsignalmast> elements.  Could you show an example of that?  There’s also a line number in the error message that can (sometimes) help.

The XML format for <signalmast> says that it wants to see the order (some are optional) systemName, userName, comment, properties, unlit, outputs, bitStrings, disabledAspects.

See  and look for the section on SignalMastType

Matrix masts expect that same order inside their <matrixsignalmast>

Bob

On Jul 24, 2017, at 1:00 PM, fraser@... [jmriusers] <jmriusers@...> wrote:

I appear to be having problems now with 4.8 with my matrix signal mast entries that have been working fine in 4.6 but now I'm getting "Invalid content was found starting with element 'outputs'. One of '{systemName, disabledAspects}' is expected. As can be seen below the disabled aspects are there but possibly in a different order than the new version is expecting. I had recently been chasing out problems with speed definitions as my signal aspects file was incorrect and after getting all that sorted the layout editor file was loading without problems showing in the system console. As guided by Bob I have had a look at the release notes but there doesn't seem to be any mention of this being a problem. Perhaps with it being comparatively new there are not so many people using it yet. Now I sit here looking at it, it seems quite strange that it is necessary to have all the disabled aspects listed in the bitStrings section. I guess there is a reason but I can't imagine what that would be.

The first definition with "outputs" and that is for the last signal before a set of terminus roads with buffer stops looks like--
Bob Jacobsen
rgj1927@...

Re: Crossing in layout editor

#138677

While I agree that frog juicers can be used in cases where simple logic
should suffice, that is not true in all cases. For example, I have several
gauge separation turnouts on my layout, where dual gauge track splits into
separate tracks of each gauge. These have no moving parts, so there is no
need for a control switch. However, they do have a frog that needs its
polarity switched due to the gauge of the train. (Some have a second frog,
but that one doesn't need its polarity switched.) A frog juicer is the
easiest way to change the polarity of these frogs.

Frog juicers can also eliminate the need for controls for track crossings.

Dave Heine
Easton, PA

Show quoted text

On Mon, Jul 24, 2017 at 3:13 PM, fraser@... [jmriusers] <
jmriusers@...> wrote:

David

A frog juicer is the tech geeks expensive way of solving a problem that
doesn't really exist and everytime it activates, the spark caused by the
short will slowly but surely pit the rail surface and lead to dirt buildup
and poor running. As has been pointed out in other responses here the
situations where the polarity of the frogs have to be set one way or the
other are easily defined and logix can be used to drive a turnout(s) to
energise relay(s) to switch the correct polarity to each frog. It's very
mundane doing it that way but far better in the long run. The same thing
applies to reversing loops and triangular junctions where many people think
a juicer is the only solution. In fact there can really be no justification
for ever using a juicer.

Fraser

Re: Crossing in layout editor

#138676

On Mon, Jul 24, 2017 at 3:13 PM, fraser@... [jmriusers] <
jmriusers@...> wrote:

David

A frog juicer is the tech geeks expensive way of solving a problem that
doesn't really exist and everytime it activates, the spark caused by the
short will slowly but surely pit the rail surface and lead to dirt buildup
and poor running. As has been pointed out in other responses here the
situations where the polarity of the frogs have to be set one way or the
other are easily defined and logix can be used to drive a turnout(s) to
energise relay(s) to switch the correct polarity to each frog. It's very
mundane doing it that way but far better in the long run. The same thing
applies to reversing loops and triangular junctions where many people think
a juicer is the only solution. In fact there can really be no justification
for ever using a juicer.

Fraser





------------------------------------
Posted by: fraser@...
------------------------------------


------------------------------------

Yahoo Groups Links

Re: I am a little confused following this story. As I understand it the "JMRI" is not connected to the layout, they use a seperate programming track. Here a statement is made that the "JMRI"doesn't ptogram the decoders, the DCC systems ...

#138675

Sorry, I didn't mean to ruffle feathers here. As to which "thread", I thought by replying to the immeadiate email it was obvious..thay's what I dislike about Yahoo..it disconnects story lines tandomly.
All that aside, yes,I am a long time DCC user now having moved to NEC for our layout. Sorry about the confusion of my statement about not using a "system" to program. I guess I have always thought of my SPROG3 as a computer interface and not an actual system as in NCE, MRC, DIGITRAX,etc. Okay, wrong choice of words.
What I wS hoping to do was maybe clarify that the club was using an interface like a SPROG and not actually hooked up to a "system", thus no connection to the layout.
  For those of us who do not disect JMRI but simply use the fine programs, we may not be versed in all the syntax and code writing that so many here take for granted. Whrn we post a problem we do so in the o ly wst we know how to explain what "we" see on our system. I have learned a lot at this and the Facebook JMRI  sites. Until I encountered my first problem with DecoderPro at update 4.6, I had no idea there were logs and such to look at or submit for people to troubleshhot with. I don't know how old or what year DecoderPro was first introduced, but I began using it many years ago when I met a guy at a On30 meet in New York state who had it on a laptop and kindly showed me the advantages of programming decoders in whole pages instead of one CV at a time.
I'm a big fan of DecoderPro and couldn't tell you what the other programs are for. I'm simply a happy user and I appreciate whoever is responsible for inventing the program in the first place.
Thanks again for making our model railroading more fun!!



Sent from my Verizon, Samsung Galaxy smartphone

Show quoted text

-------- Original message --------
From: "jceiermann@... [jmriusers]" <jmriusers@...>
Date: 7/24/17 9:36 AM (GMT-07:00)
To: jmriusers@...
Subject: [jmriusers] Re: I am a little confused following this story. As I understand it the "JMRI" is not connected to the layout, they use a seperate programming track. Here a statement is made that the "JMRI"doesn't ptogram the decoders, the DCC systems does.

Snide remarks aside you do use DCC to program your locos. If you are using DecodePro it has to be attached to a DCC system in order for it to read/write to the decoders. So embrace DCC and enjoy the wonderful hobby of Model Railroading.

Jack Eiermann

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

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

Re: JMRI 4.8 is available for download

#138674

Mike,

Did you upload a new copy after removing all of the signal masts?  I am not able to find it.  The one from this morning is still there.

When you copy JMRI to /Applications, are you selecting replace?  If you select merge the results are quite unpredictable.

Dave Sand

Re: DecoderPro issue

Steven Burns

#138682

blockquote, div.yahoo_quoted { margin-left: 0 !important; border-left:1px #715FFA solid !important; padding-left:1ex !important; background-color:white !important; } Understand. Thanks Jon.?

Sent from Yahoo Mail for iPad

Show quoted text

On Monday, July 24, 2017, 1:12 PM, Jon Miller atsfus@... [jmriusers] <jmriusers@...> wrote:

?
/On 7/24/2017 9:26 AM, Steven Burns sburns2302@... [jmriusers]
wrote://
/
/Command station: DB150 [Empire builder]/The DB150 does not have a programming track (i.e. no readback), only
can POM (program on the main). This from the spec sheet;

_Programming Track__
__No__
__Program read/write__
__Write only_

-- 
Jon Miller
For me time stopped in 1941
Digitrax Chief/Zephyr systems, JMRI User
NMRA Life member #2623
Member SFRH&MS

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


  #yiv8513731921 #yiv8513731921 -- #yiv8513731921ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv8513731921 #yiv8513731921ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv8513731921 #yiv8513731921ygrp-mkp #yiv8513731921hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv8513731921 #yiv8513731921ygrp-mkp #yiv8513731921ads {margin-bottom:10px;}#yiv8513731921 #yiv8513731921ygrp-mkp .yiv8513731921ad {padding:0 0;}#yiv8513731921 #yiv8513731921ygrp-mkp .yiv8513731921ad p {margin:0;}#yiv8513731921 #yiv8513731921ygrp-mkp .yiv8513731921ad a {color:#0000ff;text-decoration:none;}#yiv8513731921 #yiv8513731921ygrp-sponsor #yiv8513731921ygrp-lc {font-family:Arial;}#yiv8513731921 #yiv8513731921ygrp-sponsor #yiv8513731921ygrp-lc #yiv8513731921hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv8513731921 #yiv8513731921ygrp-sponsor #yiv8513731921ygrp-lc .yiv8513731921ad {margin-bottom:10px;padding:0 0;}#yiv8513731921 #yiv8513731921actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv8513731921 #yiv8513731921activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv8513731921 #yiv8513731921activity span {font-weight:700;}#yiv8513731921 #yiv8513731921activity span:first-child {text-transform:uppercase;}#yiv8513731921 #yiv8513731921activity span a {color:#5085b6;text-decoration:none;}#yiv8513731921 #yiv8513731921activity span span {color:#ff7900;}#yiv8513731921 #yiv8513731921activity span .yiv8513731921underline {text-decoration:underline;}#yiv8513731921 .yiv8513731921attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv8513731921 .yiv8513731921attach div a {text-decoration:none;}#yiv8513731921 .yiv8513731921attach img {border:none;padding-right:5px;}#yiv8513731921 .yiv8513731921attach label {display:block;margin-bottom:5px;}#yiv8513731921 .yiv8513731921attach label a {text-decoration:none;}#yiv8513731921 blockquote {margin:0 0 0 4px;}#yiv8513731921 .yiv8513731921bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv8513731921 .yiv8513731921bold a {text-decoration:none;}#yiv8513731921 dd.yiv8513731921last p a {font-family:Verdana;font-weight:700;}#yiv8513731921 dd.yiv8513731921last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv8513731921 dd.yiv8513731921last p span.yiv8513731921yshortcuts {margin-right:0;}#yiv8513731921 div.yiv8513731921attach-table div div a {text-decoration:none;}#yiv8513731921 div.yiv8513731921attach-table {width:400px;}#yiv8513731921 div.yiv8513731921file-title a, #yiv8513731921 div.yiv8513731921file-title a:active, #yiv8513731921 div.yiv8513731921file-title a:hover, #yiv8513731921 div.yiv8513731921file-title a:visited {text-decoration:none;}#yiv8513731921 div.yiv8513731921photo-title a, #yiv8513731921 div.yiv8513731921photo-title a:active, #yiv8513731921 div.yiv8513731921photo-title a:hover, #yiv8513731921 div.yiv8513731921photo-title a:visited {text-decoration:none;}#yiv8513731921 div#yiv8513731921ygrp-mlmsg #yiv8513731921ygrp-msg p a span.yiv8513731921yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv8513731921 .yiv8513731921green {color:#628c2a;}#yiv8513731921 .yiv8513731921MsoNormal {margin:0 0 0 0;}#yiv8513731921 o {font-size:0;}#yiv8513731921 #yiv8513731921photos div {float:left;width:72px;}#yiv8513731921 #yiv8513731921photos div div {border:1px solid #666666;min-height:62px;overflow:hidden;width:62px;}#yiv8513731921 #yiv8513731921photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv8513731921 #yiv8513731921reco-category {font-size:77%;}#yiv8513731921 #yiv8513731921reco-desc {font-size:77%;}#yiv8513731921 .yiv8513731921replbq {margin:4px;}#yiv8513731921 #yiv8513731921ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv8513731921 #yiv8513731921ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv8513731921 #yiv8513731921ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv8513731921 #yiv8513731921ygrp-mlmsg select, #yiv8513731921 input, #yiv8513731921 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv8513731921 #yiv8513731921ygrp-mlmsg pre, #yiv8513731921 code {font:115% monospace;}#yiv8513731921 #yiv8513731921ygrp-mlmsg * {line-height:1.22em;}#yiv8513731921 #yiv8513731921ygrp-mlmsg #yiv8513731921logo {padding-bottom:10px;}#yiv8513731921 #yiv8513731921ygrp-msg p a {font-family:Verdana;}#yiv8513731921 #yiv8513731921ygrp-msg p#yiv8513731921attach-count span {color:#1E66AE;font-weight:700;}#yiv8513731921 #yiv8513731921ygrp-reco #yiv8513731921reco-head {color:#ff7900;font-weight:700;}#yiv8513731921 #yiv8513731921ygrp-reco {margin-bottom:20px;padding:0px;}#yiv8513731921 #yiv8513731921ygrp-sponsor #yiv8513731921ov li a {font-size:130%;text-decoration:none;}#yiv8513731921 #yiv8513731921ygrp-sponsor #yiv8513731921ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv8513731921 #yiv8513731921ygrp-sponsor #yiv8513731921ov ul {margin:0;padding:0 0 0 8px;}#yiv8513731921 #yiv8513731921ygrp-text {font-family:Georgia;}#yiv8513731921 #yiv8513731921ygrp-text p {margin:0 0 1em 0;}#yiv8513731921 #yiv8513731921ygrp-text tt {font-size:120%;}#yiv8513731921 #yiv8513731921ygrp-vital ul li:last-child {border-right:none !important;}#yiv8513731921

Re: JMRI 4.8 is available for download

#138673

Hi

I appear to be having problems now with 4.8 with my matrix signal mast entries that have been working fine in 4.6 but now I'm getting "Invalid content was found starting with element 'outputs'. One of '{systemName, disabledAspects}' is expected. As can be seen below the disabled aspects are there but possibly in a different order than the new version is expecting. I had recently been chasing out problems with speed definitions as my signal aspects file was incorrect and after getting all that sorted the layout editor file was loading without problems showing in the system console. As guided by Bob I have had a look at the release notes but there doesn't seem to be any mention of this being a problem. Perhaps with it being comparatively new there are not so many people using it yet. Now I sit here looking at it, it seems quite strange that it is necessary to have all the disabled aspects listed in the bitStrings section. I guess there is a reason but I can't imagine what that would be.

The first definition with "outputs" and that is for the last signal before a set of terminus roads with buffer stops looks like 

    <signalmast class="jmri.implementation.configurexml.MatrixSignalMastXml" userName="CW12">
      <systemName>IF$xsm:BR-2003 fws:F+4+c($0012)-2t</systemName>
      <userName>CW12</userName>
      <unlit allowed="no" />
      <outputs>
        <output matrixCol="output1">CW12 Ch1</output>
        <output matrixCol="output2">CW12 Ch2</output>
      </outputs>
      <bitStrings>
        <bitString aspect="Danger">00</bitString>
        <bitString aspect="Caution">10</bitString>
        <bitString aspect="Flash Caution">00</bitString>
        <bitString aspect="Preliminary Caution">00</bitString>
        <bitString aspect="Flash Preliminary Caution">00</bitString>
        <bitString aspect="Proceed">00</bitString>
        <bitString aspect="Diverging1C">00</bitString>
        <bitString aspect="Diverging1pC">00</bitString>
        <bitString aspect="Diverging1P">00</bitString>
        <bitString aspect="Diverging2C">00</bitString>
        <bitString aspect="Diverging2pC">00</bitString>
        <bitString aspect="Diverging2P">00</bitString>
        <bitString aspect="Diverging3C">00</bitString>
        <bitString aspect="Diverging3pC">00</bitString>
        <bitString aspect="Diverging3P">00</bitString>
        <bitString aspect="Off">01</bitString>
      </bitStrings>
      <disabledAspects>
        <disabledAspect>Diverging1pC</disabledAspect>
        <disabledAspect>Diverging3pC</disabledAspect>
        <disabledAspect>Diverging2pC</disabledAspect>
        <disabledAspect>Proceed</disabledAspect>
        <disabledAspect>Diverging3C</disabledAspect>
        <disabledAspect>Preliminary Caution</disabledAspect>
        <disabledAspect>Diverging1C</disabledAspect>
        <disabledAspect>Diverging2C</disabledAspect>
        <disabledAspect>Diverging2P</disabledAspect>
        <disabledAspect>Diverging3P</disabledAspect>
        <disabledAspect>Flash Caution</disabledAspect>
        <disabledAspect>Flash Preliminary Caution</disabledAspect>
        <disabledAspect>Diverging1P</disabledAspect>
      </disabledAspects>
    </signalmast>

Thanks

Fraser

Re: Crossing in layout editor

#138693

Fraser,

I guess we will have to agree to disagree. How will JMRI help when the layout is not using JMRI. Like in a Freemo set up at a show. Or when a person turns on a club layout to run trains but doesn't need JMRI. Out club successfully uses a hundred plus juicers.

  I don't need to know any programming to make things work. Just hook up 3 wires and drive my train and never think if that frog is dead or the right polarity.

David Klemm
Sent from my iPhone 7 Plus
________________________________
From: jmriusers@... <jmriusers@...> on behalf of fraser@... [jmriusers] <jmriusers@...>
Sent: Monday, July 24, 2017 2:13:08 PM
To: jmriusers@...
Subject: [jmriusers] Re: Crossing in layout editor



David

A frog juicer is the tech geeks expensive way of solving a problem that doesn't really exist and everytime it activates, the spark caused by the short will slowly but surely pit the rail surface and lead to dirt buildup and poor running. As has been pointed out in other responses here the situations where the polarity of the frogs have to be set one way or the other are easily defined and logix can be used to drive a turnout(s) to energise relay(s) to switch the correct polarity to each frog. It's very mundane doing it that way but far better in the long run. The same thing applies to reversing loops and triangular junctions where many people think a juicer is the only solution. In fact there can really be no justification for ever using a juicer.

Fraser

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

Re: Blocks must have unique sensors?

#138672

Larry,

If you think about it, a block can only have one sensor and one sensor can
only mean one block. Since it is one sensor, those track segments must be
one block because you can't tell where within the block a train is by
looking at the one sensor. Many improvements went into the latest release
and a number of them are now enforcing proper behavior that was not enforced
before.

-Ken Cameron, Member JMRI Dev Team

www.jmri.org

www.fingerlakeslivesteamers.org

www.cnymod.com

www.syracusemodelrr.org

Re: Crossing in layout editor

#138671

David

A frog juicer is the tech geeks expensive way of solving a problem that doesn't really exist and everytime it activates, the spark caused by the short will slowly but surely pit the rail surface and lead to dirt buildup and poor running. As has been pointed out in other responses here the situations where the polarity of the frogs have to be set one way or the other are easily defined and logix can be used to drive a turnout(s) to energise relay(s) to switch the correct polarity to each frog. It's very mundane doing it that way but far better in the long run. The same thing applies to reversing loops and triangular junctions where many people think a juicer is the only solution. In fact there can really be no justification for ever using a juicer. 

Fraser

Blocks must have unique sensors?

#138670

Perhaps this changed since I upgraded to the latest version of JMRI.
 
 I have a segment of track, short straight, turnout, short straight, which I want to report all as one detection block.  in Panel Pro, I had each block defined, and assigned to the same sensor.  The sensor is one connection on a BDL168.
 
 Today, Panel Pro give me an error "Block1 is already assigned as the occupancy sensor for Sensor 1". I can change the blocks in the Block Table to reuse sensors, however, in the Layout, I receive the error if I try to edit the block.
 
 Has anyone experienced this?
 
 Thanks,
 Larry

Re: JMRI 4.8 parse error

#138669

On Jul 24, 2017, at 7:56 AM, mikeca@... [jmriusers] <jmriusers@...> wrote:

After upgrading I got the following parse Error

while parsing the file .....xml Exception:org.jdom2.input.JDOMParseException Error on line 2871 cvc-complex-type.4: Attribute 'class' must appear on element 'key'.

I have uploaded my xml file called Carney config file.

How do I fix ?
I’m going to give a general answer, in case others with similar issues read this.

Although JMRI release notes are long, it’s good to read them, particularly if you’re having a problem.  The JRMI 4.8 release note (at ) says about this:

"JMRI applications will not load a panel file that fails XML validation; an error will be shown that should explains the error, allowing it to be fixed using an editor. (The explanations remain a work in progress.) The usual cause of something like this is (imperfect) manual editing of the file, but it can happen for multiple reasons. If you encounter this, try these things:
	? Use a copy of JMRI 4.6 to load and rewrite the file into the proper format;
	? Or set your preferences to execute the "TurnOffXmlValidation.py" script before JMRI loads your panel file;
	? Or finally, ask for help fixing the file on the JMRIusers list.
"It's a good idea to keep a copy of the original file as you work on this, just in case.”

The first one (write the panel file with JMRI 4.6) should make a permanent fix; if it doesn’t, I’d really like to get copies of the before and after files to understand why.  It’ll also clean up other issues that might have accumulated in the file. The second (run a script) bypasses the problem. At some point, you’ll want to solve it before it actually bites you, so you can also rewrite the file after reading it that way. The third one, ask for help here, will probably result in somebody just running your file through a current JMRI version and sending it back, so it’s similar to the first two.

Bob
--
Bob Jacobsen
rgj1927@...

Re: DecoderPro issue

Jon Miller

#138666

/On 7/24/2017 9:26 AM, Steven Burns sburns2302@... [jmriusers] 
wrote://
/
/Command station: DB150 [Empire builder]/    The DB150 does not have a programming track (i.e. no readback), only 
can POM (program on the main).  This from the spec sheet;

_Programming Track__
__No__
__Program read/write__
__Write only_

-- 
Jon Miller
For me time stopped in 1941
Digitrax  Chief/Zephyr systems, JMRI User
NMRA Life member #2623
Member SFRH&MS

Re: Crossing in layout editor

#138665

[...] so I was thinking about putting a sensor custom icon and assign an action to the sensor to operate the servo. Is this the way to go or am I overcomplicating?  That's the way I'd go… In the Sensor table create an internal sensor then in the layout editor choose the "Sensor Icon" (round) radio button and then the internal sensor in the combobox dropdown menu... then shift-click on the layout view next to the crossing where you want the icon.
 
 If you're doing signals all this could be tied together (both physically on (under? ;-) your layout and virtually in JMRI).

Re: JMRI 4.8 upgrade second parse error

[email protected]

#138667

Hi Dave, 

 I deleted all the signal masts.  They were an experiment that I never completed and they are not used.  I just use signal heads now.
 
 I upgraded again and I got a 2nd parse error.  
 
 Error on line 5662 cvc-complex-type 3.2.2.  Attribute grid size is not allowed to appear in element "LayoutEditor'
 
 I have my config in Loconet Simulator.  Not sure why you get a different error than I do when loading the xml file in 4.8.  I updated the revised xml file.  It is called Carney Config File.
 
 I am running JMRI on Mac OS 10.12.5 Sierra, Java Version 1.8.0_141
 
 How do I fix this error ?
 
 Mike Carney

Re: DecoderPro issue

Steven Burns

#138668

Steve, Well, rats. Thanks much for the quick response.  Steve.  Sent from Yahoo Mail for iPad On Monday, July 24, 2017, 12:13 PM, breezlys@... [jmriusers] <jmriusers@...> wrote:   Steve, The DB150 does not have CV readback ability (it lacks the required circuitry). JMRI cannot "'fix" that, so to read CV's you will need to obtain hardware such as the PR3 which supports that functionality. HTH, (Another) Steve "Breezlys" ---In jmriusers@..., <sburns2302@...> wrote : Hi, I am having a problem implementing the DecoderPro. The Read Type from Decoder is grayed out. Not sure why. Does not seem to be communicating with the DCC system. Using Windows 7 on a Samsung netbook. DecoderPro version 4.6-R8149dc. Computer interface is the RR Cirkits LocoBuffer-USB, Rev N. The driver installed successfully. Java version 8, update 141. The DecoderPro settings: DCC system: Digitrax Serial port: LocoBuffer-USB [com 3] Command station: DB150 [Empire builder] Connection prefix: L Connection name: LocoNet Do you have any idea what I am doing wrong, or not doing? Thanks. Steve

开云体育