![eye fi x2 eye fi x2](https://s3.manualzz.com/store/data/024253893_1-b2e6ce7ebfb10958519065ab2f6368c2.png)
I'm concerned about bricking other cards somehow.Įye-Fi released a new card model recently.
EYE FI X2 SOFTWARE
I'm going to hold off on actually releasing the software for a bit.
![eye fi x2 eye fi x2](https://live.staticflickr.com/5002/5286754227_a47998ba71_n.jpg)
This is not the first time I've managed to break one of these cards, and I'm hoping the support will be as great as it was last time. The odd part is that the official software does something in a very similar order. The card never responded to another command, despite a number of reformats. I think it happened just after I started direct mode, then asked the card to scan and then give me a list of configured networks. The bad news is that I bricked a card doing this.
![eye fi x2 eye fi x2](https://www.popphoto.com/uploads/2019/01/17/OV2UY6GXX4BPGFV6ANKE2VJFVU.jpg)
This is useful for pairing, and corresponds to a button of the same name in the Eye-Fi Center GUI. S: tells the card to "Start Direct Mode Network".O: DIRECT_WAIT_AFTER_TRANSFER: Corresponds to "will stay on YY seconds after the last item is received" slider.0 means "direct mode off" and 0xff means "wait forever" O: DIRECT_WAIT_FOR_CONNECTION: Corresponds to "wait for XX seconds for a device to connect" slider in Eye-Fi center.Two of them are big 'O' integer commands: an ASCII 'O' followed by a command-number byte (like an ioctl()), an argument length byte, and then a single byte for the number being fed in to the command. The good news: I believe I have direct mode working.