5:31 a.m.
Hi,
I am running connman in a 4G LTE device in Linux system, are there
anyway to get SIM ID? and the Operator and LTE signalling strength?
Unfoutuantly, I don't have connmanctl due to the limitation of the
space to install Python.
Thank you.
Kind regards,
- jh
8:56 a.m.
On 31.10.19 06:31, JH wrote:
I am running connman in a 4G LTE device in Linux system, are there
anyway to get SIM ID? and the Operator and LTE signalling strength?
Unfoutuantly, I don't have connmanctl due to the limitation of the
space to install Python.
Hi jh,
Assuming you're using ofono to provide your 4G LTE connectivity, it
provides a dbus interface where it exposes a lot of detail about GSM
status (including SIM serial, IMSI, current network, signal strength etc).
All you need is a dbus client. There's one in Debian package "dbus"
called dbus-send. Some sample commands I use with ofono v 1.21:
# Get list of modems
$ sudo dbus-send --system --print-reply --dest=org.ofono /
org.ofono.Manager.GetModems
# Get general configuration of modem "/quectel_0"; enable roaming
$ sudo dbus-send --system --print-reply --dest=org.ofono /quectel_0
org.ofono.ConnectionManager.GetProperties
$ sudo dbus-send --system --print-reply --dest=org.ofono /quectel_0
org.ofono.ConnectionManager.SetProperty string:"RoamingAllowed"
variant:boolean:true
# Get status of network registration on modem "/quectel_0"
$ sudo dbus-send --system --print-reply --dest=org.ofono /quectel_0
org.ofono.NetworkRegistration.GetProperties
# List all GPRS contexts
$ sudo dbus-send --system --print-reply --dest=org.ofono /quectel_0
org.ofono.ConnectionManager.GetContexts
# Get status of GPRS context number 1
$ sudo dbus-send --system --print-reply --dest=org.ofono
/quectel_0/context1 org.ofono.ConnectionContext.GetProperties
I've also used Python to build my own simple dbus client for GSM
monitoring purposes. I used the 'pydbus' library provided by Debian
package "python3-pydbus". You can look for other alternatives if you're
low on disk space, e.g. going with dbus-send or implementing your custom
dbus client in C/C++.
--
Kind regards,
Tarmo
12:05 p.m.
Hi Tarmo,
On 10/31/19, Tarmo Kuuse <tarmo.kuuse(a)gmail.com> wrote:
Assuming you're using ofono to provide your 4G LTE connectivity,
it
provides a dbus interface where it exposes a lot of detail about GSM
status (including SIM serial, IMSI, current network, signal strength etc).
Yes, I am using ofono.
All you need is a dbus client. There's one in Debian package
"dbus"
called dbus-send. Some sample commands I use with ofono v 1.21:
# Get list of modems
$ sudo dbus-send --system --print-reply --dest=org.ofono /
org.ofono.Manager.GetModems
# Get general configuration of modem "/quectel_0"; enable roaming
$ sudo dbus-send --system --print-reply --dest=org.ofono /quectel_0
org.ofono.ConnectionManager.GetProperties
$ sudo dbus-send --system --print-reply --dest=org.ofono /quectel_0
org.ofono.ConnectionManager.SetProperty string:"RoamingAllowed"
variant:boolean:true
# Get status of network registration on modem "/quectel_0"
$ sudo dbus-send --system --print-reply --dest=org.ofono /quectel_0
org.ofono.NetworkRegistration.GetProperties
# List all GPRS contexts
$ sudo dbus-send --system --print-reply --dest=org.ofono /quectel_0
org.ofono.ConnectionManager.GetContexts
# Get status of GPRS context number 1
$ sudo dbus-send --system --print-reply --dest=org.ofono
/quectel_0/context1 org.ofono.ConnectionContext.GetProperties
That is great, I do have dbus-send in the device, but I know little
about it, I tried to play it, but could not get into array and dict
entry, sorry for asking a dbus-send syntax question, how could you run
dbus-send to display the array and dict entry for string
"CardIdentifier" variant value?
# dbus-send --system --print-reply --dest=org.ofono /ubloxqmi_0
org.ofono.SimManager.GetProperties
method return time=1572518707.814990 sender=:1.4 -> destination=:1.9 serial=85 2
array [
dict entry(
string "Present"
variant boolean true
)
dict entry(
string "CardIdentifier"
variant string "xxxxxxxxxxxxx"
)
............
I tried following command, apparently it is wrong, could you please
show me a correct command syntax?
# dbus-send --system --print-reply --dest=org.ofono /ubloxqmi_0
org.ofono.SimManager.array.dict:string:CardIdentifier
....incorrect Aborted
I've also used Python to build my own simple dbus client for GSM
monitoring purposes. I used the 'pydbus' library provided by Debian
package "python3-pydbus". You can look for other alternatives if you're
low on disk space, e.g. going with dbus-send or implementing your custom
dbus client in C/C++.
Yeah, long way to go :-), first have to lean the dbus-send command
line, my application is using C++, so I will use the C++.
Thank you so much Tarmo
Kind regards,
- jh
12:21 p.m.
On 31.10.19 13:05, JH wrote:
On 10/31/19, Tarmo Kuuse <tarmo.kuuse(a)gmail.com> wrote:
> Assuming you're using ofono to provide your 4G LTE connectivity, it
> provides a dbus interface where it exposes a lot of detail about GSM
> status (including SIM serial, IMSI, current network, signal strength etc).
Yes, I am using ofono.
> All you need is a dbus client. There's one in Debian package "dbus"
> called dbus-send. Some sample commands I use with ofono v 1.21:
>
> # Get list of modems
> $ sudo dbus-send --system --print-reply --dest=org.ofono /
> org.ofono.Manager.GetModems
>
> # Get general configuration of modem "/quectel_0"; enable roaming
> $ sudo dbus-send --system --print-reply --dest=org.ofono /quectel_0
> org.ofono.ConnectionManager.GetProperties
> $ sudo dbus-send --system --print-reply --dest=org.ofono /quectel_0
> org.ofono.ConnectionManager.SetProperty string:"RoamingAllowed"
> variant:boolean:true
>
> # Get status of network registration on modem "/quectel_0"
> $ sudo dbus-send --system --print-reply --dest=org.ofono /quectel_0
> org.ofono.NetworkRegistration.GetProperties
>
> # List all GPRS contexts
> $ sudo dbus-send --system --print-reply --dest=org.ofono /quectel_0
> org.ofono.ConnectionManager.GetContexts
> # Get status of GPRS context number 1
> $ sudo dbus-send --system --print-reply --dest=org.ofono
> /quectel_0/context1 org.ofono.ConnectionContext.GetProperties
That is great, I do have dbus-send in the device, but I know little
about it, I tried to play it, but could not get into array and dict
entry, sorry for asking a dbus-send syntax question, how could you run
dbus-send to display the array and dict entry for string
"CardIdentifier" variant value?
# dbus-send --system --print-reply --dest=org.ofono /ubloxqmi_0
org.ofono.SimManager.GetProperties
method return time=1572518707.814990 sender=:1.4 -> destination=:1.9 serial=85 2
array [
dict entry(
string "Present"
variant boolean true
)
dict entry(
string "CardIdentifier"
variant string "xxxxxxxxxxxxx"
)
............
I tried following command, apparently it is wrong, could you please
show me a correct command syntax?
# dbus-send --system --print-reply --dest=org.ofono /ubloxqmi_0
org.ofono.SimManager.array.dict:string:CardIdentifier
....incorrect Aborted
I understand exactly :) I'm not an expert, but it seems like all the
dbus query interfaces defined by ofono
(org.ofono.<component>.GetProperties) return a big composite response
with all data items. When you want to get an individual data item out of
it, you need to parse it yourself.
So you can't query for a single item and dbus-send doesn't seem to
support extracting a single item out of the composite response.
Hence the custom Python query client I wrote (which has maybe 100 lines,
most of it command line options processing). You can probably get away
with processing dbus-send's almost-machine-readable text output with awk
or whatever text tools you have available.
> I've also used Python to build my own simple dbus client for
GSM
> monitoring purposes. I used the 'pydbus' library provided by Debian
> package "python3-pydbus". You can look for other alternatives if
you're
> low on disk space, e.g. going with dbus-send or implementing your custom
> dbus client in C/C++.
Yeah, long way to go :-), first have to lean the dbus-send command
line, my application is using C++, so I will use the C++.
Have fun!
--
Kind regards,
Tarmo Kuuse
11:03 p.m.
On 10/31/19, Tarmo Kuuse <tarmo.kuuse(a)gmail.com> wrote:
I understand exactly :) I'm not an expert, but it seems like all
the
dbus query interfaces defined by ofono
(org.ofono.<component>.GetProperties) return a big composite response
with all data items. When you want to get an individual data item out of
it, you need to parse it yourself.
So you can't query for a single item and dbus-send doesn't seem to
support extracting a single item out of the composite response.
That should be fine, just wandering if it is my ignorance about the
dbus-send :-). I can use bash command awk etc to parse it.
Hence the custom Python query client I wrote (which has maybe 100
lines,
most of it command line options processing). You can probably get away
with processing dbus-send's almost-machine-readable text output with awk
or whatever text tools you have available.
Exactly, that works fine. Will go C++ parsing.
Thank you very Tarmo, it is great kind help, really appreciate it.
Kind regards,
- jh
9:23 a.m.
Sorry Tarmo, I tried following command to get LTE signaling strength
level, but it give me 0:
dbus-send --system --print-reply=literal --type=method_call --dest
=org.ofono /ubloxqmi_0 org.ofono.NetworkRegistration.GetProperties
array [
dict entry(
Status variant registered )
dict entry(
Mode variant auto )
dict entry(
CellId variant uint32 136855820
)
dict entry(
Technology variant lte )
dict entry(
MobileCountryCode variant 505 )
dict entry(
MobileNetworkCode variant 01 )
dict entry(
Name variant Telstra )
dict entry(
Strength variant byte 0
)
]
Are you able to get LTE signaling strength? Or was it a wrong command?
If you won't mind what would be a correct the command to get signaling
strength?
Thank you.
Kind regards,
- jh
On 11/1/19, JH <jupiter.hce(a)gmail.com> wrote:
> On 10/31/19, Tarmo Kuuse <tarmo.kuuse(a)gmail.com> wrote:
>> I understand exactly :) I'm not an expert, but it seems like all the
>> dbus query interfaces defined by ofono
>> (org.ofono.<component>.GetProperties) return a big composite response
>> with all data items. When you want to get an individual data item out of
>> it, you need to parse it yourself.
>>
>> So you can't query for a single item and dbus-send doesn't seem to
>> support extracting a single item out of the composite response.
>
> That should be fine, just wandering if it is my ignorance about the
> dbus-send :-). I can use bash command awk etc to parse it.
>
>> Hence the custom Python query client I wrote (which has maybe 100 lines,
>> most of it command line options processing). You can probably get away
>> with processing dbus-send's almost-machine-readable text output with awk
>> or whatever text tools you have available.
>
> Exactly, that works fine. Will go C++ parsing.
>
> Thank you very Tarmo, it is great kind help, really appreciate it.
>
> Kind regards,
>
> - jh
>
11:11 a.m.
On Thu, Oct 31, 2019 at 03:31:30PM +1100, JH wrote:
Hi,
I am running connman in a 4G LTE device in Linux system, are there
anyway to get SIM ID? and the Operator and LTE signalling strength?
Unfoutuantly, I don't have connmanctl due to the limitation of the
space to install Python.
connmanctrl is writtin in C.
$ls -lh connmanctl
-rwxrwxr-x 1 wagi users 270K Sep 26 08:19 connmanctl
$ ldd connmanctl
linux-vdso.so.1 (0x00007ffc00020000)
libdbus-1.so.3 => /usr/lib64/libdbus-1.so.3 (0x00007efbff65d000)
libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007efbff537000)
libreadline.so.8 => /lib64/libreadline.so.8 (0x00007efbff4e3000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007efbff4de000)
libc.so.6 => /lib64/libc.so.6 (0x00007efbff317000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007efbff2f5000)
libsystemd.so.0 => /usr/lib64/libsystemd.so.0 (0x00007efbff248000)
libpcre.so.1 => /usr/lib64/libpcre.so.1 (0x00007efbff1af000)
libtinfo.so.6 => /lib64/libtinfo.so.6 (0x00007efbff17e000)
/lib64/ld-linux-x86-64.so.2 (0x00007efbff6d5000)
librt.so.1 => /lib64/librt.so.1 (0x00007efbff173000)
liblzma.so.5 => /usr/lib64/liblzma.so.5 (0x00007efbff13d000)
liblz4.so.1 => /usr/lib64/liblz4.so.1 (0x00007efbff11b000)
libgcrypt.so.20 => /usr/lib64/libgcrypt.so.20 (0x00007efbfeffa000)
libgpg-error.so.0 => /usr/lib64/libgpg-error.so.0 (0x00007efbfefd6000)
Some interesting dependencies I'd say...
Thanks,
Daniel
391
days inactive
397
days old
6 comments
3 participants
participants (3)
-
Daniel Wagner -
JH -
Tarmo Kuuse