WS63 Wireless Module Integration | Obeita
Delivered project. The completed hardware and software met the customer’s agreed requirements in testing. Specifications for a new project must be agreed separately.


Obeita completed a WS63/Hi3863 wireless-module integration project, carrying customer requirements through contract confirmation, hardware and firmware/software design, physical testing and delivery. The focus was fitting a selected wireless function into an embedded host and its enclosure.
Radio selection defines the integration job
The public platform description includes SLE 1.0, Wi-Fi 6 and BLE 5.2 protocol directions. A product integration needs a defined peer, host role and payload behavior before those capabilities can become an application connection. Obeita developed the agreed hardware and software implementation around the customer’s requirements, with the module-to-host boundary central to the work.
The protocol list is a set of platform directions, not a statement that all radios operate simultaneously. Firmware selection and scheduling govern the actual operating mode. This distinction matters when adapting the module for a sensor, actuator or local device-control link.
Antenna placement and electrical access
The documented design offers PCB-antenna and IPEX external-antenna alternatives. A PCB antenna depends on clearance from metal and a suitable keep-out area; an IPEX connection permits a different antenna location while adding cable and connector requirements. In a new design, the external-antenna cable route, ground reference and final mounting position need RF review. These mechanical choices need to match the device enclosure rather than being selected independently of it.
The breakout provides UART, GPIO and reset access alongside power and ground. Host wiring and firmware pin functions must refer to the same module revision. The listed module dimensions and supply input also need to remain distinct from a powered development board or finished DTU.
From wireless hardware to a host data path
The integration architecture connects radio-mode selection with provisioning, reconnection and host-message framing. Defining those behaviors makes the wireless module part of the application rather than just a separate radio board. For a new project, the host voltage, payload timing and required connection behavior establish the useful software and interface scope.
Documented architecture and configuration
This table records the project’s documented architecture and selection boundaries. Options, variants and design inputs remain qualified as shown; their inclusion here is not an independent guarantee that every option formed part of the delivered configuration.
| Item | Configuration |
|---|---|
| Platform | WS63 / Hi3863 |
| Protocol directions | SLE 1.0 / Wi-Fi 6 / BLE 5.2 |
| Antenna choices | PCB antenna or IPEX external antenna |
| Module design input | 24 × 16 × 3 mm; 3.3 V listing, revision check required |
| Host access | UART, GPIO and reset on breakout |
| Use cases | Sensors, actuators and local device control |
Delivered integration and physical testing
The agreed WS63/Hi3863 integration was delivered as a hardware and software implementation. Obeita completed physical testing, and the tested functions met the customer’s requirements. That confirmation applies to the project’s agreed configuration; it does not claim universal interoperability, simultaneous multi-radio operation or a guaranteed communication distance.
Alternative antennas and firmware modes remain selection decisions. If a new project requires concurrent radio modes, its test scope should cover the requested combination, memory use and scheduling with the selected firmware. A metal enclosure, different peer device or changed radio schedule introduces conditions that need their own integration and test definition.
Scope a similar wireless-module integration
Share the required SLE, Wi-Fi or BLE mode, host MCU voltage, payload needs and enclosure drawing with Obeita. We can define module, antenna, host-interface and physical-test requirements for your connected device.