27 Industrial and Wearable Kits

27.1 Start With the Story

This section: Start With the Story — Industrial and wearable prototypes meet people, machines, and environments that do not forgive vague evidence.

Industrial and wearable prototypes meet people, machines, and environments that do not forgive vague evidence. A wearable must respect body placement, comfort, privacy, battery life, and maintenance. An industrial kit must survive noise, safety expectations, physical access limits, and support ownership. The useful story begins with the person or process that must trust the result.

This chapter uses kits as controlled trials. Pick the kit that exposes the real context, capture measurements and workflow notes, and record which compliance, safety, or durability questions still require a stronger prototype.

27.2 Industrial vs Wearable Kit Risks

This section: Industrial vs Wearable Kit Risks — Figure 27.1 separates industrial site tests from wearable body tests before integration.

Industrial kits should expose site constraints: 24 V control power, isolated inputs, relay or transistor outputs, RS-485, CAN, Ethernet, Modbus, OPC UA, PLC or SCADA boundaries, cabinet mounting, cable strain, service access, and recovery after a noisy interruption. A kit that only works on a desk has not answered the industrial question.

Figure 27.1 separates industrial site tests from wearable body tests before integration.

+

The pump-room monitor must show how its 24 V supply, RS-485 link, cable strain, service access, and recovery behave at the site. A wearable needs different evidence: body placement, contact pressure, motion artifact, comfort, and charging under the intended task. Each kit should be tested against its own disturbance before their records are combined. The route ends with a review of what the separate setups proved and what the combined product still has to test. A clean bench stream from either kit cannot establish reliable reporting in a pump room or on a moving body.

Wearable kits should expose body constraints: placement, contact pressure, motion artifacts, sweat, comfort, charging rhythm, BLE pairing, phone permission limits, data minimization, and what the wearer sees when sensing fails. A kit that only streams clean data from a hand-held board has not answered the wearable question.

• Industrial question: can the prototype behave near the equipment, wiring, gateway, enclosure, and maintenance workflow it will meet later?
• Wearable question: can the prototype stay useful, comfortable, charged, private, and understandable while attached to a person?
• Shared question: which result survives the move to a carrier board, sealed enclosure, garment fixture, phone app, or field pilot?

For example, a pump-room monitor might start with an Arduino Opta, Siemens LOGO!, WAGO controller, or Moxa gateway because the risk is not simply reading a sensor. The team needs to know how 24 V control power, terminal blocks, relay outputs, Modbus RTU over RS-485, Ethernet, local status LEDs, cabinet clearance, and technician access behave near the real equipment. A successful desk demo is only the first clue. The useful industrial record says which site conditions were represented and which still need a cabinet or field fixture.

A wearable fatigue or safety prototype has a different evidence shape. A Nordic Thingy, nRF52840 Sense board, Movesense sensor, Shimmer kit, BMI270 IMU board, MAX30101 optical sensor, or textile fixture should be judged by placement, motion artifact, strap pressure, battery runtime, BLE reconnect, wearer feedback, cleaning, consent, and data minimization. The question is not whether the electronics can stream numbers. The question is whether the worn system can be used during a real shift without producing misleading data or an unacceptable burden.

27.3 Match Kit Families to Risk

This section: Match Kit Families to Risk — Industrial experiments may use Arduino Portenta Machine Control, Arduino Opta, Siemens LOGO!

Industrial experiments may use Arduino Portenta Machine Control, Arduino Opta, Siemens LOGO! or S7-1200 starter kits, WAGO controllers, Phoenix Contact PLCnext hardware, Beckhoff CX controllers, Advantech or Moxa edge gateways, Seeed reComputer Industrial systems, Raspberry Pi Compute Module carriers, or DIN-rail I/O modules. Wearable experiments may use Nordic nRF52840 or nRF5340 development kits, Nordic Thingy sensor platforms, Arduino Nano 33 BLE Sense, Adafruit Feather nRF52840 Sense, Seeed XIAO nRF52840 Sense, Movesense sensors, Shimmer sensing kits, SparkFun and Adafruit Qwiic/STEMMA QT sensor boards, MAX30101 or MAX86150 optical and ECG front ends, Bosch BMI270-class IMUs, and LiPo charger or fuel-gauge boards.

• For industrial fit: log supply voltage, input threshold, isolation boundary, relay or MOSFET load, terminal-block strain, enclosure clearance, DIN-rail access, protocol timing, gateway restart, and local fault indication.
• For wearable fit: log body location, strap or clip method, IMU motion artifact, PPG or ECG contact quality, skin temperature, sweat exposure, cleaning step, charge time, battery runtime, BLE reconnect, and wearer-facing failure cue.
• For the phone or gateway path: log BLE GATT characteristics, iOS CoreBluetooth or Android BLE permission state, background behavior, MQTT or HTTPS handoff, timestamp freshness, duplicate messages, dropped samples, and offline queue length.
• For handoff: mark which connector, board size, antenna position, battery, sensor package, enclosure, textile, firmware library, and compliance assumption is kit-only.

