RaSPy - the story continues

Thanks go to my fellow MDPer and blogger Brian Davis for taking my program and improving it using a multi-state SWITCH block (wish I had thought of it first). And he implemented the LOOP block for the initial 1...2...3...

Brian, nice clean program... great work. - Jim


Anonymous said…
I see concurrent processing!

Within the lefthand loop, how do you make A/B/C motors all 'do their thing' at the same time?

Wow, you guys have been busy, this is great stuff! I love what kids come up with when it comes to 'how to use the technology'.
What I've enjoyed about the project is watching how improvements have been made very quickly.

The early version (both hardware and software) was thrown together quickly... with no real design plan... just make it work.

Brian streamlined the software and I was able to look at the original hardware and see where it needed improvement (practically everwhere!).

Wouldn't you love to see what the original AlphaRex looked like?
Anonymous said…
hi Jim!
Yes, i would like to see how the original AlphaRex looked like if you can get a video or pictures of it!
Thanks for a great blog!!

Brian Davis said…
As to "concurrent" or parallel processing, all I did was drop some blocks off below the main sequence beam (the white LEGO beam holding all the programming blocks together). You can then "wire" a new sequence beam off of the main one to your "orphaned" block, and that's it! The new parallel sequence beam acts as an independant string of commands (very similar to a task, for those of you who prefer that term).

Brian Davis
Anonymous said…
Awesome Brian, that's about what I was hoping for.

So, how many 'concurrent tasks' can you run... umm... concurrently? RCX had a hard limit of 10 separate processing paths, wondering how limited this environment is.

Popular Posts