Unable to send or update Nova

I am unable to send or receive any messages from my Pi attached Nova. It appears to not be able to connect to the cloud server:
pi@raspberrypi:~ $ sudo hologram send --sms --devicekey ‘z8$M.q7U’ --destination +11234567890 ‘test again’ -vv
DEBUG: checking for vid_pid: (‘12d1’, ‘1506’)
DEBUG: checking for vid_pid: (‘12d1’, ‘1001’)
DEBUG: checking for vid_pid: (‘05c6’, ‘90b2’)
INFO: Detected modem NovaM
DEBUG: checking port ttyUSB0
DEBUG: checking port ttyUSB1
DEBUG: [AT]
DEBUG: {AT}
DEBUG: {OK}
INFO: found working port at ttyUSB1
INFO: chatscript file: /usr/local/lib/python2.7/dist-packages/Hologram/Network/Modem/chatscripts/default-script
DEBUG: [ATE0]
DEBUG: {ATE0}
DEBUG: {OK}
DEBUG: [AT+CMEE=2]
DEBUG: {}
DEBUG: {OK}
DEBUG: [AT+CPIN?]
DEBUG: {}
DEBUG: {+CPIN: READY}
DEBUG: {}
DEBUG: {OK}
DEBUG: [AT+CPMS=“ME”,“ME”,“ME”]
DEBUG: {}
DEBUG: {+CPMS: 1,23,1,23,1,23}
DEBUG: {}
DEBUG: {OK}
DEBUG: [AT+CMGF=0]
DEBUG: {}
DEBUG: {OK}
DEBUG: [AT+CNMI=2,1]
DEBUG: {}
DEBUG: {OK}
DEBUG: [AT+CEREG=2]
DEBUG: {}
DEBUG: {OK}
INFO: Instantiated a NovaM interface with device name of /dev/ttyUSB1
DEBUG: [AT+CGMM]
DEBUG: {}
DEBUG: {SARA-R410M-02B}
DEBUG: {}
DEBUG: {OK}
DEBUG: Destination number: +11234567890
DEBUG: SMS: test again
DEBUG: [AT+CEREG?]
DEBUG: {}
DEBUG: {+CEREG: 2,5,“D101”,“3312701”,8}
DEBUG: {}
DEBUG: {OK}
INFO: Connecting to: cloudsocket.hologram.io
INFO: Port: 9999
DEBUG: [AT+USOCR=6]
DEBUG: {}
DEBUG: {+USOCR: 0}
DEBUG: {}
DEBUG: {OK}
DEBUG: [AT+USOCO=0,“cloudsocket.hologram.io”,9999]
ERROR: Failed to connect socket
INFO: Disconnecting from cell network
INFO: Failed to disconnect from cell network
ERROR: Failed to connect socket

I also tried to update to the latest code and it also times out. Here is the info in the log file:

