<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>RDM Protocol</title>
	<atom:link href="http://www.rdmprotocol.org/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rdmprotocol.org</link>
	<description>Faster than the ladder!</description>
	<lastBuildDate>Tue, 19 Mar 2013 02:05:23 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>European RDM and sACN Developers Conference and Plugfest 2013</title>
		<link>http://www.rdmprotocol.org/european-rdm-and-sacn-developers-conference-and-plugfest-2013/</link>
		<comments>http://www.rdmprotocol.org/european-rdm-and-sacn-developers-conference-and-plugfest-2013/#comments</comments>
		<pubDate>Thu, 14 Feb 2013 18:39:32 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://www.rdmprotocol.org/?p=799</guid>
		<description><![CDATA[PLASA Technical Standards in action.
PLASA’s Technical Resource Office announces that the RDM and sACN Developers Conference and Plugfest returns for 2013 and will take place on the 25th-27th April, in the UK, at Gatwick Manor, London Road at Lowfield Heath, just south of Gatwick Airport.
This  [...]]]></description>
				<content:encoded><![CDATA[<p>PLASA Technical Standards in action.</p>
<p>PLASA’s Technical Resource Office announces that the RDM and sACN Developers Conference and Plugfest returns for 2013 and will take place on the 25<sup>th</sup>-27<sup>th</sup> April, in the UK, at Gatwick Manor, London Road at Lowfield Heath, just south of Gatwick Airport.</p>
<p>This Developers Conference aims to provide a European forum for manufacturers, designers, consultants and prospective users; and to ensure that the adoption of these new standards achieves desired levels of interoperability and reliability.</p>
<p>The “Conference” includes presentations in understanding, implementing and using the published PLASA control protocols suites. Discussions will also embrace the current protocol developments that form part of the PLASA Technical Standards Program.  The past 12 months has seen considerable advancement in the development of “RDMnet” – with various drafts of BSR E1.33 being offered for public review, so this is an active topic for consideration.</p>
<p>The “Plugfest” is a hands-on opportunity for product developers to try their products and code implementations with products from a variety of other manufacturers, with support from their industry peers in an environment that encourages co-operation and improved understanding of the standards, and with the aim of achieving high levels of interoperability.  Typically, engineers participate in these events with the ability to code and debug aspects of their implementations on site, sometimes retreating to their hotel rooms to craft improvements before returning to the “Plugfest” to continue testing.</p>
<p>The sessions, despite their apparent informality, can be a valuable opportunity to learn how not to make the same mistakes, or misguided assumptions, as others may have done.</p>
<p>Participation is by invitation, and limited to registered delegates.  The conference is designed to appeal to Lighting Designers, System integrators, Theatre Consultants, Production Electricians, Rental company technical staff and product development engineers. The focus for Thursday will be broad, and designed to appeal to all categories of participant.  Friday and Saturday will be orientated towards product development engineers who are either considering or actively implementing these standards.</p>
<p>A single registration fee of UK£60 per person, payable in advance, covers participation and a buffet lunch.  Delegates may attend one or more days as they think appropriate. The registration fee is fixed, regardless of the number of days you attend, but you are required to indicate your proposed level of participation in advance.</p>
<p>Further information and signup is available at <a href="http://www.plasa.org/rdm/">http://www.plasa.org/rdm/</a></p>
<p>Any enquiries should be directed to Ron Bonner at PLASA. (<a href="mailto:ron.bonner@plasa.org">ron.bonner@plasa.org</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rdmprotocol.org/european-rdm-and-sacn-developers-conference-and-plugfest-2013/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The RDM PID Popularity Contest</title>
		<link>http://www.rdmprotocol.org/rdm-pid-popularity/</link>
		<comments>http://www.rdmprotocol.org/rdm-pid-popularity/#comments</comments>
		<pubDate>Mon, 04 Feb 2013 16:19:14 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://www.rdmprotocol.org/?p=783</guid>
		<description><![CDATA[Simon Newton
4/2/2013
At the January Control Protocols Plugfest, Peter Kirkup suggested that I analyse at the data collected by the rdm.openlighting.org site and see if there are any interesting patterns in the supported parameters reported.
Of the 112 responders we have supported parameters  [...]]]></description>
				<content:encoded><![CDATA[<h5 style="text-align: center;"><em>Simon Newton</em></h5>
<p style="text-align: center;">4/2/2013</p>
<p>At the January Control Protocols Plugfest, Peter Kirkup suggested that I analyse at the data collected by the <a href="http://rdm.openlighting.org">rdm.openlighting.org</a> site and see if there are any interesting patterns in the supported parameters reported.</p>
<p>Of the 112 responders we have supported parameters information for, I took the latest software version of each and counted the number of responders that supported each PID. If a PID occurs multiple times in a SUPPORTED_PARAMETERS response, it was only counted once.</p>
<p>There are a couple of interesting trends here. Firstly, there are still some devices that continue to declare support for required PIDs. Those PIDs are highlighted in red in the table below. If you have a copy of E1.20 (RDM) around, you can refer to section 10.4.1 where it says:</p>
<p>&nbsp;</p>
<p style="text-align: center;"><em>“PIDs that are included in the minimum support list, indicated by the “Required” column of Table A-3, shall not be reported.”</em></p>
<p>I won’t name the devices here, but if you’re in the business of building responders, be sure to run the <a href="http://www.opendmx.net/index.php/RDM_Responder_Testing">RDM Responder Tests</a> against your device. It will detect problems like this.</p>
<p>Of the non-required PIDs, DEVICE_MODEL_DESCRIPTION is the most-supported, closely followed by DEVICE_LABEL and MANUFACTURER_LABEL. The least supported PIDs are ones from E1.37-1, which doesn’t come as a huge surprise since it’s still relatively new.</p>
<p>There are 5 devices which declare support for PIDs 0&#215;2070 and 0&#215;2080. These PIDs are within the PLASA standard range (0&#215;0000 &#8211; 0x7fff), but to my knowledge have not been used in any PLASA standard. If you convert the PIDs to decimal you get 8304 and 8320 so someone is probably confusing hexadecimal and decimal here. I’ve emailed the manufacturer involved.</p>
<p>QUEUED_MESSAGE is only supported in 31 responders, or 28% of those analysed.  STATUS_MESSAGE does a bit better with support in 51 responders, but CLEAR_STATUS_ID only comes in with 7. The expected behaviour of CLEAR_STATUS_ID is not well defined in the E1.20 standard, which probably contributes to the lack of support. The task group is planning on correcting this in the next iteration of RDM.</p>
<p>Sensor support is widespread, with 82 responders (73%) reporting support for SENSOR_DEFINITION and SENSOR_VALUE. Only 4 responders support RECORD_SENSORS however.</p>
<p>The <a href="http://rdm.openlighting.org/model/display?manufacturer=19792&amp;model=1610">Mac III Performance</a> wins the ‘most manufacturer specific PIDs’ (28) and the ‘most supported PIDs’  (54) categories. I suspect the LabPack XT actually beats it in the latter category, but that’s not listed in the responder index.</p>
<p>I’ve made a change to the <a href="http://rdm.openlighting.org/">rdm.openlighting.org</a> site so on the page for each PID, it now shows which responders support the PID. For example if you want to see devices which support the PROXIED_DEVICES PID, you can do so <a href="http://rdm.openlighting.org/pid/display?manufacturer=0&amp;pid=16">here</a>.</p>
<p><strong>Update</strong>: Michael Karlsson pointed out I should look at the PIDs that none of the responders supported. I&#8217;ve added a second table with this data. Of these PIDs, all except SUB_DEVICE_STATUS_REPORT_THRESHOLD are from E1.37-1.</p>
<p>&nbsp;</p>
<p style="text-align: center;">Table 1. Number of Responders Supporting each PID</p>
<table style="width: 410px; margin-left: auto; margin-right: auto;">
<tbody>
<tr>
<th>PID</th>
<th>PID Name</th>
<th># of Responders</th>
</tr>
<tr>
<td>0&#215;0001</td>
<td><span style="color: #ff0000;">DISC_UNIQUE_BRANCH</span></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;0002</td>
<td><span style="color: #ff0000;">DISC_MUTE</span></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;0003</td>
<td><span style="color: #ff0000;">DISC_UNMUTE</span></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;0010</td>
<td>PROXIED_DEVICES</td>
<td>8</td>
</tr>
<tr>
<td>0&#215;0011</td>
<td>PROXIED_DEVICE_COUNT</td>
<td>8</td>
</tr>
<tr>
<td>0&#215;0015</td>
<td>COMMS_STATUS</td>
<td>3</td>
</tr>
<tr>
<td>0&#215;0020</td>
<td>QUEUED_MESSAGE</td>
<td>31</td>
</tr>
<tr>
<td>0&#215;0030</td>
<td>STATUS_MESSAGE</td>
<td>51</td>
</tr>
<tr>
<td>0&#215;0031</td>
<td>STATUS_ID_DESCRIPTION</td>
<td>37</td>
</tr>
<tr>
<td>0&#215;0032</td>
<td>CLEAR_STATUS_ID</td>
<td>7</td>
</tr>
<tr>
<td>0&#215;0050</td>
<td><span style="color: #ff0000;">SUPPORTED_PARAMETERS</span></td>
<td>14</td>
</tr>
<tr>
<td>0&#215;0051</td>
<td><span style="color: #ff0000;">PARAMETER_DESCRIPTION</span></td>
<td>25</td>
</tr>
<tr>
<td>0&#215;0060</td>
<td><span style="color: #ff0000;">DEVICE_INFO</span></td>
<td>4</td>
</tr>
<tr>
<td>0&#215;0070</td>
<td>PRODUCT_DETAIL_ID_LIST</td>
<td>16</td>
</tr>
<tr>
<td>0&#215;0080</td>
<td>DEVICE_MODEL_DESCRIPTION</td>
<td>110</td>
</tr>
<tr>
<td>0&#215;0081</td>
<td>MANUFACTURER_LABEL</td>
<td>109</td>
</tr>
<tr>
<td>0&#215;0082</td>
<td>DEVICE_LABEL</td>
<td>107</td>
</tr>
<tr>
<td>0&#215;0090</td>
<td>FACTORY_DEFAULTS</td>
<td>34</td>
</tr>
<tr>
<td>0x00a0</td>
<td>LANGUAGE_CAPABILITIES</td>
<td>20</td>
</tr>
<tr>
<td>0x00b0</td>
<td>LANGUAGE</td>
<td>1</td>
</tr>
<tr>
<td>0x00c0</td>
<td><span style="color: #ff0000;">SOFTWARE_VERSION_LABEL</span></td>
<td>11</td>
</tr>
<tr>
<td>0x00c1</td>
<td>BOOT_SOFTWARE_VERSION</td>
<td>5</td>
</tr>
<tr>
<td>0x00c2</td>
<td>BOOT_SOFTWARE_LABEL</td>
<td>3</td>
</tr>
<tr>
<td>0x00e0</td>
<td>DMX_PERSONALITY</td>
<td>76</td>
</tr>
<tr>
<td>0x00e1</td>
<td>DMX_PERSONALITY_DESCRIPTION</td>
<td>75</td>
</tr>
<tr>
<td>0x00f0</td>
<td><span style="color: #ff0000;">DMX_START_ADDRESS</span></td>
<td>36</td>
</tr>
<tr>
<td>0&#215;0120</td>
<td>SLOT_INFO</td>
<td>45</td>
</tr>
<tr>
<td>0&#215;0121</td>
<td>SLOT_DESCRIPTION</td>
<td>57</td>
</tr>
<tr>
<td>0&#215;0122</td>
<td>DEFAULT_SLOT_VALUE</td>
<td>39</td>
</tr>
<tr>
<td>0&#215;0141</td>
<td>DMX_FAIL_MODE</td>
<td>1</td>
</tr>
<tr>
<td>0&#215;0200</td>
<td>SENSOR_DEFINITION</td>
<td>82</td>
</tr>
<tr>
<td>0&#215;0201</td>
<td>SENSOR_VALUE</td>
<td>82</td>
</tr>
<tr>
<td>0&#215;0202</td>
<td>RECORD_SENSORS</td>
<td>4</td>
</tr>
<tr>
<td>0&#215;0340</td>
<td>DIMMER_INFO</td>
<td>1</td>
</tr>
<tr>
<td>0&#215;0341</td>
<td>MINIMUM_LEVEL</td>
<td>1</td>
</tr>
<tr>
<td>0&#215;0342</td>
<td>MAXIMUM_LEVEL</td>
<td>1</td>
</tr>
<tr>
<td>0&#215;0343</td>
<td>CURVE</td>
<td>3</td>
</tr>
<tr>
<td>0&#215;0344</td>
<td>CURVE_DESCRIPTION</td>
<td>3</td>
</tr>
<tr>
<td>0&#215;0345</td>
<td>OUTPUT_RESPONSE_TIME</td>
<td>2</td>
</tr>
<tr>
<td>0&#215;0346</td>
<td>OUTPUT_RESPONSE_TIME_DESCRIPTION</td>
<td>2</td>
</tr>
<tr>
<td>0&#215;0347</td>
<td>MODULATION_FREQUENCY</td>
<td>1</td>
</tr>
<tr>
<td>0&#215;0348</td>
<td>MODULATION_FREQUENCY_DESCRIPTION</td>
<td>1</td>
</tr>
<tr>
<td>0&#215;0400</td>
<td>DEVICE_HOURS</td>
<td>50</td>
</tr>
<tr>
<td>0&#215;0401</td>
<td>LAMP_HOURS</td>
<td>23</td>
</tr>
<tr>
<td>0&#215;0402</td>
<td>LAMP_STRIKES</td>
<td>20</td>
</tr>
<tr>
<td>0&#215;0403</td>
<td>LAMP_STATE</td>
<td>15</td>
</tr>
<tr>
<td>0&#215;0404</td>
<td>LAMP_ON_MODE</td>
<td>3</td>
</tr>
<tr>
<td>0&#215;0405</td>
<td>DEVICE_POWER_CYCLES</td>
<td>15</td>
</tr>
<tr>
<td>0&#215;0500</td>
<td>DISPLAY_INVERT</td>
<td>31</td>
</tr>
<tr>
<td>0&#215;0501</td>
<td>DISPLAY_LEVEL</td>
<td>37</td>
</tr>
<tr>
<td>0&#215;0600</td>
<td>PAN_INVERT</td>
<td>34</td>
</tr>
<tr>
<td>0&#215;0601</td>
<td>TILT_INVERT</td>
<td>34</td>
</tr>
<tr>
<td>0&#215;0602</td>
<td>PAN_TILT_SWAP</td>
<td>9</td>
</tr>
<tr>
<td>0&#215;0603</td>
<td>REAL_TIME_CLOCK</td>
<td>5</td>
</tr>
<tr>
<td>0&#215;0640</td>
<td>LOCK_PIN</td>
<td>1</td>
</tr>
<tr>
<td>0&#215;0641</td>
<td>LOCK_STATE</td>
<td>1</td>
</tr>
<tr>
<td>0&#215;0642</td>
<td>LOCK_STATE_DESCRIPTION</td>
<td>1</td>
</tr>
<tr>
<td>0&#215;1000</td>
<td><span style="color: #ff0000;">IDENTIFY_DEVICE</span></td>
<td>4</td>
</tr>
<tr>
<td>0&#215;1001</td>
<td>RESET_DEVICE</td>
<td>60</td>
</tr>
<tr>
<td>0&#215;1010</td>
<td>POWER_STATE</td>
<td>6</td>
</tr>
<tr>
<td>0&#215;1020</td>
<td>PERFORM_SELF_TEST</td>
<td>11</td>
</tr>
<tr>
<td>0&#215;1021</td>
<td>SELF_TEST_DESCRIPTION</td>
<td>4</td>
</tr>
<tr>
<td>0&#215;1030</td>
<td>CAPTURE_PRESET</td>
<td>2</td>
</tr>
<tr>
<td>0&#215;1031</td>
<td>PRESET_PLAYBACK</td>
<td>2</td>
</tr>
<tr>
<td>0&#215;1040</td>
<td>IDENTIFY_MODE</td>
<td>2</td>
</tr>
<tr>
<td>0&#215;2070</td>
<td></td>
<td>5</td>
</tr>
<tr>
<td>0&#215;2080</td>
<td></td>
<td>5</td>
</tr>
<tr>
<td>0&#215;8000</td>
<td></td>
<td>20</td>
</tr>
<tr>
<td>0&#215;8001</td>
<td></td>
<td>13</td>
</tr>
<tr>
<td>0&#215;8002</td>
<td></td>
<td>7</td>
</tr>
<tr>
<td>0&#215;8003</td>
<td></td>
<td>6</td>
</tr>
<tr>
<td>0&#215;8004</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8005</td>
<td></td>
<td>4</td>
</tr>
<tr>
<td>0&#215;8006</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8007</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8008</td>
<td></td>
<td>3</td>
</tr>
<tr>
<td>0&#215;8009</td>
<td></td>
<td>3</td>
</tr>
<tr>
<td>0x800a</td>
<td></td>
<td>7</td>
</tr>
<tr>
<td>0x800b</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0x800c</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0x800d</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8010</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8011</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8012</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8014</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8015</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8016</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8017</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8018</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8019</td>
<td></td>
<td>3</td>
</tr>
<tr>
<td>0x801a</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0x801b</td>
<td></td>
<td>5</td>
</tr>
<tr>
<td>0x801c</td>
<td></td>
<td>5</td>
</tr>
<tr>
<td>0x801d</td>
<td></td>
<td>3</td>
</tr>
<tr>
<td>0x801e</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0x801f</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8020</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8030</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8050</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8051</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0x80dd</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0x80f1</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8100</td>
<td></td>
<td>4</td>
</tr>
<tr>
<td>0&#215;8101</td>
<td></td>
<td>11</td>
</tr>
<tr>
<td>0&#215;8102</td>
<td></td>
<td>11</td>
</tr>
<tr>
<td>0&#215;8103</td>
<td></td>
<td>8</td>
</tr>
<tr>
<td>0&#215;8104</td>
<td></td>
<td>7</td>
</tr>
<tr>
<td>0&#215;8105</td>
<td></td>
<td>6</td>
</tr>
<tr>
<td>0&#215;8106</td>
<td></td>
<td>7</td>
</tr>
<tr>
<td>0&#215;8107</td>
<td></td>
<td>7</td>
</tr>
<tr>
<td>0&#215;8108</td>
<td></td>
<td>4</td>
</tr>
<tr>
<td>0&#215;8109</td>
<td></td>
<td>7</td>
</tr>
<tr>
<td>0x810a</td>
<td></td>
<td>6</td>
</tr>
<tr>
<td>0x810b</td>
<td></td>
<td>6</td>
</tr>
<tr>
<td>0x810c</td>
<td></td>
<td>6</td>
</tr>
<tr>
<td>0x810d</td>
<td></td>
<td>5</td>
</tr>
<tr>
<td>0x810e</td>
<td></td>
<td>6</td>
</tr>
<tr>
<td>0x810f</td>
<td></td>
<td>4</td>
</tr>
<tr>
<td>0&#215;8111</td>
<td></td>
<td>4</td>
</tr>
<tr>
<td>0&#215;8112</td>
<td></td>
<td>4</td>
</tr>
<tr>
<td>0&#215;8113</td>
<td></td>
<td>4</td>
</tr>
<tr>
<td>0&#215;8114</td>
<td></td>
<td>4</td>
</tr>
<tr>
<td>0&#215;8115</td>
<td></td>
<td>4</td>
</tr>
<tr>
<td>0&#215;8116</td>
<td></td>
<td>4</td>
</tr>
<tr>
<td>0&#215;8117</td>
<td></td>
<td>4</td>
</tr>
<tr>
<td>0&#215;8118</td>
<td></td>
<td>4</td>
</tr>
<tr>
<td>0&#215;8120</td>
<td></td>
<td>3</td>
</tr>
<tr>
<td>0&#215;8121</td>
<td></td>
<td>4</td>
</tr>
<tr>
<td>0&#215;8122</td>
<td></td>
<td>3</td>
</tr>
<tr>
<td>0&#215;8123</td>
<td></td>
<td>3</td>
</tr>
<tr>
<td>0&#215;8124</td>
<td></td>
<td>3</td>
</tr>
<tr>
<td>0&#215;8125</td>
<td></td>
<td>3</td>
</tr>
<tr>
<td>0&#215;8126</td>
<td></td>
<td>3</td>
</tr>
<tr>
<td>0&#215;8127</td>
<td></td>
<td>3</td>
</tr>
<tr>
<td>0&#215;8130</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8150</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8160</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8190</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8191</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8192</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8201</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8202</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8203</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8204</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8300</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8301</td>
<td></td>
<td>3</td>
</tr>
<tr>
<td>0&#215;8302</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8305</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8306</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8307</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8308</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8310</td>
<td></td>
<td>3</td>
</tr>
<tr>
<td>0&#215;8311</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8312</td>
<td></td>
<td>3</td>
</tr>
<tr>
<td>0&#215;8330</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8331</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8332</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8340</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8400</td>
<td></td>
<td>3</td>
</tr>
<tr>
<td>0&#215;8401</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8402</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8403</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8404</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8405</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8406</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8407</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8500</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8501</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8502</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8503</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8602</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8603</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8604</td>
<td></td>
<td>3</td>
</tr>
<tr>
<td>0&#215;8700</td>
<td></td>
<td>9</td>
</tr>
<tr>
<td>0&#215;8702</td>
<td></td>
<td>2</td>
</tr>
<tr>
<td>0&#215;8703</td>
<td></td>
<td>5</td>
</tr>
<tr>
<td>0&#215;8704</td>
<td></td>
<td>5</td>
</tr>
<tr>
<td>0&#215;8705</td>
<td></td>
<td>6</td>
</tr>
<tr>
<td>0&#215;8706</td>
<td></td>
<td>6</td>
</tr>
<tr>
<td>0&#215;8707</td>
<td></td>
<td>6</td>
</tr>
<tr>
<td>0&#215;8800</td>
<td></td>
<td>4</td>
</tr>
<tr>
<td>0&#215;8802</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;8803</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0x8a00</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0x8a0c</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0x8a40</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0x8a41</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0x8a42</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0x8a44</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0x8a92</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0x8a94</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0x8aa0</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0x8aa1</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0x8aa2</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0x8ab0</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0x8ab1</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0x8ab2</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0x8ac0</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0x8ac2</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;9000</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;9002</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;9004</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;9005</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;9010</td>
<td></td>
<td>8</td>
</tr>
<tr>
<td>0&#215;9020</td>
<td></td>
<td>8</td>
</tr>
<tr>
<td>0&#215;9050</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;9054</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0&#215;9059</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0xc860</td>
<td></td>
<td>1</td>
</tr>
<tr>
<td>0xff01</td>
<td></td>
<td>1</td>
</tr>
</tbody>
</table>
<p style="text-align: center;">Table 2. PIDs which none of the 112 responders support</p>
<table style="width: 410px; margin-left: auto; margin-right: auto;">
<tbody>
<tr>
<th>PID</th>
<th>PID Name</th>
</tr>
<tr>
<td>0&#215;0033</td>
<td>SUB_DEVICE_STATUS_REPORT_THRESHOLD</td>
</tr>
<tr>
<td>0&#215;0140</td>
<td>DMX_BLOCK_ADDRESS</td>
</tr>
<tr>
<td>0&#215;0142</td>
<td>DMX_STARTUP_MODE</td>
</tr>
<tr>
<td>0&#215;0440</td>
<td>BURN_IN</td>
</tr>
<tr>
<td>0&#215;1041</td>
<td>PRESET_INFO</td>
</tr>
<tr>
<td>0&#215;1042</td>
<td>PRESET_STATUS</td>
</tr>
<tr>
<td>0&#215;1043</td>
<td>PRESET_MERGE_MODE</td>
</tr>
<tr>
<td>0&#215;1044</td>
<td>POWER_ON_SELF_TEST</td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://www.rdmprotocol.org/rdm-pid-popularity/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Second European E1.20 Remote Device Management Conference and Plugfest heralded as another great success</title>
		<link>http://www.rdmprotocol.org/second-european-e1-20-remote-device-management-conference-and-plugfest-heralded-as-another-great-success/</link>
		<comments>http://www.rdmprotocol.org/second-european-e1-20-remote-device-management-conference-and-plugfest-heralded-as-another-great-success/#comments</comments>
		<pubDate>Sun, 14 Oct 2012 16:05:32 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://www.rdmprotocol.org/?p=765</guid>
		<description><![CDATA[European lighting manufacturers implementing the Remote Device Management (RDM) protocol (ANSI E1.20-2010 Standard: Remote Device Management over USITT DMX512 ), met again recently for a two day conference and Plugfest near Gatwick Airport in the UK.
Organised by Peter Willis (Howard Eaton  [...]]]></description>
				<content:encoded><![CDATA[<p>European lighting manufacturers implementing the Remote Device Management (RDM) protocol (ANSI E1.20-2010 Standard: Remote Device Management over USITT DMX512 ), met again recently for a two day conference and Plugfest near Gatwick Airport in the UK.</p>
<p>Organised by Peter Willis (Howard Eaton Lighting), Simon Hobday (Artistic Licence Engineering), Hamish Dumbreck (Jese Ltd) and Peter Kirkup (Lumen Radio), in conjunction with PLASA’s Technical Resources Manager, Ron Bonner, the event attracted some 35 engineers from over 22 manufacturing companies, with representation across the Entertainment and Architectural lighting sectors.</p>
<p>The conference kicked off with a review of the impact of the RDM exhibition stand presented at the recent PLASA show at Earl’s Court, and the issues of compliance that sometimes surface whilst attempting to utilise RDM enabled products.</p>
<p>Discussions on possible methods for reviewing products and their adherence to the standard ensued, with separate proposals for Responders, Data Distribution (Splitters) and Controllers emerging.</p>
<p>As always, Plugfests provide an opportunity for engineers to scrutinise their product’s operation in conjunction with a variety of other devices, make changes as required and re-evaluate. It is also an opportunity to discuss best practices, identify known pitfalls and improve your product for the benefit of the industry as a whole.</p>
<p>On the second day, an attempt was made to trial a procedure for evaluating responders, in an effort to facilitate a more robust and standardised means of reviewing RDM compatibility.</p>
<p>Based on initial feedback, it is clear that these events should be regular, to enable manufactures to build consistency into their products, and planning is now underway for further activities in 2013.</p>
<p>For those companies actively involved with (or who are considering) implementing RDM and have not yet attended a Plugfest, the PLASA Technical Resource Office would encourage you make to the effort to support and attend future events.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rdmprotocol.org/second-european-e1-20-remote-device-management-conference-and-plugfest-heralded-as-another-great-success/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>European RDM Plugfest Report</title>
		<link>http://www.rdmprotocol.org/gatwick2012-2/</link>
		<comments>http://www.rdmprotocol.org/gatwick2012-2/#comments</comments>
		<pubDate>Wed, 10 Oct 2012 01:59:35 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[plugfest]]></category>

		<guid isPermaLink="false">http://www.rdmprotocol.org/?p=728</guid>
		<description><![CDATA[Simon Newton
4/10/2012 &#8211; 5/10/2012

I recently attended the RDM plugfest in Gatwick and had the opportunity to run the RDM Responder Tests on diverse set of responders. At the suggestion of Peter Kirkup, I&#8217;ve run some analysis on the data in an attempt to understand how the quality of RDM  [...]]]></description>
				<content:encoded><![CDATA[<h5 style="text-align: center;"><em>Simon Newton</em></h5>
<p style="text-align: center;">4/10/2012 &#8211; 5/10/2012</p>
<p><img class="size-medium wp-image-753 alignright" title="Engineers at work" src="http://www.rdmprotocol.org/webtest/wp-content/uploads/2012/10/DCP_4640-300x225.jpeg" alt="" width="300" height="225" /></p>
<p>I recently attended the RDM plugfest in Gatwick and had the opportunity to run the <a href="http://www.opendmx.net/index.php/RDM_Responder_Testing">RDM Responder Tests</a> on diverse set of responders. At the suggestion of Peter Kirkup, I&#8217;ve run some analysis on the data in an attempt to understand how the quality of RDM implementations is progressing.  The data presented here has been aggregated and anonymized so that test results for any specific manufacture aren&#8217;t identifiable. The tests themselves do not perform exhaustive timing checks so even if a responder achieves a perfect score it may not fully comply with the RDM standard.</p>
<p>The procedure involved running the RDM Responder Tests (git SHA1 id <a href="http://code.google.com/p/open-lighting/source/detail?r=58fb444b9342ea6d9ba70ecdda8f720cc88692ff">58fb444b9342ea6d9ba70ecdda8f720cc88692ff</a> for those who are interested) on a Macbook Pro with a Robe Universal Interface.  During the course of testing I found two bugs in the RDM tests which caused the test script to crash. I fixed both bugs and since these bugs caused crashes rather than false positives, the bugs would not have affected the results of the responders tested prior to the bugs being found.</p>
<p>In total 27 responders from 20 manufacturers were tested. 7 of the 27 responders received perfect scores, which is the highest result ever for a plugfest. At previous plugfests only two responders have managed a similar result. Congratulations to Cooper Controls &#8211; Zero 88, Creative Lighting, Howard Eaton Lighting Limited, LumenRadio &amp; SUMOLIGHT GMBH. The test scores for each responder is shown in Table 1.</p>
<div style="text-align: center;">
<table style="width: 410px; margin-left: auto; margin-right: auto;">
<colgroup>
<col width="116" />
<col width="92" />
<col width="91" />
<col width="108" /></colgroup>
<tbody>
<tr>
<th>Responder Name</th>
<th>Tests Passed</th>
<th>Tests Run</th>
<th>Pass Rate (%)</th>
</tr>
<tr>
<td>Responder 1</td>
<td>231</td>
<td>231</td>
<td>100.0</td>
</tr>
<tr>
<td>Responder 2</td>
<td>231</td>
<td>231</td>
<td>100.0</td>
</tr>
<tr>
<td>Responder 3</td>
<td>229</td>
<td>229</td>
<td>100.0</td>
</tr>
<tr>
<td>Responder 4</td>
<td>232</td>
<td>232</td>
<td>100.0</td>
</tr>
<tr>
<td>Responder 5</td>
<td>233</td>
<td>233</td>
<td>100.0</td>
</tr>
<tr>
<td>Responder 6</td>
<td>229</td>
<td>229</td>
<td>100.0</td>
</tr>
<tr>
<td>Responder 7</td>
<td>229</td>
<td>229</td>
<td>100.0</td>
</tr>
<tr>
<td>Responder 8</td>
<td>229</td>
<td>232</td>
<td>98.7</td>
</tr>
<tr>
<td>Responder 9</td>
<td>226</td>
<td>231</td>
<td>97.8</td>
</tr>
<tr>
<td>Responder 10</td>
<td>224</td>
<td>230</td>
<td>97.4</td>
</tr>
<tr>
<td>Responder 11</td>
<td>226</td>
<td>233</td>
<td>97.0</td>
</tr>
<tr>
<td>Responder 12</td>
<td>223</td>
<td>231</td>
<td>96.5</td>
</tr>
<tr>
<td>Responder 13</td>
<td>224</td>
<td>233</td>
<td>96.1</td>
</tr>
<tr>
<td>Responder 14</td>
<td>217</td>
<td>228</td>
<td>95.2</td>
</tr>
<tr>
<td>Responder 15</td>
<td>220</td>
<td>233</td>
<td>94.4</td>
</tr>
<tr>
<td>Responder 16</td>
<td>214</td>
<td>229</td>
<td>93.4</td>
</tr>
<tr>
<td>Responder 17</td>
<td>205</td>
<td>220</td>
<td>93.2</td>
</tr>
<tr>
<td>Responder 18</td>
<td>214</td>
<td>234</td>
<td>91.5</td>
</tr>
<tr>
<td>Responder 19</td>
<td>206</td>
<td>228</td>
<td>90.4</td>
</tr>
<tr>
<td>Responder 20</td>
<td>185</td>
<td>209</td>
<td>88.5</td>
</tr>
<tr>
<td>Responder 21</td>
<td>185</td>
<td>209</td>
<td>88.5</td>
</tr>
<tr>
<td>Responder 22</td>
<td>187</td>
<td>222</td>
<td>84.2</td>
</tr>
<tr>
<td>Responder 23</td>
<td>191</td>
<td>231</td>
<td>82.7</td>
</tr>
<tr>
<td>Responder 24</td>
<td>62</td>
<td>204</td>
<td>30.4</td>
</tr>
<tr>
<td>Responder 25</td>
<td>37</td>
<td>154</td>
<td>24.0</td>
</tr>
<tr>
<td>Responder 26</td>
<td>37</td>
<td>154</td>
<td>24.0</td>
</tr>
<tr>
<td>Responder 27</td>
<td>31</td>
<td>190</td>
<td>16.3</td>
</tr>
</tbody>
</table>
<p><strong id="internal-source-marker_0.011838254984468222">Table 1. Summary of results by responder</strong></p>
</div>
<p>&nbsp;</p>
<p>The median score is 95.2% and the median number of tests run is 229 out of 235 tests. Note that not every test is run for each responder because there is often a dependency chain between two or more tests. For example the tests need to know if a PID is supported before they know what to expect when sending a GET command for that PID.  If a test that other tests depend on fails, then the number of tests run will be reduced as is the case for the last responders in the table.</p>
<p>Each test is assigned to a category, which roughly corresponds to the RDM Categories/Parameter ID Defines table in the E1.20 document. When broken down by category, the results are seen in Table 2.</p>
<div style="text-align: center;">
<table style="width: 300px; margin-left: auto; margin-right: auto;">
<tbody>
<tr>
<th>Test Category</th>
<th>Pass Rate (%)</th>
</tr>
<tr>
<td>Core Functionality</td>
<td>95.7</td>
</tr>
<tr>
<td>Display Settings</td>
<td>91.3</td>
</tr>
<tr>
<td>Status Collection</td>
<td>90.7</td>
</tr>
<tr>
<td>Power / Lamp Settings</td>
<td>90.5</td>
</tr>
<tr>
<td>Network Management</td>
<td>90.4</td>
</tr>
<tr>
<td>Sensors</td>
<td>89.3</td>
</tr>
<tr>
<td>DMX512 Setup</td>
<td>89.2</td>
</tr>
<tr>
<td>Configuration</td>
<td>88.4</td>
</tr>
<tr>
<td>Control</td>
<td>86.9</td>
</tr>
<tr>
<td>Product Information</td>
<td>86.9</td>
</tr>
<tr>
<td>Dimmer Settings</td>
<td>84</td>
</tr>
<tr>
<td>Error Conditions</td>
<td>82.4</td>
</tr>
<tr>
<td>RDM Information</td>
<td>72.2</td>
</tr>
<tr>
<td>Sub Devices</td>
<td>54.8</td>
</tr>
</tbody>
</table>
<p><strong id="internal-source-marker_0.011838254984468222">Table 2. Per Category Pass Rates.</strong></p>
</div>
<p>&nbsp;</p>
<p>The RDM Responder Tests also produce warnings to indicate responder behavior which, while not serious enough to cause a failure, should still be correctly handled. Five responders produced no warnings. The maximum warnings produced was 261 and the median was 10.</p>
<p>Finally Table 3 shows the pass results for each test. This provides a useful insight into which areas of an RDM implementation are most often overlooked. Ignoring the tests which cover error conditions, the most common failure is the <em>SetPersonality</em>, followed by <em>ResetFactoryDefaults</em> &amp; <em>GetParamDescription.</em></p>
<table>
<colgroup>
<col width="116" />
<col width="89" />
<col width="419" /></colgroup>
<tbody>
<tr>
<th>Pass Rate (%)</th>
<th># of Tests</th>
<th>Test Names</th>
</tr>
<tr>
<td>100</td>
<td>29</td>
<td>CheckSensorConsistency, DUBFullTree, DUBInvertedFullTree, DUBInvertedRange, DUBManufacturerTree, DUBNegativeUpperBound, DUBSignedComparisons, DUBSingleUpperUID, GetDeviceInfoWithData, GetManufacturerLabel, GetSoftwareVersionLabel, GetSoftwareVersionLabelWithData, GetSupportedParameters, ProxiedDevicesControlField, SetBroadcastStartAddress, SetBurnIn, SetDMXBlockAddress, SetDevicePowerCyclesWithNoData, SetDisplayInvert, SetDisplayLevel, SetIdentifyMode, SetLampState, SetLanguage, SetPanInvert, SetPanTiltSwap, SetPowerOnSelfTest, SetPowerState, SetUnsupportedLanguage, SetVendorcastStartAddress</td>
</tr>
<tr>
<td>96</td>
<td>2</td>
<td>ClearStatusMessages, ClearStatusMessagesWithData</td>
</tr>
<tr>
<td>95.7</td>
<td>2</td>
<td>GetSlotDescriptions, GetStartAddress</td>
</tr>
<tr>
<td>95.5</td>
<td>2</td>
<td>GetPersonalityDescriptions, GetSensorValues</td>
</tr>
<tr>
<td>95.2</td>
<td>17</td>
<td>DUBAffirmativeLowerBound, DUBAffirmativeUpperBound, DUBDifferentManufacturer, DUBInvertedLowerUID, DUBInvertedUpperUID, DUBNegativeLowerBound, DUBNegativeVendorcast, DUBSingleLowerUID, DUBSingleUID, GetDefaultSlotValues, GetProxiedDeviceCount, RequestsWhileUnmuted, ResetDevicePowerCycles, SetDeviceLabel, SetDevicePowerCycles, SetLampHours, SetLampStrikesWithNoData</td>
</tr>
<tr>
<td>95</td>
<td>1</td>
<td>SetVendorcastDeviceLabel</td>
</tr>
<tr>
<td>93.8</td>
<td>1</td>
<td>RecordAllSensorValues</td>
</tr>
<tr>
<td>92</td>
<td>23</td>
<td>ClearCommsStatus, FindSelfTests, GetDeviceHoursWithData, GetDeviceInfo, GetDeviceModelDescriptionWithData, GetDisplayInvertWithData, GetLampHoursWithData, GetLampOnMode, GetLampStrikes, GetManufacturerLabelWithData, GetPresetMergeModeWithData, GetProxiedDeviceCountWithData, GetProxiedDevicesWithData, GetTiltInvert, GetTiltInvertWithData, MuteDevice, SetBurnInWithNoData, SetPanInvertWithNoData, SetParamDescription, SetProxiedDevices, SetSlotDescription, SetSlotInfo, SetTiltInvertWithNoData</td>
</tr>
<tr>
<td>91.3</td>
<td>7</td>
<td>GetPersonality, GetPersonalityDescription, GetSensorDefinition, SetLampOnMode, SetLampStrikes, SetTiltInvert, UnMuteDevice</td>
</tr>
<tr>
<td>90.9</td>
<td>2</td>
<td>RecordSensorValues, RecordUndefinedSensorValues</td>
</tr>
<tr>
<td>90.5</td>
<td>8</td>
<td>DUBPositiveVendorcast, SetBroadcastIdentifyDevice, SetDeviceHours, SetFullSizeDeviceLabel, SetIdentifyDevice, SetNonAsciiDeviceLabel, SetVendorcastIdentifyDevice, SubDeviceControlField</td>
</tr>
<tr>
<td>90</td>
<td>2</td>
<td>SetBroadcastDeviceLabel, SetLampHoursWithNoData</td>
</tr>
<tr>
<td>88</td>
<td>9</td>
<td>GetDeviceModelDescription, GetFactoryDefaults, GetFactoryDefaultsWithData, GetRecordSensors, GetSupportedParametersWithData, InvalidDiscoveryPID, RecordSensorValueWithNoData, SetPerformSelfTestWithNoData, SetPowerStateWithNoData</td>
</tr>
<tr>
<td>86.4</td>
<td>1</td>
<td>GetUndefinedSensorValues</td>
</tr>
<tr>
<td>85.7</td>
<td>3</td>
<td>DUBPositiveUnicast, SetEmptyDeviceLabel, SetOtherVendorcastIdentifyDevice</td>
</tr>
<tr>
<td>84.2</td>
<td>1</td>
<td>SetDeviceHoursWithNoData</td>
</tr>
<tr>
<td>84</td>
<td>68</td>
<td>ClearCommsStatusWithData, GetBootSoftwareLabel, GetBootSoftwareLabelWithData, GetBootSoftwareVersion, GetBootSoftwareVersionWithData, GetBurnIn, GetBurnInWithData, GetCapturePreset, GetCommsStatus, GetCommsStatusWithData, GetDMXBlockAddress, GetDMXBlockAddressWithData, GetDeviceHours, GetDeviceLabel, GetDeviceLabelWithData, GetDevicePowerCycles, GetDevicePowerCyclesWithData, GetDimmerInfo, GetDimmerInfoWithData, GetDisplayInvert, GetDisplayLevel, GetDisplayLevelWithData, GetIdentifyDevice, GetIdentifyDeviceWithData, GetIdentifyMode, GetIdentifyModeWithData, GetLampHours, GetLampOnModeWithData, GetLampState, GetLampStateWithData, GetLampStrikesWithData, GetLanguage, GetPanInvert, GetPanInvertWithData, GetPanTiltSwap, GetPanTiltSwapWithData, GetPowerOnSelfTest, GetPowerOnSelfTestWithData, GetPowerState, GetPowerStateWithData, GetPresetMergeMode, GetPresetPlayback, GetPresetPlaybackWithData, GetProductDetailIdList, GetProductDetailIdListWithData, GetProxiedDevices, GetRealTimeClock, GetRealTimeClockWithData, GetSelfTestDescription, GetSelfTestDescriptionWithNoData, GetSlotInfo, SetBootSoftwareLabel, SetBootSoftwareVersion, SetCapturePresetWithNoData, SetDMXBlockAddressWithNoData, SetDefaultSlotInfo, SetDimmerInfo, SetLampOnModeWithNoData, SetLampStateWithNoData, SetPanTiltSwapWithNoData, SetPowerOnSelfTestWithNoData, SetPresetPlayback, SetPresetPlaybackWithNoData, SetProductDetailIdList, SetProxiedDeviceCount, SetRealTimeClockWithNoData, SetZeroDMXBlockAddress, SetZeroPersonality</td>
</tr>
<tr>
<td>82.6</td>
<td>1</td>
<td>SetOutOfRangePersonality</td>
</tr>
<tr>
<td>81.8</td>
<td>1</td>
<td>ResetSensorValue</td>
</tr>
<tr>
<td>80</td>
<td>25</td>
<td>CapturePreset, GetDefaultSlotInfoWithData, GetInvalidSensorDefinition, GetLanguageCapabilities, GetLanguageCapabilitiesWithData, GetMaxPacketSize, GetParamDescriptionForNonManufacturerPid, GetPerformSelfTest, GetPerformSelfTestWithData, GetSlotInfoWithData, ResetFactoryDefaultsWithData, SetDeviceInfo, SetDeviceModelDescription, SetDeviceModelDescriptionWithData, SetDisplayInvertWithNoData, SetDisplayLevelWithNoData, SetIdentifyModeWithNoData, SetManufacturerLabel, SetManufacturerLabelWithData, SetOversizedDMXBlockAddress, SetPerformSelfTest, SetRealTimeClock, SetSensorDefinition, SetSoftwareVersionLabel, SetSupportedParameters</td>
</tr>
<tr>
<td>78.3</td>
<td>2</td>
<td>GetOutOfRangePersonalityDescription, SetOutOfRangeStartAddress</td>
</tr>
<tr>
<td>77.3</td>
<td>1</td>
<td>ResetAllSensorValues</td>
</tr>
<tr>
<td>76</td>
<td>1</td>
<td>SetNonAsciiLanguage</td>
</tr>
<tr>
<td>72.7</td>
<td>2</td>
<td>ResetUndefinedSensorValues, SetStartAddress</td>
</tr>
<tr>
<td>72.2</td>
<td>1</td>
<td>GetParamDescription</td>
</tr>
<tr>
<td>72</td>
<td>2</td>
<td>GetClearStatusMessages, GetZeroPersonalityDescription</td>
</tr>
<tr>
<td>68</td>
<td>4</td>
<td>GetInvalidSensorValue, GetSensorDefinitionWithTooMuchData, GetSlotDescriptionWithNoData, GetSlotDescriptionWithTooMuchData</td>
</tr>
<tr>
<td>66.7</td>
<td>3</td>
<td>FindSubDevices, SetOutOfRangeIdentifyDevice, SetOversizedDeviceLabel</td>
</tr>
<tr>
<td>65.2</td>
<td>1</td>
<td>SetZeroStartAddress</td>
</tr>
<tr>
<td>64</td>
<td>2</td>
<td>GetParamDescriptionWithData, ResetSensorValueWithNoData</td>
</tr>
<tr>
<td>60</td>
<td>3</td>
<td>GetSensorDefinitionWithNoData, ResetFactoryDefaults, SetOversizedPersonality</td>
</tr>
<tr>
<td>58.8</td>
<td>1</td>
<td>SetPersonality</td>
</tr>
<tr>
<td>52.4</td>
<td>1</td>
<td>SetIdentifyDeviceWithNoData</td>
</tr>
<tr>
<td>52.2</td>
<td>1</td>
<td>SetOversizedStartAddress</td>
</tr>
<tr>
<td>52</td>
<td>2</td>
<td>AllSubDevicesDeviceInfo, GetSensorValueWithNoData</td>
</tr>
<tr>
<td>48</td>
<td>1</td>
<td>MuteDeviceWithData</td>
</tr>
<tr>
<td>40</td>
<td>1</td>
<td>UnMuteDeviceWithData</td>
</tr>
</tbody>
</table>
<div style="text-align: center;"><strong id="internal-source-marker_0.011838254984468222">Table 3. Per test pass rates.</strong></div>
<div style="text-align: center;"></div>
<p>I plan to continue performing this analysis at future plugfests so we&#8217;ll have an idea of how RDM implementations are improving. It will be useful to track the maturity of RDM responders and well as monitor the diversity of manufacturers and devices we see at the plugfests.  Judging by the amount of work that got done over the 2 days I think we can expect even better scores next time! Stay tuned for another report after the Dallas plugfest in January 2013.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rdmprotocol.org/gatwick2012-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New Look Stand for RDM at PLASA</title>
		<link>http://www.rdmprotocol.org/new-look-stand-for-rdm-at-plasa/</link>
		<comments>http://www.rdmprotocol.org/new-look-stand-for-rdm-at-plasa/#comments</comments>
		<pubDate>Fri, 17 Aug 2012 15:04:56 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://www.rdmprotocol.org/?p=719</guid>
		<description><![CDATA[For several years, PLASA’s Technical Resource Office, supported by manufacturers of RDM-compliant equipment, has provided a stand at PLASA dedicated to RDM (Remote Device Management) with the aim of familiarising visitors with the RDM protocol.
This year is no exception, yet brings a slightly  [...]]]></description>
				<content:encoded><![CDATA[<p>For several years, PLASA’s Technical Resource Office, supported by manufacturers of RDM-compliant equipment, has provided a stand at PLASA dedicated to RDM (Remote Device Management) with the aim of familiarising visitors with the RDM protocol.</p>
<p>This year is no exception, yet brings a slightly different approach that reflects how the RDM protocol has become more widely recognised, understood and adopted as an industry standard. This year’s stand will go beyond explaining the basics of what RDM is and how to use it, and explore the uses and applications to which it can be put within two major market areas.</p>
<p>The stand will demonstrate two fully functioning RDM systems, one dedicated to architectural applications and one to entertainment use. Each system will have a fully working RDM network showing the strengths of the RDM protocol and how it can be used in these different environments.</p>
<p>The entertainment system will be composed of a control desk and dimmer racks and concentrate on the configuration side of the RDM protocol. Demonstrations will show how the entertainment controller allows the user to set up and configure RDM fixtures without leaving the comfort of their control desk.</p>
<p>By contrast, the architectural system will concentrate on real-time monitoring of RDM fixtures. This illustrates how the user is able to see up-to-date sensor values such as temperature and lamp life, and how this information can be sent to the outside world in the form of information or warnings.</p>
<p>The working systems will be augmented by a range of other RDM compliant equipment that demonstrates the breadth of equipment and number of manufacturers that now support the RDM protocol.</p>
<p>Members of PLASA’s Technical Resource Office and other industry RDM specialists will be on hand to demonstrate the systems and answer any RDM questions you may have.</p>
<p>RDM Stand Number: <strong>EC2-R4</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.rdmprotocol.org/new-look-stand-for-rdm-at-plasa/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A second European RDM Developers Plugfest for 2012</title>
		<link>http://www.rdmprotocol.org/a-second-european-rdm-developers-plugfest-for-2012/</link>
		<comments>http://www.rdmprotocol.org/a-second-european-rdm-developers-plugfest-for-2012/#comments</comments>
		<pubDate>Fri, 17 Aug 2012 12:43:26 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://www.rdmprotocol.org/?p=716</guid>
		<description><![CDATA[Following the success of the first European RDM Developers Conference and Plug Fest in April 2012, a second European event date has been added for 2012. Sponsored by PLASA&#8217;s Technical Resource Office, this will once again take place at Gatwick Manor Hotel (see details below) from 4-5 October  [...]]]></description>
				<content:encoded><![CDATA[<p><img class="alignright" title="Plugfest" src="https://www.plasa.org/rdm/img/Plugfest.jpg" alt="" width="300" height="199" />Following the success of the first European RDM Developers Conference and Plug Fest in April 2012, a second European event date has been added for 2012. Sponsored by PLASA&#8217;s Technical Resource Office, this will once again take place at Gatwick Manor Hotel (see details below) from 4-5 October 2012.<br />
<strong>Feedback from April&#8217;s European PlugFest:</strong><br />
<em>&#8220;The format was spot on with just the right amount of theoretical presentation balanced with quality practical development time. The venue worked really well and we will definitely be back next time&#8221;</em></p>
<p>The format will be an advance on April&#8217;s meeting which concentrated on introducing newcomers to RDM and discussions concerning RDM basics.</p>
<p>October&#8217;s session will focus its discussions on the issue of compliance. Currently, no consistent, uniform method of RDM testing exists, so manufacturers design in isolation and test to different interpretations of the standard. The Plug Fest will provide a forum for informal discussion with the aim of formulating a plan to standardise these processes for the future. In addition there will be separate test locations for the three different categories of RDM equipment: Controllers, Splitters and Responders. This will give delegates an opportunity to bring their own RDM-compliant products for &#8216;plug &amp; test&#8217; sessions.</p>
<p>This event is organised in conjunction with PLASA Technical Resources and supported by industry leading manufacturers, many of whom will be attending the meeting. Full details of the discussion plan will be released nearer the time.</p>
<p><strong>Attendance is by registration only.</strong></p>
<p><strong>Details</strong></p>
<p><strong>Date:</strong> Thursday 4th and Friday 5th October 2012<br />
<strong>Location:</strong> Gatwick Manor, London Road, Lowfield Heath, just south of Gatwick Airport<br />
<strong>Cost:</strong> £45 (including lunch)</p>
<p>For more information and to register, please see <a href="http://www.plasa.org/rdm/">http://www.plasa.org/rdm/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.rdmprotocol.org/a-second-european-rdm-developers-plugfest-for-2012/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RDM at the ABTT Theatre Show</title>
		<link>http://www.rdmprotocol.org/rdm-at-the-abtt-theatre-show/</link>
		<comments>http://www.rdmprotocol.org/rdm-at-the-abtt-theatre-show/#comments</comments>
		<pubDate>Mon, 11 Jun 2012 14:14:20 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://www.rdmprotocol.org/?p=684</guid>
		<description><![CDATA[Come along to the ABTT Theatre Show on June 13th and 14th, at the old Truman Brewery in Brick Lane for a chance to see RDM in action. Production Electrician Martin Chisnall will be on hand to demonstrate the use of RDM across a number of industry products from different manufacturers, including  [...]]]></description>
				<content:encoded><![CDATA[<p><a href="http://www.rdmprotocol.org/rdm-at-the-abtt-theatre-show/abtttrumanvfinal/" rel="attachment wp-att-685"><img class="alignright size-full wp-image-685" title="ABTTtrumanVFinal" src="http://www.rdmprotocol.org/webtest/wp-content/uploads/2012/06/news-abtt-rdm.jpg" alt="" width="300" height="273" /></a>Come along to the ABTT Theatre Show on June 13th and 14th, at the old Truman Brewery in Brick Lane for a chance to see RDM in action. Production Electrician Martin Chisnall will be on hand to demonstrate the use of RDM across a number of industry products from different manufacturers, including patching, monitoring of sensors and remote addressing of fixtures.  Visit the RDM stand at booth number 97 and learn the Facts about the powerful new industry protocols.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rdmprotocol.org/rdm-at-the-abtt-theatre-show/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>European RDM and sACN Developers Conference and Plugfest</title>
		<link>http://www.rdmprotocol.org/european-rdm-and-sacn-developers-conference-and-plugfest/</link>
		<comments>http://www.rdmprotocol.org/european-rdm-and-sacn-developers-conference-and-plugfest/#comments</comments>
		<pubDate>Fri, 02 Mar 2012 21:24:31 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://www.rdmprotocol.org/?p=664</guid>
		<description><![CDATA[PLASA&#8217;s Technical Resource Office announces that an RDM and sACN Developers Conference and Plugfest will take place on the 26 &#8211; 28 April, in the UK, at Gatwick Manor, London Road at Lowfield Heath, just south of Gatwick Airport.
This Developers Conference aims to provide a European forum for  [...]]]></description>
				<content:encoded><![CDATA[<p>PLASA&#8217;s Technical Resource Office announces that an RDM and sACN Developers Conference and Plugfest will take place on the 26 &#8211; 28 April, in the UK, at Gatwick Manor, London Road at Lowfield Heath, just south of Gatwick Airport.</p>
<p>This Developers Conference aims to provide a European forum for manufacturers, designers, consultants and prospective users; and to ensure that the adoption of these new standards achieves desired levels of interoperability and reliability.</p>
<p>The &#8220;Plugfest&#8221; is a hands-on opportunity for product developers to try their products and code implementations with products from a variety of other manufacturers, with support from their industry peers in an environment that encourages co-operation and improved understanding of the standards, and with the aim of achieving high levels of interoperability.</p>
<p>Typically, engineers participate in these events with the ability to code and debug aspects of their implementations on site, sometimes retreating to their hotel rooms to craft improvements before returning to the &#8220;Plugfest&#8221; to continue testing.</p>
<p>The sessions, despite their apparent informality, can be a valuable opportunity to learn how not to make the same mistakes, or misguided assumptions, as others may have done.</p>
<p>Participation is by invitation, and limited to registered delegates. The conference is designed to appeal to Lighting Designers, System integrators, Theatre Consultants, Production Electricians, Rental company technical staff and product development engineers. The focus for Thursday will be broad, and designed to appeal to all categories of participant. Friday and Saturday will be orientated towards product development engineers who are either considering or actively implementing these standards.</p>
<p>A single registration fee of UK£45 per person, payable in advance, covers participation and a buffet lunch. Delegates may attend one or more days as they think appropriate. The registration fee is fixed, regardless of the number of days you attend, but you are required to indicate your proposed level of participation in advance.</p>
<p>Full details and information on registration can be found on the <a title="European Plugfest" href="http://www.plasa.org/technical/rdm_sacn_plugfest.asp" target="_blank">PLASA website</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rdmprotocol.org/european-rdm-and-sacn-developers-conference-and-plugfest/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>One new RDM extension standard published and another new one in Public Review!</title>
		<link>http://www.rdmprotocol.org/one-new-rdm-extension-standard-published-and-another-new-one-in-public-review/</link>
		<comments>http://www.rdmprotocol.org/one-new-rdm-extension-standard-published-and-another-new-one-in-public-review/#comments</comments>
		<pubDate>Mon, 27 Feb 2012 08:04:20 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://www.rdmprotocol.org/?p=659</guid>
		<description><![CDATA[One new RDM extension standard published and another new one in Public Review!
February 26, 2012
&#160;
ANSI E1.37-1 (Additional Message Sets for RDM &#8211; Part 1, Dimmer Message Sets) has recently been published by PLASA.  This new standard is an extension to ANSI E1.20 (RDM) which provides a number of new  [...]]]></description>
				<content:encoded><![CDATA[<p><strong>One new RDM extension standard published and another new one in Public Review!</strong></p>
<p>February 26, 2012</p>
<p>&nbsp;</p>
<p>ANSI E1.37-1 (Additional Message Sets for RDM &#8211; Part 1, Dimmer Message Sets) has recently been published by PLASA.  This new standard is an extension to ANSI E1.20 (RDM) which provides a number of new RDM messages (PIDs) primarily geared towards dimming systems but also includes a variety of general purpose RDM messages that are useful in across a very broad range of products.</p>
<p>&nbsp;</p>
<p>The full listing of new messages available and link to purchase ANSI E1.37-1 from the ESTA Foundation can be found at <a href="http://www.rdmprotocol.org/whats-next/rdm-additional-message-sets-e1-37-1/">http://www.rdmprotocol.org/whats-next/rdm-additional-message-sets-e1-37-1/</a></p>
<p>&nbsp;</p>
<p>With E1.37-1 now published, work has moved on to BSR E1.37-2 which defines additional RDM messages for remotely configuring network interfaces.  With more and more devices also using network interfaces BSR E1.37-2 provides a means to remotely configure these network settings.  BSR E1.37-2 is now in public review until April 23.  Anyone wishing to review and submit comments during the E1.37-2 Public Review may do so by downloading the draft document and comment review form from PLASA at: <a href="http://tsp.plasa.org/tsp/documents/public_review_docs.php">http://tsp.plasa.org/tsp/documents/public_review_docs.php</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.rdmprotocol.org/one-new-rdm-extension-standard-published-and-another-new-one-in-public-review/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>January 2012 Plugfest</title>
		<link>http://www.rdmprotocol.org/january-2012-plugfest/</link>
		<comments>http://www.rdmprotocol.org/january-2012-plugfest/#comments</comments>
		<pubDate>Wed, 04 Jan 2012 02:15:27 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://www.rdmprotocol.org/webtest/?p=607</guid>
		<description><![CDATA[Plugfest 2012
Some of the most important developments in the entertainment production industry in the last five years have been in the area of control and bi-directional communication, including Remote Device Management (RDM), a protocol for communicating bi-directionally between devices in a  [...]]]></description>
				<content:encoded><![CDATA[<p>Plugfest 2012</p>
<p>Some of the most important developments in the entertainment production industry in the last five years have been in the area of control and bi-directional communication, including Remote Device Management (RDM), a protocol for communicating bi-directionally between devices in a lighting or control system, Architecture for Control Networks (ACN), a TCP/IP-like protocol for bi-direct&#8230;ional communication over Ethernet, and Streaming ACN (sACN), a protocol for streaming DMX control protocol over an ACN network. Plugfest is designed to help implement these protocols in real-world devices in order to create the future of the industry. </p>
<p>Plugfest is a “must-not-miss” event for manufacturers and developers of control protocols and devices that use any of these protocols. The event is free to attend and participate and everyone is invited.<br />
Each January and July, several manufacturers and members of the Control Protocols Working Group convene informally to test their newest firmware with other manufacturers and their gear. They methodically try to “break” their software by interconnecting it with a wide variety of devices and test equipment, which are conveniently brought by various attendees and laid out on a group of conference tables in a suite of the Marriott Solana Hotel in Westlake, Texas, the location of the bi-annual event. When they identify a bug, they can typically fix it on the spot and try it over again until it works properly. They usually work late into the night and begin again early in the morning, fueled by junk food and soft drinks.<br />
The event was originally created to test and improve the Remote Device Management protocol (ANSI E1.20 RDM) but it has expanded to cover all of the CPWG protocols, including the popular ANSI E1.31 Lightweight Streaming Protocol for Transport of DMX over ACN.</p>
<p>Plugfest has grown every year, due to its popularity and success. The next Plugfest is from Friday, January 28 through Sunday, January 30 at the Marriott Solana in Westlake, TX. If you are interested in participating, please contact Scott Blair at sblair@rdmprotocol.org to register. Plugfest is open to all, but, with its growing popularity, registration is advised in order to make space accommodations.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rdmprotocol.org/january-2012-plugfest/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
