Python – Kodi naar FIS

Tags: , , , , , ,

15 berichten aan het bekijken - 16 tot 30 (van in totaal 33)
  • Auteur
    Berichten
  • #3509
    Jürgen
    Bijdrager

    Hello Jeroen,

    Thanks for your explanation. I have uploded new logfiles from Saturday. These are lögs from incomming call without activated Addons. Tomorror i will generate new logs with aktivated
    “send to FIS” Adds and will recive a call. 🙂

    BR Jürgen

    #3558
    Janssuuh
    Sleutelbeheerder

    Hi Jürgen,
    I’ve analyzed your latest upload, but sadly there’s no Phone call logged.
    There is only TV/VIDEO and KMA on the 261/263 IDs for about 70 seconds;

    First item: 2016-12-17 14:53:46
    Last item: 2016-12-17 14:54:58

    (thats about how long the log takes to reach 7500 rows)
    Maybe the log just missed the call (in timing).

    The 665 messages was send every second with consistent data again. Though the message is different than a few days ago. (I’ve read somewhere this could be data about your phones battery and reception details.)

    Last week: 61 38 00 AA CA AA 2A
    Saterday: 61 25 00 AA 9A AA 2A

    Looking forward to your new logs 🙂

    Kind regards,
    Jeroen

    #3570
    Jürgen
    Bijdrager

    Hello Jeroen,

    Yes, the last logfiles are trash. Thats my fault, because i have changed something with VCDS in the thelefoninterface. I have deactivate “display call informations in Fis”.

    Now you have new log liles.
    Log files from 20:58 are showing syncronysing the Phonebook
    Log files from 21:13 will show an incomming call.

    I hope thats ok.

    Berst regards
    Jürgen

    #3573
    Janssuuh
    Sleutelbeheerder

    Hi Jürgen,

    Now the 265 and 267 show up:

    Log jurgen

    The 665 messages also show a sequentiality of which we might get starting to make assumptions with 🙂
    I’ll mail the full log to you, but the 665 seem to to have the following meaning;

    665#61 passif (no FSE FIS content)
    665#77 active (ANRUF …..)
    665#67 ending (first ANRUF BEENDED)
    665#63 FIS content, no calling (ANRUF BEENDED)

    (265 and 267 both twice send a message full of zero’s)

    665#61 passif (no FSE FIS content)

    I hope the 665#67xxx triggers Rns-e to stop silence mode.
    I’ll try to recode my plugin with the 665#67xxx and with the 665#63xxx message and see if it shows any result.

    With al this info I think I’ll need to add an (ugly) override to the default 665#61 FSE sends regulairly every second.

    Summarized; the FSE says every second “I’m not doing anything, any FIS line 1 and 2 (265/267) won’t set visible, but the regulair 261/263 TV/VIDEO or PHONE content will be visible. The raspberry at the same time says every second “Ok, Phone active, let me send content to 265/267. This “argue” explains the flickering.

    We might be able to reduce this to a minimum if we can catch the exact timestamp of the FSE message and directly follow it up with a raspberry 665#63xxx message. (To keep the flicker back to TV/VIDEO as short as possible, our hopefully just invisable or unnoticable) 😀

    If this ugly workaround does not turn out to be effective there might be a way to reject FSE acceptance in the device “Ring” (There is a follow up order between IDs 428 – 436 – 43A) It could be possible to break this ring, make FSE stop sending anything. Question is if it’s possible to “reconnect” FSE and have KI to accept FSE again…. Hopefully the first workaround does the trick!!

    I hope to be able to upload a new version of the plugin with this function built in before end of this week.
    You’ll be able to download it from the homepage (and send you an update about it ofcourse.)

    Kind regards,
    Jeroen

    #4056
    Janssuuh
    Sleutelbeheerder

    Hi Jürgen,

    I made a (temporary) option which lets you choose the OEM FSE overwriting message:

      

    You could now try to select each of the appearing messages, and test which one (if one!) applies the FIS overwrite, but not the silence / switch to your Phone screen. (Changes effects after pressing “OK” button.)

    Kind regards,
    Jeroen

    #4148
    Jürgen
    Bijdrager

    Hi Jeroen,

    !Happy New Year!

    I´ve testet each options step by step. No option will overwrite the FIS. The penultimate entry (772500FFCFAA2A) will slow down the flickering a little bit.

    Two other things I noticed:
    – If i deactivate the Plugin “Send Kodi to FIS”, Kodi Skin will freeze. Music will playing in background, but i can´t controll Kodi with RNS-E Buttons or Keyboard. A reboot will help me.
    I’ve always had this behavior.

    – When you change from Kodi Confluance Skin to RNS-E Skin the apply buttons “Yes ” and “No” are changed.

    Is it possible to implement an option to send the reverse Signal over Can? I will need this because the Kufatec Adapter will not swithch to Rear View Cam. I´ve analyced my Can messages and now i kow, that my Audi B6 is not sendign this Can Messages.
    I think thats an possible solution:
    We will set GND to one unused GPIO on the Raspberry an than we send the “351 00 6E 10 AE 09 76 75 05 8 Nee Byte 0, 00 vooruit / 01 achteruit” command

    -Kufatec Support is sending me following:
    Probieren Sie bitte folgendes aus:

    0x470, messagelänge: 8.

    Byte[0] = 0x20 wenn der RF-Gang eingelegt ist und
    Byte[0] = 0x00 wenn der RF-Gang wieder raus ist.

    How should the Can message look like? This is not clear to me. I should send this command every 100ms?

    Kind regards,
    Jürgen

    #4265
    Janssuuh
    Sleutelbeheerder

    Hi Jürgen,

    Happy New Year!
    Sorry for de delay in my reply, I’m packing / getting ready to go on a small holiday.

    If you’re using the Full Plugin, the “Send Kodi to FIS” functionality is built in. You could uninstall the Kodi to FIS plugin.
    (Of course, you could keep using it if you’d like to have the FIS functionality on another skin.)

    I’ll have a look at the DialogYesNo.xml. The ordering of the Yes / No buttons is different then the Confluence skin you say?

    In one of your logs I see CanID 351 was sent. So I asume it does not change from 351#00…… to 351#01…… if you reverse.
    Adding this to the script is not going to help, because of the same scenario as we saw on the FSE (contradictory messages from the devices). The 351 messages indeed is send every 100ms.

    I’ve read about the 470 message. It’s not available on my B6 (infotainment-bus).
    Did you test the Rns-e engineering mode? I don’t understand why your B6 would not tell Rns-e it’s gear position (needed for nav unit).

    Kind regards,
    Jeroen

    #4345
    Jürgen
    Bijdrager

    Good Morning,
    I wish you nice holiday.

    – Yesterday i have retried my tests with “send to FIS Option”. I don´t know that i do not need the Plugin “Kodi to FIS”. I´ve uninstalled it and do the tests again.
    Now the results are promising. When i activate one of the Can IDs in the list the flickering will stop and mute from FSE is off. I can hear the sound. I do a video clip and send it to you.

    – Yes the ordering of the Yes / No buttons is different when you switch from Confluence to RNS-E Skin. (in german language settings)
    You can see this in the second video.

    – I tested CAN ID 351. To me the construction of the Can Message is not clear. You say the first byte should be change from 351#00…… to 351#01…… if i reverse.
    351 [8] 00 00 00 00 00 6D 71 10 ‘…..mq.’

    So the first Should be switch to 01? Its intresting. In my case the firs Byte will show me the ignition. When Ignition is on the value is 00. Whene ignition is off than i saw 45 or 44. I do 2 tests an logged this.

    retour.txt will show following prozess: Ignition on –> switch to backwards and wait 4 seconds –> go to neutal –> start engine –> drive backwards –> drive forward –>switch off engine.

    retour2.txt will show: switch on ignition –> switch to backwards and wait 4 seconds –> go to neutal (4 or 5 reruns)

    In RNS-E engenering Mode the Vehicle Signal “REV” will alwas be OFF. (I will send you a picture)

    BR
    Jürgen

    #4710
    Jürgen
    Bijdrager

    Hello Jeroen,

    I have an solution for my Reverse Vehicle Signal Problem. I found out that i can simulate the switch signal with following Can ID

    cansend can0 470#20 simuliert umschaltsignal am Kufatec Multimediaadapter

    in Can ID 351 do not get the reverse Signal. Wen i send 351#02 i see that the ENS-E will switch to Revert in engeneering Mode. I Think its not posible to change the original can message?

    So please can you implement me an Option to send the 470#20 00 00 00 00 when i switch one of the GPIO on the raspberry to Ground or 3,3V?

    I have found a link with examples in python:

    Eingang lesen

    Raspberry Pi: GPIO – Ausgänge schalten, Eingänge lesen

    Thanks,
    BR Jürgen

    #4963
    Janssuuh
    Sleutelbeheerder

    Hi Jürgen,

    Have you checked which pins the canbus hardware uses?
    If this does not interfere (or the Relais Module could be used on another pin) it seems to be potentionally possible 🙂

    Do you already own the module?
    I’ll try to find some time maybe at the end of this week. (I’m expecting my second child and I am currently busy to create an extra bedroom 🙂 )

    Kind regards,
    Jeroen

    #5041
    Jürgen
    Bijdrager

    Hello,

    We can use the two Buttons S1 and S2 from PI Can Board and the red LED for status. (when switch gear to backward, LED is on and off when driving forwards)

    1.7. LED
    There is a red LED fitted to the board. This is connected to GPIO22.
    1.8. Not Fitted Items
    The board has footprint for two mini push buttons S1 and S2, they are connected to
    GPIO24 and GPIO23 respectively.

    I will send you a electric schematic drawing via email as I imagine.

    Have you news for me whats the next steps in overwrite the oriiginal FSE messages?

    I wish you a lot of fun in setting up the children’s room. All the best for your expected child and family.
    My little boy is 20 month and every day is great. He´s lerning every day new stuff and nonsense. 🙂

    I have seen you speak german. Whats your favorite language english or german?

    Best Regards
    Jürgen

    #5270
    Janssuuh
    Sleutelbeheerder

    Hi Jürgen,

    Thanks for the electric scheme!
    As for now I’ll continu to write in English if you don’t mind. I have a little less trouble finding the correct expressions than in German.
    I actually have lived near the German border for a few years, which still makes me thing I speak some German sometimes, but it just stays hard to find the right words. (In school we’ve been taught perfect grammer though! – Der Die Das Des Dem Den :))

    I’ll try to add some (plain) python (like your example link) to the plugin which you could use to test on.
    Als the FSE project seems to stall a bit. I’ll add a ‘Kill FSE’ option, which tells the FSE to stop writing to the FIS.
    It’s not the end result we want, but if it does stop sending to the FIS it might be a something!

    Kind regards,
    Jeroen

    #5414
    Janssuuh
    Sleutelbeheerder

    Hi Jürgen,

    There was an issue with a unknown character in a comment tag 😎
    I tested the script now, and because I’m lucky enough to have the old board with the real buttons:

    Pican Board

    It is now sending the can-message each 100ms (while pressed) (S1 sends the 470 and S2 sends the 351 message).
    Posted a demo on YouTube;

    I’ll mail you the test plugin, *very curious whether it will switch your RNS-E to REV-Cam :)*

    Kind regards,
    Jeroen

    #5417
    Jürgen
    Bijdrager

    Hello Jeroen,

    Thanks, on your PI Board how much ohm are the resistors? 1k Ohm like your picture or 10K ohm?

    BR Juergen

    #5469
    Jürgen
    Bijdrager

    Hello Jeroen,

    I´ve testet the new skin and it works. Thank you. Only a little flickering i´ve seen.

    Maybe this is a timing problem. Every 100ms i think. I do not have this information. Only this:

    0x470, messagelänge: 8.
    Byte[0] = 0x20 wenn der RF-Gang eingelegt ist und
    Byte[0] = 0x00 wenn der RF-Gang wieder raus ist.

    I will upload my CAN logs taken, while i took the video.

    Best Regards,
    Jürgen

15 berichten aan het bekijken - 16 tot 30 (van in totaal 33)
  • Je moet ingelogd zijn om een reactie op dit onderwerp te kunnen geven.