Octave - mangOH yellow IP? connectivity issue - UK

Octave
1

I’m experiencing issues with what I think could be an IP connectivity issue . When I power the mangOH yellow I see radio level connectivity - but no data or messages arrive at the Octave cloud.

I don’t know if the below diagnostic methods are valid for Octave I’ve included them anyway.

Check connectivity via

root@swi-mdm9x28-wp:~# cm data
Index:                         1
APN:                           iot.swir
PDP Type:                      IPV4V6
Connected:                     no

root@swi-mdm9x28-wp:~# cm radio
Power:                         ON
Current Network Operator:      Sierra Wireless
Current RAT:                   GSM network (LE_MRC_RAT_GSM)
Status:                        Registered to a roaming network (LE_MRC_REG_ROAMING)
Signal:                        Very strong signal strength (5)
PS:                            Packet Switched Registered, home network (LE_MRC_REG_HOME)

Check the versions via AT commands

ati8
Legato Ver: 19.11.0_6d3414b175168e60f99d5bf05dc6a879
Yocto Ver:  SWI9X06Y_02.32.02.00 2020-01-30_00:30:56
OS Ver: Linux version 3.18.140 (oe-user@oe-host) (gcc version 7.3.0 (GCC) ) #1 PREEMPT Wed Jan 29 23:58:06 UTC 2020
LK Ver: SWI9X06Y_02.32.02.00
RootFS Ver: SWI9X06Y_02.32.02.00 2020-01-30_00:30:56
UserFS Ver: unknown
MCU Ver: 002.013

An Octave app

root@swi-mdm9x28-wp:~# app info cloudInterface
cloudInterface
  status: running
  running processes:
    cloudInterface[1571] (1571)
  app.name: cloudInterface
  app.md5: d38624da27e448da66ffe29e6215f7df
  app.version: 0.2.2
  legato.version: 19.11.0

image

Trying a manual IP connection

root@swi-mdm9x28-wp:~# cm data connect
Setting up profile 1
Connecting ... ok
Checking if device 'rmnet_data0' is up ... ok
Routing inet ... ok
Updating /etc/resolv.conf ... ok
Testing connection ... failed

Check the IP connection

root@swi-mdm9x28-wp:~# cm data
Index:                         1
APN:                           iot.swir
PDP Type:                      IPV4V6
Connected:                     yes
Interface:                     rmnet_data0
Family[IPv4]:                  inet
IP[IPv4]:                      10.16.1.253
Gateway[IPv4]:                 10.16.1.254
Dns1[IPv4]:                    52.17.142.62
Dns2[IPv4]:                    52.17.142.62

IP Link check

root@swi-mdm9x28-wp:~# ping 52.17.142.62
PING 52.17.142.62 (52.17.142.62): 56 data bytes
64 bytes from 52.17.142.62: seq=0 ttl=63 time=839.264 ms
64 bytes from 52.17.142.62: seq=1 ttl=63 time=239.086 ms

Check the current cellular network operator

Operator was “O2”

at
OK
at+cops?
+cops: 0,0,"O2 - UK Sierra Wireless",3

OK

Does this mean? - maybe not as below EE works and also returns “3”

<stat> 0 Unknown networks
1 Network available
2 Current (registered)
3 Forbidden network

Manually connect to EE cellular network

If I force the radio onto the EE network
and reboot

at+cops=1,2,23430

Reboot

at+cops?
+cops: 1,0,"EE Sierra Wireless",3

image

2

@johnofleek,

The 3 just indicates its on GSM with EDGE so its still attached and given you have an IP address tells me that there is an active data connection so there should not be any reason for the data to not be getting through.

Regards

Matt

3

Hi Matt

We didn’t find a description of the AT+COPS commands / responses in the WP7702 AT command manual.

Plundering the AirPrime_HL6_and_HL8_Series_AT_Commands_Interface_Guide_Rev16_0.pdf the HL76 manual and other internet resources - is the following correct?

Syntax
AT+COPS?

Response
+COPS: [,,[,< AcT>]]

Parameters
…

<AcT>

0 GSM
1 GSM Compact
2 UTRAN
3 GSM with EGPRS
4 UTRAN with HSDPA
5 UTRAN with HSUPA
6 UTRAN with HSDPA and HSUPA
7 E-UTRAN

Is this a complete list - are there any other possible values?

Does <AcT> mean Access Technology?

Which of the above <AcT> are supported by the WP7702?

4

As a follow up to my original post and to clarify my findings so far

For a few days my Octave Edge device with default settings was unable to communicate with the Octave cloud. It seems likely that the system would have recovered at the end of the problem period.

Summary of the original problem

The primary issue was that for a number of days Octave Edge was unable to communicate with Octave cloud until I forced the WP7702 module to a different cellular network provider (O2 -> EE).

This primary issue appeared to cause a secondary issue (This is best guess work on my part so could be wrong) where

  1. Octave was not automatically making an IP connection - although it was possible to make an IP connection manually
  2. If an IP connection was manually made (cm data connect) there would be no Octave data passed
  3. It was possible to ping an IP address in the Octave system - maybe indicating that WAN IP traffic was possible.

Summary of testing today 2020/03/18 10 am

Octave is now able to communicate Edge<>Cloud when connected via the UK “O2” network. The following is the process I followed

Check current network registration state
note that the radio had been manually locked to “EE” by using the COPS command

at+creg?
+CREG: 0,5

and the cops setting

at+cops?
+cops: 0,0,"EE Sierra Wireless",3

Switch the cops setting back to automatic

at+cops=0

Check for network registration

at+creg?
+CREG: 0,2

at+creg?
+CREG: 0,5

Check which cellular radio network was selected

at+cops?
+cops: 0,0,"O2 - UK Sierra Wireless",3

OK

The module is now communicating with Octave

image

Summary of testing today 2020/03/18 2.40 pm

Octave Edge / Octave Cloud data connectivity failed

We also observed a random reboot and a failure to boot.

Next step is to investigate the power supply path to the module.

Stage 1 - power the mangOH with a 5V 10A bench power supply via the expansion connector 5V CN805 PIN 1.

5

Step 1. power supply upgrade - didn’t fix the issue

Step 2. try an older FW version
After manually flashing the WP7702 to an older WP77xx / Octave edge version the mangOH yellow connected to the Octave cloud and remained connected (so far). The following info is for the older FW image

module-2.1.0.wp77xx.spk

Legato version
OTVMODULE2.1.0_03288fcd1015098878f8419aa0b052c6

I then tried using Octave FOTA to update the mangOH yellow from 2.1.0 to 2.1.3 but unfortunately this failed - details are here

Image of the older FW reported at the Octave cloud UI

image

Any ideas what to try next - I guess a manual load of 2.1.3 if we have the image?

6

Hi

This issue was resolved when I manually upgraded to a 2.1.3 WP770X image. Testing for over week without any observed problems.

I have just today successfully used FOTA to upgrade to 2.1.4 WP770x image and will continue testing.

I realise that running a WP770x image on a mangOH yellow is not ideal but it is useful for me because we are just testing ORP.

At some point I’ll run a parallel test on the 2.1.4 image for mangOH WP770x and add an update on this thread

1 Like