Sorry to hear about the issues you are having!
The ImportError is usually caused by trying to import the wrong version of the Python library.
RoboPi-Libs-and-Demos.zip has "RoboPy2.7" and "RoboPy3.2" versions of the libraries included.
If you are running IDLE3, you need the RoboPy3.2 libraries to run the demos.
I'd suggest you copy the files appropriate version into the Python_Demos directory.
The Python code hanging is usually caused by one of:
1) /dev/ttyAMA0 is still being used for a serial console
As you have followed the instructions on p.9 this is likely not the cause
2) firmware is not loaded into RoboPi
I am quite sure that I loaded the firmware and tested the board before I sent the board to Tim
3) wrong version of firmware present in RoboPi
This is quite possible, as I sent the board to Tim quite some time ago
I will be adding a "How to load the RoboPi firmware onto RoboPi" section to the manual, until then, here is how you should be able to load it:
1) download the latest released EEPROM image from
http://www.mikronauts.com/wp-content/up ... _v0.81.zipunzip it into a "firmware" directory
2) download the propeller loader used to program RoboPi
http://www.mikronauts.com/wp-content/up ... -rpi-3.ziprename "RoboPi v0.81.eeprom" to RoboPi.eeprom using the file manager
unzip it into the firmware, and make sure it is an executable ("chmod +x propeller_load" if necessary)
3) To program the firmware into RoboPi:
sudo ./propeller-load -e RoboPi.eeprom -r
If that does not work, then I have uploaded a newer propeller load to my site, for which the command is
sudo ./propeller-load -p /dev/ttyAMA0 -Dreset=gpio,17,0 -r RoboPi.eeprom
Let me know how it goes...
Best Regards,
Bill