I've just uploaded a newer version, so download from the same link. This version is more configurable, so can change the raspberry pi's hostname/ip address and port etc.

Let me know how it goes and see what changes you think it may need.

SimpleScratch wrote:

Re pin numbering
I use physical pin numbering in my Scratch 1.4 stuff so that's what I prefer.

Easy edit, just change the Scratch names in the s2e file, so you can rename GPIOx to Piny etc.
Let me know how it goes. Just seen the Camjam on the raspberrypi website which looks handy. May have to order one!

I must apologise for not testing this yet but real life getting in the way!

I'm off to cinema with daughter adn then there is Brazil vs Germany later!!

Simon

SimpleScratch wrote:

I must apologise for not testing this yet but real life getting in the way!

I'm off to cinema with daughter adn then there is Brazil vs Germany later!!

Simon

That's ok. I've ordered a camjam so will be able to test properly in a few days myself I hope!

Love this idea.

when green flag clicked
say [Felix was here] for (2) secs

Well got everything plugged in but not quite there on getting pins to actually change state

Turns out that Webiopi is using broadcom pin numbering go for instance to change physical pin 7 from in to out I used
Set GPIO 4 function out

and that worked fine

But I'm at a loss as to how to make the pin change state as the parameter box seems to be the wrong type

regards

Simon

It's a pointy box so takes a Boolean. To make it go high use

<[1] = [1]>

and for false

<[1] = [0]>

or maybe use

<key [space v] pressed?>

I did try that but I it doesn't change the pin state on my setup

Simon

I've gone backwards now - I can't change the pin from input to output anymore
Off to sleep now - will try again tomorrow

That's annoying. I suppose first thing to try is use the browser and ensure that webiopi can change the pin states itself. if you run webiopi with the -d command then it goes into debug mode and you can it's messages. Annoyance with that is that Scratch's polling 30 times a second means that you just get screenfulls of GET/* messages. I'll probably have to add some instrumentation into the extension.

mm - tried rebooting my this morning and its not working now so maybe I have other issues

One thing I did notice once but didn't investigate was that if I had the extension running to the Pi and then used the browser to access WebIOPi then the connection from the extension to the Pi was dropped. In other words use them sequentially and not in parallel. If youuse webiopi in debug mode then you'll know the extension is connected and Scratch is connected to the extension because of the continual polling and so constant stream of debug messages.

Ta - I was using them in paralell - I've had to remake a new SD card as the old one decided that yesterday was a good day to die

Simon

Ok back up but no luck at all this time

Would it possible to have some debug output from your .exe file to see what its receiving from Scratch 2 and then sending off to the Pi?

Maybe webiopi needs 1/0 values and not true/false?

Simon

Had an email that the camjam has shipped so hopefully get that by the weekend. The extension should convert the true/false to 1/0 or whatever is necessary. I'll add some debug statements in.

Only build and uploaded didn't test. But if you download from the same link if the extension is run with a -d command line parameter (now where did I get that idea from ;-) it will enter a debug mode and print message to the console. It doesn't print poll messages as that would just get in the way. Hopefully that will help?

Debug mode on
Connecting to Raspberry pi at raspberrypi:8000
Listening on port 8080
Press return to exit.
Scratch Request : /setGPIOFn/4/OUT
Scratch Request : /setGPIO/4/true

So the requests are being made to your help app but nothing going onwards to the Pi (or at least no debug info)

Simon

Getting somewhere - restarted things and made sure green circle was lit on the extension in Scratch

Listening on port 8080
Press return to exit.
Scratch Request : /setGPIOFn/4/OUT
POSTing WebIOPi : /GPIO/23/function/OUT
WebIOPi response : OUT
Scratch Request : /setGPIO/4/true
POSTing WebIOPi : /GPIO/23/value/1
WebIOPi response : 1

So it looks like the wring GPIO number is being sent to the Pi

I put a LED on GPIO 23 (physical pin 16) - and it switches off and on at my command

Simon

Good news!
The conversion I do from RaspberryPi GPIO number to BCM GPIO numbering is;

Think they are the correct mappings. See this https://projects.drogon.net/raspberry-pi/wiringpi/pins/ for mapping to physical pin outs too.