<?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>TILE!™ Support &#187; Michael</title>
	<atom:link href="http://www.tilesupport.com/tilesupport/author/michael/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tilesupport.com/tilesupport</link>
	<description></description>
	<lastBuildDate>Tue, 27 Sep 2011 15:45:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Debugging GPIB Issues</title>
		<link>http://www.tilesupport.com/tilesupport/debugging-gpib-issues/</link>
		<comments>http://www.tilesupport.com/tilesupport/debugging-gpib-issues/#comments</comments>
		<pubDate>Thu, 30 Apr 2009 20:50:07 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[FAQs]]></category>

		<guid isPermaLink="false">http://www.tilesupport.com/tilesupport/?p=68</guid>
		<description><![CDATA[One of our software engineers, Dr. Gemei &#34;Mel&#34; Yang, sent some instructions&#160;about debugging GPIB communication to&#160;a&#160;customer&#160;as an email. It&#160;could be useful to others so I decided to capture it as a post on our blog. These are some tips for debugging GPIB commands with TILE! 4. It assumes you are using a National Instruments GPIB [...]]]></description>
			<content:encoded><![CDATA[<p>One of our software engineers, Dr. Gemei &quot;Mel&quot; Yang, sent some instructions&nbsp;about debugging GPIB communication to&nbsp;a&nbsp;customer&nbsp;as an email. It&nbsp;could be useful to others so I decided to capture it as a post on our blog.</p>
<p>These are some tips for debugging GPIB commands with TILE! 4. It assumes you are using a National Instruments GPIB interface.First, start NI MAX, then start NI Spy. Set it to monitoring mode. Start by checking the GPIB connection.&nbsp; You can test it by using &ldquo;Communicate with Instrument&rdquo; in MAX when you find the device in your MAX&#8217;s device tree.<br />
Second, go to Tile menu File-&gt;Options-&gt;GPIB. In that tab, you should see &ldquo;nigpib32&rdquo; or &ldquo;nigpib&rdquo; in the text box. Click the &ldquo;Browse&rdquo; button, and search for nigpib.dll file in your Tile4 default directory. Load it.<br />
&nbsp;<br />
Then, close TILE! and restart it. <br />
&nbsp;<br />
Fourth, try to connect your NI GPIB to a device that you have a driver for. Load the driver in your instrument window. Make sure give the device a name and the GPIB address must be consistent with NI MAX&rsquo;s finding.<br />
&nbsp;<br />
Finally, use &ldquo;GPIB&rdquo; tool in your TILE! tool bar (it looks like a hand with pen), connecting to the driver you connected, and send &ldquo;*IDN?&rdquo; by clicking &ldquo;Write&rdquo; button; then click &ldquo;Read&rdquo; to see what you get in return. You can watch your NI Spy for the status of the communication.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.tilesupport.com/tilesupport/debugging-gpib-issues/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