2019-11-08 09:34:44,567 - DEBUG - Started
2019-11-08 09:34:44,568 - DEBUG - Checking for confirmation
2019-11-08 09:34:48,022 - DEBUG - checking for vid_pid: ('12d1', '1506')
2019-11-08 09:34:48,049 - DEBUG - checking for vid_pid: ('12d1', '1001')
2019-11-08 09:34:48,069 - DEBUG - checking for vid_pid: ('05c6', '90b2')
2019-11-08 09:34:48,088 - INFO - Detected modem NovaM
2019-11-08 09:34:48,107 - DEBUG - checking port ttyUSB0
2019-11-08 09:34:48,111 - DEBUG - checking port ttyUSB1
2019-11-08 09:34:48,115 - DEBUG - [AT]
2019-11-08 09:34:48,117 - DEBUG - {}
2019-11-08 09:34:48,118 - DEBUG - {OK}
2019-11-08 09:34:48,118 - INFO - found working port at ttyUSB1
2019-11-08 09:34:48,119 - INFO - chatscript file: /usr/local/lib/python2.7/dist-packages/Hologram/Network/Modem/chatscripts/default-script
2019-11-08 09:34:48,122 - DEBUG - [ATE0]
2019-11-08 09:34:48,124 - DEBUG - {}
2019-11-08 09:34:48,125 - DEBUG - {OK}
2019-11-08 09:34:48,132 - DEBUG - [AT+CMEE=2]
2019-11-08 09:34:48,133 - DEBUG - {}
2019-11-08 09:34:48,133 - DEBUG - {OK}
2019-11-08 09:34:48,140 - DEBUG - [AT+CPIN?]
2019-11-08 09:34:48,142 - DEBUG - {}
2019-11-08 09:34:48,143 - DEBUG - {+CPIN: READY}
2019-11-08 09:34:48,143 - DEBUG - {}
2019-11-08 09:34:48,143 - DEBUG - {OK}
2019-11-08 09:34:48,150 - DEBUG - [AT+CPMS="ME","ME","ME"]
2019-11-08 09:34:48,152 - DEBUG - {}
2019-11-08 09:34:48,154 - DEBUG - {+CPMS: 1,23,1,23,1,23}
2019-11-08 09:34:48,154 - DEBUG - {}
2019-11-08 09:34:48,155 - DEBUG - {OK}
2019-11-08 09:34:48,161 - DEBUG - [AT+CMGF=0]
2019-11-08 09:34:48,163 - DEBUG - {}
2019-11-08 09:34:48,164 - DEBUG - {OK}
2019-11-08 09:34:48,170 - DEBUG - [AT+CNMI=2,1]
2019-11-08 09:34:48,172 - DEBUG - {}
2019-11-08 09:34:48,173 - DEBUG - {OK}
2019-11-08 09:34:48,180 - DEBUG - [AT+CEREG=2]
2019-11-08 09:34:48,182 - DEBUG - {}
2019-11-08 09:34:48,182 - DEBUG - {OK}
2019-11-08 09:34:48,182 - INFO - Instantiated a NovaM interface with device name of /dev/ttyUSB1
2019-11-08 09:34:48,183 - DEBUG - [AT+CGMM]
2019-11-08 09:34:48,185 - DEBUG - {}
2019-11-08 09:34:48,186 - DEBUG - {SARA-R410M-02B}
2019-11-08 09:34:48,186 - DEBUG - {}
2019-11-08 09:34:48,187 - DEBUG - {OK}
2019-11-08 09:34:48,187 - WARNING - Confirming modem type
2019-11-08 09:34:48,190 - DEBUG - [AT+CGMM]
2019-11-08 09:34:48,191 - DEBUG - {}
2019-11-08 09:34:48,192 - DEBUG - {SARA-R410M-02B}
2019-11-08 09:34:48,192 - DEBUG - {}
2019-11-08 09:34:48,193 - DEBUG - {OK}
2019-11-08 09:34:48,193 - WARNING - Checking current modem version
2019-11-08 09:34:48,194 - DEBUG - [ATI9]
2019-11-08 09:34:48,202 - DEBUG - {}
2019-11-08 09:34:48,203 - DEBUG - {L0.0.00.00.05.06,A.02.01}
2019-11-08 09:34:48,204 - DEBUG - {}
2019-11-08 09:34:48,204 - DEBUG - {OK}
2019-11-08 09:34:48,204 - WARNING - Got version L0.0.00.00.05.06,A.02.01
2019-11-08 09:34:48,206 - DEBUG - Removing existing firmware directory
2019-11-08 09:34:48,206 - DEBUG - making dir: /home/pi/hologram-tools/novaupdate/fw/0201
2019-11-08 09:34:48,207 - DEBUG - fw url: https://ublox-firmware.s3.amazonaws.com/L0506A0201-to-L0508A0204.zip
2019-11-08 09:34:48,213 - DEBUG - Starting new HTTPS connection (1): ublox-firmware.s3.amazonaws.com:443
2019-11-08 09:34:53,649 - DEBUG - https://ublox-firmware.s3.amazonaws.com:443 "GET /L0506A0201-to-L0508A0204.zip HTTP/1.1" 200 17308888

And it times out at this point.

Any help appreciated.

You might be running into this network issue: Open Network Issue With Cat-M

Try updating your Nova firmware as described in here:

Oh wait, sorry I missed that you already tried that. Let me reread your post

The firmware update should not be run over the cellular connection. Make sure your pi has a connection via wifi or ethernet before running.

Hi Reuben,

I have a wifi connection to the Pi and the default route is via the wifi interface:

pi@raspberrypi:~/hologram-tools/novaupdate $ ifconfig -a
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether b8:27:eb:79:e1:2d  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.251  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::dcf9:cf14:2a50:a63a  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:2c:b4:78  txqueuelen 1000  (Ethernet)
        RX packets 7338  bytes 2367890 (2.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 435  bytes 61511 (60.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wwan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 169.254.205.26  netmask 255.255.0.0  broadcast 169.254.255.255
        inet6 fe80::c409:6c1:2e3c:d290  prefixlen 64  scopeid 0x20<link>
        ether c6:6d:b9:10:d7:2c  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 120  dropped 0 overruns 0  carrier 0  collisions 0

pi@raspberrypi:~/hologram-tools/novaupdate $ netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG        0 0          0 wlan0
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 wwan0
192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 wlan0

And for fun I was able to manually download it using wget… Odd that it’d be trying via the cellular network in the updater script?

pi@raspberrypi:~/hologram-tools/novaupdate/fw/0201 $ sudo wget https://ublox-firmware.s3.amazonaws.com/L0506A0201-to-L0508A0204.zip
--2019-11-08 12:36:15--  https://ublox-firmware.s3.amazonaws.com/L0506A0201-to-L0508A0204.zip
Resolving ublox-firmware.s3.amazonaws.com (ublox-firmware.s3.amazonaws.com)... 52.216.92.19
Connecting to ublox-firmware.s3.amazonaws.com (ublox-firmware.s3.amazonaws.com)|52.216.92.19|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 17308888 (17M) [application/zip]
Saving to: ‘L0506A0201-to-L0508A0204.zip’

L0506A0201-to-L0508A0204.zip               100%[======================================================================================>]  16.51M   272KB/s    in 29s     

2019-11-08 12:36:44 (589 KB/s) - ‘L0506A0201-to-L0508A0204.zip’ saved [17308888/17308888]

Yeah I’m not sure what to make of that. The firmware updater doesn’t try to start up PPP or anything like that. Do you have any kind of separate modem manager running?

I was able to get the update to load after manually downloading it. Sending messages via SMS worked as well. Looks like that was the issue.

Thanks!

1 Like