Attach LTE-M issue with NRF9160 modem

[Adil]

I have successfully installed the drivers and downloaded the latest firmware version, but the connexion fails and I can not use the AT interfaces command for the modem controller as you can see in the screenshot below, can you please help me to fixe this issue

[Øyvind]

Hello, 

Thanks for reaching out, and sorry to hear about the issue. 

Are you working with the nRF9160 DK or Thingy:91? Have you programmed the latest version of the Asset Tracker, or the AT Client? Can you please take me through the steps you have followed?

Kind regards,
Øyvind

[Adil]

Hi,

i changed the SIM card, the Attach is working but when i tried a ping test it's failing 

Thanks and Regards,

Adil

[Adil]

Hello

I just want to ping test to the public address google 8.8.8.8, the module attaches is well to our Orange network, but I can not do the ping test, there is a way to do speedtest?

Thank you

Kind regards

Adil

[Øyvind]

You could have a look at the Modem Shell sample, available in the NCS v1.6.0-rc2 tag. This sample includes a ping function:

mosh:~$ ping
Usage: ping [optional options] -d destination

mandatory options:
  -d, --destination, [str] Name or IP address
optional options:
  -t, --timeout, [int]     Ping timeout in milliseconds
  -c, --count, [int]       The number of times to send the ping request
  -i, --interval, [int]    Interval between successive packet transmissions
                           in milliseconds
  -l, --length, [int]      Payload length to be sent
  -I, --cid, [int]         Use this option to bind pinging to specific CID.
                           See link cmd for interfaces
  -6, --ipv6,              Force IPv6 usage with the dual stack interfaces
  -h, --help,              Shows this help information

And iperf

mosh:~$ iperf3 --manual
Usage: iperf3 [-s|-c host] [options]
       iperf3 [-m|--manual] [-v|--version]

Server or Client:
  -p, --port      #         server port to listen on/connect to
  -f, --format   [kmgtKMGT] format to report: Kbits, Mbits, Gbits, Tbits
  -i, --interval  #         seconds between periodic throughput reports
  -B, --bind      <host>    bind to the interface associated with the address <host>
  -V, --verbose             more detailed output
  -J, --json                output in JSON format
  -d, --debug               emit debugging output
  -v, --version             show version information and quit  -m, --manual              show this message and quit
  -I, --interface <apn>     use this option to bind to PDN with specific APN.
      --pdn_id <pdn_id>     use this option to bind to PDN with actual PDN ID.

Server specific:
  -s, --server              run in server mode
  -1, --one-off             handle one client connection then exit

Client specific:
  -c, --client    <host>    run in client mode, connecting to <host>
  -u, --udp                 use UDP rather than TCP
  --connect-timeout #       timeout for control connection setup (ms)
  -b, --bitrate #[KMG][/#]  target bitrate in bits/sec (0 for unlimited)
                            (default 1 Mbit/sec for UDP, unlimited for TCP)
                            (optional slash and packet count for burst mode)
  -t, --time      #         time in seconds to transmit for (default 10 secs)
  -n, --bytes     #[KMG]    number of bytes to transmit (instead of -t)
  -k, --blockcount #[KMG]   number of blocks (packets) to transmit (instead of -t or -n)
  -l, --length    #[KMG]    length of buffer to read or write
                   (default 3540 Bytes for TCP, dynamic or 1200 for UDP)
  -R, --reverse             run in reverse mode (server sends, client receives)
  -2, --bidir               run in bidirectional mode.
  -4, --version4            only use IPv4
  -6, --version6            only use IPv6
  -O, --omit N              omit the first n seconds
  -T, --title str           prefix every output line with this string

[KMG] indicates options that support a K/M/G suffix for kilo-, mega-, or giga-

iperf Done.

Kind regards,
Øyvind

[Adil]

Dear colleague,

i don't find the Modem shell sample, below the application installed with nRF9160

Thanks and Regards,

Adil

[Øyvind]

Adil, 

The nRF Connect for Desktop is not same as the nRF Connect SDK (NCS). You will need to install NCS on you computer in order to access the relevant samples. That said, you can install NCS through nRF Connect for Desktop through the Toolchain Manager app. You will then need to install NCS v1.6.0-rc2:

Once installed you can open the IDE to test our samples using the "Open nRF Connect SDK project" under File. Follow the instructions given in our documentation

Kind regards,
Øyvind

[Adil]

Dear colleague,

i don't have the "Open IDE" icone, it's normal?

Thanks and Regards,

Adil

[Øyvind]

Hi Adil, 

This is often seen when the computer is behind a corporate firewall. Is it possible to try another open network or outside of office? Also, please make sure that your install path is as short as possible. 

Kind regards,
Øyvind

[Adil]

Hi,

I don't understand why the commands AT are not working for Data tests (Ping, Data HTTTP), the application are installed correctily and the Attach LTE-M under our network is OK, can you please check and help us the fix this issue

Thanks and Regards,

Adil

[Adil]

Hi,

The SMS is failing also, can you please check 

Thanks and Regards,

Adil

[Øyvind]

Adil, 

Please read our documentation.

Adil said:

I don't understand why the commands AT are not working for Data tests (Ping, Data HTTTP), the application are installed correctily and the Attach LTE-M under our network is OK, can you please check and help us the fix this issue

 You are currently running the Asset Tracker application which supports the AT Host, running a set of 3GPP standard commands. From the AT Command Reference Guide

"This document describes the AT commands used to control the modem in nRF91 Series devices. The nRF91 series AT command API enables modem control for firmware running in the application core on nRF91 series devices.

The AT command API can also be exposed on one of the nRF91 serial interfaces by programming appropriate firmware in the application core. The nRF Connect SDK contains examples of such proxy firmware that can be run stand-alone or as part of other firmware functionality in the nRF91 application core. The stand-alone example is called at_client. This way, an external MCU or computer can get access to the modem API either exclusively or in addition to application firmware running on the nRF91 itself.

The AT commands described in this document apply to all versions of the nRF9160 module hardware."

The nRF91 series AT commands do not support PING, data, HTTP.

The PING, DATA and HTTPCCON AT commands are available in the Serial LTE Modem application. This application sample uses a series of proprietary AT commands to let the nRF91 development kit operate as a Serial LTE Modem (SLM).

---

Please reprogram your device with the Serial LTE Modem or the Modem Shell.

If you are not able to do so, please reach out to your RSM.

Kind regards,
Øyvind

[Adil]

Hi,

Do you have video that shows how to configure the serial port?

Thanks and Regards,

Adil