<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Enhanced IRSeekerV2 NXT-G Block and NXC Function</title>
	<atom:link href="http://www.hitechnic.com/blog/ir-seeker/enhanced-irseekerv2-block-and-nxc/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hitechnic.com/blog/ir-seeker/enhanced-irseekerv2-block-and-nxc/</link>
	<description>All about HiTechnic products and projects</description>
	<lastBuildDate>Sat, 08 Dec 2012 17:18:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Gus</title>
		<link>http://www.hitechnic.com/blog/ir-seeker/enhanced-irseekerv2-block-and-nxc/comment-page-1/#comment-3022</link>
		<dc:creator>Gus</dc:creator>
		<pubDate>Wed, 17 Oct 2012 18:56:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.hitechnic.com/blog/?p=674#comment-3022</guid>
		<description>The only constants that you need to use are the mode constants: HTIR2_MODE_1200 and HTIR2_MODE_600.  The other constants are the I2C registers that the function implementation uses to communicate with the sensor.  You don&#039;t need these unless you do your own I2C interactions with the sensor.

Use SetHTIRSeeker2Mode to set the AC mode of the IRSeeker V2.  1200 and 600 refers to the pulsed signal that the sensor should look for when you use AC mode.  If you have a pulsed 1200Hz signal, then the default 1200 Hz mode will work the best.  If you have a 600 Hz pulsed signal, then you will want to change the mode of the sensor to HTIR2_MODE_600.  If you are looking at the DC direction and signal strength then the 1200 or 600 mode setting will have no effect.</description>
		<content:encoded><![CDATA[<p>The only constants that you need to use are the mode constants: HTIR2_MODE_1200 and HTIR2_MODE_600.  The other constants are the I2C registers that the function implementation uses to communicate with the sensor.  You don&#8217;t need these unless you do your own I2C interactions with the sensor.</p>
<p>Use SetHTIRSeeker2Mode to set the AC mode of the IRSeeker V2.  1200 and 600 refers to the pulsed signal that the sensor should look for when you use AC mode.  If you have a pulsed 1200Hz signal, then the default 1200 Hz mode will work the best.  If you have a 600 Hz pulsed signal, then you will want to change the mode of the sensor to HTIR2_MODE_600.  If you are looking at the DC direction and signal strength then the 1200 or 600 mode setting will have no effect.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matthias feicht</title>
		<link>http://www.hitechnic.com/blog/ir-seeker/enhanced-irseekerv2-block-and-nxc/comment-page-1/#comment-3018</link>
		<dc:creator>matthias feicht</dc:creator>
		<pubDate>Mon, 15 Oct 2012 20:28:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.hitechnic.com/blog/?p=674#comment-3018</guid>
		<description>Hello,
I&#039;ve bought a IRseeker. 
on the Hitechnic website I would like to find some more information about the APIs (NXC).
Could you please publish some more infos about the SetHTIRSeeker2Mode function.
especially the HiTechnic IRSeeker2 constants
(http://bricxcc.sourceforge.net/nbc/nxcdoc/nxcapi/group___h_t_i_r_seeker2_constants.html)

Thanks,
Matthias Feicht</description>
		<content:encoded><![CDATA[<p>Hello,<br />
I&#8217;ve bought a IRseeker.<br />
on the Hitechnic website I would like to find some more information about the APIs (NXC).<br />
Could you please publish some more infos about the SetHTIRSeeker2Mode function.<br />
especially the HiTechnic IRSeeker2 constants<br />
(<a href="http://bricxcc.sourceforge.net/nbc/nxcdoc/nxcapi/group___h_t_i_r_seeker2_constants.html" rel="nofollow">http://bricxcc.sourceforge.net/nbc/nxcdoc/nxcapi/group___h_t_i_r_seeker2_constants.html</a>)</p>
<p>Thanks,<br />
Matthias Feicht</p>
]]></content:encoded>
	</item>
</channel>
</rss>
