Nova USB Modem - RasPi - Not connecting

[ChrisCUVM]

I am having trouble with getting a RasPi to recognize and connect a Nova to the network. When I boot with the Nova plugged into one of the four USB ports on the RasPi, I do get the red power LED to come on, but no signal lights. Additional info below.

System Configuration:
SIM has been activated on Hologram Dashboard, RasPi 3 Model B V1.2, Debian 9. Cell Modem is a Nova, plugged into one of the four USB ports on the RasPi directly (not via a powered hub). Antenna is firmly connected. The only other USB device is a Logitech USB wireless keyboard/mouse combo. I am using a 2.4 A microsub power source to power the RasPi.

Downloads and Setup:
I have followed (this tutorial to do the following;

• Installed Hologram SDK, with no errors using:
• apt-get update
• curl -L hologram.io/python-install | bash

What isn’t clear to me is whether I need to do something with usb_modeswitch. The Nova appears to be recognized as a ttyACM not ttyUSB based on /dev lists below when it is plugged in and not. It seems like other tutorials dealing with another modem seem to focus on the usb_modeswitch step, but the tutorial above for the Nova does not.

Log of Commands and Outputs:

NOTE: All commands follow a sudo –i command.

Directly Following Boot with Nova Plugged in

root@SmartValvePi1:~# hologram version
0.6.1

root@SmartValvePi1:~# hologram modem signal
Signal strength: 99,99

root@SmartValvePi1:~# hologram modem location
ERROR: PDP Context setup failed
Location: Not Available

pi@SmartValvePi1:~ $ lsusb
Bus 001 Device 006: ID 1546:1102 U-Blox AG
Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@SmartValvePi1:~ $ ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::cea2:ae89:ad2f:73d6 prefixlen 64 scopeid 0x20
ether b8:27:eb:1e:3b:5b txqueuelen 1000 (Ethernet)
RX packets 5253 bytes 4432910 (4.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4612 bytes 1626620 (1.5 MiB)
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
loop txqueuelen 1 (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.12 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::a8e1:430d:7222:72c6 prefixlen 64 scopeid 0x20
ether b8:27:eb:4b:6e:0e txqueuelen 1000 (Ethernet)
RX packets 56 bytes 15395 (15.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 34 bytes 5588 (5.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

pi@SmartValvePi1:~ $ ls /dev
autofs loop6 ram2 tty2 tty48 uinput
block loop7 ram3 tty20 tty49 urandom
btrfs-control loop-control ram4 tty21 tty5 usb
bus mapper ram5 tty22 tty50 vc-cma
cachefiles mem ram6 tty23 tty51 vchiq
char memory_bandwidth ram7 tty24 tty52 vcio
console mmcblk0 ram8 tty25 tty53 vc-mem
cpu_dma_latency mmcblk0p1 ram9 tty26 tty54 vcs
cuse mmcblk0p10 random tty27 tty55 vcs1
disk mmcblk0p2 raw tty28 tty56 vcs2
fb0 mmcblk0p5 rfkill tty29 tty57 vcs3
fd mmcblk0p6 serial tty3 tty58 vcs4
full mmcblk0p7 serial1 tty30 tty59 vcs5
fuse mmcblk0p8 shm tty31 tty6 vcs6
gpiochip0 mmcblk0p9 snd tty32 tty60 vcs7
gpiochip1 mqueue stderr tty33 tty61 vcsa
gpiochip2 net stdin tty34 tty62 vcsa1
gpiomem network_latency stdout tty35 tty63 vcsa2
hidraw0 network_throughput tty tty36 tty7 vcsa3
hidraw1 null tty0 tty37 tty8 vcsa4
hwrng ppp tty1 tty38 tty9 vcsa5
initctl ptmx tty10 tty39 ttyACM0 vcsa6
input pts tty11 tty4 ttyACM1 vcsa7
kmsg ram0 tty12 tty40 ttyACM2 vcsm
log ram1 tty13 tty41 ttyACM3 vhci
loop0 ram10 tty14 tty42 ttyACM4 watchdog
loop1 ram11 tty15 tty43 ttyACM5 watchdog0
loop2 ram12 tty16 tty44 ttyACM6 zero
loop3 ram13 tty17 tty45 ttyAMA0
loop4 ram14 tty18 tty46 ttyprintk
loop5 ram15 tty19 tty47 uhid

pi@SmartValvePi1:~ $ dmesg
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.41-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #1023 SMP Tue Aug 8 16:00:15 BST 2017
…
[ 0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p7 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait splash plymouth.ignore-serial-consoles
…
[ 0.078149] hw-breakpoint: maximum watchpoint size is 8 bytes.
[ 0.078321] Serial: AMBA PL011 UART driver
[ 0.080220] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[ 0.080766] uart-pl011 3f201000.serial: could not find pctldev for node /soc/gpio@7e200000/uart0_pins, deferring probe
[ 0.150093] bcm2835-dma 3f007000.dma: DMA legacy API manager at bb80f000, dmachans=0x1
[ 0.151948] SCSI subsystem initialized
[ 0.152129] usbcore: registered new interface driver usbfs
[ 0.152230] usbcore: registered new interface driver hub
[ 0.152346] usbcore: registered new device driver usb
[ 0.159072] raspberrypi-firmware soc:firmware: Attached to firmware from 2017-08-08 12:01
[ 0.160595] clocksource: Switched to clocksource arch_sys_counter
[ 0.207748] VFS: Disk quotas dquot_6.6.0
[ 0.207858] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.208079] FS-Cache: Loaded
[ 0.208346] CacheFiles: Loaded
[ 0.220451] NET: Registered protocol family 2
[ 0.221389] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.221526] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.221737] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.221851] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.221918] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.222150] NET: Registered protocol family 1
[ 0.222585] RPC: Registered named UNIX socket transport module.
[ 0.222617] RPC: Registered udp transport module.
[ 0.222645] RPC: Registered tcp transport module.
[ 0.222672] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.223719] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
[ 0.226021] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[ 0.242053] FS-Cache: Netfs ‘nfs’ registered for caching
[ 0.243047] NFS: Registering the id_resolver key type
[ 0.243098] Key type id_resolver registered
[ 0.243126] Key type id_legacy registered
[ 0.245570] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[ 0.245714] io scheduler noop registered
[ 0.245744] io scheduler deadline registered (default)
[ 0.246068] io scheduler cfq registered
[ 0.251716] BCM2708FB: allocated DMA memory fa910000
[ 0.251769] BCM2708FB: allocated DMA channel 0 @ bb80f000
[ 0.302169] Console: switching to colour frame buffer device 228x61
[ 0.332709] bcm2835-rng 3f104000.rng: hwrng registered
[ 0.332968] vc-cma: Videocore CMA driver
[ 0.333089] vc-cma: vc_cma_base = 0x00000000
[ 0.333228] vc-cma: vc_cma_size = 0x00000000 (0 MiB)
[ 0.333384] vc-cma: vc_cma_initial = 0x00000000 (0 MiB)
[ 0.333743] vc-mem: phys_addr:0x00000000 mem_base=0x3dc00000 mem_size:0x3f000000(1008 MiB)
[ 0.349389] brd: module loaded
[ 0.358552] loop: module loaded
[ 0.358685] Loading iSCSI transport class v2.0-870.
[ 0.359383] usbcore: registered new interface driver smsc95xx
[ 0.359556] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[ 0.587794] Core Release: 2.80a
[ 0.587900] Setting default values for core params
[ 0.588069] Finished setting default values for core params
[ 0.788637] Using Buffer DMA mode
[ 0.788744] Periodic Transfer Interrupt Enhancement - disabled
[ 0.788911] Multiprocessor Interrupt Enhancement - disabled
[ 0.789073] OTG VER PARAM: 0, OTG VER FLAG: 0
[ 0.789214] Dedicated Tx FIFOs mode
[ 0.789685] WARN::dwc_otg_hcd_init:1032: FIQ DMA bounce buffers: virt = 0xba904000 dma = 0xfa904000 len=9024
[ 0.789984] FIQ FSM acceleration enabled for :
Non-periodic Split Transactions
Periodic Split Transactions
High-Speed Isochronous Endpoints
Interrupt/Control Split Transaction hack enabled
[ 0.790612] dwc_otg: Microframe scheduler enabled
[ 0.790664] WARN::hcd_init_fiq:459: FIQ on core 1 at 0x8058f7fc
[ 0.797432] WARN::hcd_init_fiq:460: FIQ ASM at 0x8058fb6c length 36
[ 0.804188] WARN::hcd_init_fiq:486: MPHI regs_base at 0xbb87a000
[ 0.810876] dwc_otg 3f980000.usb: DWC OTG Controller
[ 0.817642] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[ 0.824517] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
[ 0.831263] Init: Port Power? op_state=1
[ 0.837943] Init: Power Port (0)
[ 0.844675] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.851399] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.858093] usb usb1: Product: DWC OTG Controller
[ 0.864680] usb usb1: Manufacturer: Linux 4.9.41-v7+ dwc_otg_hcd
[ 0.871385] usb usb1: SerialNumber: 3f980000.usb
[ 0.878833] hub 1-0:1.0: USB hub found
[ 0.885581] hub 1-0:1.0: 1 port detected
[ 0.893004] dwc_otg: FIQ enabled
[ 0.893009] dwc_otg: NAK holdoff enabled
[ 0.893013] dwc_otg: FIQ split-transaction FSM enabled
[ 0.893026] Module dwc_common_port init
[ 0.893244] usbcore: registered new interface driver usb-storage
[ 0.900134] mousedev: PS/2 mouse device common for all mice
[ 0.907827] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
[ 0.914733] bcm2835-cpufreq: min=600000 max=1200000
[ 0.921750] sdhci: Secure Digital Host Controller Interface driver
[ 0.928349] sdhci: Copyright(c) Pierre Ossman
[ 0.935292] sdhost-bcm2835 3f202000.sdhost: could not get clk, deferring probe
[ 0.944296] mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe
[ 0.951201] sdhci-pltfm: SDHCI platform and OF driver helper
[ 0.960608] ledtrig-cpu: registered to indicate activity on CPUs
[ 0.967704] hidraw: raw HID events driver (C) Jiri Kosina
[ 0.974783] usbcore: registered new interface driver usbhid
[ 0.981611] usbhid: USB HID core driver
[ 0.989323] vchiq: vchiq_init_state: slot_zero = 0xba980000, is_master = 0
[ 0.998108] Initializing XFRM netlink socket
[ 1.005164] NET: Registered protocol family 17
[ 1.012189] Key type dns_resolver registered
[ 1.019570] Registering SWP/SWPB emulation handler
[ 1.027205] registered taskstats version 1
[ 1.034510] vc-sm: Videocore shared memory driver
[ 1.041588] [vc_sm_connected_init]: start
[ 1.048962] [vc_sm_connected_init]: end - returning 0
[ 1.061992] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
[ 1.070745] sdhost: log_buf @ ba907000 (fa907000)
[ 1.110720] Indeed it is in host mode hprt0 = 00021501
[ 1.150622] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[ 1.159930] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
[ 1.166979] mmc-bcm2835 3f300000.mmc: DMA channel allocated
[ 1.205168] random: fast init done
[ 1.247832] mmc0: host does not support reading read-only switch, assuming write-enable
[ 1.255182] of_cfs_init
[ 1.262360] of_cfs_init: OK
[ 1.269951] Waiting for root device /dev/mmcblk0p7…
[ 1.279203] mmc0: new high speed SDHC card at address 59b4
[ 1.290267] mmcblk0: mmc0:59b4 USD00 14.7 GiB
[ 1.305134] mmcblk0: p1 p2 < p5 p6 p7 p8 p9 p10 >
[ 1.310634] usb 1-1: new high-speed USB device number 2 using dwc_otg
[ 1.310768] Indeed it is in host mode hprt0 = 00001101
[ 1.327259] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[ 1.336476] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 1.344958] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 1.354602] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[ 1.393453] EXT4-fs (mmcblk0p7): INFO: recovery required on readonly filesystem
[ 1.400373] EXT4-fs (mmcblk0p7): write access will be enabled during recovery
[ 1.466652] mmc1: new high speed SDIO card at address 0001
[ 1.540885] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[ 1.547854] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.555797] hub 1-1:1.0: USB hub found
[ 1.562866] hub 1-1:1.0: 5 ports detected
[ 1.890678] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[ 2.020928] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[ 2.027879] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2.037744] smsc95xx v1.0.5
[ 2.134458] smsc95xx 1-1.1:1.0 eth0: register ‘smsc95xx’ at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:1e:3b:5b
[ 2.240631] usb 1-1.2: new full-speed USB device number 4 using dwc_otg
[ 2.375494] usb 1-1.2: New USB device found, idVendor=046d, idProduct=c534
[ 2.382798] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.390123] usb 1-1.2: Product: USB Receiver
[ 2.397315] usb 1-1.2: Manufacturer: Logitech
[ 2.411085] input: Logitech USB Receiver as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.0/0003:046D:C534.0001/input/input0
[ 2.442892] EXT4-fs (mmcblk0p7): recovery complete
[ 2.454488] EXT4-fs (mmcblk0p7): mounted filesystem with ordered data mode. Opts: (null)
[ 2.462137] VFS: Mounted root (ext4 filesystem) readonly on device 179:7.
[ 2.471092] devtmpfs: mounted
[ 2.480449] Freeing unused kernel memory: 1024K (80b00000 - 80c00000)
[ 2.488574] hid-generic 0003:046D:C534.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-3f980000.usb-1.2/input0
[ 2.504078] input: Logitech USB Receiver as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.1/0003:046D:C534.0002/input/input1
[ 2.581389] hid-generic 0003:046D:C534.0002: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-3f980000.usb-1.2/input1
[ 2.901687] systemd[1]: System time before build time, advancing clock.
[ 2.980644] usb 1-1.4: new high-speed USB device number 5 using dwc_otg
[ 3.024310] NET: Registered protocol family 10
[ 3.043192] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 3.084539] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[ 3.094048] systemd[1]: Detected architecture arm.
[ 3.111446] usb 1-1.4: New USB device found, idVendor=8087, idProduct=07ed
[ 3.111455] usb 1-1.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 3.158533] systemd[1]: Set hostname to .
[ 3.655356] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[ 3.675366] systemd[1]: Created slice System Slice.
[ 3.697440] systemd[1]: Mounting POSIX Message Queue File System…
[ 3.718233] systemd[1]: Created slice User and Session Slice.
[ 3.738582] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 3.759691] systemd[1]: Listening on udev Control Socket.
[ 3.797256] systemd[1]: Listening on udev Kernel Socket.
[ 3.840565] usb 1-1.4: USB disconnect, device number 5
[ 3.943237] i2c /dev entries driver
[ 8.230658] usb 1-1.4: new high-speed USB device number 6 using dwc_otg
[ 8.374689] usb 1-1.4: New USB device found, idVendor=1546, idProduct=1102
[ 8.374701] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 8.374707] usb 1-1.4: Product: u-blox Wireless Module
[ 8.374714] usb 1-1.4: Manufacturer: u-blox
[ 8.374722] usb 1-1.4: SerialNumber: 357520072304922
[ 8.723858] cdc_acm 1-1.4:1.0: ttyACM0: USB ACM device
[ 8.730176] cdc_acm 1-1.4:1.2: ttyACM1: USB ACM device
[ 8.737923] cdc_acm 1-1.4:1.4: ttyACM2: USB ACM device
[ 8.744371] cdc_acm 1-1.4:1.6: ttyACM3: USB ACM device
[ 8.748585] cdc_acm 1-1.4:1.8: ttyACM4: USB ACM device
[ 8.781495] cdc_acm 1-1.4:1.10: ttyACM5: USB ACM device
[ 8.785723] cdc_acm 1-1.4:1.12: ttyACM6: USB ACM device
[ 8.787632] usbcore: registered new interface driver cdc_acm
[ 8.787640] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 11.739258] EXT4-fs (mmcblk0p7): re-mounted. Opts: (null)
[ 11.842446] systemd-journald[130]: Received request to flush runtime journal from PID 1
[ 12.212201] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[ 12.760911] usbcore: registered new interface driver brcmfmac
[ 13.227354] random: crng init done
[ 13.235407] brcmfmac: Firmware version = wl0: Aug 7 2017 00:46:29 version 7.45.41.46 (r666254 CY) FWID 01-f8a78378
[ 16.888196] uart-pl011 3f201000.serial: no DMA platform data
[ 17.506967] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 17.507022] brcmfmac: power management disabled
[ 17.974233] smsc95xx 1-1.1:1.0 eth0: hardware isn’t capable of remote wakeup
[ 18.184654] Adding 102396k swap on /var/swap. Priority:-1 extents:1 across:102396k SSFS
[ 18.393446] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 19.577447] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[ 21.333751] Bluetooth: Core ver 2.22
[ 21.333814] NET: Registered protocol family 31
[ 21.333818] Bluetooth: HCI device and connection manager initialized
[ 21.333834] Bluetooth: HCI socket layer initialized
[ 21.333841] Bluetooth: L2CAP socket layer initialized
[ 21.333862] Bluetooth: SCO socket layer initialized
[ 21.349626] Bluetooth: HCI UART driver ver 2.3
[ 21.349633] Bluetooth: HCI UART protocol H4 registered
[ 21.349636] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 21.349743] Bluetooth: HCI UART protocol Broadcom registered
[ 21.574851] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 21.574860] Bluetooth: BNEP filters: protocol multicast
[ 21.574873] Bluetooth: BNEP socket layer initialized
[ 21.699195] Bluetooth: RFCOMM TTY layer initialized
[ 21.699217] Bluetooth: RFCOMM socket layer initialized
[ 21.699235] Bluetooth: RFCOMM ver 1.11
[ 23.001428] fuse init (API version 7.26)
[ 26.175627] FAT-fs (mmcblk0p9): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 26.273614] EXT4-fs (mmcblk0p8): recovery complete
[ 26.273627] EXT4-fs (mmcblk0p8): mounted filesystem with ordered data mode. Opts: (null)
[ 26.370958] EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: (null)
[ 26.487586] EXT4-fs (mmcblk0p10): recovery complete
[ 26.487600] EXT4-fs (mmcblk0p10): mounted filesystem with ordered data mode. Opts: (null)
pi@SmartValvePi1:~ $

