Project

General

Profile

Actions

Feature #61

closed

Enable internet access on the SolidSense

Added by Emmanuel Jubera [SAFT] 7 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Target version:
-
Start date:
10/17/2023
Due date:
% Done:

100%

Estimated time:
Hardware platform:
Solidrun (aarch64)
OS Affects Version/s:
arz-1.1-update
OS Fix Version/s:
Labels:

Description

We would like to explore different scenarios aiming at providing internet access on the SolidSense. This access would be achieved through cellular networks.
Here are a couple of scenarios we came up with and some questions that arose:

1) Enabling the on-board LTE chip and access it like a network interface. In this case we would have to buy SIM cards from a cellular operator and handle devices with a fleet management software like Mender.

2) Adding a cellular module to the board. For example Telit sells cellular modules including a SIM and also offers a fleet management UI.

  • Would it be possible to handle such a cellular module with Redpesk OS ?
  • Would it be possible to replace the on-board LTE chip by another one or could SolidRun deliver boards with an empty cellular chip connector ?
Actions #1

Updated by Sebastien Douheret [IoT.bzh] 7 months ago

  • Assignee changed from Marc-Antoine Riou to Valentin Geffroy
Actions #2

Updated by Valentin Geffroy 7 months ago

  • Status changed from New to In Progress
Actions #3

Updated by Valentin Geffroy 6 months ago

  • % Done changed from 0 to 10
Actions #4

Updated by Valentin Geffroy 6 months ago

  • OS Affects Version/s arz-1.1-update added

After booting a redpesk OS image on the Solidrun Solidsense N8 Compact LTE, it seems the 4G module isn't enabled. A deeper investigation is needed to check if vendor firmwares or kernel configs are needed. The goal is to have a SIM which enables a network interface in the system.

Actions #5

Updated by Valentin Geffroy 6 months ago

Valentin Geffroy wrote in #note-4:

After booting a redpesk OS image on the Solidrun Solidsense N8 Compact LTE, it seems the 4G module isn't enabled. A deeper investigation is needed to check if vendor firmwares or kernel configs are needed. The goal is to have a SIM which enables a network interface in the system.

Thanks to a Emmanuel's comment, it seems the 4G is up on the hardware. It asks the PIN code:

[root@localhost ~]# mmcli -m 0
  -----------------------------
  General  |              path: /org/freedesktop/ModemManager1/Modem/0
           |         device id: e7611519e5c3dc939d875fde070c6b11b33693a9
  -----------------------------
  Hardware |      manufacturer: Quectel
           |             model: EG25
           | firmware revision: EG25GGBR07A08M2G
           |         supported: gsm-umts, lte
           |           current: gsm-umts, lte
           |      equipment id: 867698045366534
  -----------------------------
  System   |            device: /sys/devices/platform/soc@0/32c00000.bus/32e40000.usb/ci_hdrc.0/usb1/1-1/1-1.2
           |           drivers: option
           |            plugin: quectel
           |      primary port: ttyUSB2
           |             ports: ttyUSB0 (qcdm), ttyUSB1 (gps), ttyUSB2 (at), ttyUSB3 (at)
  -----------------------------
  Status   |              lock: sim-pin
           |    unlock retries: sim-pin (3), sim-pin2 (3), sim-puk (10), sim-puk2 (10)
           |             state: locked
           |       power state: on
           |    signal quality: 0% (cached)
  -----------------------------
  Modes    |         supported: allowed: 2g, 3g, 4g; preferred: none
           |           current: allowed: 2g, 3g, 4g; preferred: none
  -----------------------------
  IP       |         supported: ipv4, ipv6, ipv4v6
  -----------------------------
  3GPP     |     enabled locks: sim
  -----------------------------
  SIM      |  primary sim path: /org/freedesktop/ModemManager1/SIM/0

Actions #6

Updated by Valentin Geffroy 6 months ago

After some development, the LTE connection is enabled on the board:

[root@localhost ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UP group default qlen 2048
    link/can 
3: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether ae:54:ff:9e:dd:0e brd ff:ff:ff:ff:ff:ff
4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 8a:d0:3f:42:33:29 brd ff:ff:ff:ff:ff:ff
8: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 3
    link/ppp 
    inet 10.15.167.17 peer 10.64.64.64/32 scope global ppp0
       valid_lft forever preferred_lft forever
    inet 10.15.167.17/32 scope global noprefixroute ppp0
       valid_lft forever preferred_lft forever

Indeed I have no WiFi, no Ethernet but only the LTE to have a Internet access:

[root@localhost ~]# ping 8.8.8.8 -c 1
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=117 time=76.1 ms

--- 8.8.8.8 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 76.106/76.106/76.106/0.000 ms

A written documentation will be send to Emmanuel to help him to deploy the feature on his board.

Actions #7

Updated by Valentin Geffroy 6 months ago

  • % Done changed from 10 to 100
Actions #8

Updated by Valentin Geffroy 5 months ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF