Eye fi bug

  • 9 Replies
  • 1453 Views
*

Offline timgor

  • ***
  • 150
Eye fi bug
« on: 05 / March / 2015, 10:38:25 »
Advertisements
My topic is not related to the CHDK directly but people that developed the EYE fi module can probably help me because they know some "structure" of eye fi card.
There is a problem with eye fi. It stops working (transferring) after about month. Actually it stops working every few hours and resume to work after I reset the power but after about a month it stops transferring pictures and start again only after I re-format it.
It' not a single case. there was a few times when i had "X2 connect" and It happened again with a Pro X2.

Do you have Idea what is it?
Do you know how to resolve this issue?
Is there any way how to re-format or "refresh" the card from CHDK keeping files not to be deleted?

I don't ask for exact solution I just ask what can I try to "refresh" the card and keeping the files not to be deleted.


I have some additional information about my conditions:
I take too many timelapse pictures every day 500 to 1000.  That can be the reason why other people that normali use the EYE fi card do not have that issue...
may be there is some hidden files that counts the pictures and may be they  just stuck after a huge amount of transferred pictures and may be I just clean it up by formatting....

« Last Edit: 05 / March / 2015, 13:54:01 by timgor »

*

Offline reyalp

  • ******
  • 11268
Re: Eye fi bug
« Reply #1 on: 05 / March / 2015, 15:53:32 »
This is likely something related to the software that runs on the eye-fi itself. Your best bet is probably to contact eye-fi themselves for support. CHDK's interaction is limited to a simple file based interface.

You might also consider the hackable, linux based Transcend cards:
http://hackaday.com/2013/09/19/advanced-transcend-wifi-sd-hacking-custom-kernels-x-and-firefox/
http://chdk.setepontos.com/index.php?topic=11262.0

There has been some previous, inconclusive discussion about rebooting eye-fi cards
http://chdk.setepontos.com/index.php?topic=6364.0
http://chdk.setepontos.com/index.php?topic=5563.msg53792#msg53792 (oh, you were in that discussion too...)
Don't forget what the H stands for.

*

Offline timgor

  • ***
  • 150
Re: Eye fi bug
« Reply #2 on: 05 / March / 2015, 16:17:01 »
Thanks, the rebooting of the eye-fi card is a different issue than what I have now.
By the way there is another question. A1400 camera has an indicator of eye-fi card that shows if it's transferring pictures or not.
What kind of function in CHDK would be responsible for it?

*

Offline reyalp

  • ******
  • 11268
Re: Eye fi bug
« Reply #3 on: 07 / March / 2015, 15:52:38 »
A1400 camera has an indicator of eye-fi card that shows if it's transferring pictures or not.
What kind of function in CHDK would be responsible for it?
I believe that's a Canon firmware function, not CHDK.
Don't forget what the H stands for.


*

Offline timgor

  • ***
  • 150
Re: Eye fi bug
« Reply #4 on: 11 / March / 2015, 11:54:04 »
Ok, I can ask more particular question. It's related to reyalp and philmoz who created eye fi module.
There are five hidden files in the eye-fi card: RSPC REQM REQC RSPC RSPM.

1. What file is responsible for collecting data during eye-fi work?
Some file must be responsible for it because eye-fi has a function to Get Eyefi card Log via eye-fi center function.

2. What file can be affected by formatting the eye-fi card?
The formatting really "clean up" some "bug" and helps to resume transferring.

Right now my card stuck after 5 days of work and I've got log file (see the attachment).
I didn't do anything with it.

3. If you don't know the answer to the first two questions - is there any way to take data from the card at this point then format it and take data after formatting and compare it to the first one?
May be it will help to figure out what is the bug and how to clean it out by a program without formatting the whole card.



*

Offline philmoz

  • *****
  • 3066
    • Photos
Re: Eye fi bug
« Reply #5 on: 11 / March / 2015, 14:54:07 »
Ok, I can ask more particular question. It's related to reyalp and philmoz who created eye fi module.
There are five hidden files in the eye-fi card: RSPC REQM REQC RSPC RSPM.

1. What file is responsible for collecting data during eye-fi work?
Some file must be responsible for it because eye-fi has a function to Get Eyefi card Log via eye-fi center function.

2. What file can be affected by formatting the eye-fi card?
The formatting really "clean up" some "bug" and helps to resume transferring.

