<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Wireless Ethernet Bridge</title>
	<link>http://embedded-system.net/wireless-ethernet-bridge.html</link>
	<description>Microcontrollers, Embedded Systems, SDK, Development Boards, Modules, Tools and Circuits</description>
	<pubDate>Fri, 09 Jan 2009 02:53:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.3</generator>

	<item>
		<title>by: &#187; Time Attendance Networking at Automated Machines WebLog</title>
		<link>http://embedded-system.net/wireless-ethernet-bridge.html#comment-47</link>
		<pubDate>Tue, 20 Feb 2007 07:53:46 +0000</pubDate>
		<guid>http://embedded-system.net/wireless-ethernet-bridge.html#comment-47</guid>
					<description>[...] More robust and friendly networking technology is WiFi (Wireless Fidelity). Some new time and attendance vendors has put this technology on their machine. I think the advantage is already clear to see, WiFi does not need cabling, easy to install and easy to move. WiFi is relatively new technology if we compared to RS-485 and wired Ethernet, so the price is still a little bit high. Other hot issue of WiFi is its weak security. If your chosen machine has Ethernet facility, you can easily convert it to be wireless by using inexpensive Ethernet to WiFi Bridge [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] More robust and friendly networking technology is WiFi (Wireless Fidelity). Some new time and attendance vendors has put this technology on their machine. I think the advantage is already clear to see, WiFi does not need cabling, easy to install and easy to move. WiFi is relatively new technology if we compared to RS-485 and wired Ethernet, so the price is still a little bit high. Other hot issue of WiFi is its weak security. If your chosen machine has Ethernet facility, you can easily convert it to be wireless by using inexpensive Ethernet to WiFi Bridge [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
