Difference between revisions of "Developer:LPEC"

From LinnDocs
Jump to: navigation, search
(New page: = Introduction<br> = Linn's UPnP products can be controlled over a home network in an ever increaing number of ways.<br> The primary means of control is, of course, UPnP itself, which su...)
 
Line 1: Line 1:
 
= Introduction<br> =
 
= Introduction<br> =
  
Linn's UPnP products can be controlled over a home network in an ever increaing number of ways.<br>
+
Linn's UPnP products can be controlled over a home network in an ever increaing number of ways. The primary means of control is, of course, UPnP itself, which subdivides product control into smaller units called services. A DS product, for instance, will provide some standard UPnP AV services:<br>
  
The primary means of control is, of course, UPnP itself, which subdivides product control into smaller units called services.<br>
 
  
A DS product, for instance, will provide some standard UPnP AV services:<br>
 
  
* AVTransport<br>
+
* AVTransport
 
* RenderingControl<br>
 
* RenderingControl<br>
* ConnectionManager<br>
+
* ConnectionManager
 +
 
 +
 
  
 
and additional Linn-specific services, such as:<br>
 
and additional Linn-specific services, such as:<br>
 +
 +
  
 
* Ds<br>
 
* Ds<br>

Revision as of 09:39, 17 June 2008

Introduction

Linn's UPnP products can be controlled over a home network in an ever increaing number of ways. The primary means of control is, of course, UPnP itself, which subdivides product control into smaller units called services. A DS product, for instance, will provide some standard UPnP AV services:


  • AVTransport
  • RenderingControl
  • ConnectionManager


and additional Linn-specific services, such as:


  • Ds
  • Volkano
  • Product
  • Ui


It is possible in Bute and later software releases to control a Linn UPnP product using an alternative mechanism known as the Linn Protocol for Eventing and Control.


This is a basic Telnet-like protocol, which relies on the developer knowing in advance, or having discovered by some means, the TCP/IP of the device to be controlled. Knowing this, LPEC can be accessed by creating a raw socket session to port 23 of the device.


The rest of this document describes the format of the messages that LPEC expects and delivers.