I have an ideal solution in mind to configure a wireless embedded device for those end users who does not have too much affection with computers. Unfortunately I did not find a solution so far to get started realizing that idea. Hopefully someone can give me some suggestions or keywords to get started.
Here’s what I like to realize.
I want to create a device using an EMX board with a WiFi module, but without any display for user interaction. Initially when the end user receives such a device for the first time he/she needs to configure its WiFi settings in order to have that device connect to his wireless router/network.
Initially I like to have the device acting as an router access point, so that the user can use his laptop, tablet or WiFi enabled smart phone to easily connect to the device. Once connected it can use his browser to go to a configuration page to enter the wireless router/network settings. Once setup has been completed the device can be rebooted. The device will start in normal mode and connect as a client to the wifi router.
I looked at the AD HOC mode which is now available at GHIs WiFi module based on Redpine. I have made a small test program to setup an EMX as an ad hoc creator, but from there I don’t know how to exchange data with an application running for example on a PC. Can I for example bind a socket to the connection?
Hopefully I expressed my idea well enough and I’m looking forward for some suggestions.
Yes, you will use a socket to communicate. When you install the .net micro framework(Samples | Microsoft Learn), there is a samples directory (Documents\Microsoft .NET Micro Framework 4.1\Samples\SocketClient). Look at the SocketClient and SocketServer samples.
Daniel6 i am familiar with sockets and wrote a few communications applications using them. I was more wondering how to communicate with a .net mf app that have WiFi configured as AdHoc creator. For example if i add a listening socket in my EMX app… How does my app on another device knows how to access that EMX app, what kind op protocol is used??
For those interested, the solution was easier as expected Just assign a static IP address starting with 169.254 to the network interface and you are able to communicate in ad-hoc mode.