Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


jordan8thepie1

73 posts

Master Geek
+1 received by user: 18


#317500 22-Oct-2024 14:42
Send private message

 We have a Samsung PS-63P71FH 63 inch plasma TV in the lobby at work. TV Spec page https://www.samsung.com/nz/support/model/PS63P71FHX/RAD/

 

We recently in the last month moved our Raspberry Pi running Yodeck over to this TV from a portable TV that worked fine with HDMI-CEC commands. 

 

Problem is that the HDMI-CEC command to turn off the TV fails and then TV stays on all night displaying no signal on HDMI 3. All other HDMI-CEC functions like Turning on the TV and Switching Input works fine as the Raspberry PI happily sends these commands to the TV.

 

I have tried different HDMI ports to no avail. Switching to a different HDMI Port in the long term is not an option as most of the ports are located at the back of the TV and the bracket does not have a lot of room behind it hence why we use HDMI 3 located on the side of the TV.

 

 


Create new topic
gehenna
8667 posts

Uber Geek
+1 received by user: 3883

Moderator
Trusted
Lifetime subscriber

  #3299900 22-Oct-2024 15:16
Send private message

According to the manual it needs the PC input to be HDMI 2 and then define that port to be named PC once connected.  It says other ports aren't guaranteed to work and depends on the settings of those input devices.




jordan8thepie1

73 posts

Master Geek
+1 received by user: 18


  #3299952 22-Oct-2024 15:39
Send private message

I did try connecting to HDMI 2 and did label the port as PC but it still didn't work i also did the same with HDMI 1 which has the same effect.


gehenna
8667 posts

Uber Geek
+1 received by user: 3883

Moderator
Trusted
Lifetime subscriber

  #3299961 22-Oct-2024 16:05
Send private message

Those old TVs are pretty inconsistent in how well they implemented support for ARC and CEC and PC connections. Heck, even my 2020 Samsung QLED has never fully worked properly with my PC.



robjg63
4161 posts

Uber Geek
+1 received by user: 1427

Subscriber

  #3299963 22-Oct-2024 16:11
Send private message

The manual says:

 

When a PC with a resolution of 1920 x 1080@60Hz is
connected to the HDMI IN 2 port, you should set the
HDMI2 mode to PC in the Edit Name of the Input mode.
If the HDMI2 mode is not PC, it works depending on the
TV setting.

 

Jeez - kinglish maybe?

 

Did you ensure the Pi is set to 1920 x 1080@60Hz.

 

Maybe try another HDMI cable.

 

Did you ensure Anynet is enabled in the TV menu an that Power On/Off is enabled:

 





Nothing is impossible for the man who doesn't have to do it himself - A. H. Weiler


jordan8thepie1

73 posts

Master Geek
+1 received by user: 18


  #3299965 22-Oct-2024 16:16
Send private message

Yes I have anynet+ and auto turn off enabled in settings and the Raspberry Pi is outputting at 1920x1080p 60hz.

 

Other Anynet+ functions work and the TV sees the Raspberry Pi as an anynet+ device.


richms
29099 posts

Uber Geek
+1 received by user: 10214

Trusted
Lifetime subscriber

  #3300001 22-Oct-2024 17:06
Send private message

The calling the input PC thing was to defeat the always on overscan that older screens had on them to make them look bigger when on display, it would also in some cases make the edid show all the VESA modes that the display would accept, whereas otherwise it was only the CEA resolutions but PC's dont tend to care what the EDID says and let you pick what you want anyway.





Richard rich.ms

Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.