http://doip.org/ 2012-05-20T14:26:13+02:00 http://doip.org/ http://doip.org/lib/images/favicon.ico text/html 2010-05-04T09:15:48+02:00 http://doip.org/about?rev=1272957348&do=diff About DoIP The DoIP system is designed to let devices communicate with eachother while requiring as little configuration as possible. A DoIP system automatically connects devices based on their presence and capabilities. Technical overview The DoIP protocol consists of three components, which handle different phases in the process of configuration and operation. The different phases are visualized in the graph on the right. text/html 2010-05-17T20:49:33+02:00 http://doip.org/ambient_lighting?rev=1274122173&do=diff Using the DoIP technology, it is very easy to create ambient lighting in a room. Ambient lighting is also known as 'Ambilight', a function found on the more expensive televisions from Philips. Such televisions typically have a few LED or CCFL lights on their back, which illuminate the wall to which the television is mounted with a color that is generated from the image that is currently displayed (i.e. the average of all colors on the screen, the most occurring color, etc.). Ambilight has a few … text/html 2010-06-14T10:04:15+02:00 http://doip.org/building_doip_on_linux?rev=1276502655&do=diff Building DoIP under Linux Currently, DoIP can be built under Linux; although it supports both ARM and x86/x64, the currently included build scripts can only build for ARM. With minor modifications, it should be possible to build for x86/x64 too. The build configuration is tested under Debian, but other Linux flavours should work too. text/html 2010-05-18T09:06:10+02:00 http://doip.org/committers?rev=1274166370&do=diff Committers Committers have write access to the source code repository and can therefore make changes to the official version of the source code. The committers for each project are listed below; these are the people that you might want to contact if you have made a change to the source code that you'd like to share (of course, you are required to share your changes by means of the LGPL, but such a change does not have to be included in the official version if it is of little use to others. In s… text/html 2010-02-28T09:07:10+02:00 http://doip.org/concurrency_in_tjscript?rev=1267344430&do=diff Concurrency in TJScript The latest version of TJScript has new features that make programming scripts that take advantage of parallel processing and concurrency very easy. In TJScript, concurrency is expressed using futures. A future is basically a small function that calculates a certain result value using certain input values. If an input value of a future is also a future, then this future is guaranteed to be executed first, so the result value is available for the next future. Because futur… text/html 2010-03-26T10:34:18+02:00 http://doip.org/contact?rev=1269596058&do=diff Contact us Pixelspark can be reached through the following channels: * General inquiries: info (at) pixelspark.nl * Support questions: support (at) pixelspark.nl * Sales inquiries: sales (at) pixelspark.nl text/html 2010-05-17T20:13:49+02:00 http://doip.org/corespark?rev=1274120029&do=diff CoreSpark CoreSpark is a collection of cross-platform libraries that provide basic system functions such as threading, memory management, I/O as well as complete libraries for user interfaces, service discovery, persistence, networking and a scripting engine. CoreSpark is licensed under the LGPL v3. CoreSpark is used by TJShow, TJingle and EPFramework. text/html 2010-05-17T21:35:13+02:00 http://doip.org/definition?rev=1274124913&do=diff All endpoint devices that conform to the DoIP standard publish a so-called definition file that specifies the methods, or messages, that the endpoint supports. The definition file also contains a list of possible methods a client can use to send a message to the endpoint. An example of a definition file is displayed below. text/html 2010-05-17T20:53:07+02:00 http://doip.org/discovery_component?rev=1274122387&do=diff Device discovery component In DoIP, a discovery mechanism is needed for devices to be able to discover eachother. Although any discovery mechanism could be used, current implementations are based on DNS-SD/mDNS (commonly known by the Apple trademark name 'Bonjour'). In a network, devices can support multiple discovery mechanisms (as long as the devices that have to communicate with eachother support the same mechanisms and that devices take special care to make sure that devices are not doubly … text/html 2010-02-27T13:43:51+02:00 http://doip.org/dispatch_queues?rev=1267274631&do=diff Dispatch queues TJShared implements a high-level approach to concurrency which is based on queues. Using the Dispatcher class, you can allocate a thread pool that executes 'tasks', small pieces of code that can run concurrently. Tasks are added to a queue and executed as soon as there is a thread ready to do so. A Future is a special type of task that depends on another task; it can only be run as soon as all tasks it depend on have run. This, for instance, allows a computation like (1+2)*(3+4)… text/html 2010-05-17T21:35:00+02:00 http://doip.org/dns-sd_mdns?rev=1274124900&do=diff About DNS-SD/mDNS discovery The DNS-SD/mDNS discovery mechanism (also known by the Apple trademark name 'Bonjour') is the currently preferred discovery mechanism in DoIP networks. Services are advertised by DNS records, that can be retrieved in a local network by means of multicast DNS (mDNS). This means that devices using IPv6 can generate their own IP address each time they start up, and still be discovered. text/html 2010-06-10T08:01:02+02:00 http://doip.org/doip?rev=1276149662&do=diff DoIP (Domotics over IP) is a technology that allows you to connect many different devices in your home to form a single, intelligent system for home automation. DoIP is designed to be plug-and-play to the largest extent possible. DoIP devices talk to eachother through messages; devices automatically find and connect with devices that support the same messages. DoIP networks commonly run over IP (wired and wireless Ethernet) networks. The DoIP specification is open and can be freely used by anyon… text/html 2010-05-04T09:22:45+02:00 http://doip.org/doip_sdk?rev=1272957765&do=diff DoIP SDK The DoIP SDK provides programmers with the necessary tools to create DoIP-compatible applications. All downloads for the SDK can be found on the downloads page. The SDK is available for Windows (more information), Mac and Linux. The Windows SDK contains binaries that run on x86. The Mac SDK contains universal binaries that will run on the x86 and x86_64 architectures. The Linux SDK comes in two editions: one for the armel-architecture and one for the x86 architecture. text/html 2010-06-14T09:48:05+02:00 http://doip.org/doip_source?rev=1276501685&do=diff Source code There are two ways to obtain the source code to the open-source projects. The Pixelspark Subversion repository contains the official version of the source code, reviewed by Pixelspark and other authorized developers. The repository at Github is a mirror of this tree. The benefit of using Git is that exchanging patches and working in a distributed way is much easier. Note that there may be so-called 'forks' of the project on Github; these are copies of the project with custom changes… text/html 2010-05-17T20:50:04+02:00 http://doip.org/doip_specification?rev=1274122204&do=diff DoIP Protocol Suite Specification 1.0 The DoIP protocol suite consists of different components, most of which are based on standard technologies that are already in widespread use, such as HTTP, OSC and DNS-SD/mDNS. The DoIP specification also defines default sets of messages that should be supported when applicable, to improve interoperability between devices. text/html 2010-06-14T10:16:07+02:00 http://doip.org/downloads?rev=1276503367&do=diff DoIP Downloads DoIP for Debian/ARM These are the binaries that you will want to use if you want to run the DoIP software on devices like the SheevaPlug or iConnect. Note that currently, it is not possible to directly install the software on either device without having first installed a custom Debian installation on these. The binaries will work on Debian stable (lenny) as well as unstable (squeeze), except for tjbluetoothepserver (will be fixed shortly). Also, please install the mdnsd package… text/html 2010-05-17T20:10:57+02:00 http://doip.org/epframework?rev=1274119857&do=diff EPFramework The EPFramework library implements a reference version of the DoIP protocol stack. EPFramework abstracts the inner workings of DoIP away through 'endpoints' (hence the name, 'EP' stood for 'Endpoint Protocol'). It implements the device definition file format, discovery mechanisms and conditions and a few connection types. The EPFramework is meant for application developers and is designed in such a way that minimal effort is required to create applications that interact with HomeWea… text/html 2010-05-04T09:33:01+02:00 http://doip.org/epplugserver?rev=1272958381&do=diff EPPlugServer is the process that runs on DoIP bridging devices ('plugs') and makes sure that whenever a device is connected, the corresponding server is started and connects the device to the DoIP network. It also provides some other, managerial tasks. text/html 2010-05-04T09:18:13+02:00 http://doip.org/faq?rev=1272957493&do=diff General questions How is DoIP different from, say, X10? X10 is a very robust and proven protocol that allows you to connect and control devices in your home over the powerline or wirelessly. While X10 works very well for this purpose, it is not very extensible: the system is more or less 'closed', and X10 equipment is usually pretty expensive. Also, X10 only allows for very basic commands like 'lights on', while DoIP allows more complex commands and information to be used. Still, it should be … text/html 2010-05-04T09:12:58+02:00 http://doip.org/home?rev=1272957178&do=diff Pixelspark developer wiki Welcome to the Pixelspark developer wiki! The Pixelspark developer wiki is a technical reference for developers interested in using our show control and home automation systems technology. We provide a software development kit (SDK) for developers that are interested in using our technology (i.e. to integrate with other technology or to add functionality); this wiki includes full documentation to help you learn more. text/html 2010-05-17T21:34:25+02:00 http://doip.org/how-tos?rev=1274124865&do=diff On this page, you will find general tutorials on how to use the DoIP technology for different purposes. Although these descriptions are meant for end-users, they are written in a very technical way and should probably only be used by developers or equipment manufacturers, or enthousiastic hobbyists who want to write fabrics to extend home automation functionality. text/html 2010-06-21T15:29:13+02:00 http://doip.org/iconnect?rev=1277126953&do=diff Iomega iConnect The Iomega iConnect is a Marvell Kirkwood (ARM) Linux-based NAS device which comes with 4 USB ports, GbE and wireless support (802.11g). The iConnect contains the same processor as the SheevaPlug, has 256MB RAM memory and 512MB flash memory. The iConnect is perfectly capable of running multiple DoIP services. text/html 2010-06-21T15:16:32+02:00 http://doip.org/iconnect_console?rev=1277126192&do=diff iConnect Console Access To get access to the console of the iConnect, you need something that can connect using RS-232 at 3.3V (for instance, using the FT-232RL 3.3V USB adapter). Simply plug in the device, download the drivers from <http://www.ftdichip.com/Drivers/VCP.htm> FTDI] and use the following commands to connect: text/html 2010-05-04T09:17:38+02:00 http://doip.org/iphone_remote?rev=1272957458&do=diff DoIP Remote for iPhone The DoIP Remote is an application for iPhone and iPod Touch that can connect to and control DoIP devices. You can buy the application in the iTunes Store (click here). The DoIP Remote application currently supports DoIP devices that can be discovered through Bonjour (DNS-SD/mDNS) and that support OSC-over-UDP as transport. More transports will be added in the future. TJShow Remote supports most basic parameter types (int32, double, bool) and shows user-friendly icons for… text/html 2010-05-17T20:51:42+02:00 http://doip.org/mac_remote?rev=1274122302&do=diff HomeWeave Remote for Mac The DoIP Remote for Mac is a small application that sits in the system menu on the top right corner of the screen. When clicked, it presents a list of devices and available actions, which allows you to control all equipment in your home from one single place. text/html 2010-05-17T20:52:51+02:00 http://doip.org/magic_wand?rev=1274122371&do=diff Magic Wand 'Magic Wand' is an alternative, client-only implementation of the DoIP protocol, which is very simple and only supports the most commonly used protocols. It is available for the iPhone OS and is written in Objective C. Because of its simplicity, it is a great library to use if you want to learn more about the protocol. text/html 2010-01-23T12:08:33+02:00 http://doip.org/mdns?rev=1264244913&do=diff mDNS library The mDNS library implements the DNS-SD/mDNS discovery mechanism for services. This library comes in different forms, depending on the operating system: OS API library Responder program name Windows dnssd.dll mDNSResponder.exe Linux libdnssd mdnsd Mac OS X libSystem mDNSResponder Usually, programmers need not use the mDNS library directly. In fact, they are disencouraged to do so, since different service discovery mechanisms may be used in the future. Also, most of th… text/html 2009-11-11T10:21:31+02:00 http://doip.org/mediation_level?rev=1257931291&do=diff Mediation level The mediation level is a number associated with a device service to allow for greater flexibility in setting up intelligent home automation networks. In these networks, devices called fabrics are used to translate one message to another using a set of rules or scripts. text/html 2010-02-27T13:51:56+02:00 http://doip.org/memory_management?rev=1267275116&do=diff Memory management in the TJShow SDK Because the TJShow SDK interfaces with various libraries that all exchange objects and data, the SDK (and all TJShow software internally) uses a special memory management mechanism to keep track of objects, free their memory when appropriate and make programming easier. text/html 2010-05-17T20:52:44+02:00 http://doip.org/messages?rev=1274122364&do=diff About message specifications Although devices in a DoIP network can decide for themselves which messages to use, a little consensus about the definition of certain messages is needed in order to let devices communicate with eachother without configuration. Therefore, there are a few standard message sets defined. Devices can implement these sets by supporting the messages that are defined in them following the specification. It is also allowed to partially implement a message set (i.e. only a f… text/html 2010-05-17T20:53:13+02:00 http://doip.org/namespaces?rev=1274122393&do=diff Common device namespaces In DoIP, endpoints (optionally) are associated with a particular namespace (as indicated by the namespace attribute in the file). Normally, devices are identified by their unique ID or service ID on the network. This however is a problem for devices that are mobile and can be connected to the network in different ways. Bluetooth devices, for instance, can be introduced on the network through TJBluetoothServer, but there can be multiple gateways on the network that do so… text/html 2010-01-16T16:39:22+02:00 http://doip.org/negotiation_component?rev=1263656362&do=diff About negotiation In a HomeWeave network, the negotiation mechanism determines which messages a device supports and which should be used. Also, the negotiation component decides which transport mechanism to use. In other words, it determines the language spoken on the network. text/html 2010-05-17T20:50:28+02:00 http://doip.org/osc?rev=1274122228&do=diff OSC over IP as transport mechanism OSC (OpenSoundControl) is a simple format for packaging messages. It supports a variety of data types and also bundles of messages. In DoIP, OSC is a very suitable transport format. It is currently commonly implemented on top of UDP and TCP (both run on top of IP). The UDP implementation (OSC/UDP) is very simple, because it allows you to send a message to a device at any time. The TCP (OSC/TCP) implementation is a little more complex, because a device will hav… text/html 2010-05-17T20:52:12+02:00 http://doip.org/plugs?rev=1274122332&do=diff DoIP Plugs DoIP Plug devices are small form-factor devices that provide a bridge between a DoIP network and devices. In addition, they may run additional logic (such as fabrics). Plug devices are often based on an embedded platform and consume little power. A plug often runs the TJPlugManager server program, which automatically detects connected devices and starts sub-processes that connect these devices to the network. text/html 2010-05-17T20:52:31+02:00 http://doip.org/presence_detection?rev=1274122351&do=diff Bluetooth presence detection If you have a mobile phone, chances are that it has a Bluetooth radio integrated. By running a special server ('gateway') program, your mobile phone can be made part of any DoIP network, and you can have your lights turned on and off automatically depending on whether your mobile phone is in range of the Bluetooth base station. text/html 2010-02-28T09:25:11+02:00 http://doip.org/serialization?rev=1267345511&do=diff Serialization TJShared implements a serialization mechanism that allows objects to be serialized to and from an XML document. This was the first mechanism introduced; therefore, it is not as automatic or invisible as the Deepfreeze object-persistency layer in TJDB, but it is very easy to understand and use. text/html 2010-01-16T16:39:22+02:00 http://doip.org/slip?rev=1263656362&do=diff SLIP is a framing protocol that can be used to separate different messages on a stream-based connection. The SLIP protocol is defined in IETF RFC 1055, of which the most important excerpt is pasted below. In short, SLIP defines a single byte value to signal the start and end of a packet; if either value appears in the data of the packet itself, it is escaped by a special escape byte. Although the SLIP specification suggests that SLIP packets be no longer than 1066 bytes, this is not a restrictio… text/html 2010-01-23T11:45:01+02:00 http://doip.org/state_file?rev=1264243501&do=diff State file The state file indicates the state of an endpoint. It is downloaded by clients right after downloading the definition file and afterwards, if it is notified (most commonly through a change of the EPStateVersion service attribute; see DNS-SD/mDNS discovery for more information). The state file contains a list of (key, value) pairs that specify state variables. State variables can be bound to parameters (so they can be used to update the user interface) and can inform the client about … text/html 2010-02-23T22:34:43+02:00 http://doip.org/tjdb?rev=1266960883&do=diff TJDB TJDB is the database abstraction layer used in several applications. It is currently backed by SQLite, a small database engine that runs on many platforms. TJDB provides a SQL-interface to SQLite (and error handling / conversion to the types used in the SDK, such as String, Any, etc.). TJDB also provides an object persistency layer to easily persist complex object graphs with minimal work and without difficult configuration. The persistency layer is discussed below. text/html 2010-05-17T20:51:28+02:00 http://doip.org/tjfabricserver?rev=1274122288&do=diff Fabric server Fabric Server (sometimes referred to as 'TJFabric' or 'tjfabricd') is a (commercially available) server program that is able to integrate various systems (using DoIP or other protocols) using scriptable logic and automatic discovery. A 'fabric' specifies sets of devices (or a specification for discovering devices) and a set of rules that are applied to incoming messages from these devices. Each rule can have a script that defines the behaviour (and can send messages to groups of d… text/html 2010-03-26T11:14:08+02:00 http://doip.org/tjingle?rev=1269598448&do=diff TJingle TJingle is a free jingle player that allows deejays to have 400+ sounds available just two clicks or key presses away. Based on the same technology as TJShow, TJingle is also really fast and reliable. Documentation * [Keyboard cheat-sheet] (shows all keyboard combinations that you can use) text/html 2010-05-04T09:31:57+02:00 http://doip.org/tjledepserver?rev=1272958317&do=diff TJLEDEPServer TJLEDEPServer is a DoIP endpoint server program that connects (LED-)lighting controllers to a HomeWeave network. The current version supports a few devices and currently provides basic functionality for setting/fading to a particular color, dimming and power control. The TJLEDEPServer runs on Windows, Linux and Mac OS X (although device support may differ between platforms). On plugs, the EPPlugServer starts and stops a TJLEDEPServer process for each supported connected device. text/html 2010-05-04T09:40:06+02:00 http://doip.org/tjscript?rev=1272958806&do=diff TJScript TJScript is the scripting engine used in the fabric server and in TJShow. It resembles JavaScript syntax-wise, but is very different in terms of available functions. The TJScript runtime is cross-platform and is able to compile scripts to an internal bytecode format, so scripts run reasonably fast. TJScript is also built upon the memory management system from TJShared, so it works nicely together with other code that uses this. text/html 2010-03-26T11:15:45+02:00 http://doip.org/tjshow?rev=1269598545&do=diff TJShow TJShow is show controller software to create highly interactive and highly integrated shows. With the easy-to-use interface, you can create rich multimedia timelines and interaction, and control a plethora of devices and media using industry standard protocols. text/html 2010-07-20T08:58:32+02:00 http://doip.org/tjshow_faq?rev=1279609112&do=diff TJShow FAQ Installation When starting TJShow, I get an error about an 'invalid configuration'. How can this be fixed? This error appears when a particular Windows system library is not available or is of a different version. The following can be done to fix this problem: text/html 2010-03-26T11:09:12+02:00 http://doip.org/tjshow_tutorials?rev=1269598152&do=diff TJShow tutorials Some video tutorials are available to get you started with TJShow: * Creating a simple show with audio and DMX * Using instances If you have created a tutorial for TJShow, please let us know and we'll put it at this page! text/html 2010-05-17T21:34:10+02:00 http://doip.org/transport_component?rev=1274124850&do=diff The transport component of the DoIP specification is concerned with how commands (usually referred to as messages) are sent over the network to endpoint devices. The transport component consists of a transport protocol and a message format. An endpoint vendor is free to choose a protocol and format that suits the application, but it is advisable to choose one of the commonly used protocols described on this page to make sure that all clients can communicate with the endpoint. Because the definit… text/html 2010-01-16T16:39:22+02:00 http://doip.org/usingsdkwindows?rev=1263656362&do=diff Using the Windows SDK * Download the SDK installer and run it; install the SDK to any location you like * Create a new Visual Studio Solution and add at least one .cpp file * Right-click the project, go to properties and choose 'All configuration' in the leftmost dropdown list * Go to C++, General and add the SDK 'Include' directory as an additional include directory here: * Go to Linker, Input and add the library files in the SDK 'Lib' folder as dependencies: * Set the project… text/html 2010-05-17T21:33:59+02:00 http://doip.org/value_types?rev=1274124839&do=diff Value types DoIP specifies a set of types that values transferred in messages, variables and parameters are allowed to have. The type of parameters is specified in OSC messages using a 'tag' character (for example, an integer value is indicated by a single 'i' character, which stands for 'int32 variable'). In the definition file and the state file, parameter and variable types are indicated using a string. In EPFramework and in TJFabricServer (at least internally) value types are indicated by t… text/html 2010-01-23T11:30:44+02:00 http://doip.org/wake_up_light?rev=1264242644&do=diff Wake-up light Using a small fabric, it is possible to create a 'wake up light' alarm clock that fades in the lights. It would be easy to extend this to include some audio, multiple times, longer fade-in time, etcetera! <?xml version='1.0' ?> <fabric author="Tommy van der Vorst" title="Alarm clock" version="2"> <group id="input" direction="in"> <connection type="udp" /> </group> <group id="leds" direction="out"> <discover type="ep"> <requires> <supports method="/ep/basic/color…