A practical industrial kit test should include the field interface, not just the controller. If the final device reads a 4-20 mA pressure transducer, an NPN proximity sensor, or an RS-485 Modbus meter, record the actual signal range, termination, shield connection, isolation boundary, poll interval, timeout behavior, and local fault indication. If the gateway publishes to MQTT or HTTPS, record topic or endpoint, payload timestamp, retained state or queue behavior, duplicate handling, offline duration, and recovery after power loss. These details make the result reviewable when the board or gateway changes.

A practical wearable kit test should include the body fixture and phone or hub path. Record strap position, orientation, attachment force if relevant, IMU axis mapping, PPG or ECG contact quality, cleaning step, charging contact behavior, BLE service ids, phone permission state, background reconnect, and the user-visible cue when sensing fails. A ten-minute lab run is not the same as a shift trial, but it can still expose whether the kit is worth carrying into a more realistic fixture.

27.4 Physical and Operational Failures

This section: Physical and Operational Failures — Industrial and wearable failures often happen outside the code path.

Industrial and wearable failures often happen outside the code path. Ground loops, ESD, surge, EMI, cable flex, connector reversal, regulator dropout, brownout recovery, ingress, washdown, glove use, and technician access can defeat a site prototype. Motion artifacts, loose contact, skin-tone effects, strap pressure, sweat, charging contacts, phone background limits, consent, and support handoff can defeat a wearable prototype.

• Electrical boundary: separate logic ground, field wiring, surge protection, fuses, TVS placement, opto-isolation, 4-20 mA loops, 0-10 V inputs, RS-485 termination, and CAN termination from the convenient dev-board wiring.
• Mechanical boundary: check gasket pressure, IP-rated enclosure assumptions, antenna keep-out, cable glands, strain relief, clip retention, textile routing, cleaning method, and repeated donning or removal.
• Operational boundary: verify provisioning, replacement, calibration, firmware update, rollback, local logs, support diagnostics, privacy notice, retention policy, and data deletion before a field trial.
• Integration boundary: test the exact message and state contract between body node, phone or hub, site gateway, dashboard, and supervisor workflow instead of relying on two separate demos.

The kit has done its job when it exposes which industrial, wearable, data, and service checks must repeat in the next product form.

Under the hood, industrial evidence depends on protection and diagnostics as much as sensing. A prototype that ignores TVS diodes, fusing, reverse-polarity protection, opto-isolation, terminal labeling, cable glands, watchdog behavior, and local status codes can pass a lab script and still be impossible to maintain. Wearable evidence has its own hidden limits: accelerometer axes rotate with the body, optical sensors need stable contact and light control, ECG electrodes need skin preparation and safe front-end design, and small batteries change behavior with charge age and temperature.

The integration boundary also carries data risk. A body node may collect more personal information than the gateway or supervisor workflow needs. A site gateway may combine location, worker id, shift time, hazard state, and equipment status in a way that requires purpose limits, retention limits, and access control. When moving beyond kits, the record should name the telemetry fields, processing location, retention rule, visibility rule, deletion path, and failure cue that must survive the next hardware form.

27.5 Learning Objectives

This section: Learning Objectives

By the end of this chapter, you will be able to:

• Explain why industrial and wearable kits should be selected by evidence need, not brand familiarity.
• Compare harsh-environment evidence with body-worn evidence.
• Build a review matrix for interfaces, environment, form factor, energy, data handling, and handoff risk.
• Plan a combined site-and-worker prototype without hiding subsystem failures.
• Write a kit review record that preserves assumptions, rejected options, and change conditions.

27.6 Two Different Evidence Worlds

This section: Two Different Evidence Worlds — Industrial kits and wearable kits can both appear in the same IoT project, but they answer different questions.

Industrial kits and wearable kits can both appear in the same IoT project, but they answer different questions. Industrial kits help a prototype survive site realities such as equipment interfaces, electrical noise, enclosure placement, service access, local gateway behavior, and maintenance workflow. Wearable kits help a prototype survive human realities such as body placement, motion, comfort, skin contact, charging rhythm, consent, and data minimization.

Start by naming the evidence gap:

27.7 Kit Roles

This section: Kit Roles — Select the kit role that exposes the risk you need to review.

Select the kit role that exposes the risk you need to review. A kit that is excellent for a cabinet-mounted gateway may be a poor fit for a worn node. A kit that is excellent for body-signal exploration may be a poor fit for dusty installation work.

Figure 27.2 compares the disturbances that industrial and body-worn kits must expose.

+

On the industrial side, power, long cables, grounding, vibration, and service access can change a reading or prevent recovery. On the body-worn side, placement, motion, contact, sweat, and charging affect both signal quality and use. The diagram sketches these modes rather than showing recorded time-series samples, so its waveforms are questions for a trial. Log the actual disturbance, the kit setup, and the response for each path. A kit choice is credible when it can expose the conditions expected at the site or on the body, not when it simply has more sensors.

27.8 Industrial Kit Evidence

This section: Industrial Kit Evidence — Industrial prototypes often fail because the bench version did not represent the site.

Industrial prototypes often fail because the bench version did not represent the site. The kit should make the site risk visible: interfaces, mounting, enclosure, wiring, electrical environment, local recovery, and maintenance.

