BMWRaspControl - Forum

it's a bit tricky, but i can give step by step instruction tomorrow for linux system with dd

thanks Harry,

thank you harry for your passion
-the addon is always working on GPIO23 not possible to return to the BM screens.
- I have no ibus communication in BC; no car info
Thanks Harry ...

what's your setting for serial device? is it set to /dev/ttyUSB0?

hello harry.
yes it is / dev / ttyUSB0
and I start pibus with crontab with
/home/osmc/.kodi/addons/plugin.script.ibuscommunicator/resources/lib/pibus -g0 / dev / ttyUSB0
all buttons work fine but no bus info
and no BM screens. of course with GPIO23

can't follow what happens exactly between kodi and aa.
and whats your wire connection.

pibus in normal mode uses it's own button control.
what does the -g0 argument?

with your addon I connect nothing but usb ibus and GPIO23.
the switch between kodi and aa works very well,
if I disconnect GPIO23 I see CD1-4
as if using "always" on ibuscomunicator
you mean i can not use -g0 before / dev / ttyusb0?

screen enable and disable works well, also?
the question was, what does -g0?
is kodi in background, if aa is focused?
for ibuscommunicator i use some other arguments. the addon sends it's own cd emulation.

- g0 : -g <number> GPIO number to use for IBUS line monitor (0 = Use TH3122) = "elmos SO16"
- no. screens can not deactivate always stays on pibus. Why?
-no.kodi cannot be in the background, cannot minimize kodi. so we kite kodi for aa and the reverse
that's why i want to start pibus when pi starts

i have seen the text. but what's the function for this ibus line monitor. why is it required?
screens not working, tells it's not working well.
i need pibus always, because the audio source handling do it by the addon.
on kodi closing, the ibus addon kills the pibus process.