Set specific IP Address/Port
Overview
This code could be access via Cat.M1(BG96 module) of SK telecom network in Korea. Need a WIZnet IoT Shield BG96 board and development board. The code forked Daniel_Lee's mbed-os-example-cellular-BG96 repository(https://os.mbed.com/users/Daniel_Lee/code/mbed-os-example-cellular-BG96/) and added some features.
This example is known to work great on the following platforms:
Requirement
- FRDM-K64F or FRDM-K66F
- WIZnet IoT Shield BG96 board
- USIM card
Example functionality
This example showcases the following device functionality:
1. Import into Compiler
2. Compile and Program
3. If successfully connect to cellular networks(SKTelecom) then you can get below message
Device's Result
include the mbed library with this snippet
mbed-os-example-cellular Built: Sep 6 2019, 07:06:26 [MAIN], plmn: NULL Establishing connection M2Mnet(BG96) Power ON [00005500ms][INFO][CELL]: New CellularContext (20004120) [00005500ms][INFO][CELL]: CellularContext plmn NULL [00005501ms][INFO][CELL]: CellularContext connect [00006502ms][INFO][CELL]: Start connecting (timeout 1000 ms) [00006511ms][INFO][CELL]: RSSI unknown [00006519ms][INFO][CELL]: Modem ready [00006523ms][INFO][CELL]: RSSI unknown [00006523ms][INFO][CELL]: Setup SIM (timeout 1000 ms) [00006528ms][INFO][CELL]: SIM is ready [00006555ms][INFO][CELL]: RSSI unknown [00006563ms][INFO][CELL]: Network registration (timeout 1000 ms) [00006567ms][INFO][CELL]: Continue after 1 seconds [00006688ms][ERR ][CELL]: AT overflow [00007572ms][INFO][CELL]: RSSI unknown [00007578ms][INFO][CELL]: Registering network => Attaching network [00007582ms][INFO][CELL]: RSSI unknown [00007582ms][INFO][CELL]: Attaching network (timeout 1000 ms) [00007606ms][INFO][CELL]: Found PDP context 2 [00007609ms][INFO][CELL]: Activate PDP context 2 [00009626ms][INFO][CELL]: Found PDP context 2 Connection Established. [00009635ms][INFO][CELL]: Socket 0 open [00009741ms][INFO][CELL]: Socket 0 sent 4 bytes to 222.98.173.203 port 7878 TCP: Sent 4 Bytes to 222.98.173.203 [00010873ms][INFO][CELL]: Socket 0 recv 4 bytes [00011421ms][INFO][CELL]: Socket 0 closed Received from server 4 Bytes [00011421ms][INFO][CELL]: CellularContext disconnect() [00011422ms][INFO][CELL]: cb: CellularContext disconnected Success. Exiting
Server Result
Diff: README.md
- Revision:
- 26:348eec457e58
- Parent:
- 19:2cb9398aaf16
- Child:
- 28:232da3ce8a88
diff -r c891a7063581 -r 348eec457e58 README.md --- a/README.md Mon Nov 19 07:00:32 2018 +0000 +++ b/README.md Tue Nov 20 09:45:32 2018 +0000 @@ -6,11 +6,11 @@ This particular cellular application uses a cellular network and network-socket APIs that are part of [`mbed-os`](https://github.com/ARMmbed/mbed-os). -The program uses a [generic cellular modem driver](https://github.com/ARMmbed/mbed-os/tree/master/features/netsocket/cellular/generic_modem_driver) using an external IP stack (LWIP) standard 3GPP AT 27.007 AT commands to setup the cellular modem and registers to the network. +The program uses a [cellular modem driver](https://github.com/ARMmbed/mbed-os/tree/master/features/cellular/framework/API) using an external IP stack (LWIP) standard 3GPP AT 27.007 AT commands to setup the cellular modem and registers to the network. After registration, the driver opens a point-to-point protocol (PPP) pipe using LWIP with the cellular modem and connects to internet. This driver currently supports UART data connection type only between your cellular modem and MCU. -For more information on Arm Mbed OS cellular APIs and porting guide, please visit the [Mbed OS cellular API](https://os.mbed.com/docs/latest/reference/cellular-api.html) and [contributing documentation](https://os.mbed.com/docs/latest/reference/contributing-connectivity.html#cellularinterface). +For more information on Arm Mbed OS cellular APIs and porting guide, please visit the [Mbed OS cellular API](https://os.mbed.com/docs/latest/reference/cellular.html) and [contributing documentation](https://os.mbed.com/docs/latest/reference/contributing.html). ### Download the application @@ -88,11 +88,11 @@ ### Board support -The [generic cellular modem driver](https://github.com/ARMmbed/mbed-os/tree/master/features/netsocket/cellular/generic_modem_driver) this application uses was written using only a standard AT command set. It uses PPP with an Mbed-supported external IP stack. These abilities make the driver essentially generic, or nonvendor specific. However, this particular driver is for onboard-modem types. In other words, the modem exists on the Mbed Enabled target as opposed to plug-in modules (shields). For more details, please see our [Mbed OS cellular documentation](https://os.mbed.com/docs/latest/reference/cellular-api.html). +The [cellular modem driver](https://github.com/ARMmbed/mbed-os/tree/master/features/cellular/framework/API) in this example uses PPP with an Mbed-supported external IP stack. It supports targets when modem exists on the Mbed Enabled target as opposed to plug-in modules (shields). For more details, please see our [Mbed OS cellular documentation](https://os.mbed.com/docs/latest/reference/cellular-api.html). Currently supported boards with onboard modem chips are: -[u-blox C027](https://os.mbed.com/platforms/u-blox-C027/) +[u-blox C027](https://os.mbed.com/platforms/u-blox-C027/) [MultiTech MTS Dragonfly](https://os.mbed.com/platforms/MTS-Dragonfly/)