Telit driver implementation

Telit driver implementation

[Enrico Sau]

[-- Attachment #1: Type: text/plain, Size: 482 bytes --]

Dear all,
I need to use ofono on a Telit module (UE910). I tried to use he910 plugin
and atmodem driver and it seems to recognize the modem but, some of the
interfaces does not work and I also need some more commands than the one
exported by atmodem.
This request is to ask what should I do? I'm currently starting to develop
a new driver (telitmodem) with the interfaces I need.
Is my behavior correct?

Thank you for any suggestion.
​Regards​

Enrico
​ Sau​

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 1132 bytes --]

Re: Telit driver implementation

[Jonas Bonn]

[-- Attachment #1: Type: text/plain, Size: 915 bytes --]

On 09/16/14 11:16, Enrico Sau wrote:
> Dear all,
> I need to use ofono on a Telit module (UE910). I tried to use he910
> plugin and atmodem driver and it seems to recognize the modem but,
> some of the interfaces does not work and I also need some more
> commands than the one exported by atmodem.
> This request is to ask what should I do? I'm currently starting to
> develop a new driver (telitmodem) with the interfaces I need.
> Is my behavior correct?

Since the UE910 is a member of the xE910 family and extremely similar to
the HE910 in functionality, it would be better to try to extend the
he910 driver to handle this device.

If you could provide a description of your problem and requirements,
then it might be easier to give you guidance:

i) what interfaces do not work?
ii) what commands do you require that are not exported?

The more info you can provide, the better.

/Jonas

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 1781 bytes --]

Re: Telit driver implementation

[Enrico Sau]

[-- Attachment #1: Type: text/plain, Size: 1834 bytes --]

Thanx for the quick answer,
what I don't really understand is the difference between drivers and
plugins in ofono.
Let's take an example: I need radio-settings interface to get and set the
technology preference. This interface is not implemented in atmodem driver.
Is it better to extend atmodem driver or to create a new driver? If I can
do it in plugin it would be fine, but how?
Plus I will need to extend the dbus interfaces to have some more method.
Looking at the dbus code I see that it calls the driver implementations, so
I think I have to either extend the atmodem driver or to create a new one.
Am I missing someting?

Thank you.


Enrico


2014-09-16 11:24 GMT+02:00 Jonas Bonn <jonas@southpole.se>:

>  On 09/16/14 11:16, Enrico Sau wrote:
>
>  Dear all,
> I need to use ofono on a Telit module (UE910). I tried to use he910 plugin
> and atmodem driver and it seems to recognize the modem but, some of the
> interfaces does not work and I also need some more commands than the one
> exported by atmodem.
> This request is to ask what should I do? I'm currently starting to develop
> a new driver (telitmodem) with the interfaces I need.
> Is my behavior correct?
>
>
> Since the UE910 is a member of the xE910 family and extremely similar to
> the HE910 in functionality, it would be better to try to extend the he910
> driver to handle this device.
>
> If you could provide a description of your problem and requirements, then
> it might be easier to give you guidance:
>
> i) what interfaces do not work?
> ii) what commands do you require that are not exported?
>
> The more info you can provide, the better.
>
> /Jonas
>
> _______________________________________________
> ofono mailing list
> ofono(a)ofono.org
> https://lists.ofono.org/mailman/listinfo/ofono
>
>

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 3431 bytes --]

Re: Telit driver implementation

[Denis Kenzior]

[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]

Hi Enrico,

Please do not top-post on this mailing list.

On 09/16/2014 04:36 AM, Enrico Sau wrote:
> Thanx for the quick answer,
> what I don't really understand is the difference between drivers and
> plugins in ofono.

Generally drivers/ directory contains atom drivers.  e.g. 
radio_settings, gprs, netreg, etc.  plugins/ contains modem drivers. 
There are a few additional special cases, but that is essentially the 
break down.

> Let's take an example: I need radio-settings interface to get and set
> the technology preference. This interface is not implemented in atmodem
> driver.
> Is it better to extend atmodem driver or to create a new driver? If I
> can do it in plugin it would be fine, but how?

In this case it would be better to write a new atom driver. e.g. 
drivers/telitmodem/radio-settings.c.

> Plus I will need to extend the dbus interfaces to have some more method.
> Looking at the dbus code I see that it calls the driver implementations,
> so I think I have to either extend the atmodem driver or to create a new
> one.

What methods do you need exactly?

Regards,
-Denis

Re: Telit driver implementation

[Enrico Sau]

[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]

Hi Denis,

2014-09-16 15:01 GMT+02:00 Denis Kenzior <denkenz@gmail.com>:​
>
> Generally drivers/ directory contains atom drivers.  e.g. radio_settings,
> gprs, netreg, etc.  plugins/ contains modem drivers. There are a few
> additional special cases, but that is essentially the break down.


​What do you mean with modem driver?


> What methods do you need exactly?
>

​There are more than one, and I'm still working on the requirements, but,
I'm pretty sure I will need to call the AT#TESTMODE command from my
application for example. How should I handle it?​



​There is one more thing: I tried to implement a new ​driver
drivers/telitmodem/radio-settings.c
​, and I added the call in he910 plugin post_online method: ​

ofono_radio_settings_create(modem, 0, "telitmodem", data->chat
​);

Everything
​ seems fine (I got no errors), and I started daemon with

ofonod --plugin=udevng,telitmodem,atmodem,he910 -nd
​
 ​

Anyway my driver is never called. Do I need to add telitmodem name
somewhere in order to be recognized from ofono?

Thank you.
Enrico

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 3948 bytes --]