At least your projects make some progress. I have 2 or 3 that remain at the conceptual stage, continually being subverted by other projects like painting the garage doors. My wife insists that I get my Vitamin D quotient, so summer is a blowout even though the only cool place is the basement where coincidentally the projects are executed.
These are nice little displays and the data sheet is relativly understandable. They have a selectable interface with I2C, 9bit SPI, 8Bit SPI and parallel.
You usually search the web for the card that offers your comms flavour of the moment.
For me its easier to get them mounted on boards than solder the displays to your own PCB and this is where the problems begin. Not all boards are the same.
The first board I used is nice in that its mounting fabricator made their design toggle the reset line of the display on start up, so as a result, the reset default values get set up in the displays registers. This design is no longer available on the web.
Same display different mounting fabricator and a problem of garbled text and graphics has to be resolved.
Upshot is a complete rework to my software drver and a new software reset routine, that set all the display registers to the defaults that would be set if the hardware reset line had been toggled.
Time 20 hours, well at least my driver should work with most fabricators displays now?
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.