Skip to content
  • Off-topic, feedback, and everything else.

    0 0
    0 Topics
    0 Posts
    No new posts.
  • New here? Begin with these topics.

    3 3
    3 Topics
    3 Posts
    A
    Welcome! Tell us about yourself Reply to this topic and introduce yourself: Name / Nickname College or Company What block you are on What you are building or want to build One thing you want to learn from Embiq We read every introduction. Looking forward to meeting you!
  • 4 Topics
    4 Posts
    A
    A connected device without security is a loaded gun pointed at your own network — and MQTT isn't the answer to every device-side problem either. This companion post covers the two things that turn a working prototype into shippable firmware: locking it down, and reaching beyond MQTT where it fits. Lock it down Mutual TLS, done right. Server-only TLS leaves devices talking to impostors. Both sides prove identity — the device verifies the server, the server verifies the device. Two field gotchas: actually validate the CA chain (skipping verification "temporarily" becomes permanent), and sync the clock first — certificates look invalid on a device that thinks it's 1970. → Why security matters — real attacks → Certificate-based auth and device tokens Trust the code you run. Secure boot stops modified firmware from executing; signed OTA with hash verification plus automatic rollback stops a bad or malicious update from bricking the fleet. Credentials live in protected on-device storage with a provisioning flow — never as string literals in source. Assume anyone can dump your flash; design so a dump alone isn't enough. → The secure boot concept → Credential storage on the device → Secure OTA with signed firmware Reach beyond MQTT HTTP/REST for on-device APIs and cloud calls, WebSocket for local dashboards, Modbus RTU for industrial sensors on RS-485 that isn't going away, and BLE provisioning so users can configure WiFi credentials without hardcoding them. → HTTP and REST from the device → WebSocket basics for local dashboards → Modbus RTU for industrial devices → BLE provisioning of WiFi credentials Capstone A fully connected, secure IoT device — TLS-authenticated MQTT link to GrapesIoT, a clean topic schema, LWT-based presence detection, and offline buffering that survives a broker outage. Share your build in the lab submissions area when it's done. Post questions here and tag with security, tls or ble. For the device-to-cloud path (networking, MQTT, patterns), see the companion post above.
  • Post your lab results, code, wiring photos, and project demos here.

    5 5
    5 Topics
    5 Posts
    A
    How to Submit Your Lab Every lab submission must include: Session number and lab name (e.g. "Lab 2.1.1 — UART Deep Dive") What it does — one paragraph description Code — paste your firmware using code blocks Evidence — serial output screenshot OR wiring photo OR video link What you learned — one sentence Format example: Lab: 2.1.1 — UART Two-Board Communication Description: Connected two ESP32 boards via UART. Board A sends a SensorReading_t struct every 2 seconds. Board B receives, parses, and prints. // your code here Serial output: [INF][1234] Received: temp=27.4, hum=62.1 What I learned: UART needs shared GND — forgot this and got garbage data for 20 minutes. Tag your post with the block tag e.g. block-2
  • Stuck? Post here. Search the Troubleshooting Index first.

    9 9
    9 Topics
    9 Posts
    A
    Your First Dashboard in UI Studio UI Studio turns a product's data points into a mobile-style dashboard. No app build, no separate frontend project: you arrange widgets on a canvas, bind them to data points, and publish. This guide builds a small greenhouse screen with three values and one control. [image: 1794556172630-01-screens.png] The UI Studio workspace previews a product dashboard and opens the full editor in a new tab. Before you start You need: a product with data points, at least one device assigned to that product, the device online or publishing (so you can see values move). If you have not published a message yet, do the Quickstart: Device → MQTT → Live Monitor first. A dashboard with no data is hard to debug. 1. Open the studio There are two entry points: From a product card: click UI Studio. This opens the studio for that product in a new tab. From the sidebar: open UI Studio, pick the product, then click Open in Studio. The product-card route is the fastest way to start from scratch. The sidebar workspace shows the current dashboard and its component and effect counts. 2. Know the three areas The studio has three working areas: Palette on the left: the widgets you can add. Canvas in the middle: a mobile-style surface at a fixed design width. Property panel on the right: the selected widget's settings. [image: 1794556173761-03-widget-palette.png] The palette groups widgets by job: controls, charts, UI basics, controllers, and effects. The palette groups widgets by job. You will use these groups most often: CONTROL — toggles, sliders, input fields. CHARTS — line graphs and other history views. UI BASICS — text, meters, icons, shapes, colour pickers. CONTROLERS — scroll pickers, steppers, function sliders. EFFECTS — motion and other visual effects. The exact list depends on your build. If a widget is missing, it may be a newer widget that is not enabled for your account. 3. Add widgets Drag a widget from the palette onto the canvas, or click it to add it at a default position. For the greenhouse screen: Area Widget Bound data point Top Text none (title) Row 1 Value / Status temp Row 1 Value / Status humidity Row 2 Line Graph temp (history) Row 3 Toggle Switch pump Keep the canvas focused. A dashboard that shows everything is harder to use than one that answers a single question. [image: 1794556173188-02-canvas.png] The canvas is a mobile-style surface. Drag widgets from the palette, resize them, and bind each one to a data point. 4. Style and layout Select a widget to open the property panel. The tabs are: Tab What it controls STYLE Colors, typography, borders, backgrounds LAYOUT Position, size, alignment, spacing LOGIC Data binding and behaviour EFFECTS State-based visual changes [image: 1794556174353-04-property-panel.png] Select a widget to edit its style, layout, logic and effects. Logic is where data binding lives. Use LAYOUT to align widgets to a grid. The canvas is mobile-first; keep touch targets large enough to tap and avoid placing controls at the very edge. 5. Bind data Open the LOGIC tab and find Data Binding. [image: 1794556174916-05-data-binding.png] Pick the device and data point in the Logic tab. The widget starts receiving live values as soon as the device publishes. Choose the device. Choose a data point. Confirm the widget supports that data point's type. Binding rules to remember: A Status point can be read by a display widget. A Control point can be written by a toggle, slider, or button. A Both point can be read and written. A numeric widget will not bind to a string point, and a boolean widget will not bind to a number. If the data point list is empty, the device may not be assigned to the product, or the product may not have compatible points. For a line chart, bind history. If the data point does not have Storage enabled, there is no history to draw; the chart will be empty even though the live value updates. 6. Add effects (optional) EFFECTS lets a widget change its appearance based on a value. Typical uses: turn a status tile red when temperature is above a threshold, change an icon when a pump is running, show a warning state when a battery is low. Effects are evaluated on the client from live values. They are not server-side automations. Use the Automation section if you need to trigger an action rather than change a visual. 7. Publish Click PUBLISH in the top bar. The current layout is frozen into a read-only screen. [image: 1794556175450-06-published.png] PUBLISH freezes the current layout into a read-only screen that the device monitor and mobile clients can consume. The published screen: appears in the UI list, can be opened in the studio for further editing, is what the device monitor renders, is read-only at runtime, so users cannot accidentally move widgets. Publishing does not deploy firmware and does not change the data model. It only snapshots the layout and bindings. 8. Verify with live data Open the device monitor and publish a message. Confirm: the connection pill reaches Live, each bound widget shows the expected value, the toggle writes a control message when tapped, the chart fills if history is enabled. If a value is stale, check the binding first, then the payload key. A typo in dpcode is the most common cause of an empty widget. A good first-screen checklist One clear purpose per screen. A title that says what the screen is for. The three or four values that matter most, not every value in the product. Controls that are visually distinct from read-only values. Large touch targets and consistent spacing. A test with real data before you publish to users. Common questions Can I reuse a screen across devices? Bindings are per widget. If devices share the same product and data point codes, you can copy the layout and change the device binding. Keep one screen per product family. Why is my chart empty? The data point probably has Storage disabled, or the device has not published enough history yet. Why can't I bind a control? The data point is probably Status only. Change it to Both or Control, or use a display widget instead. Does publishing affect the device? No. Publishing only snapshots the dashboard. It does not send anything to the device. Next Data Point Types Explained for choosing the right widget and direction. Quickstart: Device → MQTT → Live Monitor for getting values into the platform.
  • 10 Topics
    10 Posts
    A
    A datasheet is the ground truth for every component you use. Guessing at voltage limits, timing requirements, or register values is how you fry a board or spend a week debugging something the datasheet would have told you in ten minutes. The skill isn't reading every page — it's knowing which pages matter, in what order. The structure of these documents is a skill of its own: → How technical documents are structured Read in this order Absolute Maximum Ratings — what kills the part. 5V into a 3.3V GPIO is a gamble, not a spec. Electrical Characteristics — the voltages, currents and timings you actually design to. This is where requirements turn into numbers you can hold a design to: → Extracting requirements and electrical limits Register map — the exact bit that enables the interrupt, sets the mode, or clears the flag. Timing diagrams — setup and hold, clock polarity, what the signal must look like on a scope. Register rows and timing plots are where firmware meets silicon: → Register maps, timing and protocol details App note + errata — how the vendor says to use the part, and what they corrected after printing. A worked 60-second example You need to enable a sensor's data-ready interrupt. The register map shows INT_ENABLE at address 0x2D, bit 3, "write 1 to enable, cleared on read of STATUS". That one row tells you the address, the bitmask (1 << 3), the write semantics, and the clearing rule — four facts you'd otherwise discover by trial and error. Every peripheral bring-up is this loop: map row → mask → write → verify by reading back. → Hands-on intro to reading datasheets Start at Reading Datasheets and work through it in order. Post the part number, the page/section, and what confuses you. Tag with datasheets.
  • 2 Topics
    2 Posts
    A
    Industry Problems Board Companies and startups post real engineering problems here. Students who solve them get: Recognition on their Embiq profile Direct introduction to the company Potential internship or job offer For companies: Post problems with the tag industry-problem. Include context, constraints, and what a good solution looks like. For students: Attempt problems publicly — show your reasoning, not just the answer. Multiple approaches welcome. This is the closest thing to a real technical interview the forum offers.
  • 4 Topics
    4 Posts
    A
    Curated by people who read them — not an algorithm. One book finished beats ten bookmarked. Reply with what a resource taught you, not just its name. Books (read in this order) Making Embedded Systems — Elecia White. The single best "how the job actually works" book: hardware/firmware boundary, interviews with working engineers, debugging war stories. Start here. Test-Driven Development for Embedded C — James Grenning. Writing firmware you can trust, with host-side tests running before hardware exists. Transforms how you structure C. The C Programming Language — Kernighan & Ritchie. Thin, dense, timeless. The language reference every embedded engineer should have worked through at least once. Official documentation (primary sources beat tutorials) ESP-IDF Programming Guide — the framework reference; read the peripheral and FreeRTOS sections for your chip, not random blogs first. ESP32 Technical Reference Manual — the 600-page truth about your silicon: registers, clock trees, and errata. Intimidating, indispensable. Sites & series All About Circuits — electronics fundamentals explained patiently, with a textbook-grade volume set free online. EEVblog — teardowns and rants that teach measurement technique and design scepticism by example. HiveMQ MQTT Essentials — the clearest free walkthrough of MQTT concepts, one idea per short article. A note on links: titles only, deliberately — search the current edition yourself so you never land on a stale mirror. Reply with your own recommendations and one line on what each taught you.