Cellular Connectivity Issue with Raspberry Pi 3G/4G&LTE Base HAT Telit LE910C4-NF

[samg.gregg]

I’m experiencing issues with my Raspberry Pi 3G/4G&LTE Base HAT using the Telit LE910C4-NF module. Initially, the setup was working fine, but after disconnecting from the wifi, the cellular connection functioned for about 10 minutes and then stopped broadcasting.

Current Status:

• Cellular connection shows as “Unavailable.” on the dashboard.
• Only interface on dashboard is wlan0 (Wi-Fi).
• On the core dashboard, roaming operator and LTE technology values intermittently show “NA.”

Troubleshooting Steps Taken:

• Updated the firmware on the HAT.
• Restarted core agent and core cellular services.
• Reinstalled the connect.sixfab package.

Additionally, nmcli general status shows “WWAN-HW: missing,” indicating that the modem hardware may not be detected.

Any help and guidance is greatly appreciated.

[saeed]

Hello

Could you please share the ICCID of your asset privately?

Additionally, share the logs stored in the directory " /home/sixfab/.core/logs/ ".

[samg.gregg]

cm-log:

2024-09-04 20:29:28,672 → default.py INFO ECM Connection is initiating…
2024-09-04 20:29:30,421 → default.py INFO ECM is initiated.
2024-09-04 20:29:40,624 → cm.py ERROR check_internet() → No internet!
2024-09-04 20:29:40,824 → diagnostic.py INFO Diagnostic is working…
2024-09-04 20:29:41,402 → default.py INFO Checking the network is ready…
2024-09-04 20:29:41,536 → default.py INFO Network is registered
2024-09-04 20:29:41,855 → diagnostic.py INFO Creating diagnostic report on → /home/sixfab/.core/diagnostics/diagnostic.yaml
2024-09-04 20:29:42,056 → default.py INFO Connection interface is reset…
2024-09-04 20:29:42,065 → cm.py ERROR reset_connection_interface() → Error occured while interface getting down!
2024-09-04 20:29:43,165 → default.py INFO Connection interface is reset…
2024-09-04 20:29:43,175 → cm.py ERROR reset_connection_interface() → Error occured while interface getting down!
2024-09-04 20:29:44,275 → default.py INFO Connection interface is reset…
2024-09-04 20:29:44,284 → cm.py ERROR reset_connection_interface() → Error occured while interface getting down!
2024-09-04 20:29:44,484 → default.py INFO USB interface is reset…
2024-09-04 20:29:45,927 → cm.py ERROR check_internet() → No internet!
2024-09-04 20:29:46,127 → default.py INFO Modem is resetting softly…
2024-09-04 20:29:46,325 → default.py INFO Modem is deregistered from network
2024-09-04 20:30:21,276 → monitor.py INFO Monitoring data updated with changes.
2024-09-04 20:30:22,278 → identify.py INFO Tyring to detect modem…
2024-09-04 20:30:24,385 → identify.py INFO [?] System identifying…
2024-09-04 20:30:25,138 → identify.py WARNING System setup has changed!
2024-09-04 20:30:29,138 → default.py INFO Modem configuration started.
2024-09-04 20:30:29,271 → default.py INFO Network auto-registering is enabling
2024-09-04 20:30:29,421 → default.py INFO Modem network auto-registering is enabled
2024-09-04 20:30:49,599 → default.py INFO APN is up-to-date.
2024-09-04 20:30:49,751 → default.py INFO Modem mode for EPS is OK
2024-09-04 20:30:49,751 → default.py INFO Checking the mode of modem…
2024-09-04 20:30:51,441 → default.py INFO Checking the SIM is ready…
2024-09-04 20:30:51,582 → default.py INFO SIM is ready.
2024-09-04 20:30:52,683 → default.py INFO Checking the network is ready…
2024-09-04 20:30:52,820 → cm.py ERROR check_network() → (‘Network not registered: ‘, (’\n\n+CREG: 0,0\n\n\n\nOK\n\n\n’, ‘’, 0))

agent-log:

2024-09-04 20:24:43,488 → monitoring.py DEBUG Skipping data_config, couldn’t find any changes.
2024-09-04 20:24:43,488 → monitoring.py ERROR data_geolocation not exists!
Traceback (most recent call last):
File “/opt/sixfab/core/agent/core/modules/monitoring.py”, line 86, in check_file_and_update_cloud
new_data = read_yaml_all(file_path)
^^^^^^^^^^^^^^^^^^^^^^^^
File “/opt/sixfab/core/agent/core/helpers/yamlio.py”, line 19, in read_yaml_all
with open(file) as yaml_file:
^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: ‘/home/sixfab/.core/geolocation.yaml’
2024-09-04 20:25:13,488 → monitoring.py DEBUG [CONFIGURATOR] Configs folder not found, skip for now
2024-09-04 20:25:13,490 → monitoring.py DEBUG Sending new data_monitoring : (0, 8), only_changed_values=True
2024-09-04 20:25:13,491 → monitoring.py DEBUG Skipping data_system, couldn’t find any changes.
2024-09-04 20:25:13,492 → monitoring.py DEBUG Skipping data_config, couldn’t find any changes.
2024-09-04 20:25:13,493 → monitoring.py DEBUG Sending new data_geolocation : (0, 9), only_changed_values=False
2024-09-04 20:25:13,549 → monitoring.py DEBUG Updated last monitoring data
2024-09-04 20:25:14,228 → monitoring.py DEBUG Updated last geolocation data
2024-09-04 20:25:43,493 → monitoring.py DEBUG [CONFIGURATOR] Configs folder not found, skip for now
2024-09-04 20:25:43,494 → monitoring.py DEBUG Sending new data_monitoring : (0, 10), only_changed_values=True
2024-09-04 20:25:43,495 → monitoring.py DEBUG Skipping data_system, couldn’t find any changes.
2024-09-04 20:25:43,496 → monitoring.py DEBUG Skipping data_config, couldn’t find any changes.
2024-09-04 20:25:43,497 → monitoring.py DEBUG Skipping data_geolocation, couldn’t find any changes.
2024-09-04 20:25:43,543 → monitoring.py DEBUG Updated last monitoring data
2024-09-04 20:26:13,497 → monitoring.py DEBUG [CONFIGURATOR] Configs folder not found, skip for now
2024-09-04 20:26:13,498 → monitoring.py DEBUG Skipping data_monitoring, couldn’t find any changes.
2024-09-04 20:26:13,499 → monitoring.py DEBUG Skipping data_system, couldn’t find any changes.
2024-09-04 20:26:13,500 → monitoring.py DEBUG Skipping data_config, couldn’t find any changes.

[samg.gregg]

When the device is connected with just the USB, I do not get a connected message on Sixfab Connect and am not able to open the remote terminal. However, when the device is connected through GPIO and USB, I am able to use the remote terminal on Sixfab Connect (Sixfab connect still does not display that the cellular connection status is available.). Again, any help is greatly appreciated.

[saeed]

The Sixfab CORE solution consists of core_manager and core_agent.

core_manager is responsible for configuring the mini PCIe module and setting up the cellular connection.
core_agent is responsible for updating the dashboard, maintaining the remote connection through the remote terminal.

Your setup seem to have issue with the Placeholder: core_agent.