<?xml version="1.0" encoding="iso-8859-1" standalone="yes" ?>
<rss version="2.0">
<channel>
<title>Frequently Asked Questions - The five questions posted most recently:</title>
<description>Frequently Asked Questions</description>
<link>http://faq.visionsystems.de</link>	<item>
		<title><![CDATA[Does the client software work as a SYSTEM service?]]></title>
		<description><![CDATA[<p>
No, it does not.
</p>
<p>
However the latest driver version for Windows 7 (also operates on XP and Vista) provides a chance to configure a suitable workaround. Please <a href="http://www.vscom.de/download/multiio/others/info/NetUSB_Manual.pdf">download the latest manual</a>  to see how this can be used.
</p>
<p>
 
</p>
]]></description>
		<link>http://faq.visionsystems.de/index.php?action=artikel&amp;cat=11&amp;id=55&amp;artlang=en</link>
		<pubDate>Mon, 02 Jan 2012 16:15:00 GMT</pubDate>
	</item>
	<item>
		<title><![CDATA[How to operate COM10 to COM256 in Windows?]]></title>
		<description><![CDATA[<p>
This question is very old, and should be answered and solved in today software since a long time. Surprisingly this comes up again from time to time. So here is the classic answer, digged up from the old FAQ.
</p>
<p>
Very frequently Windows programs refuse to operate with COM10
or higher. What is the reason?
</p>
<ol>
	<li>The program is an old 16-bit application. In this case
	COM9 is the highest available interface.<br />
	It is very likely this is not the cause today, but you never know.</li>
	<li>The program offers a list of ports, only containing COM1
	through COM9.<br />
	Please contact the programmer. This is a limit imposed by his application.</li>
	<li>
	The program does not open the port in the correct way,
	please contact the programmer. <br />
	Probably a name like "COM11:"
	is used to select the port. This is not allowed. The correct
	name is "\\.\COM11", i.e. with &lt;Backslash&gt;&lt;Backslash&gt;&lt;Dot&gt;&lt;Backslash&gt;
	as prefix; further the colon at the
	end is not allowed. This method also operates with COM1 through COM9.
	</li>
</ol>
<p>
Programmers shall check <a href="http://support.microsoft.com/default.aspx?scid=kb;EN-US;q115831" target="_blank" title="MSDN Q115831">the MSDN article</a>  about this problem.
</p>
]]></description>
		<link>http://faq.visionsystems.de/index.php?action=artikel&amp;cat=12&amp;id=89&amp;artlang=en</link>
		<pubDate>Wed, 21 Dec 2011 15:48:00 GMT</pubDate>
	</item>
	<item>
		<title><![CDATA[CAN support in Linux]]></title>
		<description><![CDATA[<pre>
EmRunner&#39;s CAN registers are accessed in two step:
</pre>
<pre>
 
</pre>
<pre>
1. put register address on the wire
</pre>
<pre>
2. put/read data to/from register
</pre>
<pre>
 
</pre>
<pre>
That is the reason, why standard <a href="http://freecode.com/projects/lincan" target="_blank">LinCan</a>  driver is not working as is. Following changes have to be made to make the driver working. 
</pre>
<pre>
 
</pre>
<pre>
Introduce such a global variable:
can_ioptr_t base_addr;
in gensja1000io_init_chip_data() base_addr should the value of chip_base_addr.
</pre>
<pre>
So write routine in gensja1000io.c would look like this:
</pre>
<pre>
gensja1000io_write_register( data, address)
{
can_outb(address - base_addr, base_addr); // calculate register offset
can_outb(data, base_addr + 1);
}
Read routine would look like this:
gensja1000io_read_register( address)
{
can_outb(address - base_addr, base_addr); // calculate register offset
can_inb(data, base_addr + 1);
}
</pre>
<pre>
 
</pre>
<pre>
CAN reset is to be handled the same way. 
</pre>
]]></description>
		<link>http://faq.visionsystems.de/index.php?action=artikel&amp;cat=13&amp;id=88&amp;artlang=en</link>
		<pubDate>Mon, 12 Dec 2011 11:47:00 GMT</pubDate>
	</item>
	<item>
		<title><![CDATA[My PCI serial card is not recognized under Linux - why?]]></title>
		<description><![CDATA[<p>
It could be that you have a newer card, which is not supported in the Linux mainline kernel. But we have a patch for the 2.6.33 version and it is a part of mainline kernel since version 2.6.35.
</p>
<p>
Here is a list of the newer cards:
</p>
<p>
PCI: 200I(-SI), 400I, 800I
</p>
<p>
PCI Express: 200E, 400E, 800E, 200EI(-SI), 400EH, 800EH
</p>
<p>
The link to the patch: <a href="http://kerneltrap.org/mailarchive/git-commits-head/2010/6/4/41231" target="_blank">http://kerneltrap.org/mailarchive/git-commits-head/2010/6/4/41231</a>  
</p>
]]></description>
		<link>http://faq.visionsystems.de/index.php?action=artikel&amp;cat=6&amp;id=61&amp;artlang=en</link>
		<pubDate>Fri, 11 Nov 2011 15:39:00 GMT</pubDate>
	</item>
	<item>
		<title><![CDATA[Is there user-accessible non-volatile memory in this device?]]></title>
		<description><![CDATA[<p>
Short answer: NO.
</p>
<p>
Detailed answer: There is a small EEPROM (2 kbit or less) embedded. This is used for configuration in the production.<br />
The content can be changed by special software, but only changes items like serial number. This is not much of useful information.
</p>
]]></description>
		<link>http://faq.visionsystems.de/index.php?action=artikel&amp;cat=2&amp;id=87&amp;artlang=en</link>
		<pubDate>Thu, 20 Oct 2011 10:43:00 GMT</pubDate>
	</item>
</channel>
</rss>
