@tom Any way to change the broadcast frequency as in AP?

Hi,
I am trying to connect to the softAP of the VOXL2 drone with a ALFA dongle.
VOXL-suite 1.3.1
I can connect fine with 2.4GHz and see that 5 GHz is supported on the dongle.
But when I access hostapd program in Linux the file structure seems different then what I expect. I am unable to find hostap.conf which is how I would expect this change to be made. AM I missing something within the adb shell?

Thanks!

@RSAUser1 said in Sierra Modem not showing in Device Manager/wds errors:

@tom I just heard back from Sierra wireless and they are stating this is an issue on your guys side. Not sure how to proceed. Any insight on the path forward is appreciated. Maybe if we can speak with you and Sierra wireless in a joint chat that would be easiest?

Thanks.

Sorry just want to add. We were able to get a connection to our emulator but only when the modem status shows:
voxl2:/$ systemctl status -l voxl-modem
● voxl-modem.service - Modem Initialization
Loaded: loaded (/etc/systemd/system/voxl-modem.service; enabled; vendor preset: enabled)
Active: inactive (dead)

Which seems to have confused me more. What we did was disable the vision-hub , just to allow another service to start (in theory) but then disabled modem, adb rebooted, enabled modem all while we were injecting the 5G signal (only band n5 works but handovers to supported bands do work).
Any deviation from these steps does not work, like if we reboot then inspect-services or anything besides just enabling modem it will not connect. Is this because if the drone loses power or anything the first thing it needs to do is find the network (another theory)? Even if we are connected and turn of the 5G cell from our side and turn it back on the chipset does not reconnect and it looks like it is not trying to find a cell.
Looks like this is on sierra wireless, is there anyway we can have a joint chat to troubleshoot this?

Thanks!

@tom I just heard back from Sierra wireless and they are stating this is an issue on your guys side. Not sure how to proceed. Any insight on the path forward is appreciated. Maybe if we can speak with you and Sierra wireless in a joint chat that would be easiest?

Thanks.

@tom ok Thanks for your help. Have a great day.

@tom This is a test SIM and the manufacture does support Sierra wireless. It uses the GSMA TS48 SIM profile which is a universal test profile that works with everything I have used it with as well. When we inject a signal from a base station emulator the EM9291 does not respond and this SIM works with other devices when connecting to the emulator.

Ok I wasn't sure because the EM9291 user guide states both QC and Sierra wireless should show up but yes that is not used as a add-on board.

Any idea why the wds service is giving the error?

Hi,
Using the VOXL2 with the em9291 sierra wireless chip and WLAN board (setup does get an IP address).

We are able to get the SIM profile working but still having issues with the Sierra wireless Modem and it does not show in Device manager on our PC

It does show as enabled and active (running) from the adb shell responses
Could this be the cause of 'wds' service not working or the QMI protocol errors below?

