iPad connection problems (resolving url and error 48)

[jo...@inventors-emporium.co.uk]

Hello Byron,

42s Version 3.2.1

Free42 1.4.70i

MacOS 10.8.5

Safari 6.1.6

iPad 3, iOS 7.1.2

I cannot connect to my iPad over WiFi using the URL supplied on the I/E page.

The URL is a contraction of my iPad’s name in this format:

http://myipadname.home:8000

Safari (and other browsers) simply report that I am not connected to the internet.

If I use an iOS utility or an IP scanner, I can discover the address for the 42s running on the iPad and get it working but I would probably need to check this every time I wanted to connect on a network.

On my iPod Touch, the 42s supplies a network IP address instead of a name and this does allow me to connect and exchange files reliably so far.

All devices are on the same network.

Any suggestions as to why the supplied URL format is not resolved for the iPad?

Also I now have the following error after entering the I/E screen on the iPad a few times, even though no other device is ever addressed the same way:

Error - Address already in use (48)

I don’t know how to clear the error once it has appeared.

If I turn the device’s WiFi off and quit the browser, 42s immediately reports there is no network connection, so it’s actively seeing the environment, but if WiFi is enabled again the error returns, presumably because the same IP address is being allocated.

---

Honestly Byron, I would much prefer if raw program files could at least be transferred through the 42s file system in iTunes than have to work through a networked browser interface.

A lot of apps have import/export to iTunes or expose their working files directly there. Either of these would be better in comparison to this rather clumsy dance which also results in files scattered in download folders, working folders etc.

Another, even better option, would be to allow access to Dropbox and make that the file system for the exchange of program files. Then all the devices using 42s could share the same repository of programs with very little management overhead. It could also be the location for the printer outputs etc. This would be my number one feature request to make the whole 42s ecosystem really hum.

Otherwise I'm having having a ball with 42s and it has already made some recent fieldwork much more efficient.

Thanks in advance,

Joel.

[Byron Foster]

On Friday, September 26, 2014 3:40:49 AM UTC-7, jo...@inventors-emporium.co.uk wrote:

I cannot connect to my iPad over WiFi using the URL supplied on the I/E page.

The URL is a contraction of my iPad’s name in this format:

http://myipadname.home:8000

Safari (and other browsers) simply report that I am not connected to the internet.

If I use an iOS utility or an IP scanner, I can discover the address for the 42s running on the iPad and get it working but I would probably need to check this every time I wanted to connect on a network.

On my iPod Touch, the 42s supplies a network IP address instead of a name and this does allow me to connect and exchange files reliably so far.

All devices are on the same network.

Any suggestions as to why the supplied URL format is not resolved for the iPad?

Hmm, I/E looks for an assigned device host name for convenience, prettier then an IP address i suppose.  For some reason the IP your iPad believes it resolves to does not resolve on your PC.  Strange that your iPod does not have an assigned hostname but your iPad does.  My guess is that your router is providing DNS services and is picking up the hostnames from DHCP.  your iPad is using the router's DNS service for host name resolution, but your PC is using a WAN address... just a guess though.  You can get your iPad's IP address from Settings->WiFi->[SSID name info], and I'm sure that would work.  But, yea... This is a pain.

 

Also I now have the following error after entering the I/E screen on the iPad a few times, even though no other device is ever addressed the same way:

Error - Address already in use (48)

Yea, this will happen if you switch back and forth quickly... the device is living on a port, and that port just doesn't shutdown quick enough.

 

I don’t know how to clear the error once it has appeared.

Sounds like a bug.

 

Honestly Byron, I would much prefer if raw program files could at least be transferred through the 42s file system in iTunes than have to work through a networked browser interface.

A lot of apps have import/export to iTunes or expose their working files directly there. Either of these would be better in comparison to this rather clumsy dance which also results in files scattered in download folders, working folders etc.

All true.  There is even partial support for this with the state file and printer text file.  But it just doesn't load programs. Not a very difficult addition, but I haven't heard anyone asking for this, till now.  The web interface scheme was cooked up before iOS/iTunes offered file sharing services.   If file sharing services where available I would have used them and never bothered with the web server solution.  On a side note, the web server was no small piece of work, Thomas Oaken wrote it and I think it's a pretty slick solution for the time, but I digress. 

 

Another, even better option, would be to allow

 

access to Dropbox and make that the file system for the exchange of program files. Then all the devices using 42s could share the same repository of programs with very little management overhead. It could also be the location for the printer outputs etc. This would be my number one feature request to make the whole 42s ecosystem really hum.

Yea, that would sexy... I'll look into it.

 

Otherwise I'm having having a ball with 42s and it has already made some recent fieldwork much more efficient.

Thanks in advance,

Joel.

Awesome, and thanks!

 

[jo...@inventors-emporium.co.uk]

Hi Byron,

Thanks for your comments and I hope you will have a chance to look at these issues when you have the opportunity.

For sure, the web server must have been quite a project to write, so no lack of appreciation here for the work involved, but other iOS developers whose apps I have that used the same technique have found other ways to move data around, now that those options are more accessible than they were.

Heartfelt thanks to you and Tom for bringing these great tools to us.

Joel.