- Dit onderwerp bevat 96 reacties, 17 deelnemers, en is laatst geüpdatet op 5 jaren, 2 maanden geleden door
.
-
Berichten
-
Hi David,
Thanks for your input!
Maybe / hopefully the ‘ID Problem’ could fix your issue.
This popup I programmed to becomes visible when there is an issue with the productid / serial combination.
Are you perhaps using new hardware?(I’ll check this part of the script on Kodi 17 issues and get back to you on this.)
Kind regards,
JeroenHi David,
I’d be happy to help you fix this. (It’s still just to cool to see my skin working in a R8!!)
The ProductID message is pointing in a direction which might be not to hard to solve.During all the ssh commands, have you ever had a wired connection?
Somehow it seems the script can’t generate it’s first params if there never was a wired connection.Please try to connect to internet via cable and then select the skin again.
If this does not work, could you send me a print screen of your settings menu (I don’t need IP addresses, you could erase them if you want / or send private message).
Kind regards,
JeroenPuuuuuh thats a Problem, i cant remove the Pi so Easy. Its Build in my Cd Changer and no Chance to connect a cable so quick to it 😀
I can only Put a Wifi Dongle into the USB Ports and Connect to a Wifi Point.But i will try it on the weekend.
thank u
Hey Jeroen,
i found the Problem but i cant solve it.So i restore my SD Card and do the Update Outside the Car connected via Cable.
All is Fine and Working on my Desktop, so i step into the Car.Same Problem if i activate the Skin, the Videooutput stops, but no ID Problem anymore.
So i disconnect one of the Canbus Cables and Video Signal comes back.
If i connect it again Signal goes away.So any Canbus message must blocked the VideoModul.
Is it possible to figured out with one? Is it possible to deactivate some canbus scripts by hand?I have make the Video from the Situation 🙂 : https://youtu.be/fztugl-JhdM
so i backuped my sd Card and Kodi 15 with 0.30 is working fine.
Did u have any ideas?
Thank u
regards
DaveHi Dave,
Just to be sure (I added an option at version 31 which makes it possible to enable rearview cam by pressing S1 button on the can-bus board), your case cover seems to fit very tight on tbe board. It’s not pressing S1, which makes your Kufatec interface switch to different input?
Kind regards,
Jeroenmh i didnt have any buttons on my pi2can Board ( Layout: http://skpang.co.uk/catalog/images/raspberrypi/pi_2/IMG_0002.jpg)
So the Case is not pressing anything, looks tight but its okay 🙂
should i try 0.31 on Kodi 15 ? Maybe thats the Problem, i have only 0.30 in my Car and then updatet to Kodi 17 and 0.35,0.36,0.37regards
DaveHi Dave,
I made the S1 button script optional (you can enable / disable it at the Config page, should be off by default).
Download V0.0.38Kind regards,
Jeroenmh okay, if its off by default, this should not be the problem. i will check it tomorrow, some other ideas?
Hi Dave,
I start to think it’s also possible something went wrong during your update / upgrade process.
It will help a lot to have a look at your can-traffic logfile. It should be available at /home/pi/rnslogs.Also to be sure your Video Interface is or isn’t responding to any can-messages I send, I uploaded a version which does not send any messages (so only RNS buttons should work).
Kind regards,
JeroenHey Jeroen thank u for the quick response,
i installed the whole pi new today, same Problem. No Picture.
Now i tested your NoCan-Send Skin and its works fine, no Picture issue.
But my /home/pi/rnslogs/ is empty.
Can we enable the Cansen step by step to find the wrong canmessage?
Thanks for ur quick Help 🙂
Ok iam back =)
0.38 works too, so the issue was the S1 Feature 🙂
One Little Problem is i hear a lot of “cantalk” Noises out of the Speakers and the Controls are very laggy
If i activate “Block FIS” then its all perfect!Thank u very much 🙂
Sorry for Spam 😀
I found a Bug in 0.38
Every Restart i must set “Block FIS” again.
It doesnt save the state or reset it after a Restart.If u can Fix this, the skin works Perfect =)
Hi Dave,
Getting the Skin settings to work was the biggest challenge while building the Kodi 17 skin.
I’ll have a close look soon why particulairly the FIS block isn’t saved automaticly.The quick fix is to reload the skin after you changed the setting (keyboard press F5).
This makes that the setting is directly written to the settings.xml file and therefor available after a reboot.By the way; if it is so busy on your can-network, maybe your R8 sends additional data to play with.
If you don’t mind I’ll make a new logging model to test this on your bus.Kind regards,
Jeroen
- Je moet ingelogd zijn om een antwoord op dit onderwerp te kunnen geven.