I think you've misinterpreted my post - I'm suggesting using same method of using normal Scratch going through a Python handler that talks to the serial using the reverse engineered protocol - not trying to use the GPIOYou could (possibly?) modify the board in theory to talk via GPIO, but that would be much more effort (for no good reason other than perhaps freeing a USB port - even then you can just use a hub) than just using it over USB.
I did the TU100 last year in England for £770. It was the last year before the rates were jacked up to £2500 (thank you Mr Cameron). There is absolutely no way I would/could have done it at the current price and feel lucky to have got into university studying at the old rate by the skin of my teeth. I wonder how many others out there now feel priced out of studying, settling instead for a life of unskilled work...That TU100 digital life course is £2500 in Enland
The software may be - I honestly haven't tested it thoroughly, I spent the vast majority of the time looking at the source code! On the hardware side however, using the protocol document and sending raw bytes it appeared pretty stable to me - the only bug I found was to do with the stepper motor moving more than 128 steps, but there are workarounds to this (you have to group the steps in multiples of 128 and send them a couple of seconds apart until you're done.) That's a relatively easy workaround to produce in a library by doing some concurrent stuff in the background that the user doesn't need to know about.mawds wrote:hi
sense is bug ridden and they know it, lecturers also know it yet they will still take your money. Stay clear of sense if you have any.
Users browsing this forum: No registered users and 9 guests