PXS8 ttyUSBx are locked on Linux system after SDPORT change | Telit Cinterion IoT Developer Community
December 10, 2015 - 12:49pm, 2400 views
I work under Linux, I have configured the PXS8 modem with this at command "AT^SDPORT=6" (old value is 3), after that the /dev/ttyACM0 appears but after few seconds this interface disappears and ttyUSBx reappears and SDPORTcome back to 3.
I tried to switch to ttyACM0 many ***** but I can't succeed.
I tried to change the at command "AT^SDPORT=2" to test if the value is accepted or not. The modem restart and after that I can't access to ttyUSBx, the interfaces exist but I can't write at commands, I tried with echo, microcom,.. but no result and I can't come back to sdport = 3.
Here my interfaces permissions displayed by ls /dev/ttyUSB* -l:
crw-rw---- 1 root dialout 188, 0 Feb 1 00:02 /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 1 Feb 1 00:02 /dev/ttyUSB1
crw-rw---- 1 root dialout 188, 2 Feb 1 00:05 /dev/ttyUSB2
crw-rw---- 1 root dialout 188, 3 Feb 1 00:05 /dev/ttyUSB3
Have you any solution for this problem? Is it caused by Linux driver? or It a bug in the modem firmware it self? and How can restore it?
Note: I have restarted the modem (or/and whole system) many ***** but always interfaces locked.
I have seen in AT command document (http://www.seapraha.cz/download/phs8-p_atc_v02003a.pdf, page 61 and 62) this:
sdport=2: The Modem interface is available on ASC0. The USB composite communication device is completely enumerated but no logical channel of the USB device is usable. Therefore, if URC output was active on an interface which is no longer usable due to change of AT^SDPORT setting, it is redirected to the Modem interface as could normally be done via AT^SCFG, "URC/DstIfc"
How to come back to sdport=3?
After setting AT^SDPORT=2 you can only access the module via serial interface. You need to connect the module's ASC0 with PC's serial interface (RS232) and then you will be able to change the SDPORT setting.
The SDOPRT setting should not be changing by itself and the driver should also not change it.
Have you checked the syslog?
Please also check the module's ATI1 reply to verify the firmware version.