Directly Following Removal of Nova from USB Port

dmesg: (truncated output)
[ 243.968449] usb 1-1.4: USB disconnect, device number 6

root@SmartValvePi1:~# lsusb
Bus 001 Device 010: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@SmartValvePi1:~#
console=tty1 root=/dev/mmcblk0p7 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait splash plymouth.ignore-serial-consoles

root@SmartValvePi1:~# ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::cea2:ae89:ad2f:73d6 prefixlen 64 scopeid 0x20
ether b8:27:eb:1e:3b:5b txqueuelen 1000 (Ethernet)
RX packets 8902 bytes 5433065 (5.1 MiB)
RX errors 0 dropped 2 overruns 0 frame 0
TX packets 7494 bytes 2745146 (2.6 MiB)
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
loop txqueuelen 1 (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.12 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::a8e1:430d:7222:72c6 prefixlen 64 scopeid 0x20
ether b8:27:eb:4b:6e:0e txqueuelen 1000 (Ethernet)
RX packets 350 bytes 99677 (97.3 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 45 bytes 7095 (6.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

root@SmartValvePi1:~#

root@SmartValvePi1:~# ls /dev
autofs loop5 ram14 tty18 tty45 vc-cma
block loop6 ram15 tty19 tty46 vchiq
btrfs-control loop7 ram2 tty2 tty47 vcio
bus loop-control ram3 tty20 tty48 vc-mem
cachefiles mapper ram4 tty21 tty49 vcs
char mem ram5 tty22 tty5 vcs1
console memory_bandwidth ram6 tty23 tty50 vcs2
cpu_dma_latency mmcblk0 ram7 tty24 tty51 vcs3
cuse mmcblk0p1 ram8 tty25 tty52 vcs4
disk mmcblk0p10 ram9 tty26 tty53 vcs5
fb0 mmcblk0p2 random tty27 tty54 vcs6
fd mmcblk0p5 raw tty28 tty55 vcs7
full mmcblk0p6 rfkill tty29 tty56 vcsa
fuse mmcblk0p7 serial1 tty3 tty57 vcsa1
gpiochip0 mmcblk0p8 shm tty30 tty58 vcsa2
gpiochip1 mmcblk0p9 snd tty31 tty59 vcsa3
gpiochip2 mqueue stderr tty32 tty6 vcsa4
gpiomem net stdin tty33 tty60 vcsa5
hidraw0 network_latency stdout tty34 tty61 vcsa6
hidraw1 network_throughput tty tty35 tty62 vcsa7
hwrng null tty0 tty36 tty63 vcsm
initctl ppp tty1 tty37 tty7 vhci
input ptmx tty10 tty38 tty8 watchdog
kmsg pts tty11 tty39 tty9 watchdog0
log ram0 tty12 tty4 ttyAMA0 zero
loop0 ram1 tty13 tty40 ttyprintk
loop1 ram10 tty14 tty41 uhid
loop2 ram11 tty15 tty42 uinput
loop3 ram12 tty16 tty43 urandom
loop4 ram13 tty17 tty44 usb
root@SmartValvePi1:~#

Directly Following Replacement of Nova in USB port (no reboot)

root@SmartValvePi1:~# hologram version
0.6.1

root@SmartValvePi1:~# hologram modem signal
Signal strength: 99,99

root@SmartValvePi1:~# hologram modem location
ERROR: PDP Context setup failed
Location: Not Available

root@SmartValvePi1:~# lsusb
Bus 001 Device 012: ID 1546:1102 U-Blox AG
Bus 001 Device 010: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@SmartValvePi1:~#
root@SmartValvePi1:~# ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::cea2:ae89:ad2f:73d6 prefixlen 64 scopeid 0x20
ether b8:27:eb:1e:3b:5b txqueuelen 1000 (Ethernet)
RX packets 8682 bytes 5391836 (5.1 MiB)
RX errors 0 dropped 2 overruns 0 frame 0
TX packets 7341 bytes 2608128 (2.4 MiB)
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
loop txqueuelen 1 (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.12 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::a8e1:430d:7222:72c6 prefixlen 64 scopeid 0x20
ether b8:27:eb:4b:6e:0e txqueuelen 1000 (Ethernet)
RX packets 312 bytes 87415 (85.3 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 45 bytes 7095 (6.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

root@SmartValvePi1:~#

root@SmartValvePi1:~# ls /dev
autofs loop6 ram2 tty2 tty48 uinput
block loop7 ram3 tty20 tty49 urandom
btrfs-control loop-control ram4 tty21 tty5 usb
bus mapper ram5 tty22 tty50 vc-cma
cachefiles mem ram6 tty23 tty51 vchiq
char memory_bandwidth ram7 tty24 tty52 vcio
console mmcblk0 ram8 tty25 tty53 vc-mem
cpu_dma_latency mmcblk0p1 ram9 tty26 tty54 vcs
cuse mmcblk0p10 random tty27 tty55 vcs1
disk mmcblk0p2 raw tty28 tty56 vcs2
fb0 mmcblk0p5 rfkill tty29 tty57 vcs3
fd mmcblk0p6 serial tty3 tty58 vcs4
full mmcblk0p7 serial1 tty30 tty59 vcs5
fuse mmcblk0p8 shm tty31 tty6 vcs6
gpiochip0 mmcblk0p9 snd tty32 tty60 vcs7
gpiochip1 mqueue stderr tty33 tty61 vcsa
gpiochip2 net stdin tty34 tty62 vcsa1
gpiomem network_latency stdout tty35 tty63 vcsa2
hidraw0 network_throughput tty tty36 tty7 vcsa3
hidraw1 null tty0 tty37 tty8 vcsa4
hwrng ppp tty1 tty38 tty9 vcsa5
initctl ptmx tty10 tty39 ttyACM0 vcsa6
input pts tty11 tty4 ttyACM1 vcsa7
kmsg ram0 tty12 tty40 ttyACM2 vcsm
log ram1 tty13 tty41 ttyACM3 vhci
loop0 ram10 tty14 tty42 ttyACM4 watchdog
loop1 ram11 tty15 tty43 ttyACM5 watchdog0
loop2 ram12 tty16 tty44 ttyACM6 zero
loop3 ram13 tty17 tty45 ttyAMA0
loop4 ram14 tty18 tty46 ttyprintk
loop5 ram15 tty19 tty47 uhid
root@SmartValvePi1:~#

[ 320.966531] usb 1-1.2: new full-speed USB device number 7 using dwc_otg
[ 321.101406] usb 1-1.2: New USB device found, idVendor=046d, idProduct=c534
[ 321.101421] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 321.101429] usb 1-1.2: Product: USB Receiver
[ 321.101437] usb 1-1.2: Manufacturer: Logitech
[ 321.107355] input: Logitech USB Receiver as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.0/0003:046D:C534.0003/input/input2
[ 321.177779] hid-generic 0003:046D:C534.0003: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-3f980000.usb-1.2/input0
[ 321.185463] input: Logitech USB Receiver as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.1/0003:046D:C534.0004/input/input3
[ 321.247481] hid-generic 0003:046D:C534.0004: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-3f980000.usb-1.2/input1
[ 321.696432] usb 1-1.4: new high-speed USB device number 8 using dwc_otg
[ 321.827274] usb 1-1.4: New USB device found, idVendor=8087, idProduct=07ed
[ 321.827289] usb 1-1.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 322.560545] usb 1-1.4: USB disconnect, device number 8
[ 326.956372] usb 1-1.4: new high-speed USB device number 9 using dwc_otg
[ 327.100527] usb 1-1.4: New USB device found, idVendor=1546, idProduct=1102
[ 327.100537] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 327.100541] usb 1-1.4: Product: u-blox Wireless Module
[ 327.100547] usb 1-1.4: Manufacturer: u-blox
[ 327.100551] usb 1-1.4: SerialNumber: 357520072304922
[ 327.139678] cdc_acm 1-1.4:1.0: ttyACM0: USB ACM device
[ 327.142360] cdc_acm 1-1.4:1.2: ttyACM1: USB ACM device
[ 327.145070] cdc_acm 1-1.4:1.4: ttyACM2: USB ACM device
[ 327.148081] cdc_acm 1-1.4:1.6: ttyACM3: USB ACM device
[ 327.150551] cdc_acm 1-1.4:1.8: ttyACM4: USB ACM device
[ 327.153370] cdc_acm 1-1.4:1.10: ttyACM5: USB ACM device
[ 327.155923] cdc_acm 1-1.4:1.12: ttyACM6: USB ACM device

[ChrisCUVM]

I read this replicate and it mentioned having to force a connection with the hologram command line. So I checked that out. And then learned I could get more info using the command

sudo hologram modem connect -v

The result:

INFO: Detected modem Nova
INFO: found working port at /dev/ttyACM0
INFO: chatscript file: /usr/local/lib/python2.7/dist-packages/Hologram/Network/Modem/chatscripts/default-script
INFO: Instantiated a Nova interface with device name of /dev/ttyACM0
INFO: Connecting to cell network with timeout of 200 seconds
INFO: Checking for existing PPP sessions
INFO: Found existing PPP session on pid: 972
ERROR: Existing PPP session(s) are established by pid(s) [972]. Please close/kill these processes first

Process 972 is:

    root       972  0.0  0.2   3992  2160 pts/0    T    01:28   0:00 /usr/sbin/pppd connect /usr/sbin/chat -v -f /usr/local/lib/python2.7/dist-packa

I’m not sure what that is or how it got started.

I tried killing the process and was able to. Then I ran into another process conflict with PPP:

root       967  0.0  0.3   7224  3372 pts/0    T    01:28   0:00 /usr/bin/sudo /usr/sbin/pppd connect /usr/sbin/chat -v -f /usr/local/lib/python

Killed that one also.

Running a sudo hologram modem connect -v again…

INFO: Detected modem Nova
INFO: found working port at /dev/ttyACM0
INFO: chatscript file: /usr/local/lib/python2.7/dist-packages/Hologram/Network/Modem/chatscripts/default-script
INFO: Instantiated a Nova interface with device name of /dev/ttyACM0
INFO: Connecting to cell network with timeout of 200 seconds
INFO: Checking for existing PPP sessions
INFO: Failed to connect to cell network

I’m puzzled why the Nova is showing up as a ttyACM_ device.

Has anyone else out there been successful with a Nova (uBlox) on RasPi 3 B v1.2? If so, can you post some lsusb, dev info, or a ‘-v’ connect output to help me out?

[Brad_Gibson]

Did you ever find a solution to this issue? I think I have the same issue.

pi@sumpi2:~ $ sudo hologram modem connect -v
INFO: Detected modem Nova_U201
INFO: found working port at /dev/ttyACM0
INFO: chatscript file: /usr/local/lib/python2.7/dist-packages/Hologram/Network/Modem/chatscripts/default-script
INFO: Instantiated a Nova_U201 interface with device name of /dev/ttyACM0
INFO: Connecting to cell network with timeout of 200 seconds
INFO: Checking for existing PPP sessions
INFO: Failed to connect to cell network

pi@sumpi2:~ $ lsusb
Bus 001 Device 006: ID 1546:1102 U-Blox AG
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Thanks,
Brad

[ming]

In my experiences, there are two possible causes for “PDP context setup failure”:

1. you have not yet activated your Hologram Sim card. If not done yet, you need to create your Hologram Dashboard account, add your device (a device here means your SIM card), take a data plan for your device. I just choose the free developer 1MB data monthly, I have being working on Hologram Nova since a week, only consumed 7kB, so it is enough for your testing.
2. you forgot to connect the antenna to your Hologram Nova. There are two of them out of the box, I picked the shorter one and it provides a very good signal reception/transmission. Without antenna, your Nova may be well configured (proof is your hologram recognize the modem and lsusb has well listed “U-Blox AG”), but your data won’t reach the cellular tower and won’t go to the Holo Cloud.

One more thing is the “”/dev/ttyACM0" in the discussion is a normal behaviour: when you run “sudo hologram modem …”, you specifically want to use Holo Nova as a modem, in this setup your Raspberry Pi actually communicate with Holo Nova through a serial connection over USB. Here is my log with my Holo Nova in a working state (sudo hologram send “hi” is working):
pi@raspberrypi:~ $ sudo hologram modem connect -v
INFO: Detected modem Nova_U201
INFO: found working port at /dev/ttyACM0
INFO: chatscript file: /usr/local/lib/python2.7/dist-packages/Hologram/Network/Modem/chatscripts/default-script
INFO: Instantiated a Nova_U201 interface with device name of /dev/ttyACM0
INFO: Connecting to cell network with timeout of 200 seconds
INFO: Checking for existing PPP sessions
INFO: Rerouting packets to ppp0 interface
INFO: found working port at /dev/ttyACM1
INFO: Successfully connected to cell network
pi@raspberrypi:~ $

When Holo Nova is correctly installed, configured and SIM card activated, I have:
pi@raspberrypi:~ $ sudo hologram send “hi to me 20”
RESPONSE MESSAGE: Message sent successfully

To check the reception in Cloud, go to your https://dashboard.hologram.io, click on your device (mine is #158411),
then click on “LOGS” below “Usage report” to see the received “hi to me 20”.

Hope this helps and it works out for you too.

[ChrisCUVM]

The solution I found was to make a second boot sim using raspbian 9.1 (stretch) without any desktop. This seems much more well suited to using the Nova. All modem commands work and the connection is very stable. I also noted that there can be no Ethernet or wifi connection when trying to use the Nova. Would love for someone else to confirm this. I.e., is it possible to send certain traffic to the cell modem and other traffic via wifi or Ethernet?

[nitish91]

Hey Brad,

Did you find a solution to this? I have the same issue.

It would be great if you can help me out!

Thanks

[nitish91]

Hey Chris,

I followed your solution and burned a latest raspbian stretch (without desktop) on a new SD card. Installed the hologram SDK and inserted the Nova. But I only get the red solid light and not the blue one.

Do you have any alternate solution?

Thanks!!

[ChrisCUVM]

These are the steps I followed:

1. Fresh SD with Raspbian 9.1 (stretch) without any desktop
2. sudo apt-get update
3. curl -L hologram.io/python-install | bash
4. sudo hologram modem connect -v

[Don_Mitchinson]

Hey Chris:
Can you confirm that your modem is not recognized - and no blue light - when connected to Ethernet?
I can confirm that it DOES work in parallel with WiFi connection, but my current setup with Ethernet
doesn’t show blue light and comes back with “Modem not detected” if I try the “sudo hologram modem signal” command

Just a note that when I did change my wpa_supplicant to accept new wifi - it started working again - and I didn’t have to unplug or disable ethernet

[Don_Mitchinson]

I confirmed that it was very problematic with both Ethernet + WiFi connected - but is very stable with just WiFi - haven’t tried with just Ethernet - but it kind of makes sense as Ethernet uses USB bus. Probably have to treat it similar to Huwaei modems

[ChrisCUVM]

Thanks Don.

[rockman55]

Hey Chris ,
Did you place the files ssh and wpa_supplicant.conf in the /boot folder before starting up your install?
Thanks

[ChrisCUVM]

I did not. That is only needed for accessing the RasPi over wifi I believe. I hooked up a monitor and keyboard and worked locally.

[ChrisCUVM]

@Don_Mitchinson

Probably have to treat it similar to Huwaei modems

Don, what do you mean specifically by treat it like Huwaei modems?

[Don_Mitchinson]

I really don’t know - that was a while ago and I think I had been looking at instructions for using Huwaei modems as an Internet connection - it looks like you’re not using WiFi or Ethernet?
Maybe I was assuming too much or trying to associate documentation to a different problem than yours?

If you need me to check results from mine to troubleshoot yours let me know.

I use WiFi only for Internet - and the Nova just for receiving texts - not sending. But maybe my device setup will help?

[benstr]

Hey all,

Sorry, our support team did not chime in sooner. Let me run through the issues you have mentioned in the comments above.

@ChrisCUVM

Signal strength: 99,99

This means your modem does not have any tower signal. Either you are in a dead zone or the antenna is not attached. We’ve seen rare occasions where full network propagation of newly activated SIMs took up to an hour. That would also result in 99999 results.

@ChrisCUVM

sudo hologram modem connect -v

The result:

INFO: Detected modem Nova
INFO: found working port at /dev/ttyACM0
INFO: chatscript file: /usr/local/lib/python2.7/dist-packages/Hologram/Network/Modem/chatscripts/default-script
INFO: Instantiated a Nova interface with device name of /dev/ttyACM0
INFO: Connecting to cell network with timeout of 200 seconds
INFO: Checking for existing PPP sessions
INFO: Found existing PPP session on pid: 972
ERROR: Existing PPP session(s) are established by pid(s) [972]. Please close/kill these processes first

You can kill all previous PPP sessions with $ sudo hologram network disconnect.

@ChrisCUVM

The solution I found was to make a second boot sim using raspbian 9.1 (stretch) without any desktop. This seems much more well suited to using the Nova.

The Nova SDK works with all Raspbian version from Jessie on, both UI and non-UI versions. Not sure why it decided to work for you without the UI but I can verify it works as expected on all versions.

@Don_Mitchinson

I confirmed that it was very problematic with both Ethernet + WiFi connected - but is very stable with just WiFi - haven’t tried with just Ethernet - but it kind of makes sense as Ethernet uses USB bus. Probably have to treat it similar to Huwaei modems

This is interesting. Can you share your /etc/network/interfaces file?

The Nova SDK was specifically designed to work alongside other networks. If you want to use the Nova in tandem with another network then I’d suggest not calling $ sudo hologram connect.

Instead, use your other networks as normal then call Nova SDK send/receive functions as needed. In the background, the Nova SDK will call raw AT commands and not modify the network interfaces.

I’m happy to provide further assistance if you share the code that is causing issues.

[rockman55]

Chris thanks for your comments on installing the modem. I finally got my to work using your instructions. I was getting the same error about ERROR: PDP Context setup failed, I ran everything like you said and left out the part about the ssh and wpa_supplicant.conf files. The only thing I changed hardware wise was I placed on the larger antenna. My small antenna had come apart at the connection from changing it back and forth.
Thanks again
Danny

[ChrisCUVM]

Hey, glad it worked out eventually.

[ChrisCUVM]

@benstr

Sorry, our support team did not chime in sooner. Let me run through the issues you have mentioned in the comments above.

Thanks Ben. Maiky had been providing support off-forum on this one and I was trying to also post the results of that here for others to benefit from.

@benstr

Signal strength: 99,99

This means your modem does not have any tower signal. Either you are in a dead zone or the antenna is not attached. We’ve seen rare occasions where full network propagation of newly activated SIMs took up to an hour. That would also result in 99999 results.

The local signal was confirmed as 100% with another cellular device, and the mechanical antenna connection was confirmed. I think there is a third possibility when troubleshooting a “Signal strength: 99,99”, namely, that the modem hasn’t been initialized correctly. The key command for me in all of this was:

@benstr

sudo hologram modem connect -v

As it provides a lot more info than anything else.

@benstr

The Nova SDK works with all Raspbian version from Jessie on, both UI and non-UI versions. Not sure why it decided to work for you without the UI but I can verify it works as expected on all versions.

I can’t explain it either, just that it worked. I haven’t had time to circle back and try again with the UI. But, frankly, simple is good. I can use the non-UI setup and get into less trouble!

@benstr

The Nova SDK was specifically designed to work alongside other networks. If you want to use the Nova in tandem with another network then I’d suggest not calling $ sudo hologram connect.

Instead, use your other networks as normal then call Nova SDK send/receive functions as needed. In the background, the Nova SDK will call raw AT commands and not modify the network interfaces.

Oh, that’s handy to know about. I didn’t realize you could do that. I had assumed you needed an established connection to use follow-on commands. What’s the best source of information on how the SDK works and doesn’t? I’ve found a list of commands, but I’m trying to get a better handle on the context; how the commands work together.

[nicocarv]

Hello guys,

I got the same problem.
Solution: I had inserted the SIM in the wrong way. Anyway, if it helps somebody I knew this by issuing the following commands on minicom:

minicom -D /dev/ttyACM0 -b9600 (check your USB port)

AT+COPS=? (it will tell you the available networks. If there is non, you have another type of problem)

AT+COPS=0 (this will try to connect to an operator. In my case I got the message no SIM inserted)

hope it helps somebody.