04-17-2024, 09:43 PM
(This post was last modified: 04-17-2024, 09:45 PM by JohnA.
Edit Reason: qml vs qmi mistake
)
OK, more notes.
I've been trying to get the ofonod program to work, as I'm hoping it will have the full comms with the car interface, including the telephone book, answering calls from the car, and so on.
I had originally hoped to just tune the config files, but it seems more difficult. There's confusion between the gobi, quectelqmi and quectel plugins & the atmodem and quectelqmi drivers. It seems that I need to make a quectelppp plugin which farms out the needed tasks to the quectelqmi and atmodem drivers, as it seems the ppp has divided up the responsibilities between a qmi interface for power, signal strength etc. and the atmodem for actual modem dialup and similar commands.
Of course I could be wrong ... maybe a single "tweak" will get it all going, but that's my current path.
At least I'm now much more familiar with how dbus and udev work.
Please let me know if there has been progress elsewhere!
Cheers, John.
I've been trying to get the ofonod program to work, as I'm hoping it will have the full comms with the car interface, including the telephone book, answering calls from the car, and so on.
I had originally hoped to just tune the config files, but it seems more difficult. There's confusion between the gobi, quectelqmi and quectel plugins & the atmodem and quectelqmi drivers. It seems that I need to make a quectelppp plugin which farms out the needed tasks to the quectelqmi and atmodem drivers, as it seems the ppp has divided up the responsibilities between a qmi interface for power, signal strength etc. and the atmodem for actual modem dialup and similar commands.
Of course I could be wrong ... maybe a single "tweak" will get it all going, but that's my current path.
At least I'm now much more familiar with how dbus and udev work.
Please let me know if there has been progress elsewhere!
Cheers, John.