LGA DevKit + PLS83-W Module / AT Commands problem | Thales IoT Developer Community
June 18, 2021 - 1:56pm, 5356 views
Hi,
I am currently trying to set up QMI/RmNet on the PLS83-W module so following this tutorial (PLS63/83 QMI/RMNET Setup and Linux qmi_wwan / ModemManager Integration | Thales IoT Developer Community (thalesgroup.com) ). I first need to configure the module via GTKterm with AT commands.
Problem is, I want to send AT commands through the native USB port of the LGA Devkit but GTKTerm terminal doesn't detect any USB ports means I am unable to communicate with the module with AT commands.
On the other hand, when I send AT commands through ASC0 USB port (VCP USB), I am able to select an USB port and see the AT Terminal so I can send commands.
In short, I was wondering if there is a way to be able to send AT commands through native USB port via a terminal ?
Thank you in advance for your answer,
Best Regards
A Random Intern
Hello,
In general it is possible to use native USB. Have you tried with Windows for comparison?
Did you check lsusb and dmesg outputs?
BR,
Bartłomiej
Hi,
I just checked lsusb and dmesg output, here they are :*
lsusb :
dmesg :
I retried opening GTKTerm again to check if i can access to LGA DevKit's USB port but it still doesn't show any port I can use to send AT commands, here is a screenshot of the ports available (I tried them and none of them is connected to the DevKit) :
In comparison, when I plug the DevKit with its ASC0 (VCP) USB port, I can select it and I am able to send AT commands (as below) :
Thank you for your answer,
Best Regards,
A Random Intern
USB PID 006b looks like an engineering sample or rather old firmware to me.
According to the kernel patch for the qmi_wwan driver the USB PID should be 006f and the serial
ports are available as /dev/ttyACM*:
[4567975.356067] usb 2-3.2: new high-speed USB device number 114 using ehci-pci
[4567975.438875] usb 2-3.2: New USB device found, idVendor=1e2d, idProduct=006f
[4567975.438878] usb 2-3.2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[4567975.438880] usb 2-3.2: Product: PLSx3
[4567975.438882] usb 2-3.2: Manufacturer: Cinterion Wireless Modules
[4567975.438884] usb 2-3.2: SerialNumber: 12345678
[4567975.440933] cdc_acm 2-3.2:1.0: ttyACM0: USB ACM device
[4567975.442018] cdc_acm 2-3.2:1.2: ttyACM1: USB ACM device
[4567975.443320] cdc_acm 2-3.2:1.4: ttyACM2: USB ACM device
[4567975.444569] cdc_acm 2-3.2:1.6: ttyACM3: USB ACM device
[4567975.447285] qmi_wwan 2-3.2:1.8: cdc-wdm0: USB WDM device
[4567975.448313] qmi_wwan 2-3.2:1.8 wwan0: register 'qmi_wwan' at usb-0000:00:1d.7-3.2, WWAN/QMI device, f6:b9:9b:e1:95:2a
Regards,
Reinhard
Hello,
I connected mine to Ubuntu and it enumerated with idProduct 0x0069.
According to AT spec if the module is configured as ECM all USB devices of the UE enumerate
with PID 0x0069. If it's configured as WWAN device all USB devices of the UE enumerate with PID 0x006F.
Can you paste ATI1 and ATI8 replies?
BR,
Bartłomiej
Hello Bartłomiej,
Thank you for your answer.
Here are the ATI1 and ATI8 replies :
Best Regards
A Random Intern
Thank you for your answer !
Actually, yes, it should be 006f as I set the AT^SSRVSET="actSrvset",11 command on the module... But it's not and I don't really know why.
I checked under /dev and I don't have any ttyACM file...
Do you have any idea about how I could send AT commands through native USB ? I currently tried ASC0 (VCP), both ports but native USB on itself won't allow me to send AT commands as my GTKTerm terminal can't detect its port when it's on native.
Best Regards,
A Random Intern
Hello,
How about ECM **** - is USB enumerated properly?
It seems that you have quite an old firmware - the first customer sample. The AT spec for this version states (for setting 11) that CDC5 (USB5) and nd CDC6 (USB6) enumerate as RmNet device. All USB devices of the UE enumerate with PID 0x006B.
I think that you need to update the firmware to a newer version. But for that purpose you have to contact your Thales technical sales person or module provider.
BR,
Bartłomiej
Hello Bartłomiej,
I think it is enumerated properly for ECM as I have this output :
I see, thank you for your help.
Best Regards,
A Random Intern
Hello,
Can you see the assigned interfaces like below:
[ 287.259160] cdc_acm 2-7:1.0: ttyACM0: USB ACM device
[ 287.285125] cdc_acm 2-7:1.2: ttyACM1: USB ACM device
[ 287.289685] cdc_acm 2-7:1.4: ttyACM2: USB ACM device
[ 287.292539] cdc_acm 2-7:1.6: ttyACM3: USB ACM device
Are you able to communicate?
BR,
Bartłomiej
Hi Bartłomiej,
Sorry for the delay. We sent back the modules to get them updated so here are the new AT1 and AT8 replies :
Here is my new dmesg output and I can now see the interfaces below (along with some errors that I haven't solved yet :
I also tried checking if the module is ready but it returns the error below :
If you have any idea what those errors could be related to, could you let me know ?
Thank you for your help.
Best Regards,
A Random Intern
Pages