10-20-2023, 11:21 AM
@MakeUseOfRaspi:
- Activating tv input although it is already active switches the RNS-E video mode (picture gets stretched so the bottom 20% is cut off) and I do not need it, so I leave it to „False“ (just for information: this „effect“ is also present when radio switches to reverse camera. I think it expects a NTSC signal and therefore only displays 480 instead of the 576 pixels)
-> I've seen the same. Don't know yet if it's because of PAL/NTSC or something else. There are two different can messages to activate tv input. On goes "fullscreen" for me, on has 20% black bar at the bottom.
- Writing to the DIS does not work at all (I have not understood yet if I have to code out my original handsfree for it to work. Maybe I will test it with VCDS)
-> It's better to have hands free not coded/connected otherwise the text in dis/fis will switch/flicker between hands free messages and the messages from the script and your phone book will open with steering wheel controls. The script will check if hands free messages are existing. If so it will not send it by itself.
- Button control unfortunately does not work at all (I hope that previous/next work properly here and that I can also use the steering wheel button)
-> No Buttons? Steering wheel buttons has to be tested. Didn't had much users to really test that good.
- Reverse gear: did I understand it correctly that the api function does not work? Right now I am using the GPIO to trigger the video grabber (not using raspberry camera), but I really would like to get rid of the extra cabling since the gear info is on can anyway. Maybe the api function and reverse gear detection can be combined somehow?
-> The script can read can bus message to check if forward or reverse gear is engaged.
-> It is possible to trigger oap reversecamera function, but in my case i didn't got an image at all. Because of that i use PiCamera to show reversecamera image.
- Activating tv input although it is already active switches the RNS-E video mode (picture gets stretched so the bottom 20% is cut off) and I do not need it, so I leave it to „False“ (just for information: this „effect“ is also present when radio switches to reverse camera. I think it expects a NTSC signal and therefore only displays 480 instead of the 576 pixels)
-> I've seen the same. Don't know yet if it's because of PAL/NTSC or something else. There are two different can messages to activate tv input. On goes "fullscreen" for me, on has 20% black bar at the bottom.
- Writing to the DIS does not work at all (I have not understood yet if I have to code out my original handsfree for it to work. Maybe I will test it with VCDS)
-> It's better to have hands free not coded/connected otherwise the text in dis/fis will switch/flicker between hands free messages and the messages from the script and your phone book will open with steering wheel controls. The script will check if hands free messages are existing. If so it will not send it by itself.
- Button control unfortunately does not work at all (I hope that previous/next work properly here and that I can also use the steering wheel button)
-> No Buttons? Steering wheel buttons has to be tested. Didn't had much users to really test that good.
- Reverse gear: did I understand it correctly that the api function does not work? Right now I am using the GPIO to trigger the video grabber (not using raspberry camera), but I really would like to get rid of the extra cabling since the gear info is on can anyway. Maybe the api function and reverse gear detection can be combined somehow?
-> The script can read can bus message to check if forward or reverse gear is engaged.
-> It is possible to trigger oap reversecamera function, but in my case i didn't got an image at all. Because of that i use PiCamera to show reversecamera image.