>
>> I do think it'd be nice to have an Ethernet Discoverer application for
>> both Android and iOS. Like the Windows version, it would open a web
>> browser with the IP address clicked on the list of found devices. We'll
>> probably do that eventually where I work.
>>
>> If the device you're talking to is the only one on the network (an ad
>> hoc
>> network created by the device), I think the DNS server would work. Any
>> domain name would return the IP address of the device. But, on a general
>> network this would not work.
>>
>> Harold
>>
>>
>
> It is never the only one since it needs a wireless access (wifi
> router) point to talk to the phone. And normally this access point is par=
t
> of a
> home network, connected to internet and a bunch of other
> wired and wireless computers and devices.
>
> The adhoc method with a wifi module wouldn't work good in this case
> either since the phone is almost always connected to the wireless
> network that has internet access (a home network). Which would mean
> that I first have to change the wifi connection on the phone, connect to
> my
> device (adhoc), change settings so it connects to the existing
> wifi router instead of using adhoc, restart it, change back the wifi
> setting on the phone and I still can't connect to it with my phone
> without knowing the IP address.
>
> Besides, the android (older ones anyway) can't use adhoc (in theory
> they can but needs to be rooted first).
>
> So, the only option for my needs as I see it now is an Android
> version of Microchips device discoverer software. And that would have to
> be
> placed in Google Play (app market) in order for the user to
> find it.
>
> I did a quick search on Google Play (market) and did find an app that was
> designed just as the microchip device discoverer but on my phone
> it just crashes instantly. The app is called Device Discoverer and is
> free.
>
> An earlier version of my device does actually use the wifi module but I
> decided
> to drop that since there could be even more problems trying to install
> that in
> an existing network with a random router using any type of security.
> Handling
> support calls would have been a nightmare.
> With a wired interface it is just to plug it in and the device is
> instantly part of the LAN.
>
> I also thought that the WiFi module was a bit flaky and it
> disconnected (and reconnected) pretty often. I havn't tried the new
> MRF24WG module though.
>
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Ruben J=F6nsson


Thanks for the comments! I have so far only done wired Ethernet, so you
have more experience with embedded Wi-Fi than I.

I'll give the Device Discoverer a try. I also tried Shares Finder, which
searches a range of IP addresses (by default the subnet) for various
services (HTTP, FTP, etc.). This found my devices with HTTP servers.

Thanks!

Harold


--=20
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!
Not sent from an iPhone.
--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.