I just wanted to let everybody know that my software still works with the 4GB cards. I have a 4GB "Home Video" card, and I was able to program it just fine with my software. It claims to have the same firmware version that my 2GB card has. I have not verified that the images are the same (or very similar).
I'm pretty sure that the 4GB cards are very different internally than the 2GB cards. I get ~6MB/sec write speeds, which is at least 3x what I got before.
I'm not sure about the 8GB Pro card. Is it just a 4GB card with more flash, or truly the 3rd-generation model? Does it share firmware with the 4GB cards? I also do not know how to program the Ad-hoc networks into it. I believe that Ad-hoc networks will need to have static IPs at least, and I have no idea how to program that into the card.
BTW, does anybody have the Eye-Fi manager working under WINE these days?
Subscribe to:
Post Comments (Atom)
10 comments:
I'm getting 18 Mb/s with my Eye-Fi Home Video 4Gb card, using the internal card reader of my new HP machine running Windows 7.
I can't seem to get the 4GB working at all with the EyeFiServer Python script. You used this at all with a new ard?
*new card
Just wondering, Is eyefi-config good enough yet that it would be reasonable to get an eyefi card without having a windows box? Should stuff other than Ad-Hoc work with the Pro X2? (I mostly want the faster throughput and RAW support.)
I've actually never used the Python server. It's not actually a part of my project. You might want to ask its author.
My software can _control_ the cards from the beginning. The only issue is registering the card with the Eye-Fi management infrastructure. That's a whole different can of worms than talking with the card, and I haven't delved into it yet. I guess it is something we could ask Eye-Fi to do for us: just provide a web form to activate a card. But, that might be much more tricky and error-prone than having software do it.
Oh, and about the Pro cards... I don't have one, so I haven't tested my software at all with them, sorry. I've heard that most everything is still the same, though.
Thanks for your software - just discovered it today and used it to add a network to my card from Ubuntu at a conference (didn't have my Mac with me).
Couple of small things would be nice to see, like program parsable output (so I could make a pygtk wrapper to list / add networks), and also I noticed that the --help output lists the wrong binary name. Oh, and any idea how to update the firmware on a card without the EyeFi software? the web page reports that my card needs updating.
Andy, try this:
http://git.sr71.net/?p=eyefi-config.git;a=blob;f=eyefi-firmware-fetch.pl;h=67d35b64c0f19641ed23651f5d1f0b56a9488231;hb=0c45dfb98bed60b07196d81e451318c1eb0ab0a8
Give it your MAC and version 3.0303 then copy the output to /media/EYE-FI/EYEFIFWU.BIN. Then issue 'eyefi-config -b'. The card should upgrade.
I need to automate this. But, I need to first find the web API where you query firmware versions. I've seen it, but need to find it again. If someone knows how, they'd save me a lot of time.
If you want program-parseable output... I take patches. :) I'd also be happy to include python wrappers in my distribution.
Figured you'd say that :-) (about patches) - when I get some time after the conference I'll try to take a look into this.
/me adds another entry to the "fun projects" list...
... ah ok it's actually 3.03.01 at the moment. OK. Seems to have worked, although the -b output said "never saw card seq response", a -f confirms it now has the newer version. Cool. Thanks.
Post a Comment