It sounds like computer B has both a simulated and real connection defined. That results in LT and L2T.
The recommended procedure is to use two profiles. One has LocoNet Simulation and the other has the LocoNet DCS100 connection. The user files location for both profiles is set to the common location on DropBox.
Trying to enable/disable connections when using a single profile results in unpredictable results and issues.
Dave Sand
toggle quoted message
Show quoted text
On Nov 29, 2018, at 6:04 PM, esimard via Groups.Io <esimard@...> wrote:
Hi all
I have two machines:
¡°A¡± is a desktop running win 10 current version
JMRI 4.12+R6a9bb1
JAVA 1.8.0_191
it has one preference Loconet Simulator
¡°B¡± is a laptop touch screen running win 10 current version
JMRI 4.12+R6a9bb1
JAVA 1.8.0_191
it has two preference settings
Loconet Simulator
layout connection DCS100 PR3
When I run a CTC panel Computer B (layout connection disabled) I get the following errors
ERROR - Could not create sensor System name "LS1" in adaptor of type
jmri.jmrix.loconet.configurexml.LnSensorManagerXml
Followed by the same error for all 50 or so sensors.
ERROR - Unexpected error (Exception) while load
(/C:/Users/esima/JMRI/CTC%20v54-2(x86)2lessSND.xml) in adaptor of type
jmri.jmrix.loconet.configurexml.LnTurnoutManagerXml Exception:
java.lang.IllegalArgumentException: Invalid system name for turnout: LT10 needed L2T
See
for possibly more information. [AWT-EventQueue-0]
java.lang.IllegalArgumentException: Invalid system name for turnout: LT10 needed L2T
Followed by the same error for all turnouts.
When the panel finally loads, the turnouts are not displayed nor are the sensors as expected from the
errors. Panel sensors are represented by a ¡°?¡±, if I click on the ¡°?¡± the sensor appears and works
correctly.
Now if I disable Loconet Simulator and enable the layout connection and connect to the layout
the panel loads without any errors showing up in the log,but some sensors are still displayed by a ¡°?¡±. If I click on them the sensor appears and works correctly.
Now to computer A.
Running the same panel file it loads without error; however, some sensors are displayed by the
¡°?¡±, but clicking on them the sensor appears and works correctly.
To assure that I was using the same panel file I put the JMRI files on Dropbox and had the exact same
results.
Confusing that the errors are different across different platforms and/or the preference setting..
Thanks for any advise, particularly with the Simulator.
