I seem to have it where the simple client is seeing the turnouts ok, but it
is replying with either the wrong sensor value or many times sensor unknown,
displaying a wrong name. Many times it looks like it was truncating the
sensor value but other times, I don't know what it was translating into a
value.
This is with 4.18, on Windows, with both JMRI running on the same box for
testing. The server side is using LocoNet simulator. Anyone have a clue on
this or willing to try reproducing?
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org
Ken Cameron