Could even make a "software only" kitchen project. OK, you would need a bar code scanner or something.
You could input all the ingredients in your cupboard, along with all the spices, and stuff in the fridge. Then perform a lookup for a recipe that uses what you have, or provide you with a shopping list if you have a hankerin' for something in particular, like beef wellington, or souke goulash.
Also it could be used to provide hints when items in the back have passed their expiration date (about two years ago), particularly valuable with respect to spices.
Yes, I understand the differences in platforms. Sort of what I was going for for the problem. The problem I posed, was not a develop from scratch, then port, but a develop from scratch, or port. With the stipulation of, while developing from scratch, being mindful of issues that are specific to a platform and making provision for portability.
Arduino boards could have been too broad a group, because some of the higher end boards approach desktop capabilities. I was referring to boards like UNO or Nano or 2560, that are great for controlling stuff, but require more effort for stand alone UI.
They can be tested by having them run stand alone on Arduino, BBC, and Raspberry. Possibly switching up languages as well, porting the portable C program to Python/Tcl.
You do realize that this is a monthly contest, right? I believe the one possibility could be MicroPython. The Arduino board would have to be an ARM based board such as a Due or SAMD21 for that kind of support tough. A "C", or other language, option would take quite the undertaking to port across these platforms considering the processor and pinouts are much different. However, in my mind, something like an Arduino board (depending on your definition of Arduino), BBC (I'm assuming you are referring to a Micro:Bit) and a Raspberry Pi are different classes of dev boards considering the RasPi runs a Linux OS as do some of the Arduino boards and development on these are not the same.
Thank you for your support, and sorry for getting off topic.
I would like to see a project that is focused on software as well. Bells and whistles are hardware, as well as shiny objects, but my point from before, their focus can be a distraction at times. How about applications that are built for portability. They can be tested by having them run stand alone on Arduino, BBC, and Raspberry. Possibly switching up languages as well, porting the portable C program to Python/Tcl.
I am enjoying the interchange of ideas here. I do have a small issue with using excrement as a unit of measure when talking about some devices, though. I think what needs to be understood is, many times the complaint isn't with the hardware (DDS), but usually with the implementation software (embedded). I have implemented a four cylinder engine controller on an Arduino-Nano. However, I ran into significant limitations and timing problems when I used the installed (Arduino) package. The hardware (328p and USB) was what I was interested in using, so I compiled and loaded my own interrupt handlers and communication software, blowing away what was in there from the factory. I thought at some point, I would go back to if I could work around the problems I had with the installed loader, but haven't gotten to it yet.
The point I am trying to make is my issue with many electrical engineers in general, their training in the area of software development is sorely lacking. What I find is the words "never" and "always" get used when explaining conditions encountered with certain hardware platforms, when in fact, a person with a strong background in software can see a less common route to the solution. This also highlights an issue I have during part selection in initial development. The rating system used by an electrical engineer is based on available registers, clock speed, and assembly level instruction set. What I point out is, "when was the last time you programmed a project all in assembler?". The compiler, for whatever language you are using should be the determining factor. Does it take advantage of all the resources and instructions, and how good is it at optimization. Sadly, during development of hardware platforms, the question of how good the compiler is, is not considered.
I remain almost of the idea that focusing the attention for a monthly competition on schooling projects will open a lot of possibilities not on the Arduino only. If this will become one of the next I think it is the worth pushing on the BBC:micro possibilities. Hardware connection but not only, also good software interfacing from low and easy programming based on the native programming tool up to the integration with other devices and more.
Agree.. I suspect some people assume such devices are not functioning correctly. I've played with the so-called c*** DDS $15 sig-gen modules from ebay and their performance on several important parameters (within a realistic frequency range) is not far removed (actually way better for some parameters) from some HP sig-gen's from the 1980-1990's which are still sold on ebay for $500+..
They are missing features of course (like decent adjustable output) but to call them junk is not accurate.
Top Comments