again, these are good points. Most oscilloscopes today allow you to store machijne setups. I save my popular ones and can then recall a particular setup rather than the default. This is also a great idea for demonstrations, where everything seems to go wrong. Having the stored setup is often a relief.
One of the First things I do when working with scopes is hit the Default Setup button. I have learned from my colleague test engineers spending hours tracking down problems that are due to scope setup rather than DUT output. ALWAYS run a Default Setup (and a front-end cal, if available).
We've all done it, so don't feel bad. With power comes complexity. Many of the newer scopes have customization capabilities, so you can save your frequenctly used setups. I do that also for demo's. If anything can go wrong, it will always occur at a live demo.
One of the lesser attributes of digital scopes vs analog is that there are numerous menus to wade through to see setups, whereas with analog scopes the entire setup is immediately visible by visually scanning the knobs and switches. Just today I was getting very strange results until I finally clued in that I had left one channel on AC coupled from yesterday, a mode I very seldom use. Yeah, I felt pretty darn silly for overlooking this basic setup.
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.