Right now my card stuck after 5 days of work and I've got log file (see the attachment).
I didn't do anything with it.

3. If you don't know the answer to the first two questions - is there any way to take data from the card at this point then format it and take data after formatting and compare it to the first one?
May be it will help to figure out what is the bug and how to clean it out by a program without formatting the whole card.

The eye-fi code was added to CHDK by user buttim if I recall correctly (I just cleaned up the module).

It was based on the earlier work done by Dave Hansen which was in turn based on work done by Chris Davies.

The workings of the eye-fi card are not officially documented, the easiest way to see what the CHDK code is doing is by understanding the source code.

All the eye-fi code in CHDK does is allows some configuration of wireless access points and credentials stored on the card. It has no interaction with the recording or wireless transfer of images.

There are probably other things that can be done by manipulating the files you mentioned; but no-one has reverse engineered the card firmware to understand what could be possible (as far as I know). I don't think there is even a dump of the firmware available anywhere. All the magic stuff the eye-fi card is doing is inside the card, not in the Canon firmware code or CHDK.

If you think this is a bug in the eye-fi card itself you would be better to ask eye-fi for help - I don't think there is much we can do here.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)

*

Offline timgor

  • ***
  • 150
Re: Eye fi bug
« Reply #6 on: 11 / March / 2015, 15:09:55 »
Ok thanks, I think I will  study this case myself.
One more question. If files RSPC REQM REQC RSPC RSPM can be accessed via c++ does it mean that it can be accessed (opened) in linux? In windows they are invisible.

*

Offline reyalp

  • ******
  • 11268
Re: Eye fi bug
« Reply #7 on: 11 / March / 2015, 15:50:14 »
Ok thanks, I think I will  study this case myself.
One more question. If files RSPC REQM REQC RSPC RSPM can be accessed via c++ does it mean that it can be accessed (opened) in linux? In windows they are invisible.
CHDK just uses regular file operations, so presumably the same should be true on other OSes. My impression (not actually having any of these cards) is the card notices when files with those magic names are created or used.

Dave Hansens blog and links found there may have more information http://dave-hansen.blogspot.com/
Don't forget what the H stands for.


*

Offline timgor

  • ***
  • 150
Re: Eye fi bug
« Reply #8 on: 12 / March / 2015, 11:15:20 »
Thanks for replies but let me continue this topic that will relate to the CHDK.
Yesterday I figured out that it looks like the problem arise from corrupted files on the SD card.
Is there any utility in lua or c++ that would allow to fix corrupted files or scan and repair the whole disk...
it would be good for CHDK itself because for aborted video recording brings the same problem,
it leaves some corrupted files that must be fixed or/and deleted from time to time.

From the web I see that it is called something like "file shredder" - utility that deletes corrupted files.
Update:
it is something like
http://www.codeproject.com/Articles/22736/Securely-Delete-a-File-using-NET
http://www.codeproject.com/Articles/30453/Secure-File-Shredder

Do you like the idea to implement it to the CHDK?
« Last Edit: 12 / March / 2015, 12:16:04 by timgor »

*

Offline reyalp

  • ******
  • 11268
Re: Eye fi bug
« Reply #9 on: 12 / March / 2015, 16:16:23 »
Thanks for replies but let me continue this topic that will relate to the CHDK.
Yesterday I figured out that it looks like the problem arise from corrupted files on the SD card.
Is there any utility in lua or c++ that would allow to fix corrupted files or scan and repair the whole disk...
it would be good for CHDK itself because for aborted video recording brings the same problem,
it leaves some corrupted files that must be fixed or/and deleted from time to time.

From the web I see that it is called something like "file shredder" - utility that deletes corrupted files.

Do you like the idea to implement it to the CHDK?
You shouldn't be getting corrupted files in normal operation. If you are, it indicates a much larger problem, or an incorrect usage like powering off in the middle of a video.

If someone wants to implement something like chkdsk (http://en.wikipedia.org/wiki/CHKDSK) in a CHDK module, I wouldn't object, but I suspect it would be a lot of work, and would have a fair chance of doing more harm than help until properly debugged.

I would assume there there are some open source, low level FAT utilities out there that might server as a starting point. freedos appears to include a variant of CHDKDSK http://www.freedos.org/software/?prog=chkdsk
Don't forget what the H stands for.

 

Related Topics