Difference between revisions of "Wireless Modules"

From Humanoid Robots Wiki
Jump to: navigation, search
(UART Communication)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
 
= Justification =  
 
= Justification =  
Robust, wireless communication between multiple PCB boards decreased design constraints and wiring, allowing for much more modular and adjustable designs capable. This would allow for mobility, ease of communication, reduced clutter, and scalability.
+
Robust, wireless communication between multiple PCB boards decreased design constraints and wiring, allowing for much more modular and adjustable designs capable. This would allow for mobility, ease of communication, reduced clutter, and scalability. Could potentially
  
 
= Current Methods of Integration =  
 
= Current Methods of Integration =  
Line 7: Line 7:
 
== Connections ==  
 
== Connections ==  
 
=== UART Communication ===
 
=== UART Communication ===
* Hook up
+
* Hook up UART_TX and UART_RX to STM32.
  
 
=== I2C Communication ===
 
=== I2C Communication ===
Line 16: Line 16:
 
  * ESP32 Chip adjusted specifically for the sole purpose of wireless communication.
 
  * ESP32 Chip adjusted specifically for the sole purpose of wireless communication.
 
  * Interfaced with using UART
 
  * Interfaced with using UART
  *  
+
  *
 +
[https://www.digikey.com/en/products/detail/espressif-systems/ESP32-WROOM-32-N4/8544298 ESP32-WROOM-32]
 +
* uses UART To both receive and send data to other modules
  
 
== Pros and Cons ==
 
== Pros and Cons ==
Line 42: Line 44:
 
== TODO ==
 
== TODO ==
 
Look into the specific components of the Bluetooth modules to find ICS that can be easily used and interfaced with.
 
Look into the specific components of the Bluetooth modules to find ICS that can be easily used and interfaced with.
 +
Figure out how to interface with ESP32 software using STM32, how to send specific commands, etc.
 +
 +
 +
= Interfacing with Other Boards =
 +
== Network Setup ==
 +
=== Access Point ===
 +
Set up one device as the master. Intended purpose of the CANdaddy. Host signal and allow other devices to connect using SSID and password. In the case of the ESP32, this is done through built in libraries that allow for 
 +
== Communication Protocol ==
 +
== Data Exchange ==

Latest revision as of 08:52, 28 May 2024

Justification[edit]

Robust, wireless communication between multiple PCB boards decreased design constraints and wiring, allowing for much more modular and adjustable designs capable. This would allow for mobility, ease of communication, reduced clutter, and scalability. Could potentially

Current Methods of Integration[edit]

ESP32 Built-In[edit]

Connections[edit]

UART Communication[edit]

  • Hook up UART_TX and UART_RX to STM32.

I2C Communication[edit]

SPI Communication[edit]

Firmware[edit]

Examples[edit]

ESP32-C3-MINI-1-N4

* ESP32 Chip adjusted specifically for the sole purpose of wireless communication.
* Interfaced with using UART
*

ESP32-WROOM-32

  • uses UART To both receive and send data to other modules

Pros and Cons[edit]

Pros[edit]

Allows for convenient, easy to mount access to wireless communication. 
Easy to interface with, using UART in order to communicate data.

Cons[edit]

Bluetooth Modules[edit]

Component Selection[edit]

HC_05/HC_06[edit]

CYM4343W[edit]

 Contains both Bluetooth as well as Wifi protocols
 Uses UART for Bluetooth 
 Uses SDIO for wifi communication

Pros and Cons[edit]

Pros[edit]

  • Simple implementation with supported Code

Cons[edit]

  • Separate PCB Board interfaced with/ Not modular.

TODO[edit]

Look into the specific components of the Bluetooth modules to find ICS that can be easily used and interfaced with. Figure out how to interface with ESP32 software using STM32, how to send specific commands, etc.


Interfacing with Other Boards[edit]

Network Setup[edit]

Access Point[edit]

Set up one device as the master. Intended purpose of the CANdaddy. Host signal and allow other devices to connect using SSID and password. In the case of the ESP32, this is done through built in libraries that allow for  

Communication Protocol[edit]

Data Exchange[edit]