Hi there,
Could you help to recommend a USB LTE dongle that supports mbim protocol. I tried 330u, it seems doesn’t support it.
Thanks!
Hi,
Sierra has not made USB dongles for a ling time now, when the last one was made MBIM did not exist so we cannot recommend a Sierra one that would do this.
Regards
Matt
You can use the EM/MC devices. Just add an m2/mpcie to USB adapter. It won’t be as handy as a “real” dongle like from Huawei.
Thanks for your reply.
Yes, I ordered one MC7455 and the USB adapter as your recommanded.
Now, Could you provide some instuctions on how to finish the mode switch. By default, it works on qmi mode. I tried to do the modeswitch via AT-commands. However I can’t input anything to the serial port. It prints below messages all the time:
$GPRMC,V,N53
$GPVTG,T,M,N,K,N2C
$GPGSA,A,1,1E
$GPGGA,0,66
$GPRMC,V,N53
$GPVTG,T,M,N,K,N2C
$GPGSA,A,1,1E
$GPGGA,0,66
$GPRMC,V,N53
$GPVTG,T,M,N,K,N2C
$GPGSA,A,1,1E
$GPGGA,0,66
$GPRMC,V,N53
$GPVTG,T,M,N,K,N2C
thats the GPS port. Try another one.
Hi,
I tried the other one. however I can’t input anything. I also tried differenct baud rate, such as 57600, 115200.
I also tried it on ubuntu with minicom. It always reports “offline”.
Hi,
When you plug a unit in, assuming you have default USB configuration and the GobiSerial drivers installed you should see three /dev/ttyUSB ports, 0, 1 and 2.
0 - Diagnostic monitoring port.
1 - GPS NMEA port
2 - AT commands
Previously you have mentioned you wanted the MBIM interface did you activate this with at!usbcomp or plug the unit into a Windows 10 PC?
If you did it with an AT command what was it, what was the bit map you used as you might have disabled the AT command port.
Regards
Matt
Hi,
Thanks for your information. Now I have done the modeswitch via AT commands. The previous problem probably caused by the virtual box. I did all thing before on a virtual machine and It always reports ‘qmi_wwan…’ error messages. When I use a linux machine directly, everything goes well.
Now I meet some new issues. When I execute the umbim commands on the openwrt. some commands can’t be excuted successfully. for example:
umbim -d /dev/cdc-wdm0 registration
It reports NotInitialized. How could it be initialized?
(‘umbim -d /dev/cdc-wdm0 caps’ can work well)
below are the outprints:
root@mylinkit:/# umbim -d /dev/cdc-wdm0 registration -v
sending (16): 01 00 00 00 10 00 00 00 01 00 00 00 00 04 00 00
header_type: 0001
header_length: 0010
header_transaction: 0001
reading (16): 01 00 00 80 10 00 00 00 01 00 00 00 00 00 00 00
header_type: 80000001
header_length: 0010
header_transaction: 0001
sending (48): 03 00 00 00 30 00 00 00 02 00 00 00 01 00 00 00 00 00 00 00 a2 89 cc 33 bc bb 8b 4f b6 b0 13 3e c2 aa e6 df 09 00 00 00 00 00 00 00 00 00 00 00
header_type: 0003
header_length: 0030
header_transaction: 0002
reading (96): 03 00 00 80 60 00 00 00 02 00 00 00 01 00 00 00 00 00 00 00 a2 89 cc 33 bc bb 8b 4f b6 b0 13 3e c2 aa e6 df 09 00 00 00 00 00 00 00 30 00 00 00 00 00 00 00 01 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00
header_type: 80000003
header_length: 0060
header_transaction: 0002
command_id: 0009
status_code: 0000
nwerror: 0000 - unknown
registerstate: 0001 - deregistered
registermode: 0001 - automatic
availabledataclasses: 0000 - (null)
currentcellularclass: 0001 - gsm
provider_id: (null)
provider_name: (null)
roamingtext: (null)
sending (16): 02 00 00 00 10 00 00 00 03 00 00 00 01 00 00 00
header_type: 0002
header_length: 0010
header_transaction: 0003
reading (16): 02 00 00 80 10 00 00 00 03 00 00 00 00 00 00 00
header_type: 80000002
header_length: 0010
header_transaction: 0003
root@mylinkit:/#
Some devices want a correct sequence.
I assume you want this to work with OpenWrt and a working internet connection.
Try this mbim.sh: lteforum.at/mobilfunk/cat-6 … post-80068