Embedded and IoT

Self-check

Your score stays on your own device.

1. You have a party build a sensor for your silo. What do you ask about the readings?

   • That only the maker can view them
   • A subscription to view your own data
   • That they land on a server you own
   • That they stay on the device itself

2. A new firmware version will not boot on a device in the field. What should happen?

   • Someone drives over with a laptop
   • The device stays off until the next update
   • The customer resets it by hand
   • It falls back to the previous version

3. How do you bring in a new PLC programme without the factory standing still?

   • Program it live on the running line
   • Test it on a test set-up first
   • Let the operators try it out
   • Replace all machines at once

4. Your old machine has no connection at all. How do you still get data out of it?

   • Add sensors, such as a current meter
   • Have the operator count by hand
   • Open it up and rewire the inside
   • It cannot: without a connection, no data

5. A colleague says: 'Our cobot stands in the corner, so robots do not work for us.' What is true?

   • True: a cobot is a gadget for trade fairs
   • Not true: it only needs a new gripper
   • Not true: it lacks links to the line
   • True, unless you buy a bigger robot

6. A limit in your test system turns out too strict. Who adjusts it?

   • Nobody: once set, limits are fixed for good
   • Only the builder, for a fee
   • The lab that does the inspection
   • Your own people, in readable software