<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
<channel><generator>http://textpattern.com/?v=4.0.8</generator>
<title>Reynoldson Control Inc.</title>
<link>http://www.reynoldsoncontrol.com/</link>

<description>AMX Programming for A/V</description>
<pubDate>Thu, 30 Jul 2009 19:00:07 GMT</pubDate>

<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/ReynoldsonControlInc" type="application/rss+xml" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item><title>Fancy Power Feedback</title>
<description>
<![CDATA[<p>Here are a couple of fancy feedback statements for projector on and off buttons&#8230;</p>]]>
</description>
<content:encoded>
<![CDATA[<p>Here are a couple of fancy feedback statements for projector on and off buttons:</p>

<pre>(*-- PROJECTOR --------------------------------------------*)
  [dvPNL,211] =([dvPROJ1,127] &amp;&amp; ![dvPROJ1,227]) || ([dvPROJ1,227] &amp;&amp; nFlash)
  [dvPNL,212] =([dvPROJ1,128] &amp;&amp; ![dvPROJ1,228]) || ([dvPROJ1,228] &amp;&amp; nFlash)
</pre>

	<p>
<br />

If you can&#8217;t tell by looking at it, I use channels 127/128 for on/off state.  Channels 227/228 are used for the transition to on/off state (warming and cooling).  For the record, channels 27/28 are used for execution.</p>

	<p>Of course, you need to toggle nFlash in mainline (yes mainline) like this:</p>

<pre>WAIT 5 nFlash = !nFlash
</pre>]]>
</content:encoded>
<link>http://www.reynoldsoncontrol.com/blog/fancy-power-feedback</link>
<pubDate>Thu, 30 Jul 2009 18:54:15 GMT</pubDate>
<dc:creator>Chad Reynoldson</dc:creator>
<guid isPermaLink="false">tag:www.reynoldsoncontrol.com,2009-07-30:9baadc79886ae1d7d3b17284099f336f/54fdcf2d05e2fcedc400b14ea65aa717</guid>
</item>
<item><title>IF(dvDEV.PORT)</title>
<description>
<![CDATA[<p>I&#8217;m running into more and more IP controlled devices in the <span class="caps">AMX</span> world of control.  I have gotten into a habit of checking if a <span class="caps">DEV</span> variable has a value with IF(dvDEV) and it has worked all these year&#8230;</p>]]>
</description>
<content:encoded>
<![CDATA[<p>I&#8217;m running into more and more IP controlled devices in the <span class="caps">AMX</span> world of control.  I have gotten into a habit of checking if a <span class="caps">DEV</span> variable has a value with IF(dvDEV) and it has worked all these years for the various devices (232, IR, relay).  </p>

	<p>With IP devices, this always evaluates to false.  It seems to me that IF(dvDEV) is actually evaluating as IF(dvDEV.NUMBER) and with the case of IP devices is 0 (false).</p>

	<p>I am now changing to IF(dvDEV.PORT) so that all conditions will play nicely for IP, 232, IR, and relay devices.</p>]]>
</content:encoded>
<link>http://www.reynoldsoncontrol.com/blog/ifdvdevport</link>
<pubDate>Thu, 30 Jul 2009 13:22:59 GMT</pubDate>
<dc:creator>Chad Reynoldson</dc:creator>
<guid isPermaLink="false">tag:www.reynoldsoncontrol.com,2009-07-30:9baadc79886ae1d7d3b17284099f336f/05d46246621df3bb9eb7f0ec4ed9f42f</guid>
</item>
<item><title>Jaadu VNC</title>
<description>
<![CDATA[<p>I had recently heard of the <a href="http://www.jaaduvnc.com">Jaadu <span class="caps">VNC</span></a> viewer app for the iPhone/iTouch and I wanted to give it a try.  It is an iPhone application that provides a <span class="caps">VNC</span> client, allowing you to view the screen of an <span class="caps">AMX</span> touch panel directly on your iPhone.  It was designed with &#8220;<span class="caps">AMX</span> Touch Interface&#8221; in mind using <span class="caps">AMX</span> G4 Web Control.</p>]]>
</description>
<content:encoded>
<![CDATA[<p>I had recently heard of the <a href="http://www.jaaduvnc.com">Jaadu <span class="caps">VNC</span></a> viewer app for the iPhone/iTouch and I wanted to give it a try.  It is an iPhone application that provides a <span class="caps">VNC</span> client, allowing you to view the screen of an <span class="caps">AMX</span> touch panel directly on your iPhone.  It was designed with &#8220;<span class="caps">AMX</span> Touch Interface&#8221; in mind using <span class="caps">AMX</span> G4 Web Control.</p>

	<p>Adding an entry to a touch panel is very simple.  First, select &#8220;Manual&#8221; on the bottom.  Next, click &#8220;+&#8221; on the top.  Next, enter the entries name, ip address (stick with port 5900), security password (if any), and select &#8220;<span class="caps">AMX</span> Touch Interface&#8221; as the computer type.  Finally click &#8220;save server&#8221; and your done, with a new entry on the manual connection list.</p>

	<p>I tried it with both a 4&#215;3 and 16&#215;9 touch panel.  With both panels, it turned the view 90 degrees into landscape view.  With the 4&#215;3 panel, the image was centered on the screen with black bars on either side (no scaling).  With the 16&#215;9 panel, the image was centered and filled most of the screen.  I&#8217;ll be curious to see how <span class="caps">AMX</span>&#8217;s new <a href="http://www.amx.com/products/NXV-300.asp"><span class="caps">NXV</span>-300</a> will work, specifically at the 480&#215;272 resolution.</p>

	<p>The viewer also has built-in keyboard control that will also generate keyboard presses on native <span class="caps">AMX</span> keyboard and keypad popups (<span class="caps">AKB</span> and <span class="caps">AKP</span>).  The keyboard popups on the screen were pretty small to get an accurate touch, so it was good to see that work.  The only keyboard exception is that I could not get capital letters (<span class="caps">ABC</span>) to work.  All other keys worked fine.</p>

	<p>I&#8217;d say that for the small price ($24.99), it is a steal and fits a need.  Plus there&#8217;s no additional netlinx programming required.</p>]]>
</content:encoded>
<link>http://www.reynoldsoncontrol.com/blog/jaadu-vnc</link>
<pubDate>Thu, 30 Jul 2009 12:04:58 GMT</pubDate>
<dc:creator>Chad Reynoldson</dc:creator>
<guid isPermaLink="false">tag:www.reynoldsoncontrol.com,2009-07-30:9baadc79886ae1d7d3b17284099f336f/f0c5ff4e7a8d036bf49f6522916f7b08</guid>
</item>
<item><title>Follow me on Twitter</title>
<description>
<![CDATA[<p>My website blogging has subsided a bit over the last 3 months.  Since delivering <a href="http://www.reynoldsoncontrol.com/products/panel-tweet">PanelTweet</a> I&#8217;ve been doing more micro-blogging on Twitter.</p>]]>
</description>
<content:encoded>
<![CDATA[<p>My website blogging has subsided a bit over the last 3 months.  Since delivering <a href="http://www.reynoldsoncontrol.com/products/panel-tweet">PanelTweet</a> I&#8217;ve been doing more micro-blogging on Twitter.</p>

	<p>You can follow me: <a href="http://twitter.com/chadrey"><img src="http://www.reynoldsoncontrol.com/images/14.png" width="144" height="30" alt="Follow me on twitter" /></a></p>

	<p>I do plan on continuing the website blog as well.</p>]]>
</content:encoded>
<link>http://www.reynoldsoncontrol.com/blog/follow-me-on-twitter</link>
<pubDate>Tue, 07 Jul 2009 14:09:39 GMT</pubDate>
<dc:creator>Chad Reynoldson</dc:creator>
<guid isPermaLink="false">tag:www.reynoldsoncontrol.com,2009-07-07:9baadc79886ae1d7d3b17284099f336f/36fa1d864d4018e117110b9ab0587859</guid>
</item>
<item><title>Tandberg MXP with TVS</title>
<description>
<![CDATA[<p>I had recently programmed an <span class="caps">AMX</span> control system that controlled a Tandberg 6000MXP codec that utilized an external camera switcher, the Tandberg <span class="caps">TVS</span>.  It took some time to make it work and here is what I learned.</p>]]>
</description>
<content:encoded>
<![CDATA[<p>I had recently programmed an <span class="caps">AMX</span> control system that controlled a Tandberg 6000MXP codec that utilized an external camera switcher, the Tandberg <span class="caps">TVS</span>.  It took some time to make it work and here is what I learned.</p>

	<p>Switching the camera input requires two separate commands.  First, you switch the <span class="caps">TVS</span> using the &#8220;xconfiguration Switch Source: <1-6>&#8220; command.  Then you need to switch the <span class="caps">MXP</span> to it&#8217;s main video source using the &#8220;vidin 1&#8221; command.</p>

	<p>Now when controlling the selected <span class="caps">TVS</span> camera, you need to use camera values 8-13 like this: &#8220;xcommand cameramove camera:<8-13> direction:<value>&#8220;.</p>]]>
</content:encoded>
<link>http://www.reynoldsoncontrol.com/blog/tandberg-mxp-with-tvs</link>
<pubDate>Tue, 07 Jul 2009 13:48:48 GMT</pubDate>
<dc:creator>Chad Reynoldson</dc:creator>
<guid isPermaLink="false">tag:www.reynoldsoncontrol.com,2009-07-07:9baadc79886ae1d7d3b17284099f336f/d499d10d37d2120bc64aca8531149fb1</guid>
</item></channel>
</rss>
