<<< Back to Slackey
NASCam is similar to the stock Android camera application, but instead of
storing the images on the SD card they are directly uploaded to your FTP or
HTTP web server. The name comes from the Network Accessible Storage devices,
which usually support FTP and would be able to be used as the storage for
You can use any server you have an account on that supports FTP
or installing a web CGI or other form processing code that supports file
uploads. Since the uploads go to your own server (for example, a home machine
on a DSL line, a Virtual Private or dedicated server at a hosting facility),
you have full control over what is done with the photograps you take.
If you have any questions or concerns about NASCam,
feel free to contact us at:
For access to this application, please search for
"nascam" on the Android Market -- available on your
NASCam Application QuickStart Guide
Here is a set of configuration and example screen shots for the Android NASCam application:
FTP Image Upload
FTP uploads are done to any normal FTP server you have write
permission to. Simply specify the server location, username and password.
Options are available to set it into "Passive" mode.
HTTP Image Upload
For the HTTP server uploads, you need a form on the server to receive
the image. The form handler CGI takes fields for user-name, password
and the image data. There is an example Python-based CGI available for
To use the example HTTP upload CGI:
Right-click on the following link and select "Save to disc":
You can now use those values to upload files to your server.
Python HTTP upload CGI
Modify the top of the file to specify the username/password and a
directory to save the uploaded files to.
Copy the saved file up to your web server.
Place it in your web server's CGI directory (often "/var/www/cgi-bin")
Make sure it is executable (On Unix systems:
"chmod 755 http-upload.cgi")
FTP/HTTP File Names*
*see update below
The file-names that the files can be uploaded to can include many
date/time based "macros" to make every file-name. The macros are a two
character combination starting with percent "%" and a character from the
following table. These format styles follow the POSIX standard fairly closely.
Note: These characters are case-sensitive.
|%a||Abbreviated week-day name.||Mon|
|%A||Full week-day name.||Monday|
|%b||Abbreviated month name.||Jan|
|%B||Full month name.||January|
|%d||Day of month.||01|
|%M||Minute within hour.||59|
|%S||Seconds within minute.||59|
|%Y||Four digit year.||2009|
|%%||The literal percent character.||%|
Update — Please Note:
File names with special characters like colons, slashes, etc. may cause errors.
Depending on the "Locale" setting on your phone, this may or may not be a problem for you
since different regions use different characters as date and time separators.
In any case, if you are using the Time or Date macros "%T" "%D" in the FTP/HTTP File Name
format string, we advise you to change to the alternatives in the tables below.
You can still include the whole time and date as part of the file name by replacing "%T" and
"%D" with strings that don't contain problem characters, like: "%H.%M.%S" and "%Y-%m-%d".
|Avoid Macro||Meaning||Possibly Yields||Use Instead||OK|
|%D||Full date string ||2009/01/23||%Y-%m-%d||2009-01-23|
|%T||Full time string ||23:59:45||%H.%M.%S||23.59.45|
Frequently Asked Questions
- Q: What is wrong? Pictures will not upload to my server, and I am sure all
the server parameters are correct.
- A: You may have a filename format problem. Please see the note above regarding
Time and Date macros.
Thank you for the suggestions.