Question for NB-IoT data collection and analytics

[haroldfeng]

I was recently researching NB-IoT communication signaling and found that MobileInsight supports this function, but after setting up a test environment, I found that the signaling could not be obtained.

In Windos environment, AT command was executed through COM port and Tashi device software to obtain IMEI and other information. However, in the Ubuntu environment, mobileinsight executes normally and cannot obtain signaling data. Therefore, I would like to ask about the models of NB-IoT devices supported by mobileinsight.

[Aghiles1998]

The same probleme with me

[haroldfeng]

@Aghiles1998 Your error message is about /dev/ttyUSB0 because the device diagnostics port was not recognized. The possible cause is that the corresponding driver is not installed or the device diagnostic mode is not enabled.

[Aghiles1998]

which option to choose here?

[Aghiles1998]

how to verify this ? Your error message is about /dev/ttyUSB0 because the device diagnostics port was not recognized. The possible cause is that the corresponding driver is not installed or the device diagnostic mode is not enabled.

[haroldfeng]

It doesn't seem to open from this option. My device is NB-IoT, which is not the same as UE.

Your command line result reads :"No such file or directory: '/dev/ttyUSB0' ". You can check to see if the file exists in /dev/.

[Aghiles1998]

yes for me is : tty0

[Aghiles1998]

i plugged the google pixel 5 with my computer i try to collect data with the mobile application inisght 6 it doesn't work

[Aghiles1998]

I want a solution please ?

[haroldfeng]

My device is now not satisfied with successful operation. Your error message is no device, should be needed to load usbserial. For example, modprobe usbserial vendor=0x04e8 product=0x681c.

Official tutorial reference: http://www.mobileinsight.net/get_started_desktop.html