voxl2:/$ systemctl status voxl-modem
● voxl-modem.service - Modem Initialization
Loaded: loaded (/etc/systemd/system/voxl-modem.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2023-03-02 13:25:00 UTC; 53min ago
Process: 8075 ExecStartPre=/bin/sleep 2 (code=exited, status=0/SUCCESS)
Main PID: 8076 (voxl-modem-star)
Tasks: 4 (limit: 4915)
CGroup: /system.slice/voxl-modem.service
├─ 8076 /bin/bash /usr/bin/voxl-modem-start
├─ 8104 /usr/lib/libmbim/mbim-proxy
└─19866 sleep 1

Mar 02 14:18:29 m0054 voxl-modem-start[8076]: error: couldn't create client for the 'wds' service: QMI protocol error (5): 'ClientIdsExhausted'
Mar 02 14:18:29 m0054 voxl-modem-start[8076]: Error detected! Retrying...
Mar 02 14:18:30 m0054 voxl-modem-start[8076]: error: couldn't create client for the 'wds' service: QMI protocol error (5): 'ClientIdsExhausted'
Mar 02 14:18:30 m0054 voxl-modem-start[8076]: Error detected! Retrying...
Mar 02 14:18:31 m0054 voxl-modem-start[8076]: error: couldn't create client for the 'wds' service: QMI protocol error (5): 'ClientIdsExhausted'
Mar 02 14:18:31 m0054 voxl-modem-start[8076]: Error detected! Retrying...
Mar 02 14:18:32 m0054 voxl-modem-start[8076]: error: couldn't create client for the 'wds' service: QMI protocol error (5): 'ClientIdsExhausted'
Mar 02 14:18:32 m0054 voxl-modem-start[8076]: Error detected! Retrying...
Mar 02 14:18:33 m0054 voxl-modem-start[8076]: error: couldn't create client for the 'wds' service: QMI protocol error (5): 'ClientIdsExhausted'
Mar 02 14:18:33 m0054 voxl-modem-start[8076]: Error detected! Retrying...

I checked the board and all the cabling looks connected and boards fully seated.

Thanks!

Could something still not be seated properly or maybe a cable has come lose,?
voxl2:/$ systemctl status voxl-modem
● voxl-modem.service - Modem Initialization
Loaded: loaded (/etc/systemd/system/voxl-modem.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2023-03-02 12:58:06 UTC; 31s ago
Process: 1263 ExecStartPre=/bin/sleep 2 (code=exited, status=0/SUCCESS)
Main PID: 1861 (voxl-modem-star)
Tasks: 7 (limit: 4915)
CGroup: /system.slice/voxl-modem.service
├─1861 /bin/bash /usr/bin/voxl-modem-start
├─2144 /usr/lib/libmbim/mbim-proxy

       ******************└─2208 qmicli --device=/dev/cdc-wdm0 --device-open-proxy --wds-start-network=ip-type=4,apn=cmx500.rohde-schwa

Mar 02 12:58:14 m0054 voxl-modem-start[1861]: Waiting for wwan0 to come up...**
Mar 02 12:58:15 m0054 voxl-modem-start[1861]: Waiting for wwan0 to come up...
Mar 02 12:58:16 m0054 voxl-modem-start[1861]: Waiting for wwan0 to come up...
Mar 02 12:58:17 m0054 voxl-modem-start[1861]: Waiting for wwan0 to come up...
Mar 02 12:58:18 m0054 voxl-modem-start[1861]: Waiting for wwan0 to come up...
Mar 02 12:58:19 m0054 voxl-modem-start[1861]: wwan0 is up!
Mar 02 12:58:19 m0054 voxl-modem-start[1861]: Sierra detected!
Mar 02 12:58:20 m0054 voxl-modem-start[1861]: Starting qmi network...
Mar 02 12:58:35 m0054 voxl-modem-start[1861]: error: couldn't open the QmiDevice: Transaction timed out
Mar 02 12:58:35 m0054 voxl-modem-start[1861]: Error detected! Retrying...****************

Then sometimes it will give 'error: couldn't create client for the 'wds' service: QMI protocol error (5)'

@groupo THanks for your help! One strange thing is that I still don't have the modem listed in my PCs device manager. Still waiting on my emulator to become available to test if we see the 5G broadcast.

Seems like some part of the modem is still not reachable, as I it still cant communicate QMI device which is part of modem @tom have you seen this issue before?

@groupo Wow, trying to save time since I need to remove the SIM after I validate this connecting. Thanks, I was thinking since we were talking to it all was good. Getting some errors when doing status voxl-modem but believe thats because we have a test SIM and it cant connect to a live network.
Mar 02 12:59:53 m0054 voxl-modem-start[1854]: Service: 'wds'

   Mar 02 12:59:53 m0054 voxl-modem-start[1854]:             CID: '102'
   
   Mar 02 12:59:53 m0054 voxl-modem-start[1854]: Error detected! Retrying...
   
   Mar 02 12:59:54 m0054 voxl-modem-start[1854]: error: couldn't start network: QMI protocol error (14): 'CallFailed'
   
   Mar 02 12:59:54 m0054 voxl-modem-start[1854]: call end reason (3): generic-no-service
   
   Mar 02 12:59:54 m0054 voxl-modem-start[1854]: verbose call end reason (3,2001): [cm] no-service
   
   Mar 02 12:59:54 m0054 voxl-modem-start[1854]: [/dev/cdc-wdm0] Client ID not released:
   
   Mar 02 12:59:54 m0054 voxl-modem-start[1854]:         Service: 'wds'
   
   Mar 02 12:59:54 m0054 voxl-modem-start[1854]:             CID: '103'
   
   Mar 02 12:59:54 m0054 voxl-modem-start[1854]: Error detected! Retrying...

Going to see if we setup our BS emulator