microcontroller over wireless network

I have worked with linx RF modules for LOS communications. But, that was different from 802.11 wireless modules.

I think linx technology has some modules for your query.

Linx Technology - 802.11bg - AusLinx AL-95002A Wireless LAN PCMCIA Prism2/2.5/3

Karthik Balaguru

Thank you for the fast reply. that would do the job, indeed but I canno use a card. I was thinking about a wireless module. I found something i lantronix. what do you think about it?

Thank you

ones.

You cannot use a card. Then, i think you cannot go with linx.

MatchPort=99 b/g - Embedded Wireless Device Server -> Looks great.

Extremely affordable embedded 802.11 b/g wireless networking Wired Ethernet-to-wireless bridging Common platform form factor for a family of wired and wireless modules Bulletproof security with IEEE 802.11i-PSK,WPA-PSK, TKIP and optional

Has nice features :):) . But i have not used this .

Wireless Specifications Wireless Standards IEEE 802.11b; 802.11g Frequency Range 2.412 - 2.484 GHz Output Power 14dBm +2.0 dBm/-1.5 dBm (does not include antenna gain)

Maximum Receive Sensitivity -91dBm @ 1Mbps Data Rates With Automatic Fallback 54Mbps - 1Mbps Range Up to 328 feet indoors Modulation Techniques OFDM, DSSS, CCK, DQPSK, DBPSK, 64 QAM, 16 QAM Serial Interface Two Serial Ports Interface CMOS (Asynchronous) 3.3V-level signals, rate is software selectable (300 bps to 921,000 bps) Serial Line Formats 7 or 8 data bits, 1-2 Stop bits Parity odd, even, none Modem Control DTR, DCD Flow Control XON/XOFF (software), CTS/RTS (hardware), none Network Interface Interface Wireless 802.11b, 802.11g Protocols Supported ARP, UDP, TCP, Telnet, ICMP, SNMP, DHCP, BOOTP, Auto IP, HTTP, SMTP, TFTP Management Internal web server SNMP (read only) Serial login Telnet login DeviceInstaller software

Security IEEE 802.11i - PSK with AES-CCMP Encryption WPA - PSK TKIP Encryption

Internal Web Server Serves web pages Storage capacity: 1.2 MB

Architecture CPU, Memory Lantronix DSTni-EX x86 CPU, on-chip 256 KB zero wait static SRAM, 2,048 KB Flash, 16 KB Boot ROM, 8 GPIO Firmware Upgradeable via TFTP and serial port Power Consumption Average Power Consumption Data Transfer

Peak Supply Current 360 mA DataTransfer Environmental Operating range,WLAN -40=B0 to +70=B0C (-40=B0 to 158=B0F) Storage range -40=B0 to +85=B0C (-40=B0 to 185=B0F) Packaging Dimensions 44.4 x 44.4 x 10.4 mm (1.75 x 1.75 x .41 in) Weight 14g Material Plastic shell, 260=B0C tolerant Included Software Web manager, Windows=AE-based DeviceInstaller configuration software and Com Port Redirector.

Looks great :):) . I have not tried/used this. This is the first time i am hearing about this. But, it is up to you to decide the best one. Maybe, someone who has tried/used this for their projects in this group/internet can guide you regarding this.

Karthik Balaguru

it?

I haved used the Lantronix WiPort in a previous project. It works great and only takes about 10 minutes to set up for a basic serial to

Keith

thats nice to hear. they have a contest running and they offer the tes kit with one wireless module just for 99$

thank you both for your help

Guys do you know how the tcp/ip conversion works? I mean that I am suposed to send tcp/ip packets and lantronix shoul convert them, after that the microcontroller connected to it shoul translate that into a command for the motors that I want to control.

thank you

You will need to define a serial protocol within your microcontroller so that you interface your PC system (or whatever is on the other side of the wireless network) to your motors via the lantronix box. For instance you can setup the value 0x01 to mean "start motor" and 0x02 to mean "stop motor". You can then pass this value via the wireless network which will then get translated to a serial data stream (which you can define) within the Lantronix module. Your microcontroller will then need to read this serial data stream and look for either of these defined values so that it may act on them accordingly.

In other words, the Lantronix device is just a transparent converter within your system. You are still responsible for developing a messaging scheme (i.e. protocol) between your two devices.

Keith