|
The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024
|
|
[Date Prev][Date
Next][Thread Prev][Thread Next][Date
Index][Thread Index]
RE: xAP - The Proposed Architecture Explained...
- To: ukha_d@xxxxxxx
- Subject: RE: xAP - The Proposed Architecture
Explained...
- From: ian.bird@xxxxxxx
- Date: Wed, 14 Aug 2002 15:44:05 +0200
- Mailing-list: list ukha_d@xxxxxxx; contact
ukha_d-owner@xxxxxxx
- Reply-to: ukha_d@xxxxxxx
Most displays of these types present a parallel interface to the device
supplying the data. Voltages on these pins have to be presented in the
correct order and with the correct timings and represent the data or
commands.
Because this is hassle and takes a lot of I/O pins folks developed
serial
interfaces to them. This way you fire your data as though it was going
down
a PC serial port e.g. baud rate etc. and follow the protocol supplied by
the
interface manufacturer. The device in the middle does the interfacing
and
the display displays.
In order to connect these to another type of network which may include
RS485, TCPIP etc. there would need to be another conversion layer that
converts the inbound data to serial to send to the interface of the
display.
This way any network can be connected.
Ian B
> Like I say, I'm not that kinda guy so dunno - who's idea was
> the serial
> interface and how did they envisage linking it all up??????
>
>
Yahoo! Groups
Sponsor |
ADVERTISEMENT
| |
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
|
|