Geotagging Works!

I took a picture earlier this morning, which wasn't geotagged. I just took another and noticed that my AP had finally gotten into Skyhook's DB. I submitted it last Tuesday and it took a bit less than a week.

If you wonder what this is, I've been making cables to convert my old RAZR chargers to charge the iPhone 3G. The RAZR is a male USB Mini-B, so I need female USB Mini-B connectors which have been really hard to come by. I've been using this guy's schematic to get the right voltages on the USB data pins so the iPhone will actually charge.

P.S. Please no stalking! :)

Zaurus Development

Someone loaned me a Sharp Zaurus SL-5600 so that I might try a port of my software to it. I got an arm cross-compiler, but I can't even get "Hello World" running. It just segfaults. I bet I'm compiling for the wrong platform or something. Oh, well. I really need to get a NIC for this thing. Should make development a lot easier.

I also picked up an iPhone 3G, which got me thinking. Seeing as at least a couple of the Eye-Fi employees have iPhones and that there's already a Mac OS port of the Eye-Fi manager software, I have to wonder if we'll be seeing an Eye-Fi iPhone app some time. The biggest sticking point is that neither the iPhone or the Eye-Fi card can act as a WiFi access point as far as I know, they can only join them.

I also haven't been able to get Loki to work. As far as I can tell, there's no Linux port. Sigh... I did submit my AP to their DB, though.

Eye-Fi Explore and release 005

My old classic Eye-Fi card broke after I squished it, plugged it about 30,000 times and cut a hunk of plastic out of it. The guys at Eye-Fi replaced this "defective" (their words, not mine :) and to show they are swell folks, replaced it with one of the newfangled Eye-Fi Explore cards that do geotagging. Thanks guys! BTW, I don't consider it defective, I consider it abused.

I was able to do all of the card initialization in WINE. It would not complete the final test step, but it works fine anyway. I need to dig through those WINE logs and see if there's anything interesting in them.

New observations:

1. I have two access points running with the same ESSID, but on different channels. This works for my PCs, but made the card very mad. It would not associate for long enough to upload anything.
   
2. The card comes from the factory without its EyeFi/{reqm,rspm,...} files. The manager software must create them. I created them with dd, and was able to use the card before I ran the manager software. I also saw a 'EyeFiManufacturing' wireless network in the card log!
3. I added a network to the card before I registered it. The card DHCP'd and tried to upload its pictures, but choked once it talked to the Eye-Fi server. No surprise here, but it does open up the possibilities if someone ever reverse-engineers the server protocol.
4. I enabled geotagging, but it does not seem to work for me, yet. Anybody have this working? Anybody know of any quick ways to check Skyhooks's AP list?
   

I'm also pleased to announce Eye-Fi Configuration Tool Version 005. This should fix the crashing bugs that some people were seeing. My printf() function was screwed up and calling printf() instead of vprintf(). Git tree here.

Git tree

Because someone asked, I've also put up a git tree. I'm honestly not planning on putting out that many updates, but I figure I'll share anyway.

http://git.sr71.net/cgi-bin/gitweb.cgi?p=eyefi-config.git;a=summary

Eye-Fi Config Release 004

There are no new features or anything in here, but I wanted to at least share my recent work. I put the file that I'm using for CHDK in here, and also some bits intended to help get this running on OSX. Thanks got to Reed Wade for the work he's doing on OSX!

http://sr71.net/projects/eyefi/eyefi-config-004.tar.gz

This is completely untested because my Eye-Fi card is now completely dead. I'll probably go get one of the new "Explore" cards at some point, but I'm without a card for now.

A kind soul also lent me a Sharp Zaurus to try and get my software running on it. I'll let everyone know how that goes.

Shaky, but working again

I got the card running again with the volume serial number 'AA52-6922'. I guess that's how the Eye-Fi manager actually finds the card, rather than looking for the EyeFi/r* files like my software has been. Anybody know offhand how to find this stuff in Linux?

I also got a request to make my manager software work on OSX. I'd love to do that, but I don't have a Mac. If anyone wants to give me ssh access to one or something, I'd be happy to give it a shot. Shouldn't be more than an hour or two of work, as long as there are development tools around that I can use.

Even the Eye-Fi Manager Can't Find the Card

I think all of my formatting and messing with the card made it unrecognizable from the Eye-Fi Manager's point of view:

06/14/2008 13:28:35 000000B4 INFO Scanning initial drives...
06/14/2008 13:28:35 000000B4 INFO Not Eye-Fi Volume serial number
06/14/2008 13:28:35 000000B4 INFO Not Eye-Fi Volume serial number
06/14/2008 13:28:35 000000B4 INFO Drive scan is complete...

Could someone who has the card running in windows do a 'dir' of the Eye-Fi card for me? I think I wiped out its serial number and need to recreate it.

c:\> dir e:
Volume in drive E...
Volume Serial Number is XXXX-XXXX
...

Could you send me the X's?