-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1 from Mediatek-Cloud/develop
整理並更改路徑名稱、複製到中文版
- Loading branch information
Showing
214 changed files
with
3,528 additions
and
57 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,32 +1,31 @@ | ||
# Summary | ||
|
||
* [Introduction](README.md) | ||
* [Key Concepts](key_concept/README.md) | ||
* [Key concepts](key_concept/README.md) | ||
* [Tutorial](tutorial/README.md) | ||
* [Getting Started](tutorial/getting_started.md) | ||
* [Create your first product](tutorial/create_your_first_product.md) | ||
* [Getting started](tutorial/getting_started.md) | ||
* [Create your first prototype](tutorial/create_your_first_prototype.md) | ||
* [Create your test device](tutorial/create_your_first_device.md) | ||
* [Manage your device](tutorial/manage_your_device.md) | ||
* [Manage test device](tutorial/manage_test_device.md) | ||
* [Manage your profile](tutorial/manage_your_profile.md) | ||
* [Implementing using LinkIt ONE (Aster 2502) development Board](tutorial/implementing_using_linkit_one.md) | ||
* [Implementing using LinkIt ONE (Aster 2502) development board](tutorial/implementing_using_linkit_one.md) | ||
* [Implementing using LinkIt Connect 7681 development board](tutorial/implementing_using_mt7681_development_board.md) | ||
* [Using Notification](tutorial/setting_notification.md) | ||
* [Managing Firmware](tutorial/managing_firmware.md) | ||
* [Using notification](tutorial/setting_notification.md) | ||
* [Managing firmware](tutorial/managing_firmware.md) | ||
* [Connect device](tutorial/connect_device.md) | ||
* [Create my michael device](tutorial/create_my_michael_device.md) | ||
* [Setting User Privilege](tutorial/28_using_notification.md) | ||
* [API References](api_references/README.md) | ||
* [DataPoints](api_references/data_read_write.md) | ||
* [upload DataPoint](api_references/uploaddatapoint.md) | ||
* [retrieve DataPoint](api_references/retrievedatapoint.md) | ||
* [Device Management](api_references/device_management.md) | ||
* [retrieve device Information](api_references/retrievedeviceinfo.md) | ||
* [register a device](api_references/registerdevice.md) | ||
* [deregsiter a device](api_references/deactivatedevice.md) | ||
* [get connection](api_references/getconnection.md) | ||
* [Setting user privilege](tutorial/setting_user_privilege.md) | ||
* [API references](api_references/README.md) | ||
* [Datapoint](api_references/datapoint.md) | ||
* [Upload datapoint](api_references/upload_datapoint.md) | ||
* [Retrieve datapoint](api_references/retrieve_datapoint.md) | ||
* [Device management](api_references/device_management.md) | ||
* [Retrieve device information](api_references/retrieve_device_info.md) | ||
* [Register a device](api_references/register_device.md) | ||
* [Deregsiter a device](api_references/deactivate_device.md) | ||
* [Get connection](api_references/get_connection.md) | ||
* [Data channel format](api_references/data_channel_format.md) | ||
* [Command server format](api_references/command_server_format.md) | ||
* [Mobile Application](6_mobile_application/README.md) | ||
* [Mobile application](mobile_application/README.md) | ||
* [FAQ](faq/README.md) | ||
* [Terms of Use](terms_of_use/README.md) | ||
* [Terms of use](terms_of_use/README.md) | ||
|
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
# 7681 Data format |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 changes: 1 addition & 1 deletion
2
content/en/api_references/commanddevice.md → content/en/api_references/command_device.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
# commandDevice | ||
# Command device | ||
|
||
### Description | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
# Command Read Write | ||
# Command read write |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
# Datapoint |
2 changes: 1 addition & 1 deletion
2
...ent/en/api_references/deactivatedevice.md → ...nt/en/api_references/deactivate_device.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
# deregisterDevice | ||
# Deregister device | ||
|
||
## Description | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
# Device Management | ||
# Device management |
2 changes: 1 addition & 1 deletion
2
content/en/api_references/getconnection.md → content/en/api_references/get_connection.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
# getConnection | ||
# Get connection | ||
|
||
|
||
## Description | ||
|
2 changes: 1 addition & 1 deletion
2
content/en/api_references/registerdevice.md → content/en/api_references/register_device.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
# registerDevice | ||
# Register device | ||
|
||
## Description | ||
|
||
|
2 changes: 1 addition & 1 deletion
2
...nt/en/api_references/retrievedatapoint.md → ...t/en/api_references/retrieve_datapoint.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
# retrieveDataPoint | ||
# Retrieve datapoint | ||
|
||
## Description | ||
|
||
|
2 changes: 1 addition & 1 deletion
2
...t/en/api_references/retrievedeviceinfo.md → ...en/api_references/retrieve_device_info.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
# retrieveDeviceInfo | ||
# Retrieve device information | ||
|
||
## Description | ||
|
||
|
2 changes: 1 addition & 1 deletion
2
content/en/api_references/uploaddatapoint.md → ...ent/en/api_references/upload_datapoint.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
# uploadDataPoint | ||
# Upload datapoint | ||
|
||
## Description | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
# Mobile application |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,56 @@ | ||
# Create your first protptype | ||
|
||
![](../images/content_img/content_img-08.jpg) | ||
|
||
## How to create a prototype step by step | ||
|
||
|
||
Step 1. Click Development on the top menu bar. | ||
|
||
Step 2. Click Create button to create a new prototype. | ||
|
||
|
||
![](../images/screenshot/screen_shot-01.jpg) | ||
|
||
|
||
|
||
Step 3. Enter the Prototype name, version, and select chip type, industry and Click Save button. Your Prototype is created. | ||
|
||
Step 4. Click Detail button of the prototype just created. | ||
|
||
|
||
![](../images/screenshot/screen_shot-02.jpg) | ||
|
||
|
||
After your prototype is created, you can start to set the data channel, notification, user privilege, create and view test devices in the prototype detail page. | ||
|
||
|
||
|
||
Step 5. Click Add in the data channel tab. | ||
|
||
![](../images/screenshot/screen_shot-03.jpg) | ||
|
||
|
||
|
||
Step 6. Select the Data Channel type. eg, Controller, Display, or Hybrid. And Click Add button. | ||
|
||
![](../images/screenshot/screen_shot-04.jpg) | ||
|
||
|
||
Step 7. Enter the Data Channel name, Id, description and select Data type. | ||
|
||
|
||
Step 8. Click Save button. And now you can start create test devices for the prototype! | ||
|
||
|
||
![](../images/screenshot/screen_shot-05.jpg) | ||
|
||
|
||
For more Data Channel and Data Type information and concept, please refer to the Key concept section for more detail. | ||
|
||
|
||
|
||
|
||
|
||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,21 +1,21 @@ | ||
# Using Notification | ||
# Using notification | ||
|
||
The user can set the notification for a data channel when its value pass the limit of the defined range. The user will get email notification and the GCM notification using the mobile application.Please be noted that MCS currently only support notification for integer and float data channel type. | ||
|
||
|
||
On the Prototype detail page, click on the **Notification** tab. | ||
|
||
![](https://raw.githubusercontent.com/Mediatek-Cloud/MCS/master/graphics/notification/not1.jpg) | ||
![](../images/notification/not1.jpg) | ||
|
||
CLick on the **Add notification** to enter the notification name and select the data channel you would like to set alert for. The rules include greater than, lower then, and equal to. | ||
|
||
![](https://raw.githubusercontent.com/Mediatek-Cloud/MCS/master/graphics/notification/not2.jpg) | ||
![](../images/notification/not2.jpg) | ||
|
||
Click Add button to save. | ||
|
||
To have more than one data channel rules in a notification rule, all data channel rules need to be satisfied to trigger the notification(AND logic). The user can create separate notification rules to have the OR loigic. | ||
|
||
![](https://raw.githubusercontent.com/Mediatek-Cloud/MCS/master/graphics/notification/not3.jpg) | ||
![](../images/notification/not3.jpg) | ||
|
||
The test device will inherit all the notification rules from its parent prototype. The notification in the device cannot be editted and it will by default in on state. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
# **MediaTek Cloud Sandbox introduction** | ||
|
||
MediaTek Cloud Sandbox(MCS) offers you the data and device management services commonly needed during the development and pre-commercial testing of Wearables and IoT devices. It frees you from having to develop your own cloud infrastructure to support prototype development. | ||
|
||
Using a RESTful API you collect data from your devices, which you can view in a powerful web-based dashboard that offers a range of display and graphing options. Then you can control your Wearables and IoT devices by issuing commands from the dashboard. In addition, a complementary smartphone app lets you review collected data and control your devices from anywhere. | ||
|
||
![](images/content01.jpg) | ||
|
||
MediaTek Cloud Sandbox lets you: | ||
|
||
- Define Wearables and IoT prototype profiles and individual devices within a profile | ||
- Push and Pull DataPoints between a device and the sandbox, using data types such as geo-location, temperature, humidity and more | ||
- Remotely control your devices using state DataPoints, such as switch-state and more | ||
- Visualize DataPoints graphically | ||
- Receive notifications when DataPoints are collected or change | ||
- Manage the life cycle of devices, as you would in your live implementation | ||
- Manage and control remotely, using the complementary mobile app | ||
- Create reports about prototypes, devices and collected data | ||
- Perform FOTA firmware updates | ||
- Control access to data and devices with granular security control | ||
|
||
To support the use of these features, MediaTek Cloud Sandbox provides an API sandbox, API reference, FAQ and set of tutorials to ensure you can quickly get up to speed with the use of its features and facilities. | ||
|
||
|
||
![](images/content_img/content_img-02.jpg) | ||
|
||
|
||
|
||
MediaTek Cloud Sandbox is currently in closed-beta. | ||
|
||
|
||
|
||
|
||
## **Prerequisites for Use** | ||
To make use of MediaTek Cloud Sandbox you must: | ||
1. [Register as a member of MediaTek Labs] (http://labs.mediatek.com/dpRegister/create) | ||
2. [Sign-in to the MediaTek Cloud Sandbox] (http://mcs.mediatek.io/v2console) | ||
3. Obtain a Device ID (API key) for each device added, for use in RESTful API calls |
Oops, something went wrong.