ethernet / wireless connectivity?
noidd
Posts: 4
For the propeller.
Is anyone working on this yet before I start evil scheming... I would hate to duplicate effort.
Is anyone working on this yet before I start evil scheming... I would hate to duplicate effort.
Comments
Ethernet
http://www.lantronix.com/device-networking/embedded-device-servers/xport.html
802.11
http://www.lantronix.com/device-networking/embedded-device-servers/wiport.html
If it is the same and runs linux it completely removes the need I have for the propeller chip since I'm a UNIX programmer already and looking at the propeller as my first microprocessor.
You can get an xport from here... Fairly cheap... http://cubloc.com/product/01_08xport.php
Cheap as in like·half what the picotux is listed on their page..
Although, I'd rather not stray anyone from using a propeller...· You may find uses for it that you·hadn't originally thought of..· I know I have.
Post Edited (sharpie) : 7/24/2006 3:52:35 AM GMT
But more to the point, I sometimes wonder why the push to put network intelligence at the far end of the cable? The performance constraints and extra expense are seldom justified by the returns. As an alternative, consider a device that NewEgg (www.newegg.com) offers. It's a USB repeater for $39.99 that will drive a 150-foot CAT-5 cable with ease and provide power to the downstream device. You can read about it here: www.newegg.com/Product/Product.asp?Item=N82E16812101152. I have one and it works great. With the internal step-up DC-DC converter driving the cable, it will even assure a solid 5V supply at the downstream end. Now, considering that most network installations involve at least one PC, why not run the web server in the PC, where cheap resources abound, and hang the "web-connected device" off a USB port? The PC doesn't even need to be dedicated to the task: a web server can run in the background with hardly a dent in workstation performance. I believe the overall cost savings and flexibility far surpass what's currently available in the device server market. Plus you don't have to power the remote device (unless it's really current-hungry) or mess with Power-over-Ethernet retrofits.
-Phil
www.edtp.com
www.tibbo.com/
www.modtronix.com/
www.netburner.com/
I could keep going...(Parallax has already released the PINK module in conjunction with Netburner: http://www.parallax.com/detail.asp?product_id=30013 )
Ryan
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Ryan Clarke
Parallax Tech Support
RClarke@Parallax.com
The PINK module is exactly what I mean by a templating system and is the right approach, IMO.
Noid,
Porting Perl to one of these little beasts is quite intriguing. But I wonder if they have adequate storage and horsepower to handle CGI, much less something as large as Andy Wardley's excellent Template Toolkit (www.template-toolkit.org). This is what I mean by trying to force too much functionality to the far end of the cable, when the same or better performance could be had at the near end for far less money and grief. I have to admit, web-enabled devices carry that "wow!-cool!-gotta-have-it!" mystique. But they just don't pencil out economically, compared to USB over the same (hardwired) distances.
Sharpie,
As to using TCP/IP for extended-length serial I/O, RS422/RS485 will do the same thing with far less complexity. And with a short-haul modem you can go well beyond Ethernet's limited range.
(Please note: I'm playing devil's advocate here. I'm just as intrigued by web-enabled devices as the next guy. But before getting carried away by the sizzle, I think it's important to examine the steak.)
-Phil
You can cut perl pretty much down to the bone if you need to. Also, using libperl.so functionality you can have multiple perl processes running with very little footprint (maybe 12k per process in memory for each additional on an arm archetecture). Anyways, I disgress.
What I am researching for is that I want to put random devices on walls around my house. Yes, this is a development exercise for me. I need not want the intellegence in the device but I want it to be able to communicate with other devices and my main server here. Something as simple as being able to recieve and emit UDP packets as a low rate would be enough for me to start with.
I'm not looking for web functionality, just an IP stack I can abuse.
http://www.mouser.com/catalog/626/98.pdf
http://www.digi.com/
ethernet
http://www.digi.com/products/embeddedsolutions/digiconnectme.jsp
802.11
http://www.digi.com/products/embeddedsolutions/digiconnectwime.jsp