Wifi: Connecting a Laptop to en embedded system
in [Design]
|
From: PovTruffe on 15 Jun 2010 12:14 "Jan Panteltje" <pNaonStpealmtje(a)yahoo.com> a �crit : > Questions you need to answer here first: > 1) Does it need 1 way or 2 way communication. > 2) What speed > 3) What interfaces are available on the embedded system, and what interfaces are available on the PC. > 4) Distance > 5) Reliability. The requirements are very low: 1) Just a few bytes (commands) sent to the embedded system once a while. Thats one way communication but I dont know yet if status data may be necessary or even usefull (I am just starting to think about the project). 2) Very low speed but reaction time should not be too low. 3) Any interfaces that could be made available on a 16 bit PIC driven board. 4) Very low distance: max 20m (60ft...) 5) This is not a mission critical system The embedded system would already have a control panel so the wifi connection could just be used by some customers who would use their own laptop. Therefore the laptop could be of any type. My idea is that using wifi could be the easiest solution for this kind of application (or not?). > For example for a one way low bitrate short distance you can hang a > 430 MHz module on the serial port, and dream up some protocol. Yes but how many laptops have a serial port nowadays ? In addition most customers dont even know what a serial port is...
From: Joerg on 15 Jun 2010 12:16 PovTruffe wrote: > Hi, > > Say you want to design an embedded system that any laptop can > connect to without any Wifi network available. Is that possible ? > > Just a point to point communications would be required, not really > a full featured wireless network. A laptop would just sent a few > simple commands to the embedded system. > > Maybe BlueTooth would be more appropriate for this application but > this would require adding a costly dongle to most laptops. > > Or Zigbee ? > Possibly this can get you started: http://techpp.com/2010/01/31/how-to-build-wireless-network-without-router/ -- Regards, Joerg http://www.analogconsultants.com/ "gmail" domain blocked because of excessive spam. Use another domain or send PM.
From: D Yuniskis on 15 Jun 2010 12:27 PovTruffe wrote: > "Jan Panteltje" <pNaonStpealmtje(a)yahoo.com> a �crit : >> Questions you need to answer here first: >> 1) Does it need 1 way or 2 way communication. >> 2) What speed >> 3) What interfaces are available on the embedded system, and what interfaces are available on the PC. >> 4) Distance >> 5) Reliability. > > The requirements are very low: > 1) Just a few bytes (commands) sent to the embedded system once a while. > Thats one way communication but I dont know yet if status data may be > necessary or even usefull (I am just starting to think about the project). > 2) Very low speed but reaction time should not be too low. > 3) Any interfaces that could be made available on a 16 bit PIC driven board. > 4) Very low distance: max 20m (60ft...) > 5) This is not a mission critical system > > The embedded system would already have a control panel so the wifi > connection could just be used by some customers who would use their own > laptop. Therefore the laptop could be of any type. My idea is that using wifi > could be the easiest solution for this kind of application (or not?). > >> For example for a one way low bitrate short distance you can hang a >> 430 MHz module on the serial port, and dream up some protocol. > > Yes but how many laptops have a serial port nowadays ? > In addition most customers dont even know what a serial port is... USB serial port. Any reason why you can't use USB *directly* (i.e., why does it have to be wireless?) Does the exchange have to be interactive? (i.e., can you use some intermediary to carry data/commands back and forth -- like a thumb drive?)
From: PovTruffe on 15 Jun 2010 12:27 "D Yuniskis" <not.going.to.be(a)seen.com> a �crit : > Ad-hoc mode has your WiFi devices talking to each other > *directly*. Think of this as more of a mesh -- each device > talks *directly* to every device that it wants to > communicate with WITHOUT the presence/intervention of > an "access point" to coordinate those things. > > I.e., you can have a "wifi network" with just two wifi > devices (and *no* access point) in much the same way > that you can have a *wired* network with just two > devices (and no hub/switch). [though the analogy breaks > down once you go to more than 2 devices since you can't > just wire together N wired devices whereas you *can* > wireLESS together N WiFi devices!] "ad-hoc" this is what I was missing in order to be able to find the proper information on the net. Thanks
From: PovTruffe on 15 Jun 2010 12:30
"Joerg" <invalid(a)invalid.invalid> a �crit : > > Possibly this can get you started: > > http://techpp.com/2010/01/31/how-to-build-wireless-network-without-router/ Thank you. This is what I was looking for. Just the words "ad-hoc" in fact. |