Adam

Forum Replies Created

Viewing 5 posts - 61 through 65 (of 65 total)
  • Author
    Posts
  • in reply to: external router? #481
    Adam
    Participant

    It should work well. I’ve tested that TP-Link adapter with my D7200.

    in reply to: external router? #477
    Adam
    Participant

    Unfortunately Nikon cameras only support ad hoc wireless connections, which means the camera creates a new wireless network that you must connect to rather than having the camera connect to your existing infrastructure wireless network. Canon cameras support the infrastructure mode. If your system doesn’t have WiFi then a great USB WiFi card that I use is the TP-Link TL-WN722N – it sells for $12.84/USD on Amazon:

    http://www.amazon.com/TP-LINK-TL-WN722N-Wireless-Adapter-External/dp/B002SZEOLG/

    When you use this card be sure to change your camera’s IP address to 192.168.2.1 if your router is at 192.168.1.1. I have instructions on how to do this in the user guide at http://testcams.com/airnef/

    in reply to: Great and suggestion :D #476
    Adam
    Participant

    Hi Pierre,

    Your english looks good to me 🙂 Regarding creating a new directory in the directory selection dialog, the cross-platform user interface framework I’m using unfortunately doesn’t include that option in the Mac version of that dialog (it’s there in the Windows app). But I’ll look into what it will take to code a custom version of the dialog for a future version.

    in reply to: Two pitfalls + question #468
    Adam
    Participant

    The self-contained executable I build for the Windows platform is 32-bit so it’ll go in the Program Files (x86) folder. The virtual store alias for any data files written to the Program Files directory should be something like: C:\Users\your user name\AppData\Local\VirtualStore\Program Files (x86)\airnef

    Thanks for the tip on the Nikon Wireless Mobile App! It never would have occurred to me that Nikon would put the ability to change the camera’s ad hoc IP address/security in their mobile app and not on the camera’s menu system like Canon does. I guess it makes sense since Nikon’s only wireless software right now is their mobile app. I’ll be sure to add this info to the user guide for those who run wired+WiFi or anyone looking to secure their camera’s WiFi.

    • This reply was modified 6 years, 11 months ago by Adam.
    in reply to: Two pitfalls + question #465
    Adam
    Participant

    Hi,

    Thanks for the feedback. When two network interfaces are on the same IP subnet the system will select the interface with the fastest link/shortest route, which will be the wired ethernet connection in your case. It might be possible to juggle the metric values to route individual traffic to each interface on the same subnet but since your router is using the same IP address of the camera you’d only be able to use one at a time in your configuration. Unfortunately Nikon doesn’t allow changing the IP address of its ad hoc wireless network so my suggestion would be to change the subnet of your router to another local address, such as 192.168.2.1. This will allow you to use your home network/internet at the same time you use the camera. I’ll add this info to the user guide to help others.

    Regarding the program files directory, I covered this in the user guide and video. The Program Files directories (both 32-bit and 64-bit versions) are protected when running without admin privilege – any wires get redirected to the Windows Virtual Store, which is a shadow copy of the Program Files directory. That shadow copy is accessible but it’s generally better to just specify an alternate, real directory that’s writable, which you’ve done. For the next release I’ll probably modify the app to not default to the Program Directory on the Windows executable the first time the app runs.

    Regarding automatically pulling down new files, it’s a feature I considered in 1.00 but decided to defer to a future rev. The ideal way to implement this is to monitor event messages from the camera on the event socket and trigger a download when a new-object event is received. This would require Airnef continuously running in an event loop mode, which again is considered for a future rev. For now one hack might be to continuously run Airnef from a batch file/script, probably best with a delay between each invocation. Even with a delay however the extra WiFi activity will likely run the battery down faster plus warm the camera up a bit.

    I had an option in place to automatically delete each file on the camera as they’re downloaded but intentionally left it out for data protection reasons. I didn’t want a Rev 1 product to do file-destructive camera operations. It’s yet another feature I’d consider for a future rev. Btw the MTP command to delete a file is MTP_OP_DeleteObject.

    Hope this helps!

Viewing 5 posts - 61 through 65 (of 65 total)