Part Number:
Quantity:
Price per Unit (in USD):
Total Amt:
Log in to myMicrochip to access tools and benefits. Sign up in just one minute.
Maximize Your Experience: Reap the Personalized Advantages by Completing Your Profile to Its Fullest! Update Here
Stay in the loop with the latest from Microchip! Update your profile while you are at it. Update Here
Complete your profile to access more resources.Update Here!
true
Proprietary Wireless Modules and SoCs
Empowering Businesses to Optimize Connectivity
Featured Products
PIC32-BZ Family
- Peripheral rich, wireless MCUs support Bluetooth® Low Energy, Zigbee® and proprietary protocols
- Simple APIs provide access to the 802.15.4 transceiver functionality
- Create your proprietary stack using our MPLAB® Harmony framework
SAM R30 Family
- Reliable connectivity for sensors requiring communication through dense walls and over long range
- Extremely low-power sleep modes for multiple years of battery life
- Proprietary self-healing mesh connectivity
Choosing a Proprietary Wireless Product
Proprietary wireless products are different from their standardized counterparts—they require hardware and software consideration. The hardware provides radio functions and the software provides network connectivity. When selecting a device, you need to consider the hardware specifications and the hardware’s ability to support the software you plan to run.
Our hardware portfolio consists of a range of Integrated Circuits (ICs) that operate in sub-GHz, 2.4 GHz and dual-band frequencies
Our software portfolio includes custom and turn-key options. MAC and PHY libraries provide the ultimate flexibility by allowing you to add a protocol of your choice to our devices. If you are new to proprietary protocols or are looking to get your project to market faster, consider our turnkey, proprietary MiWi™ protocol, which can be implemented as-is or customized to your needs.
Proprietary Wireless Software Solutions
802.15.4 PHY Library to Access Physical Layer
This API library gives you access to our transceivers and wireless MCU radios’ physical (PHY) layer.
802.15.4 MAC Library to Access Data Link Layer
For additional security and features, this API library gives you access to our transceivers at the MAC level.
MiWi™ Protocol for a Turnkey Solution
Our MiWi protocol is a lightweight, proprietary mesh solution. It supports P2P, star and mesh topologies and can be customized to your requirements.
Markets and Applications
Proprietary wireless-enabled products are a good choice for solutions that cater to specific industry needs. Their enhanced performance, security and control empower businesses to optimize their wireless products and gain a competitive advantage.
Tools and Software
- Demo & Evaluation Boards
- Development Environment
The PIC32CX-BZ2 and WBZ451 Curiosity board is an all-in-one development platform that you can use to evaluate PIC32CX-BZ2 SoCs and WBZ451 modules.
The SAM R30M Xplained Pro is a hardware platform designed to evaluate the SAMR30M18A SoC.
The ATREB215-XPRO is a hardware platform designed to evaluate the AT86RF215 transceiver.
The SAM R21 Xplained Pro evaluation kit is a hardware platform to evaluate the ATSAMR21G18A microcontroller.
MPLAB® Harmony is a modular framework that provides interoperable firmware libraries for application development on 32-bit microcontrollers and microprocessors.
Microchip Studio is an Integrated Development Environment (IDE) for developing and debugging AVR® and SAM microcontroller applications. It merges all of the great features and functionality of Atmel Studio into Microchip’s well-supported portfolio of development tools to give you a seamless and easy-to-use environment for writing, building and debugging your applications written in C/C++ or assembly code.
Learn About RF and Wireless
Want to learn more about Radio Frequency (RF) applications and proprietary protocols? Check out the Microchip University Course, Getting Started With Radio Frequency Applications. This class covers RF working principles and explores the difference between standard and proprietary protocols.
Is Proprietary Wireless Right for Your Project?
- Benefits
- Versus Standard
Benefits of Proprietary Protocols
Unlike standard wireless protocols such as Wi-Fi or Bluetooth, which are widely adopted and governed by standards organizations, proprietary protocols are created to meet the specific needs of or address the challenges unique to an industry or application.
By focusing on specific requirements, proprietary protocols often provide better security, reliability and data throughput with lower latency and a smaller memory footprint when compared to standard protocols.
Proprietary protocols also provide a level of exclusivity and control over the network topology. As the owners of the protocol, you have full authority over its development, deployment and licensing. This level of control allows for tighter integration with other proprietary systems and enables businesses to maintain a competitive edge.
Selecting a proprietary wireless protocol requires careful consideration, but in many cases the gains far outweigh any negatives. And because proprietary product development involves more than hardware, it is important to choose a supplier with a proven development environment. When you work with us, you get reliable hardware and easy-to-use software that are backed by a comprehensive support ecosystem.
Proprietary vs. Standard Protocols
All protocols, standard and proprietary, have a multi-layered architecture. The stack consists of multiple layers that have their own set of functions but work with the others to facilitate data exchange and transmission. The base layers, physical and data link, handle radio transmission while the remaining layers support network control and application-specific functions.
In a standard protocol, the stack is self-contained, so you must work within the confines of the manufacturer and protocol specifications.
In a proprietary protocol, you can create your own specifications on top of the radio layers. The device manufacturer must allow access to the radio function for the proprietary protocol to interact with it. This interaction is accomplished through a set of APIs as part of Software Development Kit (SDK).
