<?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>ElectricRock Blog &#187; Informational</title>
	<atom:link href="http://www.electricrock.co.nz/blog/category/informational/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.electricrock.co.nz/blog</link>
	<description>Electronic Ramblings</description>
	<lastBuildDate>Tue, 10 Aug 2010 03:37:27 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>New C30 page, now with automated goodness</title>
		<link>http://www.electricrock.co.nz/blog/2010/03/new-c30-page-now-with-automated-goodness/</link>
		<comments>http://www.electricrock.co.nz/blog/2010/03/new-c30-page-now-with-automated-goodness/#comments</comments>
		<pubDate>Sun, 21 Mar 2010 05:25:40 +0000</pubDate>
		<dc:creator>matt</dc:creator>
				<category><![CDATA[Informational]]></category>
		<category><![CDATA[C30]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[PIC]]></category>

		<guid isPermaLink="false">http://www.electricrock.co.nz/blog/?p=133</guid>
		<description><![CDATA[I have just created a new page to put all my C30 related tutorials, etc. on.  It can be found at http://www.electricrock.co.nz/blog/microchip-c30/.
The most notable update is that my previous C30 building tutorials are now deprecated in favor of a new bash script that does it automagically.  Check out the page for more details.
]]></description>
			<content:encoded><![CDATA[<p>I have just created a new page to put all my C30 related tutorials, etc. on.  It can be found at <a href="http://www.electricrock.co.nz/blog/microchip-c30/">http://www.electricrock.co.nz/blog/microchip-c30/</a>.</p>
<p>The most notable update is that my previous C30 building tutorials are now deprecated in favor of a new bash script that does it automagically.  Check out the page for more details.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.electricrock.co.nz/blog/2010/03/new-c30-page-now-with-automated-goodness/feed/</wfw:commentRss>
		<slash:comments>26</slash:comments>
		</item>
		<item>
		<title>DLP-RFID1 library for Linux</title>
		<link>http://www.electricrock.co.nz/blog/2010/02/dlp-rfid1-library-for-linux/</link>
		<comments>http://www.electricrock.co.nz/blog/2010/02/dlp-rfid1-library-for-linux/#comments</comments>
		<pubDate>Mon, 08 Feb 2010 02:22:43 +0000</pubDate>
		<dc:creator>matt</dc:creator>
				<category><![CDATA[Informational]]></category>
		<category><![CDATA[DLP-RFID1]]></category>
		<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://www.electricrock.co.nz/blog/?p=111</guid>
		<description><![CDATA[This page is deprecated. Please see the new page at: http://www.electricrock.co.nz/tools/dlp-rfid1-library-for-linux/.



I bought a DLP-RFID1 USB RFID tag reader/writer from Digikey (Cat # 813-1013-ND).  However, I was unable to locate sufficient libraries to develop software that uses it under Linux.  So I have written a C++ library to do this.  Read on for [...]]]></description>
			<content:encoded><![CDATA[<p><strong>This page is deprecated. Please see the new page at: <a href="http://www.electricrock.co.nz/tools/dlp-rfid1-library-for-linux/">http://www.electricrock.co.nz/tools/dlp-rfid1-library-for-linux/</a>.<br />
</strong></p>
<p><span style="color: #999999;"><br />
</span></p>
<p><span style="color: #999999;">I bought a <a href="http://www.dlpdesign.com/rf/rfid1.shtml">DLP-RFID1</a> USB RFID tag reader/writer from Digikey (Cat # 813-1013-ND).  However, I was unable to locate sufficient libraries to develop software that uses it under Linux.  So I have written a C++ library to do this.  Read on for more information and to download it.<br />
<span id="more-111"></span></span> <span style="color: #999999;"><br />
The DLP-RFID1 comprises an FTDI USB-Serial IC connected to a microcontroller.  Therefore the library I have developed is based on <a href="http://www.intra2net.com/en/developer/libftdi/">libftdi</a>.  Currently, it is very basic and supports only polling for tags (not reading and writing tags).  As I currently have no need for reading and writing tags I don&#8217;t plan to add this functionality unless someone asks for it.</span></p>
<p><span style="color: #999999;">The library can be downloaded from <a href="http://www.electricrock.co.nz/files/rfid1/librfid1-0.1.0.tar.bz2">http://www.electricrock.co.nz/files/rfid1/librfid1-0.1.0.tar.bz2</a>.  Documentation is provided in the package.</span></p>
<p><span style="color: #999999;">This is my first time making a library package for Linux, so if you find any problems or have any suggestions please leave a comment and let me know.</span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.electricrock.co.nz/blog/2010/02/dlp-rfid1-library-for-linux/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Ensoniq Control 16 RJ-45 Connector Pinout</title>
		<link>http://www.electricrock.co.nz/blog/2009/09/ensoniq-control-16-rj-45-connector-pinout/</link>
		<comments>http://www.electricrock.co.nz/blog/2009/09/ensoniq-control-16-rj-45-connector-pinout/#comments</comments>
		<pubDate>Wed, 16 Sep 2009 03:59:04 +0000</pubDate>
		<dc:creator>matt</dc:creator>
				<category><![CDATA[Informational]]></category>
		<category><![CDATA[Control 16]]></category>
		<category><![CDATA[Hardware]]></category>

		<guid isPermaLink="false">http://www.electricrock.co.nz/blog/?p=60</guid>
		<description><![CDATA[As I stated in my first Control 16 post, the C16 is meant to connect to a proprietary Ensoniq PCI card (which I don&#8217;t have.)  So instead I have been reverse engineering the C16 interface so that I can convert it for use with my PC.  The C16 has two connectors on the back a [...]]]></description>
			<content:encoded><![CDATA[<p>As I stated in my <a href="http://www.electricrock.co.nz/blog/2009/08/ensoniq-control-16-undressed/">first Control 16 post</a>, the C16 is meant to connect to a proprietary Ensoniq PCI card (which I don&#8217;t have.)  So instead I have been reverse engineering the C16 interface so that I can convert it for use with my PC.  The C16 has two connectors on the back a 1/4&#8243; jack, which is used to connect an optional footswitch; and an RJ-45 connector, which is proprietary.  Both connectors are mounted on a board called <em>PWR/SER_I/F</em>.</p>
<p><span id="more-60"></span></p>
<div id="attachment_27" class="wp-caption alignnone" style="width: 310px"><a href="http://www.electricrock.co.nz/blog/wp-content/uploads/2009/08/control16-3.jpg"><img class="size-medium wp-image-27" title="Control 16 #3" src="http://www.electricrock.co.nz/blog/wp-content/uploads/2009/08/control16-3-300x207.jpg" alt="Control 16 Regulator/IO Board" width="300" height="207" /></a><p class="wp-caption-text">Control 16 Regulator/IO Board</p></div>
<p>The pinout of the RJ-45 connector is as follows (pin 1 is on the left when looking into the connector, therefore on the right in the photo above):</p>
<table border="0">
<tbody>
<tr>
<td>1</td>
<td>RS-422 data in (+)</td>
</tr>
<tr>
<td>2</td>
<td>RS-422 data in (-)</td>
</tr>
<tr>
<td>3</td>
<td>RS-422 data out (+)</td>
</tr>
<tr>
<td>4</td>
<td>+12v</td>
</tr>
<tr>
<td>5</td>
<td>GND</td>
</tr>
<tr>
<td>6</td>
<td>RS-422 data out (-)</td>
</tr>
<tr>
<td>7</td>
<td>GND</td>
</tr>
<tr>
<td>8</td>
<td>+5v</td>
</tr>
</tbody>
</table>
<p>While the above pinout may appear a little random at first glance, when using standard CAT5 cable it means that the pairs are RS422 in; RS422 out; +5v and GND; and +12v and GND.</p>
<p>Here is a schematic for a RS422 to RS232 converter, similar to what I am using myself (though I have been providing power from a lab power supply at this stage.)</p>
<div id="attachment_61" class="wp-caption alignnone" style="width: 310px"><a href="http://www.electricrock.co.nz/blog/wp-content/uploads/2009/09/c16-serial-adaptor.png"><img class="size-medium wp-image-61" title="Control16 - Adaptor" src="http://www.electricrock.co.nz/blog/wp-content/uploads/2009/09/c16-serial-adaptor-300x160.png" alt="Control 16 - Proprietary interface to RS232 adaptor" width="300" height="160" /></a><p class="wp-caption-text">Control 16 - Proprietary interface to RS232 adaptor</p></div>
<p>Please note that while I have successfully connected power and data to my control 16 without blowing it up, this information is only provided as a guide and I recommend double checking it against your actual hardware before connecting anything to your control 16.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.electricrock.co.nz/blog/2009/09/ensoniq-control-16-rj-45-connector-pinout/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Optrex DMF-50573NB-FW Datasheet</title>
		<link>http://www.electricrock.co.nz/blog/2009/08/optrex-dmf-50573nb-fw-datasheet/</link>
		<comments>http://www.electricrock.co.nz/blog/2009/08/optrex-dmf-50573nb-fw-datasheet/#comments</comments>
		<pubDate>Sun, 23 Aug 2009 02:43:54 +0000</pubDate>
		<dc:creator>matt</dc:creator>
				<category><![CDATA[Informational]]></category>
		<category><![CDATA[dmf-50573nb-fw]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[t6963c]]></category>

		<guid isPermaLink="false">http://www.electricrock.co.nz/blog/?p=37</guid>
		<description><![CDATA[I scored a few DMF-50573NB-FW 480&#215;80 pixel graphic LCDs off trademe for $NZ5 each.  However, the documentation around on the internets for this particular variant of the Optrex DMF family seems to be sparse. So here is the information that I have gleaned from the looking at the devices themselves, datasheets for other LCDs in [...]]]></description>
			<content:encoded><![CDATA[<p>I scored a few DMF-50573NB-FW 480&#215;80 pixel graphic LCDs off trademe for $NZ5 each.  However, the documentation around on the internets for this particular variant of the Optrex DMF family seems to be sparse. So here is the information that I have gleaned from the looking at the devices themselves, datasheets for other LCDs in the family, probing with a multimeter and general experimentation. No guarantees as to the accuracy of this data, but so far it has worked for me.  If anyone has a datasheet please link in the comments <img src='http://www.electricrock.co.nz/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> .</p>
<p><span id="more-37"></span></p>
<h3>T6963C Controller</h3>
<p>The 50573 is based around a Toshiba T6963C controller IC.  Documentation for these is plentiful and there is plenty of software available to talk to them (e.g. <a href="http://ssl.bulix.org/projects/lcd4linux/wiki/T6963">LCD4Linux</a>, <a href="http://serdisplib.sourceforge.net/ser/t6963.html">serdisplib</a>, etc.).  Given that the 50573 is based around the T6963C it makes it fairly similar to some of the other DMF LCDs for which datasheets are easier to find (e.g. the DMF-50136NF-FW). Beware though, the pinout is different.</p>
<h3>Pinout</h3>
<table border="1" cellspacing="1" cellpadding="1">
<tbody>
<tr>
<td>\RESET</td>
<td>1</td>
<td></td>
<td>2</td>
<td>LCD Vee</td>
</tr>
<tr>
<td>D0</td>
<td>3</td>
<td></td>
<td>4</td>
<td>NC</td>
</tr>
<tr>
<td>D1</td>
<td>5</td>
<td></td>
<td>6</td>
<td>NC</td>
</tr>
<tr>
<td>D2</td>
<td>7</td>
<td></td>
<td>8</td>
<td>C/D</td>
</tr>
<tr>
<td>D3</td>
<td>9</td>
<td></td>
<td>10</td>
<td>\CE</td>
</tr>
<tr>
<td>D4</td>
<td>11</td>
<td></td>
<td>12</td>
<td>\WR</td>
</tr>
<tr>
<td>D5</td>
<td>13</td>
<td></td>
<td>14</td>
<td>\RD</td>
</tr>
<tr>
<td>D6</td>
<td>15</td>
<td></td>
<td>16</td>
<td>NC</td>
</tr>
<tr>
<td>D7</td>
<td>17</td>
<td></td>
<td>18</td>
<td>NC</td>
</tr>
<tr>
<td>NC</td>
<td>19</td>
<td></td>
<td>20</td>
<td>Page Select</td>
</tr>
<tr>
<td>Vdd</td>
<td>21</td>
<td></td>
<td>22</td>
<td>NC</td>
</tr>
<tr>
<td>Vss</td>
<td>23</td>
<td></td>
<td>24</td>
<td>FG</td>
</tr>
</tbody>
</table>
<h4>Pin descriptions</h4>
<p>Most of these pins (\RESET, Dx, C/D, \CE, \WR, \RD)  connect directly back to the T6963C, so just have a look at the datasheet for more information.</p>
<p>Vdd and Vss are power supply, which is 5V.  Vee is the LCD driving supply, there is special timing and voltages for this, so check out the datasheet of a similar DMF display (e.g. DMF-50136NF-FW).  Basically, when the LCD is in a reset state (as it is at power up), then this should be Vdd. To actually display something on the LCD this needs to be -15v.</p>
<p>I have called pin 20 the <em>page select</em> pin, as this seems to be an appropriate name for its function, so far as I can tell.  If someone can correct me on this, then please do so.  This pin is connected to the most significant address pin of the LCD&#8217;s display RAM (which stores what is currently being displayed on the screen).  Therefore, using this signal it is possible to quickly change between &#8216;pages&#8217; in this RAM.  To be honest, I haven&#8217;t used this feature yet and have just left it tied to either Vdd or Vss with no problems.</p>
<h3>Internal Wiring</h3>
<p>There are some connections to the T6963C chip which may be of interest. The table below details them and their meanings:</p>
<table border="1" cellspacing="1" cellpadding="1">
<tbody>
<tr>
<td>MDS</td>
<td>Vdd</td>
</tr>
<tr>
<td>MD0</td>
<td>Vdd</td>
</tr>
<tr>
<td>MD1</td>
<td>Vdd</td>
</tr>
<tr>
<td>MD2</td>
<td>Vdd</td>
</tr>
<tr>
<td>MD3</td>
<td>Vss</td>
</tr>
<tr>
<td>FS0</td>
<td>Vss</td>
</tr>
<tr>
<td>FS1</td>
<td>Vss</td>
</tr>
<tr>
<td>\DUAL</td>
<td>Vdd</td>
</tr>
</tbody>
</table>
<p>These pins configure the T6963C for the following:</p>
<ul>
<li><em>Lines</em> 10</li>
<li><em>Vertical Dots</em> 80</li>
<li><em>Columns</em> 64</li>
<li><em>Font</em> 8&#215;8</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.electricrock.co.nz/blog/2009/08/optrex-dmf-50573nb-fw-datasheet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
