开云体育

Today I updated JMRI from 3.10.1 to 4.14 (I know, quite a leap). Was waiting for a production version which had fixed the NCE Macro editor and also a CATS release which would also work together.?

I have two signal heads defined as Triple Output RGB. The new version won’t load this panel and displays Parse error

”... cvc-datatype-valid.1.2.3:’blue’ is not a valid value of union type ‘AnonType_definesturnoutnameSignalHeadType’

I tried editing my xml file to delete these two heads and associated turnouts. Upon saving and reopening the panel successfully loaded. Once I tried adding these back in using 4.14 and saving, panel would not open and same message appeared.?

JMRI 4.14
Java 1.8
Win10
NCE serial?
CMRI serial

Final note- upon adding the elements back in to the edited file, I was able to control all the aspects from the Signal Head table. Once I closed that session and attempted to load the Panel was when I got the error


Mark Ziebell

Mark,

Could you cut/paste the problem signals? It will save time. The issue is how
a number of things were internally represented changed between then and now,
it looks like you found one that got missed. Since you were able to edit the
file, it seems doing this will be easy for you.

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

Here is the paste out of my XML file.? I hope this is what you were asking for, Ken.

MZ

????? <comment>SignalHead:CH10:Green</comment>
??? </turnout>
??? <turnout feedback="DIRECT" inverted="false" automate="Off">
????? <systemName>CT11</systemName>
????? <comment>SignalHead:CH10:Blue</comment>
??? </turnout>
??? <turnout feedback="DIRECT" inverted="false" automate="Off">
????? <systemName>CT12</systemName>
????? <comment>SignalHead:CH10:Red</comment>
??? </turnout>
??? <turnout feedback="DIRECT" inverted="false" automate="Off">
????? <systemName>CT28</systemName>
????? <comment>SignalHead:CH28:Green</comment>
??? </turnout>
??? <turnout feedback="DIRECT" inverted="false" automate="Off">
????? <systemName>CT29</systemName>
????? <comment>SignalHead:CH28:Blue</comment>
??? </turnout>
??? <turnout feedback="DIRECT" inverted="false" automate="Off">
????? <systemName>CT30</systemName>
????? <comment>SignalHead:CH28:Red</comment>
??? </turnout>

??? <signalhead class="jmri.implementation.configurexml.TripleOutputSignalHeadXml">
????? <systemName>CH10</systemName>
????? <turnoutname defines="green">CT10</turnoutname>
????? <turnoutname defines="blue">CT11</turnoutname>
????? <turnoutname defines="red">CT12</turnoutname>
??? </signalhead>
??? <signalhead class="jmri.implementation.configurexml.TripleOutputSignalHeadXml">
????? <systemName>CH28</systemName>
????? <turnoutname defines="green">CT28</turnoutname>
????? <turnoutname defines="blue">CT29</turnoutname>
????? <turnoutname defines="red">CT30</turnoutname>
??? </signalhead>

Mark,

Thanks and I've confirmed the error in 4.14, I've not got other versions on
hand to figure where it came in to the program. I tried the option to turn
off the XML check before loading, but that didn't make a difference. It
fails due to the reading of that head. I've posted the bug in the logging
system and will see which developer might have a chance to figure it out.
Unfortunately I don't have a work around for you nor a good clue of when
between 3.10.1 and now that got broken.

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

Since when I created this driver pretty much all I did was change 'Yellow' to 'Blue' and move a few things about a bit from the existing triple output driver, it must be something to do with 'Blue' not being on a list somewhere in the xml validation. I don't think that blue is used in any of the other drivers.

Suzie x