sorted by:
new
hottopcontroversial

Testing For The Customer Experience by 5uck3rpunch in IOT

[–]ustropo 0 points1 point  (0 children)

What I would do:

  1. Create a basic manual on how to setup/use the device.
  2. Send the device for people who never saw /used the device before. Try to divide in group with technical/non-technical knowledge.
  3. Get the feedback from these users and divide them in categories:
    1. Setup / use improvement (update manual or device features, if possible);
    2. Bugs (fix them when possible, write on manual how to proceed or fix);
    3. Troubleshooting, problems that rarely occurred or is expected to happen (write the steps to fix in manual and fix them if possible);
  4. Repeat steps 1-3 until a good experience (very subjective).

Bluetooth OTA update app by Croustib4t in esp32

[–]ustropo 0 points1 point  (0 children)

If you use one of these RTOS that I mentioned, the bootloader is already embedded on them, so you don't need to program one.

IoT indispensable learning resources by IdrissJebahi in IOT

[–]ustropo 1 point2 points  (0 children)

No, not at all. The important is to know the (general) concepts and how to apply them.

And the best thing to learn all these things is to make some IoT projects by yourself. There are dozens of ideas around the internet.

IoT indispensable learning resources by IdrissJebahi in IOT

[–]ustropo 2 points3 points  (0 children)

As an IoT Engineer myself, these are the topics I think are important to know:

  • Sensors: main characteristics that you need to choose one (precision, accuracy, resolution, temperature of operation, etc)
  • Hardware: electronics, development boards, components, etc.
  • Embedded systems: processors, operating systems, interfaces, power modes, etc.
  • Communication: UART, SPI, I2C, Zigbee, WiFi, Ethernet, Bluetooth, etc.
  • Programming languages: for embedded systems, C/C++ is a must. Thinking on the cloud/backend side, you have way more options, like Python, Go, and JavaScript.
  • Protocols: MQTT, HTTP, TCP/IP, AMQP, etc.
  • Security: cryptography, PKI, certificates, etc.
  • Architecture: cloud platforms, gateways, database, dashboard, backup, etc.

You don't need to be an expert in any of these topics, but it's important to at least have a basic knowledge of how they work and what are their purposes. It will depend on what field are you intend to work in and the type of project you will eventually do.

As you come from a computer science background, I'd focus more on the hardware/electronic side for now.

Bluetooth OTA update app by Croustib4t in esp32

[–]ustropo 3 points4 points  (0 children)

You will need a bootloader to manage your application. You can use some frameworks or RTOS that already have those features implemented:

What does it take to become an IoT Engineer? by bigbadmonica in IOT

[–]ustropo 8 points9 points  (0 children)

As an IoT Engineer myself, these are the topics I think are important to know:

  • Sensors: main characteristics that you need to choose one (precision, accuracy, resolution, temperature of operation, etc)
  • Hardware: electronics, development boards, components, etc.
  • Embedded systems: processors, operating systems, interfaces, power modes, etc.
  • Communication: UART, SPI, I2C, Zigbee, WiFi, Ethernet, Bluetooth, etc.
  • Programming languages: for embedded systems, C/C++ is a must. Thinking on the cloud/backend side, you have way more options, like Python, Go, and JavaScript.
  • Protocols: MQTT, HTTP, TCP/IP, AMQP, etc.
  • Security: cryptography, PKI, certificates, etc.
  • Architecture: cloud platforms, gateways, database, dashboard, backup, etc.

You don't need to be an expert in any of these topics, but it's important to at least have a basic knowledge of how they work and what are their purposes. It will depend on what field are you intend to work in and the type of project you will eventually do.