Quote from: c10ud on 06 / August / 2012, 08:17:15to get the job doneJob?Challenge! BTW, read the link I posted here
to get the job done
(short story: "Communication Error" when n-pics>1024 or something like that and USB is plugged to a PC.Ask Google for more users whining about it, it's a Canon firmware "feature" that leaves users happy (?) of their pricey purchase.
Communication error• Images could not be transferred to the computer or printed due to the largeamount of images (approx. 1000) stored on the memory card. Use acommercially available USB card reader to transfer the images. Insert thememory card into the printer’s card slot to print.
The camera simply doesn't show up as a device as if the firmware is locking usb, i'm currently trying to dig this in a DryOS camera (a495) but so far no result -- )
Quote from: c10ud on 06 / August / 2012, 10:08:38(short story: "Communication Error" when n-pics>1024 or something like that and USB is plugged to a PC.Ask Google for more users whining about it, it's a Canon firmware "feature" that leaves users happy (?) of their pricey purchase.Windows and/or Mac? Canon utility or default OS PTP support?Excerpt from their manual for the A495:QuoteCommunication error• Images could not be transferred to the computer or printed due to the largeamount of images (approx. 1000) stored on the memory card. Use acommercially available USB card reader to transfer the images. Insert thememory card into the printer’s card slot to print.On Linux, I patched some part (a constant) of libgphoto to remove a similar limit in libgphoto itself.Quote The camera simply doesn't show up as a device as if the firmware is locking usb, i'm currently trying to dig this in a DryOS camera (a495) but so far no result -- )May be a client issue. Or the camera runs out of RAM (it can only use a dedicated amount for this).You can find/create another topic if you feel so.
- Every platform- i know about gphoto, but it's not at that level, the device isn't even showing up in syslog- it's because of the camera, and happens with higher end models too, it's not limited to cheap models (see google) i'd just like to find out a way to stop this behaviour, i guess it's checking for how much pics are in the card and blocking the usb communication (probably some limitation in their ptp implementation, just like gphoto had), but so far no luck in disassembling the usb stack
Quote from: c10ud on 06 / August / 2012, 11:10:00- Every platform- i know about gphoto, but it's not at that level, the device isn't even showing up in syslog- it's because of the camera, and happens with higher end models too, it's not limited to cheap models (see google) i'd just like to find out a way to stop this behaviour, i guess it's checking for how much pics are in the card and blocking the usb communication (probably some limitation in their ptp implementation, just like gphoto had), but so far no luck in disassembling the usb stack The same 1000 pictures limit is stated even in the G1X manual May I ask what kind of solution do you want? Does it have to work without installing anything on the PC? If that's the case, explain it to the moderator (philmoz is the active mod these days) to split this conversation into a new topic along with a new topic title. Use the "Report to moderator" link on the first offtopic post.An idea:You could rename files (or better, their folder, if that works reliably) to something the Canon OS doesn't expect, then restart the camera. Do this so, that there are less than 1000 recognizable pictures for the camera at a time. Of course you'll need to use a file to track this, and a sophisticated script. Downside: requires some user interaction on the camera. Beware, needs to be tested on every possible camera before real use, the rename function may be broken on some ports.
i know the limits are stated in the respective manuals, but i find them at least funny in 2012.
the idea is start making the camera show up correctly in the PC (no "communication error" on the camera) and see what happens next (if it's still usable, if it shows some weird error, etc.). the idea would be: isolating the code that makes the camera fail and replace it with a simple hack - or - override the jpg counter value (?) that makes the camera fail - or - ?so far i've identified a few functions that check things when the usb cable is connected and i see they are somehow linked with spitting errors - unfortunately i'm going really slow since my disasm skills are not so great
You could rename files (or better, their folder, if that works reliably)
Started by chaonatic « 1 2 3 4 5 » CHDK Releases
Started by Lebenita General Discussion and Assistance
Started by bluephilosopher General Discussion and Assistance
Started by Stonefire « 1 2 » Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)
Started by oreste General Discussion and Assistance
