[Adam]

Hi Liviy,

Sorry for the late reply. The MTP interface that Airnef uses to communicate with the camera only allows 32-bit values for the offset and transfer size of a given file (at least for the version of the specification I have), which means the largest file it can transfer via the interface is 2^32, which works out to 4GB.

Regards,

Adam

[Adam]

Hi,

You can see sample command lines for –downloadexec including for Irfanview in the online manual at http://testcams.com/airnef/#DownloadExec

Thanks,

Adam

• This reply was modified 6 years, 1 month ago by Adam.
• This reply was modified 6 years, 1 month ago by Adam.

[Adam]

I haven’t looked into how WMU is able to request scaled images from the camera. I assume it’s an undocumented MTP request. If I have time I’ll analyze a request from WMU with Wireshark and see how it’s done.

[Adam]

I don’t currently have plans to add GoPro support, sorry 🙁

[Adam]

It’s not. I plan to create a repository in the near future.

[Adam]

Hmmm, my S120 works. The only time I’ve seen this error on Canon bodies is as the message describes – the camera thinks a client other than Airnef is registered for the WiFi config. Does the camera work with Canon’s iOS app? (CameraWindow or CameraConnect)

[Adam]

Thanks for the log. The camera is returning an invalid object handle for the parent directory of the camera’s “100NIKON” directory. This violates the MTP specification. To workaround the issue can you try commenting out line 1842 by placing a # at the start of the line. For example:

		#
		# recurse to create MTP objects for the directory tree referenced by this object if we're instructed to do
		# so and this object has a parent dir and no MtpObject exists for the parent already
		#
		if fFindAndCreateAntecendentDirs and mtpObjectInfo.parentObject and MtpObject.getByMtpObjectHandle(mtpObjectInfo.parentObject)==None:
			applog_d("Recursing to get parent dir of \"{:s}\" - objHandle=0x{:08x}, parent=0x{:08x}".format(mtpObjectInfo.filename, objHandle, mtpObjectInfo.parentObject))
#			createMtpObjectFromHandle(mtpObjectInfo.parentObject, createMtpObjectStatsStruct, cachedMtpObjectInfoListDict, fFindAndCreateAntecendentDirs)				

[Adam]

Thanks. Based on the debug data the S3700 is returning an empty serial number, which airnef doesn’t expect and results in the runtime error. Can you download the airnef source and change removeLeadingCharsFromStr() to the following (‘charPos = 0’ is only change) and then run airnef from the source and see if there are any other issues working with the S3700? Thanks!

def removeLeadingCharsFromStr(str, charsToRemoveSet):
    charPos = 0
    for charPos in xrange(len(str)):
        if str[charPos] not in charsToRemoveSet:
            break;
    return str[charPos:]

• This reply was modified 6 years, 9 months ago by Adam.
• This reply was modified 6 years, 9 months ago by Adam.
• This reply was modified 6 years, 9 months ago by Adam.
• This reply was modified 6 years, 9 months ago by Adam.
• This reply was modified 6 years, 9 months ago by Adam.
• This reply was modified 6 years, 9 months ago by Adam.

[Adam]

Can you try the same session with logging set to ‘debug’ and paste the resulting log here? Thanks.

[Adam]

Two other users have reported this. I can’t find any information about the error online. I know it’s related to the older version of Python included in the older OSX you’re running (I run 10.10.5) but unfortunately I don’t have any Mac systems running that older OSX rev to troubleshoot this.

What you can try is upgrading Python to the current latest release, which should override the older version that was included in OSX. You can download it at:

https://www.python.org/downloads/release/python-2710/

• This reply was modified 6 years, 9 months ago by Adam.

[Adam]

Hi Haldi,

When airnef searches for a camera every 5 seconds it only sends a few packets each time so the network traffic (and CPU load) is very light. Airnef supports “auto” for the IP address on Sony (and Canon) cameras so it’s not required to use a static IP address – airnef will use SSDP to find the camera.

Hope that helps!

Adam

[Adam]

Hi Serge,

Thanks for the info. I did an online search and confirmed the newer convention on Linux is to store user-specific data rooted in a unified ~/.local/share/, per your patch. I’ll be sure to include this change in the next release.

Btw thepatch as written wont have the desired effect – it’s setting the local variable ‘applicationSupportDir’ but not using that variable to modify g.appDataDir, which is the variable that will actually determine the data directory airnef uses. To resolve this you can modify the patch to set ‘g.appDataDir’ instead of ‘applicationSupportDir’.

[Adam]

They’re from the information the camera returns for the MTP object (file), which in turn typically come from the encoded timestamp for the file on the filesystem on the media card. Airnef doesn’t presently look at any EXIF data in files. I should mention Nikon presently has a bug on some cameras where the seconds portion of the MTP timestamp is always half what it actually is for the file – it’s a very odd bug. For example instead of reporting 16:34:36 for a file the camera reports 16:34:18 to an MTP client like Airnef. Or instead of 16:34:10 it reports 16:34:05. The camera reports the correct time when viewed in the playback menu and the actual filetime is correct – only the time returned to MTP clients has the issue.

[Adam]

There’s a process of elimination to get to the problem. First, are you able to connect to your D7100’s WiFi network on your Mac Pro? Then, to verify the connection and the camera’s IP address, can you open a terminal window and type “ping ipaddress”, where ipaddress is the address of the camera – for example, “ping 192.168.1.1”, and verify that the pings are successful (don’t time out). If all that seems good can you copy and paste the transfer log of a connection attempt into a reply on this thread?

• This reply was modified 6 years, 10 months ago by Adam.

[Adam]

Hi David,

Thanks for the feedback. The 6D supports selecting images in the camera during the WiFi set configuration, where you can select by some criteria including how image(s) were ranked (1-5 stars) in the playback menu. I would have thought this mechanism would work by the camera limiting which images airnef can see based on that camera-selected criteria but it appears there is some other mechanism the camera uses to notify host software (like airnef) about which images were selected. airnef doesn’t currently support whatever mechanism that is but I’ll try to find time to capture a 6D -> Canon software session with Wireshark to reverse engineer what it is.

[Author]

Posts