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]

Re: NexTViewLink, Q-Link, EasyLink - data comms over SCART?


  • To: ukha_d@xxxxxxx
  • Subject: Re: NexTViewLink, Q-Link, EasyLink - data comms over SCART?
  • From: "dermot_bradley" <bradley@xxxxxxx>
  • Date: Mon, 20 May 2002 01:28:14 -0000
  • Mailing-list: list ukha_d@xxxxxxx; contact ukha_d-owner@xxxxxxx
  • Reply-to: ukha_d@xxxxxxx

--- In ukha_d@y..., "Keith Doxey" <lists.diyha@b...> wrote:
> Pins 10 and 12 are allocated for Data Comms but there is very little
> implementation of this so far.

NexTViewLink, Q-Link, EasyLink are various terms TV and VCR vendors
use to refer to this functionality. Its been around for several years
- my own Toshiba VCR has a NexTViewLink option.

Basically as the TV and VCR can communicate then the VCR can handle a
"record now" operation by asking the TV which channel is in use.

Likewise the TV can (theoretically) download an EPG entry into the VCR
for later recording.

> Just found an interesting document
> http://www.dtg.org.uk/dtgactivities/published/connection_guidelines.pdf
>
> will print it off and read through it.

This document refers to it as AV.Link - thought NexTViewLink was the
official name.

Always thought in a HA scenario it would be great to be able to
connect to both a VCR and TV and query them.

Unfortunately I don't see much info around on how to do this.



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

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.