The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Device Control Protocol Was Serial/IP Socket Bridge


  • To: ukha_d@xxxxxxx
  • Subject: Device Control Protocol Was Serial/IP Socket Bridge
  • From: "Mark Marooth" <MMarooth@xxxxxxx>
  • Date: Thu, 6 Jun 2002 11:43:03 +0100
  • Mailing-list: list ukha_d@xxxxxxx; contact ukha_d-owner@xxxxxxx
  • Reply-to: ukha_d@xxxxxxx



Hi Patrick,

Many thanks for the suggestions, they help !

I will make use of broadcast for transmitting telemetry data and will have a
listener to service Telnet type connections so that I can also control the
serial devices by issuing commands.

I plan to use Select()  to give me Synchronous I/O Multiplexing as this will
work with both sockets and serial ports/special files at the same time.

I'm ASCII all the way as far as passing data about is concerned, saves much
grief.

With respect to protocols, I have had some experience in the realm of
SCADA/Telecontrol systems in the power industry and am aware of a number of
protocols for communication
between RTU's (Remote Terminal Unit's) and control systems.  Protocols such as
WISP, EWISP, F4F etc, both streaming and polling.

As this is a more specialised subject which many on this list will not be
interested in, perhaps, if you are interested in developing a protocol we could
start an off-line dialogue.

Anyone else interested, give me a yell and we can get something going.


Mark



For more information: http://www.automatedhome.co.uk
Post message: ukha_d@xxxxxxx
Subscribe:  ukha_d-subscribe@xxxxxxx
Unsubscribe:  ukha_d-unsubscribe@xxxxxxx
List owner:  ukha_d-owner@xxxxxxx

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.