OpenWrt Forum Archive

Topic: Telit LN930 and UMBIM

The content of this topic has been archived on 1 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi,

We are trying to get the above LTE card to work on OpenWRT.  The basics are functioning.

The issue is that we need to "register" the card on the carrier before actually connecting to the network.  In other words, we want to be able to see the registration info, such as signal strength, technology (4G/3G/2G) in use, etc. before an internet connection is established.

When OpenWRT starts, we do not want to automatically make an internet connection.  This is done manually after the router has booted.

When the LN930 comes online, we execute the following:

umbim -n -d $device subscriber

This causes the LN930 to register on the network.

The connection may stay in this state for some time, 60 minutes or more.

I then manually tell wan2 (LN930) to come online, and in turn, execute the mbim.sh script.

What is happening however is that umbim is "stuck".  When it tries to read the capabilities, it just sits for a bit, and then times out, and repeats.  Trying to just execute the umbim commands from the command line results in the same timeout issue.

/# umbim -n -d /dev/cdc-wdm0 caps -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 (64): 07 00 00 80 40 00 00 00 00 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 0b 00 00 00 14 00 00 00 09 00 00 00 14 00 00 00 3c 00 00 00 02 00 00 00 ff ff 00 00 
  header_type: 80000007
  header_length: 0040
  header_transaction: 0000
reading (64): 07 00 00 80 40 00 00 00 00 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 0b 00 00 00 14 00 00 00 0b 00 00 00 14 00 00 00 3c 00 00 00 02 00 00 00 ff ff 00 00 
  header_type: 80000007
  header_length: 0040
  header_transaction: 0000
reading (64): 07 00 00 80 40 00 00 00 00 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 0b 00 00 00 14 00 00 00 09 00 00 00 0e 00 00 00 3c 00 00 00 02 00 00 00 ff ff 00 00 
  header_type: 80000007
  header_length: 0040
  header_transaction: 0000
reading (64): 07 00 00 80 40 00 00 00 00 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 0b 00 00 00 14 00 00 00 0b 00 00 00 1b 00 00 00 3c 00 00 00 02 00 00 00 ff ff 00 00 
  header_type: 80000007
  header_length: 0040
  header_transaction: 0000
reading (64): 07 00 00 80 40 00 00 00 00 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 0b 00 00 00 14 00 00 00 07 00 00 00 0f 00 00 00 3c 00 00 00 02 00 00 00 ff ff 00 00 
  header_type: 80000007
  header_length: 0040
  header_transaction: 0000
ERROR: mbim message timeout

If we force the LN930 to reset itself, once it is back online the mbim script works fine (and all umbim commands execute quickly).  Or if we reboot, and connect immediately, it also works fine.

Is there something wrong with calling umbim subcriber and then just letting the card, and umbim, sit in this state?  If umbim is getting hung, is this a potential issue in umbim or on the LN930 itself?

Thanks for any advice, or pointers,
John

To update.  The issue with in umbim driver.  Messages get queued and out of sync and need to pay VERY special attention to -n and -t flags.

When we start the card, we now use

umbim -d $device subscriber

which seems to eliminate the issue.

The discussion might have continued from here.