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
Copy file name to clipboardExpand all lines: docs/reference/technology/connectivity/cellular.md
+6-5Lines changed: 6 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -54,23 +54,24 @@ If you use an Mbed OS target and a separate cellular hosted module via a serial
54
54
]
55
55
}
56
56
57
-
You need to change the pin-names above to actual pins, such as D0 and D1, according to your Mbed target. You may also need to define MDMRTS and MDMCTS pins if you have RTS/CTS connected on UART. If RTC/CTS are not connected on UART then define MDMRTS and MDMCTS to 'NC'.
57
+
You need to change the pinnames above to actual pins, such as D0 and D1, according to your Mbed target. You may also need to define MDMRTS and MDMCTS pins if you have RTS and CTS connected on UART. If RTC and CTS are not connected on UART, then define MDMRTS and MDMCTS as `NC`.
58
58
59
59
### Cellular APIs
60
60
61
-
As an application developer, you should use and refer only to classes located under API folder. All the other classes have implementation details which are expected to change frequently.
61
+
As an application developer, you should use and refer only to classes located under API folder. All the other classes have implementation details that are expected to change frequently.
62
62
63
63
Cellular APIs are structured based on main functionalities:
64
64
65
-
-`CellularContext` is the main interface for application. Used to connect to operators APN.
65
+
-`CellularContext` is the main interface for the application. You can use it to connect to the operator's APN.
66
66
-`CellularNetwork` for cellular network features, such as registering and attaching to a network.
67
67
-`CellularPower` for cellular hosted module power control, such as enabling power save.
68
68
-`CellularInformation` to read the cellular hosted module type and firmware version.
69
69
-`CellularSIM` to enter the PIN code and other SIM management functions.
70
70
-`CellularSMS` to read and write SMS messages.
71
71
72
-
CellularContext class can be easily instantiated with `CellularContext::get_default_instance()` which opens `CellularDevice` and via device opens `CellularContext`. Opening `CellularContext` via `get_default_instance` uses default values from mbed_app.json.
73
-
Default values are not defined by default and must be overridden in mbed_app.json if they are needed:
72
+
You can instantiate the CellularContext class with `CellularContext::get_default_instance()`, which opens `CellularDevice` and, through the device, opens `CellularContext`. Opening `CellularContext` through `get_default_instance` uses values from `mbed_app.json`.
73
+
These values are not defined by default, and you must override them in `mbed_app.json` if you need them:
0 commit comments