The post is required, and must contain letters.
The BBC has admitted that the Micro:bit, the computer it plans to give to up to one million children, is not going to arrive on time due to quality problems. The Micro:bit was announced in March as a "get kids coding" initiative. Delivery was anticipated to occur in September, so that every 11 or 12 year-old in the UK could be …
Going by the pictures in the article, seems that the power gets on the board via the edge connector or a big through-plated hole? (or the battery connector I suppose)
Which would require the kids to get hold of a bench power supply or adapt a charger etc with all the risk of getting that wrong.
So would the change be the addition of a micro-usb port so the thing could be powered by a phone charger / PC USB port and USB cable?
Seems a stinking big oversight it that's the case.
"[...] with a note about not using glue for assembly?"
A 1961 transistor radio kit solved that problem by having no circuit board. The components' wires had to be joined together with supplied 8BA nuts and bolts. The only soldering iron in most houses was a large copper bit on an iron rod with a wooden handle - which was heated in the coal fire or on the gas stove,
A sizeable proportion of kids will already have tablets, and these are perfectly powerful enough for coding.
jruby, for instance, runs on Android ("Ruboto")
Or given that one of these boards probably needs a PC to act as its mothership, you might as well program on the PC itself.
> So how do you add leds, motors, buzzers etc to a tablet? Without that ability coding on a tablet is an awful experience for kids.
By plugging an Arduino* to the USB or Bluetooth and using QPython + Firmata. This caters for driving leds, motors, and reading sensors (including analogue) directly from the Python code running on the tablet (or phone or PC or Pi)
* Arduino Nano are about $US5 on eBay.
Why do you need LED's when you have a screen? Why do you need buzzers when you have a speaker?
Honestly, the BBC Micro was a great idea because at the time there were close to zero available compute devices in schools and it opened up computing to a generation. These days we are inundated with compute devices .. phones, laptops, tablets, desktops, watches ... there is NO SHORTAGE of hardware ... in fact, we have too much.
Prediction: 70% of these devices will never be even powered up and will be thrown across the playground as some sort of high-tech skipping stone. another 20% will be powered up but junked once they reallise they wont run xbox games .. a few will get a basic bit of code written .. and less than 1% will end up actually used.
I am sure there is a good reason to not use a Pi and take advantage of all the work done on it. I'd like to hear it though.
BBC now employs people more likely to understand phrases such as "BBC Micro brand awareness" and "stay relevant at all costs" than, say, "circuit board" or "variable".
As a huge Pi fan who will defend it to the death against all comers ... the micro:bit will be better for younger kids as it is easier to get up and running. Crocodile clips and banana plugs are a lot easier to deal with than 2.54mm headers, easier to run off batteries etc
I see the micro:bit as something you use for a year or two before moving onto the Pi.
£5 board design for case-less operation versus £25 board + case + microSD + all the other stuff.
One is affordable for the scale of deployment envisioned, the other isn't.
This is assuming that the school already has a suitable computer room of course. This is just an IoT thing - use a computer to program a Thing to control something physical.
This delay/SNAFU is particularly dissapointing given that the device that was very close to the original design, the Codebug ( www.codebug.co.uk ), blew past its Kickstarter in April, shipped in July and I have three of them, all fully working, all using the same Scratch-like web-to-USB-download IDE, and being used this week by my three children. In stock now at Farnell for twelve quid fiddypee.
Well, I *think* I have three of them. My kids love them so much they kind of grabbed them and they disappeared. One was definitely running some LEDs for a Lego model at the weekend. Two were last seen pinned to clothing for the twins' birthday as fancy age badges. I'll report back when the inevitable washing machine API occurs.
Why on earth the BBC decided to go with the Micro Bit instead of the Micro Bug, I just don't know. Adding the sensors, removing the onboard CR2032 battery and adding Bluetooth (well known to be the curse of death for many projects) very late in the day seems to have fouled things up. Perhaps the coding lesson that Auntie Beeb are trying to teach our children is the old Unix addage "do only one thing and do it well". If so, they've spectacularly succeeded in providing a mistake to learn from.
Yes, they might have smaller siblings, so the kit should be delayed while a rasp and sandpaper are included so all the sharp edges in the world can be filed off before use. Oh, and we need to cut all the trees down because one of the little nippers might try to climb one. Oh, but then you have to use a chain saw! And the environmentalists!!! <initiate hand wringing session><infinite loop>
Sorry, kids, this will never be delivered....you might hurt yourselves.
Yes, this whole thing seems to be another BBC not-invented-here or 'we've got tons of public money'. I would have preferred to see them get behind the Pi, OK it's harder, but less fragmentation in the knowledge and teaching.
That said, I took a Pi into my Code Club, they'd never seen one and they were able to use [use being play Minecraft, mainly] in about 30 seconds. Digital natives are actually a breed.
The BBCs digital initiative of stuff has been a bit crap. First this delay, and then their awful "Gamechangers" film. The only "game changing" thing about that was that it was a clear statement of how to make a shit film. So perhaps it was educational in that aspect.
I have enjoyed watching the cache of 1980s Micro live programmes trawled up from the archives on iPlayer though.
Gamechangers was also an expletive-laiden post-watershed drama that no children would be allowed to watch, about a game that had a mature rating that no children had been allowed to buy, with a plotline that focussed on hidden pornography.
Quite how that managed to get related to the "teach kids to code week", I just can't imagine. I mean, Daniel Radcliffe must have cost a lot of money, the programme must have been comissioned by some fairly senior management staff at the BBC, can they really be that out-of-touch that they don't understand watersheds and age ratings?
Having said all that, it was good... for a TV movie. Worth a watch, especially as it's free on iPlayer. *If* you're old enough.
I enjoyed it. But I agree. When GTA was first mentioned as part of the make it digital campaign I couldn't imagine how it was going to be related to teaching kids to code. I was right.
GTA is one of the best games I've ever played. Completely insane to use it as part of the campaign.
I think Andrew's answer says it all - they're small enough to sew onto clothing, bluetak onto lego, glue to stuff, etc, which makes them a lot more appealing as they then become a project about coding for something you already own. Much as I love the Pi, I suspect the vast bulk of users are of the age that grew up with BBC micros, or even Sinclair calculators. Or in my case log tables and slide rules. And the Pi is more for new projects, rather than adding functionality to something you already use.
I do think that adding Bluetooth to the device is a valid reason for not going with the Codebug, as it ticks the other box of letting kids connect it to their phones.
It's a shame about the power supply delay, but they're not the first to hit that problem. I've seen too many other product launches hit the same problem. The part everyone thinks is easy turns out not to be. Although numerous shocks with stuff I built as a kid never seemed to do me much harm. It did teach me that not insulating mains terminals is a bad idea.
To turn a Pi into a Micro:Bit you need to add LEDs, buttons, Bluetooth, compass and accelerometer.
To do that you need a HAT or other add-on board. And that's really what the Micro:Bit is but self-contained, platform ambivalent, and it doesn't have the BBC supporting only a specific commercial venture which is what the Pi actually is no matter that the Foundations has charitable goals.
One could equally argue "why not an Arduino shield?". Arduino base units are far cheaper than a PI.
With regard to the comment about the Pi being a specifically commercial venture.
This is not the case. The Raspberry Pi foundation is a charity, which fully owns the Raspberry Pi trading subsidiary which does the tech development. All profits go to the charity. The charity itself spends a HUGE amount of money of educational outreach, as it's says in it charity statement.They also fund development of relevant open source software (e.g. Scratch, Sonic Pi etc). In fact the charity is overwhelmed by demand for educational help and is expanding all the time to try and meet that demand. As an example of outreach, they fund a completely free training course for teachers, held once a month, which almost everyone who has been on it says is the best teacher training they have EVER been on.
So before making 'accusations', please look at the facts.
I read an an interview with the guy who dreamed this up and he said they looked at other devices and he said to himself "I could do this" (tellingly AFTER the Raspberry PI foundation had been to see the BEEB to see about resurrecting the BBC Micro ), so effectively a nice project for him to fiddle with using license fee money, could easily have just done something around the Pi, Beaglebone or Arduino especially some of the wearable Arduinos which work out very cheap.
Also I think there's a limited expectations thing going on here saying other platforms are "too complicated" so ohh look shiny LED's but we don't want to scare you with anything like a realistic device that has the flexibility to grow with your experience.
> he said to himself "I could do this"
Interestingly, this line of thought is why we have the ARM processor today:
Acorn people went to Western Design Centre to talk about licensing their advanced 6502 compatible processors, realised the company was a couple of people doing the designs themselves in a garage, went away and did the same thing themselves from scratch.
Biting the hand that feeds IT © 1998–2019