Have you switched the setting from USB to miniPCI-e on ROS?
Have not looked at that. Thanks for the tip. I will investigate.
Also here is some potentially good info from one of the largest Sierra resellers in North America.
This was sent to me when I asked Sierra directly who I should purchase from in Canada and then I asked about QMI vs DIP...
DirectIP vs. QMI
DirectIP:
- Independent control of user plane and data plane
o Different USB interfaces for control vs data
- Data sessions can be controlled by AT commands
- Simple to setup a data session (one AT cmd to configure profile, one to trigger data session)
o User can test manually from a terminal program
- Currently supports multiple concurrent data sessions (PDP contexts) to host
o Note: works in HSPA but not fully tested on LTE
- No support for CDMA (therefore can’t be used with MC7750).
- No SDK support on MC77xx platforms as we don’t officially support CNS on MC77xx
- Windows and Linux driver support available
QMI:
- Control and data planes are multiplexed together
o Share a single USB interface for control & data
- Data sessions can only be controlled via QMI protocol
- Compared to AT cmds, much more complicated to setup a data session as control services need to be initialized before any QMI commands can be sent
o Need some sort of host program to do this (can’t be done manually)
- Currently, does not support multiple concurrent data sessions to host
o QCT has no plans to support but Sierra looking to add this support ourselves
o May be more complicated than DirectIP due to fact that we will need to split control and data planes for subsequent data sessions (i.e. one control interface for multiple data paths)
- Supports CDMA (currently only option for MC7750).
- Supported via QMI SDK in Linux and Windows
- Windows and Linux driver support available