31 replies to this topic

[JamesBond]

Sorry I'm confused.

I asked regarding my Gigablue if it doesn't send back the 0x47 to my Samsung, but you are talking still about you test case with your hd66se box, right?

[slavoo74]

Hi, I need the setting on hdmi port 2 ... how to change this setting in HDMI-CEC?

 

[slavoo74]

Hdmi test came out like this ..

[WanWizard]

Sorry I'm confused.

I asked regarding my Gigablue if it doesn't send back the 0x47 to my Samsung, but you are talking still about you test case with your hd66se box, right?

 

If my box does it, yours does to. There is no code difference between boxes.

[WanWizard]

Hi, I need the setting on hdmi port 2 ... how to change this setting in HDMI-CEC?

 

Why?

 

Address 1.2.0.0 indicates your box is connected to port 2 of a CEC switch (perhaps in some device like an amp ?) which in turn is connected to port 1 of the TV.

[JamesBond]

 

Sorry I'm confused.

I asked regarding my Gigablue if it doesn't send back the 0x47 to my Samsung, but you are talking still about you test case with your hd66se box, right?

 

If my box does it, yours does to. There is no code difference between boxes.

 

 

So you think that my Samsung does read or understand what the box sends on the 0x47 command?

Is there a way I can see the sent commands/messages from the box instead only the received ones?

 

Like I said all in CEC is working apart the name thing, so I just want to debug and understand how this works and see if I find the culprit and lean some more stuff. 

[WanWizard]

I have no clue what your TV does or doesn't do.

 

I can only say that if the box receives a 0x46 command (getDeviceName), it will respond with command 0x47 (setDeviceName). And that the TV in my office does receive it and show it.

 

If you want to know what Enigma sends back, start it in debug mode, both TX and RX commands are logged in the debug log.

[JamesBond]

Ok I run the enigma in debug mode and connect the HDMI cable while the TV was off, them turned on the TV and these was the messages that passed on the box console while connected in SSH:

 

[eHdmiCEC] received message 80 20 00 00 00

[eHdmiCEC] received message 82 00 00

[eHdmiCEC] received message 9F

[eHdmiCEC] send message 9E 04

[eHdmiCEC] received message 8C

[eHdmiCEC] send message 87 00 00 00

[eHdmiCEC] received message 8F

[eHdmiCEC] send message 90 00

[eHdmiCEC] received message 83

[eHdmiCEC] send message 84 00 00 03

[eHdmiCEC] received message 46

[eHdmiCEC] send message 47 67 62 75 65 34 6B    <<<< Looks like it sends the right code (gbue4k), but TV ignores it for some reason.

[eHdmiCEC] received message A0 00 00 F0 23

[eHdmiCEC] received message 82 00 00

[scriptmelvin †]

My TV (recent Samsung QLED) ignores it, too. Came up with some default name. Had to edit the name in the TV UI.

[JamesBond]

My TV (recent Samsung QLED) ignores it, too. Came up with some default name. Had to edit the name in the TV UI.

 

Yap, that's what I did, but for my Nintendo Switch and the Google Chromecast TV, it works and apart putting the correct name even puts the logo/image of the brand. 

 

My sat box is detected as unknow, so I start the wizard and in the end when asks the provider I do a search with "Gigablue" Tv finds it and puts a sort of receiver image/logo with Gigablue name that I can edit later to whatever I want.

Edited by JamesBond, 29 June 2022 - 17:08.

[WanWizard]

It probably has a library of know devices with logo's, there is no command in CEC to send images, so it must be a feature of the TV. And unknown is probably because the box name is not in that library to the TV can't match it.

[jort38]

My TV (recent Samsung QLED) ignores it, too. Came up with some default name. Had to edit the name in the TV UI.

Same here. Same TV