![\"Raspberry](\"http:\/\/projectbee.org\/blog\/wp-content\/uploads\/2013\/03\/RPi-iTek-1024x678.jpg\" "\\"Raspberry")
Set Up<\/h1>\n\n- Raspberry Pi Model B (512 MB RAM), running latest updated Raspbian Wheezy build (with no additional background services running) on an 8 GB class 4 SD card<\/li>\n
- itek power bank (5600mAh)<\/li>\n
- Internet connectivity through Ethernet<\/li>\n<\/ol>\n
I wrote a shell script to call a web based PHP script on my server. I set a cron to run this shell script every minute. What happens is the shell scripts passes the client side timestamp, and server writes it, along with sever side timestamp to a file.
\nThe source code of both scripts is provided below.<\/p>\n
#!\/bin\/bash\r\n\r\nrawurlencode() {\r\nlocal string=\"${1}\"\r\nlocal strlen=${#string}\r\nlocal encoded=\"\"\r\nfor (( pos=0 ; pos<strlen ; pos++ )); do\r\n c=${string:$pos:1}\r\n case \"$c\" in\r\n [-_.~a-zA-Z0-9] ) o=\"${c}\" ;; * ) printf -v o '%%%02x' \"'$c\"\r\n esac\r\n encoded+=\"${o}\"\r\n done\r\n echo \"${encoded}\"\r\n}\r\n\r\nCLIENT_TIME=`date +\"%c\"`\r\nURL=http:\/\/example.com\/ServerSideLoggerPHPScript.php?t=$(rawurlencode \"$CLIENT_TIME\")\r\n\r\n\/usr\/bin\/wget -qO- $URL &> \/dev\/null<\/pre>\n<\/pre>\nConclusion<\/h1>\n\n- The script started at 4:45:12 AM<\/strong> client time and ended at 12:07:01 PM<\/strong> client time. That’s almost 7 hours 22 minutes<\/li>\n
- The reason to attach the device to Internet was because I don’t see the point of testing a bare naked Raspbery Pi. Most real life applications would require network connectivity<\/li>\n
- That brings me to another realization: I should have used my WiFi adapter instead of Ethernet to test real world situation. I plan to do this soon.<\/li>\n
- I was fortunate not to lose Internet connectivity, but I should have logged the timestamp locally as well<\/li>\n
- 7 hours is all hunky dory but itek is a fairly heavy device, and takes eon to recharge. I don’t see it a very likely companion to my Raspberry, if I intend to shoot them in air sometime.<\/li>\n<\/ul>\n
As mentioned, I’ll test the setup again with a WiFi adapter, and update the results.<\/p>\n","protected":false},"excerpt":{"rendered":"
Summary I tested a model B Raspberry Pi (512 MB) using an itek power bank (5600 mAh), with Internet enabled. It pinged my server every minute, and ran for about 7 hours 22 minutes. Set Up Raspberry Pi Model B (512 MB RAM), running latest updated Raspbian Wheezy build (with no additional background services running) … <\/p>\n
I wrote a shell script to call a web based PHP script on my server. I set a cron to run this shell script every minute. What happens is the shell scripts passes the client side timestamp, and server writes it, along with sever side timestamp to a file.
\nThe source code of both scripts is provided below.<\/p>\n
#!\/bin\/bash\r\n\r\nrawurlencode() {\r\nlocal string=\"${1}\"\r\nlocal strlen=${#string}\r\nlocal encoded=\"\"\r\nfor (( pos=0 ; pos<strlen ; pos++ )); do\r\n c=${string:$pos:1}\r\n case \"$c\" in\r\n [-_.~a-zA-Z0-9] ) o=\"${c}\" ;; * ) printf -v o '%%%02x' \"'$c\"\r\n esac\r\n encoded+=\"${o}\"\r\n done\r\n echo \"${encoded}\"\r\n}\r\n\r\nCLIENT_TIME=`date +\"%c\"`\r\nURL=http:\/\/example.com\/ServerSideLoggerPHPScript.php?t=$(rawurlencode \"$CLIENT_TIME\")\r\n\r\n\/usr\/bin\/wget -qO- $URL &> \/dev\/null<\/pre>\n<\/pre>\nConclusion<\/h1>\n\n- The script started at 4:45:12 AM<\/strong> client time and ended at 12:07:01 PM<\/strong> client time. That’s almost 7 hours 22 minutes<\/li>\n
- The reason to attach the device to Internet was because I don’t see the point of testing a bare naked Raspbery Pi. Most real life applications would require network connectivity<\/li>\n
- That brings me to another realization: I should have used my WiFi adapter instead of Ethernet to test real world situation. I plan to do this soon.<\/li>\n
- I was fortunate not to lose Internet connectivity, but I should have logged the timestamp locally as well<\/li>\n
- 7 hours is all hunky dory but itek is a fairly heavy device, and takes eon to recharge. I don’t see it a very likely companion to my Raspberry, if I intend to shoot them in air sometime.<\/li>\n<\/ul>\n
As mentioned, I’ll test the setup again with a WiFi adapter, and update the results.<\/p>\n","protected":false},"excerpt":{"rendered":"
Summary I tested a model B Raspberry Pi (512 MB) using an itek power bank (5600 mAh), with Internet enabled. It pinged my server every minute, and ran for about 7 hours 22 minutes. Set Up Raspberry Pi Model B (512 MB RAM), running latest updated Raspbian Wheezy build (with no additional background services running) … <\/p>\n