Improving Scratch -RaspberryPi GPIO Control Performance

The light at the end of the tunnel is getting a bit brighter šŸ™‚

The reason my current doesn’t handle sequential variable changes is that Scratch codes them up differently (for efficiency) and that I need to use something like thisĀ

to handle them.

Also, the CPU time used by Scratch seems to increase whenever you create more variables. Ā I’m assuming this is because it starts checking for changes in variables when RSC is enabled. Ā This increase in CPU load doesn’t seem to take place if using broadcasts so I’m going to change my python code to try andĀ incorporateĀ these two things and lets see if we can improve performance šŸ™‚

Backup your Pi

Every now and then and especially once you’ve made a very useful change to your RPi (got your wifi USB adaptor working or made it autostart into LXDE etc) then I recommend creating a backup image of your whole SD card.

On windows, the easiest way is to connect your card to your PC and use Win32 Disk Imager in read mode.
e.g Insert SD card into your computer/Card Adaptor and run Win32 Disk Imager, click on browse icon and create a new file somewhere to save your image – then click Read and the program will do the rest. šŸ™‚