You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 24, 2019. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+6-8Lines changed: 6 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -24,14 +24,12 @@ This document describes how to start using the mbed Client example application o
24
24
25
25
To run the example:
26
26
27
-
1. Go to the [mbed Device Connector website](http://connector-test.dev.mbed.com) and log in with your mbed.org account.
27
+
1. Go to the [mbed Device Connector website](https://connector.mbed.com) and log in with your mbed.org account.
28
28
29
29
2. Configure the mbed Client example program as needed. See the [Running and build instructions](#running-and-build-instructions) chapter for more information.
30
30
31
31
4. Build the application with yotta. See the [Running and build instructions](#running-and-build-instructions) chapter for more information.
32
32
33
-
5. Run the application from the command prompt. See the [Running the mbed Client Linux example](#running-the-mbed-client-linux-example) chapter for more information.
34
-
35
33
## Running and build instructions
36
34
### Review: building for two connection modes
37
35
@@ -71,7 +69,7 @@ First, made sure you've installed yotta and all necessary toolchains. See instru
71
69
72
70
- Set `MBED_SERVER_PORT` to `5684`.
73
71
74
-
C. Go to the [mbed Device Connector website](http://connector-test.dev.mbed.com).
72
+
C. Go to the [mbed Device Connector website](https://connector.mbed.com).
75
73
76
74
D. Go to **My devices>Security credentials**.
77
75
@@ -113,7 +111,7 @@ First, made sure you've installed yotta and all necessary toolchains. See instru
113
111
114
112
Ensure that you have the example application running on your Linux environment (see [Running the mbed Client Linux example](#running-the-mbed-client-linux-example)).
115
113
116
-
1. Go to the [mbed Device Connector website](http://connector-test.dev.mbed.com).
114
+
1. Go to the [mbed Device Connector website](https://connector.mbed.com).
117
115
118
116
2. Log in using your mbed account.
119
117
@@ -123,12 +121,12 @@ Ensure that you have the example application running on your Linux environment (
123
121
124
122
- Go to **mbed Device Connector>API Console**.
125
123
126
-
- Click the URL to create a request. For example: `http://ds-test.dev.mbed.com/v1/endpoints/mbed-linux-endpoint/Test/0/S?sync=true` creates a GET request to the static **/Test/0/S** resource.
127
-
124
+
- Click the URL to create a request. For example: `https://api.connector.mbed.com/v1/endpoints/mbed-linux-endpoint/Test/0/S?sync=true` creates a GET request to the static **/Test/0/S** resource.
128
125
- **/Test/0/D** represents the dynamic resource that the mbed Device Server can read. The example program automatically increments the resource's value every 10 seconds, displaying **Resource Value /Test/0/D : <Value>** on the console. The value starts from zero and the increments are steps of one.
129
-
130
126
- **/Test/0/S** represents the static resource that has a fixed value in the mbed Client.
131
127
132
128
**NOTE:** If you changed your endpoint's name (the variable `MBED_ENDPOINT_NAME` in `sources/security.h`) from the default `mbed-linux-endpoint`, you will need to change it in the above URLs as well.
133
129
130
+
For more information on the mbed Device Connector REST API, see help pages.
131
+
134
132
To stop and deregister the mbed Client example, you need to interrupt the program by pressing CTRL+C. This sends an unregister message to mDS. The console displays **Unregistering endpoint**. After a successful deregistration, the console displays **Unregistration done --> exiting** and terminates the program. Also, the endpoint disappears from the **Connected devices** list on the mbed Device Connector web UI.
0 commit comments