Hmm. Two things come to mind;dlivingstone wrote:Great news.
I was trying out the gpioserver examples - working well, but a little quirk in my own simple LED test program that a broadcast to switch off a LED doesnt always seem to have an effect - perhaps when the delay after switching the LED on is quite small?
It had better not be. Post your .scratch.ini file as well if possible. Oh, and if you can cause the problem deliberately, check your directory for a SqueakDebug.log file and include that is you can find it. Often provides some extra clues.dlivingstone wrote:More notably, the scratch.ini setting suggested on the Scratch gpio documentation page doesn't seem to work - simply results in Scratch reporting an error at start up. Is this a common error??.
Yes please - just in case there is a hidden character or something weird. Always best to test with there closest possible situation.dlivingstone wrote:Hi Tim,
will grab the screens and upload when I can
There was no .scratch.ini file in my home folder initially, so I created a new one containing only the single line to set the gpioserver on - happy to send the script though.
I really hope not. But I can test on B/+/2/A+ here to make sure.dlivingstone wrote:As a 'for info', I was running this on a revision 1 (or was it 1.1? Again I can check tonight!) model B - don't know if that makes a difference?
Yup, that should work just fine . A 1 second delay with the led on ought to be visible.dlivingstone wrote: ... the very simple script in in the image below:
I'm completely unable to replicate this so far. My .scratch.ini (has to be in the /home/pi directory remember - I didn't the first time!) isdlivingstone wrote:The other attached image shows the error message I get when setting up the .scratch.ini file. I'll have to set up the pi again to get the actual ini file, as I forgot to copy it off... doh!
D'oh! I didn't test what happened with multiple blank lines; it works for a single blank line...dlivingstone wrote:The comment about whitespaces after the line helped... I had two CRs.
Removed those and the error disappeared.
All working now...
Fixed for the next releasetimrowledge wrote: D'oh! I didn't test what happened with multiple blank lines; it works for a single blank line...
Currently it seems this got messed up in the last stages of the release and the alsa config stuff has moved from /etc/modprobe.d to somewhere not yet known by me. More details later.timrowledge wrote:I forgot to point to the script to install the MIDI general instrument support - I'll get it on the main Doc section eventually but for now you can use - (and since a .sh file is not allowed on the forum you'll have to unzip it)
Sadly not. Well, not that does anyone any good; the issue is the way wiringPi does timing.. .or something like that. The best I've been able to get so far is very unstable results with a plausible precision of about 4ft. Not terribly useful!Forris wrote:Have you had any luck with adding support for the HR-04 ultrasonic sensor yet, please?