I’ve gone through the Getting Started Guide, and have enabled the redCloud app with “app start redCloud”. I immediately get the correct values updated on AirVantage (GPS, IMU Gyro, & Acceleromter); however there are no further updates - unless I stop the app, and restart it. I’ve left it powered up for 24 hours with the redCloud app running, but still no further updates. However, if I stop and restart the app, I get another update.
Are updates supposed to be automatic? How long should there be between cloud updates? Do I need to change or activate a timer?
I’ve just tried “Configure Communication” on AirVantage. I set the heartbeat and status report for 15 minutes; then on the mangOH red system, I stopped, and restarted the redCloud app. This forced the 1st data upload to AirVantage as well as allow the communication configuration to be “Successful”. However, after 17 minutes, it still had not provided an additional update on the AirVantage dashboard. I’m still stuck.
I just tried something else (without success - but it may help someone help me resolve the issue). I noticed that my MangOH red system is listed as “Inventory” and not “Active” on the AirVantage portal. So, I tried to “Activate” it, but I received an error message (on AirVantage) that said “Offer is incompatible”. Is this because I’m using a “trial” version of AIrVantage? Do I need to “Activate” the device before it can periodically send data to portal? Do I need to upgrade my AirVantage portal? Or is the Getting Started trial version supposed to handle all these subscription and activation?
root@swi-mdm9x28-wp:~# cm data connect
Checking if device ‘rmnet_data0’ is up … ok
Routing inet … ok
Updating /etc/resolv.conf … ok
Updating /etc/resolv.conf … ok
Testing connection … root@swi-mdm9x28-wp:~#
Here is the logread -f | grep -i err for a couple of minutes
root@swi-mdm9x28-wp:~# logread -f | grep -i err
Jun 7 23:01:48 swi-mdm9x28-wp user.err kernel: [ 2445.943107] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
Jun 7 23:01:48 swi-mdm9x28-wp user.err kernel: [ 2445.958335] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
Jun 7 23:01:58 swi-mdm9x28-wp user.err kernel: [ 2455.942847] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
Jun 7 23:01:58 swi-mdm9x28-wp user.err kernel: [ 2455.957651] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
Jun 7 23:02:08 swi-mdm9x28-wp user.err kernel: [ 2465.943140] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
Jun 7 23:02:08 swi-mdm9x28-wp user.err kernel: [ 2465.957900] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
Jun 7 23:02:18 swi-mdm9x28-wp user.err kernel: [ 2475.943138] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
Jun 7 23:02:18 swi-mdm9x28-wp user.err kernel: [ 2475.957896] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
Jun 7 23:02:28 swi-mdm9x28-wp user.err kernel: [ 2485.941532] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x001363c8 OPER:0x00000090
Jun 7 23:02:28 swi-mdm9x28-wp user.err kernel: [ 2485.956346] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x001363c8 OPER:0x00000090
Jun 7 23:02:38 swi-mdm9x28-wp user.err kernel: [ 2495.943175] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
Jun 7 23:02:38 swi-mdm9x28-wp user.err kernel: [ 2495.957936] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
Jun 7 23:02:48 swi-mdm9x28-wp user.err kernel: [ 2505.942807] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
Jun 7 23:02:48 swi-mdm9x28-wp user.err kernel: [ 2505.957605] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
Jun 7 23:02:58 swi-mdm9x28-wp user.err kernel: [ 2515.943126] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
Jun 7 23:02:58 swi-mdm9x28-wp user.err kernel: [ 2515.957885] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
Jun 7 23:03:08 swi-mdm9x28-wp user.err kernel: [ 2525.943111] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
Jun 7 23:03:08 swi-mdm9x28-wp user.err kernel: [ 2525.957869] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
Jun 7 23:03:18 swi-mdm9x28-wp user.err kernel: [ 2535.943131] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
Jun 7 23:03:18 swi-mdm9x28-wp user.err kernel: [ 2535.957887] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
Jun 7 23:03:28 swi-mdm9x28-wp user.err kernel: [ 2545.942640] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
Jun 7 23:03:28 swi-mdm9x28-wp user.err kernel: [ 2545.957871] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
Jun 7 23:03:38 swi-mdm9x28-wp user.err kernel: [ 2555.943163] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
Jun 7 23:03:38 swi-mdm9x28-wp user.err kernel: [ 2555.957917] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
0x3a is a built in micro in the WP module. The nack message is due to the micro being in sleep mode when the modem tries to talk to it. So this is not a real error.
So far I cant see any real errors/issues.
Can you do the following:
a. dmesg -c
b. reboot your unit
c. dmesg > out.txt (send me this file)
d. logread -f > log.txt (send me this file).
e. snap shot of your AV window.
I’m making a little progress. Here are screenshots from AirVantage. I had configured the communications for 15 minutes as shown, with a template for all data. I now get an update every 15 minutes, but it does not contain any data - just a “Registration Update”. My next reply will contain the log.txt file you requested.
OK…your dmesg looks fine but logread doesnt…
I need more information for the following:
``Jun 9 21:52:25 swi-mdm9x28-wp user.crit Legato: CRT | avcDaemon[1425]/framework T=main | fdMonitor.c StopMonitoringFd() 182 | epoll_ctl(DEL) resulted in EBADF. Probably because fd 49 was closed before deleting FD Monitor ‘LWM2M Client’.
Thanks Ashish. Here is a 10 minute log file - as close to the reboot as I can get (to my limited knowledge), but before starting the redCloud app. log.txt (10.4 KB)
The SIM card is activated. I can Ping google. When I start the redCloud app, I do get an immediate update of data from the GPS, IMU, and Accelerometer (and the data is correct). On AirVantage, I can click on “Sync” and then when I stop and restart redCloud, I get a larger amount of data (I think 139 bytes), which includes all the info regarding the radio. Also, when the MangOH red board is connected to my laptop through the USB port, but before I have the VM running, I can Connect to the cellular connection through Windows 10; and browse the web. All this make me think that the SIM card is working fine.
The out.txt file I provided this last time is from after a reboot. I ran the command “logread >out.txt” as soon as I could SSH to the board. This is BEFORE doing anything else (like starting the redCloud app). Is it possible that the error message is from before everything has booted up? Should I run the command after waiting longer (maybe several minutes after bootup - or after starting the redCloud app)?
After following the “Getting Started” guide for a non-SierraWireless SIM (AT&T), I get NO data in the AirVantage account.
After modifying some of the AirVantage account settings (without any instructions), I was able to get the GPS, IMU, and Accelerometer data ONCE for each time that I “Start” the redCloud app. I can “Stop” and “Restart” the app, and get another set of data. The modifications that I’m making to AirVantage, is to create a Template and Dataset for the red MangOH WP7700 and apply them to my registered device on AirVantage. I’m just guessing at this - there is nothing in the mangOH red Getting Started manual that talks about this step. One point about the Template and Dataset - the AirVantage portal does NOT have the template for the exact version of firmware that I obtained with the leaf search command. The latest version from the leaf search is legato version 20.04.0, however the latest version on the AirVantage portal is version 19.07.0. While playing around on the AirVantage portal, I tried a “Synchronize” operation. When I look at the Synchronize status, I have several warnings (see attached image).
It almost seems that I need to get the AirVantage template and the mangOH red firmware version to be the same - but I’m just guessing here because there is nothing in the Getting Started Guide about this. I’m going down a rabbit hole, or am I onto something?
Since I have deviated from the “Getting Started” guide by making changes to AirVantage - let me remove those changes and start fresh. I’ll resend the logs as a fresh setup (without the AirVantage changes and by following the Getting Started guide).
