Hi,
I want to connect network and get data by using Sixfab 4G/LTE Cellular Modem Kit for NVIDIA Jetson Nano DevKit. But device is not connected to cellular network. Device Status is OK but Cellular Status is NOT.
Hi,
I want to connect network and get data by using Sixfab 4G/LTE Cellular Modem Kit for NVIDIA Jetson Nano DevKit. But device is not connected to cellular network. Device Status is OK but Cellular Status is NOT.
Hi,
Could you please enable the remote support and PM me your remote-support token so I can check and fix it?
Additionally, I will request you to send the ICCID.
Hello @ensar & @a.dangac ,
Was this issue resolved? I have similar issue with one of my Jetson nano LTE boards. The cellular connection will be active for a few minutes after reboot of the nano but goes offline after that.
Hi @nkamidi ,
Did you get any errors when you ran your installation code? Which OS version are you using? Can you confirm if there are any problems with your WiFi connection? Can you share the status of core_agent service?
Hello @ensar ,
There were no errors during the installation. This Jetson Orin Nano is running Jetpack 5.1.2 (Ubuntu 20.04). Please see the saved outputs below. I also downloaded the core-manager and core-agent logs. I can share those if necessary.
Note: I would like to highlight is that first I installed core agent without the suffix " -b Jetson -d" but later on reinstalled by adding this parameter. Not sure if that makes a difference.
=====================================================
[INFO] Sixfab user already exists, updating...
[INFO] Updating sudoers...
[INFO] Sudoers updated
[INFO] Updating system package index...
[INFO] Looking for dependencies...
[INFO] Board: Nvidia Jetson Nano - OS: Ubuntu
[INFO] Initializing environment file...
[INFO] Initialized environment file
[INFO] Temporary environment removing
[INFO] Agent source already exists, updating...
[INFO] Applying dev mode to agent...
[INFO] Creating virtual environment and installing agent requirements...
[INFO] Initializing agent service...
[INFO] Agent service initialized successfully.
[INFO] Manager source already exists, updating...
[INFO] Applying dev mode to manager...
[INFO] Creating virtual environment and installing manager requirements...
[INFO] Virtual environment deactivated.
[INFO] Initializing manager service...
[INFO] Manager service initialized successfully.
[DONE] Installation completed successfully.
-----------------------------------------------------------------------
Press ENTER to reboot your system. (Recommended)
Press Ctrl+C (^C) to finish installation without reboot.
Reminder: Plug the USB cable to Sixfab HAT!
Warning: Network priority settings will be effective after reboot!
NVIDIA NVIDIA Orin Nano Developer Kit
L4T 35.4.1 [ JetPack UNKNOWN ]
Ubuntu 20.04.6 LTS
Kernel Version: 5.10.120-tegra
CUDA 11.4.315
CUDA Architecture: 8.7
OpenCV version: 4.5.4
OpenCV Cuda: NO
CUDNN: 8.6.0.166
TensorRT: 8.5.2.2
Vision Works: NOT_INSTALLED
VPI: 2.3.9
Vulcan: 1.3.204
● core_agent.service - Sixfab Core Agent
Loaded: loaded (/etc/systemd/system/core_agent.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2024-01-17 21:14:48 PST; 1 day 16h ago
Main PID: 734 (bash)
Tasks: 7 (limit: 7453)
Memory: 44.4M
CGroup: /system.slice/core_agent.service
├─ 734 /bin/bash /opt/sixfab/core/agent/run.sh
├─ 830 /opt/sixfab/core/agent/venv/bin/python3 /opt/sixfab/core/agent/run.py
└─1542 /opt/sixfab/core/agent/core/modules/pty/builds/arm64
● core_manager.service - Sixfab Core Manager
Loaded: loaded (/etc/systemd/system/core_manager.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2024-01-17 21:14:48 PST; 1 day 16h ago
Main PID: 735 (bash)
Tasks: 5 (limit: 7453)
Memory: 58.1M
CGroup: /system.slice/core_manager.service
├─735 /bin/bash /opt/sixfab/core/manager/run.sh
└─851 /opt/sixfab/core/manager/venv/bin/python3 /opt/sixfab/core/manager/core_manager/run.py
@ensar,
If this helps, here is what I see in the logs.
CM-LOG
2024-01-19 13:44:40,672 --> cm.py ERROR identify_modem -> Modem vendor couldn't be found!
2024-01-19 13:44:42,781 --> identify.py INFO Tyring to detect modem...
2024-01-19 13:44:42,795 --> identify.py WARNING Modem don't exist in list of supported modems!
2024-01-19 13:44:42,795 --> identify.py WARNING Modem vendor couldn't be found!
2024-01-19 13:44:42,795 --> cm.py ERROR identify_modem -> Modem vendor couldn't be found!
2024-01-19 13:44:44,904 --> identify.py INFO Tyring to detect modem...
2024-01-19 13:44:44,918 --> identify.py WARNING Modem don't exist in list of supported modems!
2024-01-19 13:44:44,918 --> identify.py WARNING Modem vendor couldn't be found!
2024-01-19 13:44:44,918 --> cm.py ERROR identify_modem -> Modem vendor couldn't be found!
2024-01-19 13:44:47,026 --> identify.py INFO Tyring to detect modem...
2024-01-19 13:44:47,039 --> identify.py WARNING Modem don't exist in list of supported modems!
2024-01-19 13:44:47,039 --> identify.py WARNING Modem vendor couldn't be found!
2024-01-19 13:44:47,039 --> cm.py ERROR identify_modem -> Modem vendor couldn't be found!
AGENT-LOG
2024-01-19 13:43:10,162 --> main.py WARNING Disconnected from the broker, rc=5
2024-01-19 13:43:10,163 --> main.py DEBUG Didn't used last updated connection sequence yet, skipping
2024-01-19 13:43:11,461 --> monitoring.py DEBUG Not connected to MQTT broker, ignoring monitoring thread. Retrying in 10 secs
2024-01-19 13:43:21,469 --> monitoring.py DEBUG Not connected to MQTT broker, ignoring monitoring thread. Retrying in 10 secs
2024-01-19 13:43:31,477 --> monitoring.py DEBUG Not connected to MQTT broker, ignoring monitoring thread. Retrying in 10 secs
2024-01-19 13:43:41,485 --> monitoring.py DEBUG Not connected to MQTT broker, ignoring monitoring thread. Retrying in 10 secs
2024-01-19 13:43:51,493 --> monitoring.py DEBUG Not connected to MQTT broker, ignoring monitoring thread. Retrying in 10 secs
2024-01-19 13:44:01,501 --> monitoring.py DEBUG Not connected to MQTT broker, ignoring monitoring thread. Retrying in 10 secs
2024-01-19 13:44:11,509 --> monitoring.py DEBUG Not connected to MQTT broker, ignoring monitoring thread. Retrying in 10 secs
2024-01-19 13:44:21,517 --> monitoring.py DEBUG Not connected to MQTT broker, ignoring monitoring thread. Retrying in 10 secs
2024-01-19 13:44:31,525 --> monitoring.py DEBUG Not connected to MQTT broker, ignoring monitoring thread. Retrying in 10 secs
2024-01-19 13:44:41,533 --> monitoring.py DEBUG Not connected to MQTT broker, ignoring monitoring thread. Retrying in 10 secs
Thank you for your detailed sharing.
Can you send me(ensar@sixfab.com) the cm-log and agent-log files?
Just emailed the files.