Looks like I am always tail end Charlie. However I have to work with what I have here so at least It should be compatible with what we have in England. Looks Like a good article of yours, so will read up on it tonight.
There are some more blogs to come, of which one will be my attempt at making a home brew PCB reflow oven. Just waiting for the K type thermocouple chips to come through the post and I can then get leathal with 230VAC mains and PIC and Atmel chips.
Likewise if you are in my area drop in and we can get some real ale at the local pub.
I started out with PIC uCs back in 1995 or so, and my tool was DOS-based. I actually hung on to that system (running on an old 386DX40 system) until about 5 years ago when I finally switched over to a newer programmer... Which is now hooked up to my system through a USB-Serial converter... Progress marches on and leaves us luddites behind, I guess. D'oh.
In that vein, though, I just found the following amazing little thing from Newark/Element14 : Freescale evel/de kits! For $12.95 ea, I bought 2 - one for work and one for home. Something else to learn, I guess - one more tool in the box.
Along those same lines, I have a friend who's been out of the engineering world for a while (he is currently a tech writer and is miserable). He bought an Arduino UNO to try and learn some stuff. As always, it's hard to learn if you don't have a project to directly apply learnings, so I've been teaching a 1-on1 microcontroller class... And filming it - not because I think I'm awesome (which you surely know by now I'm just a doddering old fool), but I figure there's a bunch of people out there who could use that kind of thing... We get a new "lesson" done about once every 2 weeks or so, and I assign homeworks & discuss the last lesson, etc.
Keep up the good work, and if you're ever in the area, give me a ring & we'll go out for dinner and a brew.
Hmmm, there are various levels of compatibility. Remember the Arduino project adopting the Wiring language as its programming language; Wiring has been ported to a variety of other chips (including TI MSP430 and Tiva, with the Energia IDE, the Digilent chipKit (PIC32) which Max wrote about, the NavSpark (LEON SPARC processor), and the Intel Galileo (x86)).
Some of these use the Arduino IDE. However, low level Atmel code can't be ported (and some vendors like to use low level code).
Also, Arduino shield connectors are everywhere. For example, ST's Nucleo boards combine a STM32, mbed enviornment, and Arduino shield connectors, for <$11 (including the very powerful STM32F401 model).
@alex_m1: Thanks for both the posts. It's good to know that someone is reading the blog and considers it worth a reply.
I hope that people will post ineresting things about how they got started and where they are going to.
I am looking forward to my LPLC - Low Power, Low Cost PIC18 Development Board by Mike Hibbett, that I get as a reward from backing this on Kickstarter. I should at last get an insight into using these chips and their diffrent architecture, as he is providing a beginners instruction class on how to use it.
The fact that this project past it's funding goals, by a lot, shows there is a need for other vehicles for micro experimentation.
One response to the arduino was the mbed. It's not as simple as the arduino , but it's relatively simple, and is supported by a growing variety of microcontrollers.
And regarding simplicity and FPGA's: Multi core mcu's offer an interesting alternative to some fpga applications with a simper programming model. Another alternative is c-to-gates tools offered by altera and xilinx.
Another benefit is that the community is guided towards simplicity, so you get easy to use libraries and support .
One of the best example of this is they encourage people not to use pointers(especially in library interfaces) , since pointers are really hard for beginners to grasp. They recommend instead to use references and even standard data structures, like std:vector etc which can fit embedded hardware using the uSTL library.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.