Merge branch 'master' of https://gitee.com/seankwok/m5-docs
|
After Width: | Height: | Size: 79 KiB |
|
After Width: | Height: | Size: 38 KiB |
|
After Width: | Height: | Size: 29 KiB |
|
After Width: | Height: | Size: 29 KiB |
@@ -100,7 +100,7 @@ var header = new Vue({
|
||||
},
|
||||
{
|
||||
name:'Blockly库',
|
||||
link:'/#/zh_CN/uiflow/uiflow_home_page?id=blockly'
|
||||
link:'/#/zh_CN/uiflow/uiflow_home_page?id=iotcloud'
|
||||
},
|
||||
{
|
||||
name:'Micropython APIs',
|
||||
@@ -239,7 +239,7 @@ var header = new Vue({
|
||||
},
|
||||
{
|
||||
name:'Blockly Collections',
|
||||
link:'/#/en/uiflow/uiflow_home_page?id=blockly'
|
||||
link:'/#/en/uiflow/uiflow_home_page?id=iotcloud'
|
||||
},
|
||||
{
|
||||
name:'Micropython APIs',
|
||||
@@ -542,6 +542,7 @@ var search = new Vue({
|
||||
computed: {
|
||||
SearchInputClass: function () {
|
||||
if(this.InputShowStatus){
|
||||
this.$refs.InputTarget.focus();
|
||||
this.SearchShowResult = true;
|
||||
return "transition: all ease .25s;width:330px;opacity:1;"
|
||||
}else{
|
||||
|
||||
@@ -406,6 +406,7 @@ The chip contains a high-performance, low power RISC-V ISA-based dual core 64-bi
|
||||
- **datasheet**
|
||||
- [MPU6886](https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/core/MPU-6886-000193%2Bv1.1_GHIC_en.pdf)
|
||||
- [SH200Q](https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/core/SH200Q_en.pdf)
|
||||
- [OV7740](https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/core/stickv/OV7740_datasheet.pdf)
|
||||
|
||||
- **Web page**
|
||||
- [Sipeed](https://maixpy.sipeed.com/en/)
|
||||
|
||||
@@ -6,13 +6,13 @@
|
||||
|
||||
## Description
|
||||
|
||||
**COM.LoRaWAN470** is a LoRaWAN communication module suitable for 470MHz frequency launched by M5Stack. The module adopts the Ai-Thinker Ra-07 module solution, which supports long-distance communication and has both ultra-low power consumption and high sensitivity. The module integrates the LoRaWAN protocol stack and adopts a serial communication interface (using AT command set for control), and can be used as a collection node to access a large number of gateways for data collection and management.
|
||||
**COM.LoRaWAN470** is a LoRaWAN communication module suitable for 470MHz frequency launched by M5Stack. The module adopts the ASR6501 solution, which supports long-distance communication and has both ultra-low power consumption and high sensitivity. The module integrates the LoRaWAN protocol stack and adopts a serial communication interface (using AT command set for control), and can be used as a collection node to access a large number of gateways for data collection and management.
|
||||
|
||||
An external power supply is provided (5V-12V input can be adjusted by switching the dial on-board switches). The module fits for long distance low power IoT communication applications, such as deployment of environmental monitoring nodes.
|
||||
|
||||
## Product Features
|
||||
|
||||
- Ai-Thinker Ra-07 module solution
|
||||
- ASR6501
|
||||
- Operating frequency: 470MHz
|
||||
- SMA antenna
|
||||
- Communication interface: UART
|
||||
|
||||
@@ -6,13 +6,13 @@
|
||||
|
||||
## Description
|
||||
|
||||
**COM.LoRaWAN915** is a LoRaWAN communication module suitable for 915MHz frequency launched by M5Stack. The module adopts the Ai-Thinker Ra-07H module solution, which supports long-distance communication and has both ultra-low power consumption and high sensitivity. The module integrates the LoRaWAN protocol stack and adopts a serial communication interface (using AT command set for control), and can be used as a collection node to access a large number of gateways for data collection and management.
|
||||
**COM.LoRaWAN915** is a LoRaWAN communication module suitable for 915MHz frequency launched by M5Stack. The module adopts the ASR6501 solution, which supports long-distance communication and has both ultra-low power consumption and high sensitivity. The module integrates the LoRaWAN protocol stack and adopts a serial communication interface (using AT command set for control), and can be used as a collection node to access a large number of gateways for data collection and management.
|
||||
|
||||
An external power supply is provided (5V-12V input can be adjusted by switching the dial on-board switches). The module fits for long distance low power IoT communication applications, such as deployment of environmental monitoring nodes.
|
||||
|
||||
## Product Features
|
||||
|
||||
- Ai-Thinker Ra-07H module solution
|
||||
- ASR6501
|
||||
- Operating frequency: 915MHz
|
||||
- SMA antenna
|
||||
- Communication interface: UART
|
||||
|
||||
@@ -94,6 +94,7 @@
|
||||
{"a":"/#/en/unit/gps", "img":"https://static-cdn.m5stack.com/image/m5-docs_homepage/unit/unit_gps_01.webp", "p":"GPS", "sku":"U032" ,"kw":"AT6558"},
|
||||
{"a":"/#/en/unit/rs485", "img":"https://static-cdn.m5stack.com/image/m5-docs_homepage/unit/unit_rs485_01.webp", "p":"RS485", "sku":"U034" ,"kw":"SP485EEN"},
|
||||
{"a":"/#/en/unit/rfid", "img":"https://static-cdn.m5stack.com/image/m5-docs_homepage/unit/unit_rfid_01.webp", "p":"RFID", "sku":"U031" ,"kw":"RC522"},
|
||||
{"a":"/#/en/unit/uhf_rfid", "img":"https://static-cdn.m5stack.com/image/m5-docs_homepage/unit/uhf_rfid_01.webp", "p":"UHF-RFID", "sku":"U107" ,"kw":"JRD-4035 840-960MHz"},
|
||||
{"a":"/#/en/unit/laser-rx", "img":"https://static-cdn.m5stack.com/image/m5-docs_homepage/unit/laser_rx_01.webp", "p":"LASER.RX", "sku":"U065" ,"kw":"LASER"},
|
||||
{"a":"/#/en/unit/laser-tx", "img":"https://static-cdn.m5stack.com/image/m5-docs_homepage/unit/laser_tx_01.webp", "p":"LASER.TX", "sku":"U066" ,"kw":"LASER"},
|
||||
{"a":"/#/en/unit/can", "img":"https://static-cdn.m5stack.com/image/m5-docs_homepage/unit/can.webp", "p":"CAN", "sku":"U085" ,"kw":"CAN"},
|
||||
|
||||
@@ -0,0 +1,105 @@
|
||||
# UIFlow-Access-Azure
|
||||
|
||||
## Overview
|
||||
|
||||
>This tutorial will take building a temperature and humidity collection node as an example to demonstrate how to access the Azure IoT cloud service platform through a UIFlow programming device.
|
||||
|
||||
## Create project
|
||||
|
||||
>Before accessing, you need to create an IoT center through the Azure portal and register a new device. [Click here to visit Azure official documentation for details](https://docs.microsoft.com/zh-cn/azure/iot-hub/iot-hub-create-through-portal)
|
||||
|
||||
<img src="/image/iotcloud/azure/azure_docs.webp" width="70%">
|
||||
|
||||
## Connection information
|
||||
|
||||
>After creating the device according to the official Azure documentation, before connecting to Azure IoT, we need to obtain two strings, namely `Primary Connection String` and `SAS Token`.
|
||||
|
||||
- Among them, `Primary Connection String`, we can directly see the device property interface (as shown in the figure below).
|
||||
|
||||
<img src="/image/iotcloud/azure/primary_connection_string.webp">
|
||||
|
||||
- [Click the link to see how to obtain SAS Token](https://docs.microsoft.com/zh-cn/azure/iot-hub/iot-hub-devguide-security#protocol-specifics)
|
||||
|
||||
|
||||
## Burn firmware
|
||||
|
||||
>Burn UIFlow firmware for your device (firmware requires v1.7.3 and above), click the corresponding document link below to view the detailed programming steps.
|
||||
|
||||
[UIFlow firmware burning steps](/zh_CN/quick_start/m5core/m5stack_core_get_started_MicroPython)
|
||||
|
||||
## Programming
|
||||
|
||||
- [Click to download the case program m5f file](https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/m5f/UIFlow-Azure-Core2.m5f), open the file in UiFlow, or follow Drag and drop the code block in the figure below.
|
||||
|
||||
>The data format uploaded in the case program is `JSON`, which can facilitate the subsequent expansion and transmission of data, such as extension to Power BI and other applications.
|
||||
|
||||
<img src="/image/iotcloud/azure/block_example.webp">
|
||||
|
||||
|
||||
```clike
|
||||
Connection String: "Primary Connection String"
|
||||
SAS Token: "SAS Token"
|
||||
|
||||
```
|
||||
|
||||
- Micropython API
|
||||
|
||||
```clike
|
||||
|
||||
from IoTcloud.Azure import Azure
|
||||
|
||||
def azure_fun(msg_data):
|
||||
global msg_count, temp, humid, up_msg, up_msg_str
|
||||
c2d_msg.set_text(str(msg_data))
|
||||
pass
|
||||
|
||||
azure = Azure(connection_string='xxxxxxx', sas_token='xxxxxxx')
|
||||
azure.subscribe(azure_fun)
|
||||
azure.start()
|
||||
|
||||
up_msg = {'messageId':msg_count,'deviceId':'UIFlow-Azure-Core2-Temp-Humid','Temperature':temp,'Humidity':humid}
|
||||
up_msg_str = json.dumps(up_msg)
|
||||
azure.publish(str(up_msg_str))
|
||||
|
||||
```
|
||||
|
||||
|
||||
## View device upload data
|
||||
|
||||
>After pushing the code to Core2, the device will start uploading data according to the content of the program. The way to view the data is not unique. This case will demonstrate the viewing of uploaded data through the Azure plug-in of VSCode. [Click to visit the VSCode download page](https://code.visualstudio.com/)
|
||||
|
||||
- Install Azure Tools plugin
|
||||
|
||||
<img src="/image/iotcloud/azure/azure_vscode_tool.webp">
|
||||
|
||||
- Install Azure IoT Hub plugin
|
||||
|
||||
<img src="/image/iotcloud/azure/azure_vscode_hub.webp">
|
||||
|
||||
|
||||
>After the installation is complete, press the shortcut key `shift`+`ctrl`+`p`, call the command line, call the command `Start Monitoring Built-in Event Endpoint` function, enter the corresponding key and confirm (the incoming password The key string can be in the Azure portal, `Iot Center`-`Settings`-`Built-in Endpoints`-`Event Center-Compatible Endpoints` ). You can see the temperature and humidity data uploaded by the device to the platform.
|
||||
|
||||
<img src="/image/iotcloud/azure/azure_vscode_endpoint.webp">
|
||||
|
||||
<img src="/image/iotcloud/azure/azure_vscode_endpoint_key.webp">
|
||||
|
||||
<img src="/image/iotcloud/azure/azure_vscode_start.webp">
|
||||
|
||||
## Send message to device
|
||||
|
||||
>Call the command line, call the command `Azure IoT Hub: Send C2D Message to Device`, and enter the `Primary Connection String` seen in the device properties interface (refer to the steps above).
|
||||
|
||||
<img src="/image/iotcloud/azure/azure_vscode_send.webp">
|
||||
|
||||
<img src="/image/iotcloud/azure/azure_vscode_key.webp">
|
||||
|
||||
>Select the **Device ID** of the device to be sent, and then enter the message to be sent, and the message can be sent to the device.
|
||||
|
||||
<img src="/image/iotcloud/azure/azure_vscode_device.webp">
|
||||
|
||||
<script>
|
||||
|
||||
anchor_search();
|
||||
scrollFunc();
|
||||
|
||||
</script>
|
||||
@@ -43,7 +43,8 @@ const quickstart = {
|
||||
const iotcloud = {
|
||||
'title':"IoT-Cloud",
|
||||
'item':{
|
||||
'Tencent':'#/en/uiflow/iotcloud/tencent'
|
||||
'Tencent':'#/en/uiflow/iotcloud/tencent',
|
||||
'Azure IoT':'#/en/uiflow/iotcloud/azure'
|
||||
},
|
||||
"id":"iotcloud"
|
||||
};
|
||||
|
||||
@@ -0,0 +1,251 @@
|
||||
# UHF-RFID
|
||||
|
||||
<el-tag effect="plain">SKU:U107</el-tag>
|
||||
|
||||
<div class="product_pic"><img src="assets/img/product_pics/unit/uhf_rfid/uhf_rfid_01.webp"><img src="assets/img/product_pics/unit/uhf_rfid/uhf_rfid_02.webp"><img src="assets/img/product_pics/unit/uhf_rfid/uhf_rfid_03.webp"></div>
|
||||
|
||||
## Description
|
||||
|
||||
**UHF-RFID** is an ultra-high frequency (UHF) embedded wireless radio frequency reader module. The JRD-4035 module solution with built-in ceramic antenna completely eliminates the technical uncertainty that ordinary UHF modules need to be equipped with additional antennas for users. Optimize the RF design to realize the low power consumption and high performance of the module, and the transmission power of 100MW can reach the effective distance of more than 1.5M. Use serial communication interface, cooperate with built-in encapsulated AT command set, realize plug and play, provide good development and use experience. It is suitable for application scenarios such as warehousing logistics management and smart retail, and meets the application requirements of monitoring and reading multiple product tags.
|
||||
|
||||
## Product Features
|
||||
|
||||
- Stable recognition distance 1.5m-2m
|
||||
- Working spectrum range: 840-960MHz
|
||||
- Air interface protocol:
|
||||
* EPCglobal UHF Class 1 Gen 2
|
||||
* ISO 18000-6C
|
||||
- UART communication interface (baud rate: 115200bps)
|
||||
- The buffer area can hold up to 200 tags
|
||||
- Tag recognition is sensitive and stable
|
||||
|
||||
## Contains
|
||||
|
||||
- 1x UHF-RFID
|
||||
- 1x HY2.0 cable (5CM)
|
||||
|
||||
## Application
|
||||
|
||||
- Warehouse logistics pallet management
|
||||
- Vehicle management
|
||||
- Smart retail
|
||||
|
||||
## Specifications
|
||||
|
||||
<table class="table-1">
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Specifications</th>
|
||||
<th>Parameters</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>Air interface protocol</td>
|
||||
<td>EPCglobal UHF Class 1 Gen 2 / ISO 18000-6C</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Work area support</td>
|
||||
<td>
|
||||
US, Canada and other regions following U.S.
|
||||
FCC. Europe and other regions following ETSI EN 302 208,
|
||||
Mainland China, Japan, Korea, Malaysia, Taiwan
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Working spectrum range</td>
|
||||
<td>840-960MHz</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Tag cache area</td>
|
||||
<td>200 tags</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Communication protocol</td>
|
||||
<td>UART (Baud rate: 115200bps)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Net weight</td>
|
||||
<td>41g</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Gross weight</td>
|
||||
<td>58.8g</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Product size</td>
|
||||
<td>56*48*11.5mm</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Package size</td>
|
||||
<td>88*61*21mm</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Shell material</td>
|
||||
<td>Plastic (PC )</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
## EasyLoader
|
||||
|
||||
- **Windows**
|
||||
- [UHF-RFID TEST](https://m5stack.oss-cn-shenzhen.aliyuncs.com/EasyLoader/Windows/UNIT/For%20M5Core/EasyLoader_UHF_RFID.exe)
|
||||
|
||||
## Pin mapping
|
||||
|
||||
**When connecting UHF-RFID Unit to PortC, the pin mapping is as follows**
|
||||
|
||||
<table>
|
||||
<tr><td>M5Core(PORT C)</td><td>GPIO16</td><td>GPIO17</td><td>5V</td><td>GND</td></tr>
|
||||
<tr><td>UHF-RFID Unit</td><td>TXD</td><td>RXD</td><td>5V</td><td>GND</td></tr>
|
||||
</table>
|
||||
|
||||
## Schematic
|
||||
|
||||
<img src="assets/img/product_pics/unit/uhf_rfid/uhf_rfid_sch.webp">
|
||||
|
||||
## Related Links
|
||||
|
||||
- [Firmware Communication Protocol](https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/unit/uhf_rfid/MagicRF%20M100%26QM100_Firmware_manual_cn.pdf)
|
||||
|
||||
## Example
|
||||
|
||||
### 1. Arduino
|
||||
|
||||
- [Click here to get the Arduino sample program](https://github.com/m5stack/M5-ProductExampleCodes/tree/master/Unit/UHF_RFID)
|
||||
|
||||
- Communication protocol instruction set
|
||||
|
||||
```clike
|
||||
|
||||
//0. Hardware version
|
||||
BB 00 03 00 01 00 04 7E
|
||||
|
||||
//1. Software version
|
||||
BB 00 03 00 01 01 05 7E
|
||||
|
||||
//2.manufacturers
|
||||
BB 00 03 00 01 02 06 7E
|
||||
|
||||
//3. Single polling instruction
|
||||
BB 00 22 00 00 22 7E
|
||||
|
||||
//4. Multiple polling instructions
|
||||
BB 00 27 00 03 22 27 10 83 7E
|
||||
|
||||
//5. Stop multiple polling instructions
|
||||
BB 00 28 00 00 28 7E
|
||||
|
||||
//6. Set the SELECT parameter instruction
|
||||
BB 00 0C 00 13 01 00 00 00 20 60 00 30 75 1F EB 70 5C 59 04 E3 D5 0D 70 AD 7E
|
||||
|
||||
//7. Get the SELECT parameter
|
||||
BB 00 0B 00 00 0B 7E
|
||||
|
||||
//8. Set the SELECT mode
|
||||
BB 00 12 00 01 01 14 7E
|
||||
|
||||
//9. Read label data storage area
|
||||
BB 00 39 00 09 00 00 FF FF 03 00 00 00 02 45 7E
|
||||
|
||||
//10. Write the label data store
|
||||
BB 00 49 00 0D 00 00 FF FF 03 00 00 00 02 12 34 56 78 6D 7E
|
||||
|
||||
//11. Lock the LOCK label data store
|
||||
BB 00 82 00 07 00 00 FF FF 02 00 80 09 7E,
|
||||
|
||||
//12. Inactivate the kill tag
|
||||
BB 00 65 00 04 00 00 FF FF 67 7E
|
||||
|
||||
//13. Set communication baud rate
|
||||
BB 00 11 00 02 00 C0 D3 7E
|
||||
|
||||
//14. Get parameters related to the Query command
|
||||
BB 00 0D 00 00 0D 7E
|
||||
|
||||
//15. Set the Query parameter
|
||||
BB 00 0E 00 02 10 20 40 7E
|
||||
|
||||
//16. Set up work area
|
||||
BB 00 07 00 01 01 09 7E
|
||||
|
||||
//17. Acquire work locations
|
||||
BB 00 08 00 00 08 7E
|
||||
|
||||
//18. Set up working channel
|
||||
BB 00 AB 00 01 01 AC 7E
|
||||
|
||||
//19. Get the working channel
|
||||
BB 00 AA 00 00 AA 7E
|
||||
|
||||
//20. Set to automatic frequency hopping mode
|
||||
BB 00 AD 00 01 FF AD 7E
|
||||
|
||||
//21. Insert the working channel
|
||||
BB 00 A9 00 06 05 01 02 03 04 05 C3 7E
|
||||
|
||||
//22. Acquire transmitting power
|
||||
BB 00 B7 00 00 B7 7E
|
||||
|
||||
//23. Set the transmitting power
|
||||
BB 00 B6 00 02 07 D0 8F 7E
|
||||
|
||||
//24. Set up transmitting continuous carrier
|
||||
BB 00 B0 00 01 FF B0 7E
|
||||
|
||||
//25. Gets the receiving demodulator parameters
|
||||
BB 00 F1 00 00 F1 7E
|
||||
|
||||
//26. Set the receiving demodulator parameters
|
||||
BB 00 F0 00 04 03 06 01 B0 AE 7E
|
||||
|
||||
//27. Test the RF input block signal
|
||||
BB 00 F2 00 00 F2 7E
|
||||
|
||||
//28. Test the RSSI signal at the RF input
|
||||
BB 00 F3 00 00 F3 7E
|
||||
|
||||
//30. Module hibernation
|
||||
00 BB 00 17 00 00 17 7E
|
||||
|
||||
//31. Idle hibernation time of module
|
||||
BB 00 1D 00 01 02 20 7E
|
||||
|
||||
//32. The IDLE mode
|
||||
BB 00 04 00 03 01 01 03 0C 7E
|
||||
|
||||
//33.NXP G2X label supports ReadProtect/Reset ReadProtect command
|
||||
BB 00 E1 00 05 00 00 FF FF 00 E4 7E
|
||||
|
||||
//34. The NXP G2X label supports the CHANGE EAS directive
|
||||
BB 00 E3 00 05 00 00 FF FF 01 E7 7E
|
||||
|
||||
//35. The NXP G2X tag supports the EAS_ALARM directive
|
||||
BB 00 E4 00 00 E4 7E
|
||||
|
||||
//36.NXP G2X label 16bits config-word
|
||||
BB 00 E0 00 06 00 00 FF FF 00 00 E4 7E
|
||||
|
||||
//37.Impinj Monza 4 Qt tags support Qt instructions
|
||||
BB 00 E5 00 08 00 00 FF FF 01 01 40 00 2D 7E
|
||||
|
||||
//38.The BlockPermalock directive permanently locks blocks of a user's Block
|
||||
BB 00 D3 00 0B 00 00 FF FF 01 03 00 00 01 07 00 E8 7E
|
||||
|
||||
```
|
||||
|
||||
## Video
|
||||
|
||||
<video width="500" controls>
|
||||
<source src="https://m5stack.oss-cn-shenzhen.aliyuncs.com/video/Product_example_video/Unit/UHF-RFID_VIDEO.mp4" type="video/mp4">
|
||||
</video>
|
||||
|
||||
<script>
|
||||
|
||||
var purchase_link ='https://m5stack.com/products/uhf-rfid-unit-jrd-4035';
|
||||
|
||||
anchor_search(purchase_link);
|
||||
scrollFunc();
|
||||
|
||||
</script>
|
||||
@@ -301,8 +301,9 @@ UNIT-V does not currently recognize all types of MicroSD cards. We have tested s
|
||||
|
||||
## Related Link
|
||||
|
||||
- **Web page** - [sipeed](https://maixpy.sipeed.com/en/)
|
||||
- **datasheet** - [K210](https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/core/kendryte_datasheet_en.pdf)
|
||||
- [maixpy docs](https://maixpy.sipeed.com/en/)
|
||||
- [K210 datasheet](https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/core/kendryte_datasheet_en.pdf)
|
||||
- [OV7740 datasheet](https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/core/stickv/OV7740_datasheet.pdf)
|
||||
|
||||
## PinMap
|
||||
|
||||
|
||||
|
After Width: | Height: | Size: 145 KiB |
|
After Width: | Height: | Size: 10 KiB |
|
After Width: | Height: | Size: 6.2 KiB |
|
After Width: | Height: | Size: 43 KiB |
|
After Width: | Height: | Size: 70 KiB |
|
After Width: | Height: | Size: 35 KiB |