AD – "I don't think anyone knew how precarious the situation was for the first few days"
At one point in my career, I worked with a former US Air force pilot whom had flown C-141 transports to Israel during that war. He described having to fly a very narrow corridor through the Mediterranean to avoid the airspace of the various countries that didn't want to get involved, or didn't want to let any help in. There was one area that was served by (then) Soviet air traffic control. He said it was quite uncomfortable to be relying on them, when flying in opposition to their allies, and while the possibility of nuclear war was being tossed about.
I was 16 when the Yom Kippur War took place -- my best friend at that time was Jeremy Goodman who lived about six houses down the road / around the corner from us. Jeremy and I were the only two boys in our area (apart from Robert across the road who was a bit older than us and he was a slimy toady of no account) and we grew up together from when we were little kids (we're still in touch).
I remember when the War started and my mom sent me round with something she'd baked to give to Mr & Mrs Goodman, just to let them know we were thinking about them. And I remember how happy we all were when the war ended. I don't think I fully appreciated the magnitude of what was happening at the time.
I remember Intel used an off-sheet convention on its SBC (Multibus) schematics. Unfortunately, this no longer seems to be practiced, and I know of no current CAD system that provides this option.
Altium treats each sheet of a schematic as an individual sheet which must be added individually to a project. In my opinion this is an archaic approach since items of commonality like the title are not flowed through, bu must be added on each sheet. The interconnection is handled through an hierarchical inteconnection diagram which actually does define which sheet to access.
But for me it is no panacea. I still work with paper and so this is just another piece of paper and an added intermediate step. Nor does it indicate where on the sheet I should look for the net. I suppose we could institute a standard bringing all off-sheet nets to an edge.
I pretty much made the same transition through the years as far as schematic tools go. No we don't have any written standards for schematics (yet), but we also find we need to make many of our own symbols. I keep trying symbols offered by companies like TI, Microchip, Analog Devices, ect, but either they are not segmented logically (from my perspective) or they don't look good (text in weird places ect or overlapping lines). When we create symbols, we try to share within our small design group (3 engineers).
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.