Thanks Scott - that certainly solves that question.I think what you are seeing is the TCP server for the SW Remote. It's listening on 5015 also.
I have focussed on trying and testing the TCP link using all known tried and tested ports. I've also used "socketTest 3" (TCP client/server testing) connecting to Mapfactor Navigator TCP (send & received), and a useful "reverse test" on Housebot TCP with messages successfully sending and receiving.
I'm now convinced the TCP basic connection is good between Navigator and Housebot. I think the issue may lie with something like:
1) Formatting of data within TCP plugin - how is it being sent in terms of ASCII or HEX etc?
2) No ability to use \n or \n\r within TCP plugin (from what I have read in the HB forums)
3) Something even more trivial such as timeouts?
Not sure where I go from here...
EDIT:
If anyone can test this themselves, it's a free application: http://navigatorfree.mapfactor.com/en/
Go to settings: remote communication device, for the TCP setup. No GPS needed for commands such as $software_version