Review industrial kit evidence with these questions:

27.9 Wearable Kit Evidence

This section: Wearable Kit Evidence — Wearable prototypes fail when the electronics work but the body-worn system does not.

Wearable prototypes fail when the electronics work but the body-worn system does not. The kit must help answer whether the sensing path, attachment method, energy rhythm, and data boundary make sense for a real person and a real workflow.

Review wearable kit evidence with these questions:

27.10 Evidence Matrix

This section: Evidence Matrix — Industrial and wearable kits should be compared by the evidence they can produce.

Industrial and wearable kits should be compared by the evidence they can produce. The same project may need both categories, but each should own a different part of the review.

Figure 27.3 asks what site and body tests each kit can retain.

+

An industrial controller or gateway should expose supply, communication, cable, and recovery behavior under the planned installation. A wearable sensor or fixture should expose signal quality during movement, placement changes, comfort, and maintenance. The evidence column asks for logs or measurements that another reviewer can inspect. The hidden-risk column marks what a clean demonstration leaves unresolved. Compare kits within the same deployment question before scoring their features. If a body signal survives a bench trial but fails in motion, or a gateway works without site cable strain, the relevant decision remains open.

Use the matrix to avoid false comparisons:

27.11 Worked Scenario: Worker Safety Prototype

This section: Worked Scenario: Worker Safety Prototype — A team is prototyping a worker safety system for a noisy outdoor worksite.

A team is prototyping a worker safety system for a noisy outdoor worksite. A body-worn device should detect motion and heat-stress indicators, and a site gateway should collect status summaries for supervisors. The team avoids a single all-in-one demo because it would hide both site and body risks.

prototype=worker-safety-monitor
current_question=can body-worn status and site gateway recovery work together?
wearable_evidence=placement notes, motion effects, comfort notes, charge rhythm, signal quality
site_evidence=gateway location, buffering, local status, network recovery, service access
integration_boundary=kit boards prove message path; next prototype must check enclosure, attachment, antenna, and shift workflow again
rejected_option=single all-in-one demo because it hides body placement and site recovery failures
next_step=carrier fixture for gateway plus worn enclosure mockup with repeatable attachment

27.12 Integration Boundary

This section: Integration Boundary — The kit proves evidence, not the final product.

The kit proves evidence, not the final product. Draw a boundary before the team commits to enclosures, garments, gateway locations, or production workflow.

Figure 27.4 separates two legitimate kit records from the assurance that remains. The Industrial bench can bound interface, placement, and recovery behavior; the Wearable trial can expose attachment, power, and data-boundary evidence.

+

The dark rail in Figure 27.4 states the transfer rule: interface logs, placement limits, and recovery steps may cross. Enclosure, attachment, comfort, cleaning, privacy, gateway operation, and service ownership do not. Retest whenever one of those product conditions changes.

27.13 Kit Review Record

This section: Kit Review Record — Leave a record that another reviewer can challenge.

Leave a record that another reviewer can challenge. The record should show what the kit proved, what it did not prove, and what must be checked again.

Figure 27.5 makes the worker-safety kit decision inspectable.

+

The record names the worker-safety-monitor prototype, its handoff stage, review owner, and current question. The question is whether body-worn status and site-gateway recovery work together. Keep the wearable’s placement and movement observations separate from the industrial gateway’s power, link, and restart logs. Each result needs its tested conditions and an unresolved-risk field. The integration decision should then identify which body and site conditions still need a combined test. The record prevents a pass from an isolated kit setup being read as proof that a worker alert will survive the whole path.

Use this template:

prototype=
stage=
current_question=
selected_kit_role=
site_or_body_context=
evidence_captured=
rejected_option=
integration_boundary=
data_boundary=
change_condition=
next_action=
review_owner=
review_date=

27.14 Knowledge Check

This section: Knowledge Check

27.15 Common Failure Patterns

This section: Common Failure Patterns

27.16 Summary

This section: Summary — First, Industrial kits are strongest when they expose site evidence: interfaces, environment, gateway recovery, service access, and installation assumptions.

First, Industrial kits are strongest when they expose site evidence: interfaces, environment, gateway recovery, service access, and installation assumptions. Next, Wearable kits are strongest when they expose body evidence: placement, comfort, motion effects, energy rhythm, data boundaries, and human workflow. Then, Combined worker-facing systems should stage wearable evidence, site evidence, and integration evidence separately. After that, Kit evidence must be separated from final product responsibilities such as enclosure, garment, antenna, service process, and data policy. Finally, A review record makes the decision revisable when the prototype moves to a carrier, fixture, enclosure mockup, garment prototype, or field trial.

27.17 Key Takeaway

This section: Key Takeaway — Industrial and wearable kits need extra scrutiny for enclosure, safety, durability, provisioning, maintenance, and user context before their demo value becomes design evidence.

Industrial and wearable kits need extra scrutiny for enclosure, safety, durability, provisioning, maintenance, and user context before their demo value becomes design evidence.

27.18 What’s Next

This section: What’s Next