Fcot,
Are you using some serial to ethernet adapter? If that is the case I suspect
your setup for things like how it knows when to send packets is not correct.
I've seen a lot of those devices that default for expecting some sort of
text or other form with a known delimiter to trigger sending the buffer as
one packet. But this traffic isn't like that. It needs to do something like
raw and a very short timeout, so it will complete the packet to JMRI (or the
other way, to the DCC+++ device).
OTOH, if somebody knows the protocol for DCC+++ and it is formed with a
known 'end' character, then making sure the interface knows that character
might make the difference.
That's my guess, but that's only if the interface is a serial to ethernet
buffer. If the DCC+++ command station is native ethernet, then I would doubt
this is related to your problem.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org
Ken Cameron