Skip to main content

quick recollection on setting things up

  • If I can swear that the password is correct, then it's possible that I'm getting the ID wrong.

    Hadn't logged into the web server in a couple of months and was unable to SSH into it. After an hour or so, I ended up deleting the instance and recreating a clean instance (read: erasing everything).
    I then realized I'd been putting the wrong ID.
     
  • apt-get install
  • sudo apt-get install

Anyways, some links I visited when setting things up (pretty much a dump of whatever I copy-pasted to notes) :

Raspberry Pi
http://www.makeuseof.com/tag/optimize-the-power-of-your-raspberry-pi-with-raspbian/


Logging
http://docs.python.org/2/howto/logging-cookbook.html


Tornado - Python webserver that supports Websocket
http://stackoverflow.com/questions/2924991/what-popular-webservers-have-support-for-html5-websocket
http://lowpowerlab.com/blog/2013/01/17/raspberrypi-websockets-with-python-tornado/
http://stackoverflow.com/questions/11695375/tornado-identify-track-connections-of-websockets

Installing Python in Ubuntu
http://eli.thegreenplace.net/2011/10/10/installing-python-2-7-on-ubuntu/


Physical computing with Raspberry Pi
http://www.cl.cam.ac.uk/projects/raspberrypi/tutorials/robot/buttons_and_switches/


Comments

Popular posts from this blog

websockets and mobile networks and ssl

Gahhh. Just going to ramble on this one: Websockets is unstable going through cellular networks Searched Google and solution seems to be SSL connections Tried to implement, and it works to some extent,  but realized that I'll have to have both Apache, which was running my web front end, and Tornado both listen to 443 which cannot happen Realize finally that Tornado is a SERVER just like Apache Try to implement web client through Tornado It works but Websocket server and the web client still different instances so still can't have both listen, or that's what I'm thinking but I don't have time to think about it at present. Gotta sleep.

setting up pwm

There's always an obstacle.. I implemented the pwm module as described in the link in the previous post, but oddly enough, it didn't work. The error I received: AttributeError: 'module' object has no attribute 'PWM' After some time scratching my head, I came to the realization that somehow my python was running an older version of the RPi.GPIO library, as PWM control was a pretty recent addition to the library.  And indeed it was.  Not really sure what's happening in detail, but it seems that there are two different... entities? that manage libraries for Python. One is through the usual "apt-get" command and the other is "pip." It appears that Python looks at "pip" first, and it currently linked RPi.GPIO to a really old version of the library.  Uninstalling that older version ("pip uninstall RPi.GPIO") and using the version I obtained through apt-get ("apt-get install python-rpi.gpio...

pwm..

I just realized that the RPi.GPIO library (for programming the Raspberry Pi's input/output) already has PWM control, giving me a much more efficient control of duty cycles... At least the previous exercise ("duty cycle testing") refreshed me on it. PWM control on RPi.GPIO: http://code.google.com/p/raspberry-gpio-python/wiki/PWM