88 replies to this topic

[Dimitrij]

This not openPLi image.

[Dimitrij]

Ok.

I confirm.

 

Pulse 4K HDMI-CEC enabled

 

 

TV remote:

1)TV remote off  --> Pulse 4K standby

 

2)TV remote on --> Pulse 4K not wake up(not Live TV)

 

 

Pulse 4K remote:

1)Pulse 4K off(standby)  --> TV off

 

2)Pulse 4K press power(current standby-->Live TV and goto standby within one second) -->TV on

Need to press the power button(Pulse 4K remote)  again to goto Live TV.

 

Check all plugin settings HDMI-CEC.

Edited by Dimitrij, 5 January 2023 - 19:04.

[WanWizard]

Do you see the CEC command from the TV arrive on the box when the box is in standby?

[Pr2]

Sorry but the ABCom Pulse 4K is working fine with HDMI-CEC in this scenario:
 
TV Off - Pulse 4k Off
 
Press the Pulse 4K RCU power button then the TV turn on and the Pulse 4K too and I can watch TV.
 
Press the Pulse 4K RCU power button then the TV turn off and the Pulse 4K return into standby.
 
I have installed Pulse 4K at my parents and they use only the Pulse 4K RCU to watch TV and trust me if there was problem I would be immediately informed. 
 
just add a delay of 50 ms and everything works fine.

config.hdmicec.control_receiver_standby=true
config.hdmicec.control_receiver_wakeup=true
config.hdmicec.enabled=true
config.hdmicec.fixed_physical_address=1.0.0.0
config.hdmicec.minimum_send_interval=50
config.hdmicec.repeat_wakeup_timer=0
config.hdmicec.tv_wakeup_detection=wakeup
config.hdmicec.volume_forwarding=true
config.hdmicec.volume_forwarding_repeat=1

BUT having a VU+ Duo 4K and the Pulse 4K connected to the same TV was a real nightmare.

Edited by Pr2, 5 January 2023 - 20:28.

[WanWizard]

A problem with the hardware design of the CEC bus, in combination with variations in manufacturer implementation.

 

It is a single electrical bus (no matter how many hubs you have), so everything connected has an influence on everything else. And every manufacturer only ensures their own equipment works flawlessly.

 

The biggest case in point is still the ET10000. Plug it in, and CEC is completely dead. Even between two completely unrelated devices (for example DVD player and AMP).

[tulok]

Do you see the CEC command from the TV arrive on the box when the box is in standby?

 

That's a good question! Because I can't see it in standby mode!!!

 

Edited by tulok, 13 January 2023 - 10:47.

[tulok]

 

Do you see the CEC command from the TV arrive on the box when the box is in standby?

 

That's a good question! Because I can't see it in standby mode!!!

 

 

When the pulse 4k goes into standby mode, I don't see the HDMI CEC command on the TV!

 

https://heavenface.c...7e2d389382f.jpg

[s3n0]

Exactly as @WanWizard mentions.

 

There is a frequent problem of different combinations, from different manufacturers of all kinds of devices.

 

Today, HDMI 2.0 and newer versions have better and better standardized CEC commands (CEC communication), but the old HDMI versions represent a big problem.

 

A problem often arises even with the types of cheap HDMI cables themselves. Very often, very old and cheap HDMI cables are supplied to set-top boxes, only as basic HDMI cables for video and audio transmission, which unfortunately DO NOT SUPPORT CEC (pins on the HDMI connector for CEC communication). I have already seen HDMI cable v1.4, which had unconnected pins for CEC . I also saw an HDMI 2.0 cable on which CEC communication did not work properly, but after changing the cable to a different type (more expensive cable, old version of HDMI 1.4), then everything worked OK there.

 

If someone wants to help, they must enable debugging in the HDMI CEC settings (plugin settings or system settings - you can find it depending on how Enigma2 uses HDMI CEC, because not every Enigma2 has HDMI CEC support built-in). Next, it is possible to debug the HDMI CEC communication. If you find out, publish, write where exactly the problem arises, then it is possible to add the right to the python code in Enigma2.

[tulok]

Exactly as @WanWizard mentions.

 

There is a frequent problem of different combinations, from different manufacturers of all kinds of devices.

 

Today, HDMI 2.0 and newer versions have better and better standardized CEC commands (CEC communication), but the old HDMI versions represent a big problem.

 

A problem often arises even with the types of cheap HDMI cables themselves. Very often, very old and cheap HDMI cables are supplied to set-top boxes, only as basic HDMI cables for video and audio transmission, which unfortunately DO NOT SUPPORT CEC (pins on the HDMI connector for CEC communication). I have already seen HDMI cable v1.4, which had unconnected pins for CEC . I also saw an HDMI 2.0 cable on which CEC communication did not work properly, but after changing the cable to a different type (more expensive cable, old version of HDMI 1.4), then everything worked OK there.

 

If someone wants to help, they must enable debugging in the HDMI CEC settings (plugin settings or system settings - you can find it depending on how Enigma2 uses HDMI CEC, because not every Enigma2 has HDMI CEC support built-in). Next, it is possible to debug the HDMI CEC communication. If you find out, publish, write where exactly the problem arises, then it is possible to add the right to the python code in Enigma2.

The Impulse 4k receiver cannot be woken from standby mode. I would be grateful if someone could help. Thanks!

09:52:55.8217 +++ start logging +++ physical address: 1.2.0.0 - logical address: 4 - device type: <Playback 1>
09:52:55.8217 Tx: 09:52:55 <Give System Audio Mode Stat> 7D [0x05]
09:52:56.2503 [ ] timeout for check TV state!
09:52:56.2520 Rx: 09:52:56 <Give OSD Name> < 46 00
09:52:58.3061 Tx: 09:52:58 <Routing Information> > 81 12 00 [0x0F]
09:52:59.8290 Rx: 09:52:59 <Give OSD Name> < 46 00
09:52:59.8319 Tx: 09:52:59 <Give Device Power Status> > 8F [0x00]
09:52:59.8338 [ ] timeout for check TV state!
09:52:59.8372 Rx: 09:52:59 <Give OSD Name> < 46 B6
09:52:59.8385 Tx: 09:52:59 <Set OSD Name> > 47 pulse4k [0x05]
09:52:59.8397 Rx: 09:52:59 <Give OSD Name> < 46 A8
09:52:59.8406 Tx: 09:52:59 <Set OSD Name> > 47 pulse4k [0x05]
09:52:59.8416 Rx: 09:52:59 <System Audio Mode Status> < 7E 01
09:52:59.8421 [ ] volume forwarding to device 05 enabled
09:52:59.8428 Tx: 09:52:59 <Set OSD Name> > 47 pulse4k [0x00]
09:52:59.8440 Rx: 09:52:59 <Set Stream Path> < 86 12
09:52:59.8446 [ ] streaming path has changed... to our address: True
09:52:59.8456 Tx: 09:52:59 <Set OSD Name> > 47 pulse4k [0x00]
09:52:59.8480 Tx: 09:52:59 <Active Source> > 82 12 00 [0x0F]
09:53:01.3789 Rx: 09:53:01 <Report Power Status> < 90 00
09:53:12.5427 Rx: 09:53:12 <Set System Audio Mode> < 72 01
09:53:12.5434 [ ] volume forwarding to device 05 enabled
09:53:12.7652 Rx: 09:53:12 <Set System Audio Mode> < 72 01
09:53:12.7659 [ ] volume forwarding to device 05 enabled
09:53:12.9212 Rx: 09:53:12 <Set Stream Path> < 86 11
09:53:12.9220 [ ] streaming path has changed... to our address: False
09:53:12.9226 [ ] go into standby...
09:53:12.9525 [ ] Skip turning off TV
09:53:13.0306 Rx: 09:53:13 <Active Source> < 82 11
09:53:13.2616 Rx: 09:53:13 <Set Stream Path> < 86 11
09:53:13.3881 Rx: 09:53:13 <Routing Information> < 81 11
09:53:14.0756 Rx: 09:53:14 <Set Stream Path> < 86 11
09:53:14.1856 Rx: 09:53:14 <Active Source> < 82 11
09:57:09.2674 Tx: 09:57:09 <Image View On> > 04 [0x00]
09:57:09.2686 Tx: 09:57:09 <Active Source> > 82 12 00 [0x0F]
09:57:09.2696 Tx: 09:57:09 <User Control Pressed> > 44 6D [0x05]
09:57:09.2704 Tx: 09:57:09 <System Audio Mode Request> > 70 12 00 [0x05]
09:57:10.7222 Rx: 09:57:10 <Set Stream Path> < 86 11
09:57:10.7393 Rx: 09:57:10 <Active Source> < 82 11
09:57:10.7403 [ ] our receiver is active source: False
09:57:10.7412 Tx: 09:57:10 <Routing Information> > 81 12 00 [0x0F]
09:57:10.7425 Rx: 09:57:10 <User Control Pressed> < 44 6D
09:57:10.7621 Tx: 09:57:10 <Active Source> > 82 12 00 [0x0F]
09:57:10.7741 Rx: 09:57:10 <Set System Audio Mode> < 72 01
09:57:10.7841 [ ] volume forwarding to device 05 enabled
09:57:10.7890 Tx: 09:57:10 <Routing Information> > 81 12 00 [0x0F]
09:57:12.8944 Rx: 09:57:12 <Set Stream Path> < 86 00
09:57:12.8957 [ ] go into standby...
09:57:12.9267 [ ] Skip turning off TV
09:57:12.9632 Rx: 09:57:12 <Set System Audio Mode> < 72 00
09:57:12.9639 [ ] volume forwarding to device 00 enabled
09:57:14.9216 Rx: 09:57:14 <Give Physical Address> < 83 A9
09:57:14.9225 Tx: 09:57:14 <Report Physical Address> > 84 12 00 04 [0x0F]
09:59:58.1354 Tx: 09:59:58 <Image View On> > 04 [0x00]
09:59:58.1364 Tx: 09:59:58 <Active Source> > 82 12 00 [0x0F]
09:59:58.1373 Tx: 09:59:58 <User Control Pressed> > 44 6D [0x05]
09:59:58.1383 Tx: 09:59:58 <System Audio Mode Request> > 70 12 00 [0x05]
09:59:59.6470 Rx: 09:59:59 <Give Physical Address> < 83 00
09:59:59.6630 Tx: 09:59:59 <Report Physical Address> > 84 12 00 04 [0x0F]
09:59:59.6649 Rx: 09:59:59 <Give Physical Address> < 83 A8
09:59:59.6658 Tx: 09:59:59 <Report Physical Address> > 84 12 00 04 [0x0F]
09:59:59.6668 Rx: 09:59:59 <Give Physical Address> < 83 A8
09:59:59.6677 Tx: 09:59:59 <Report Physical Address> > 84 12 00 04 [0x0F]
09:59:59.6701 Rx: 09:59:59 <Give OSD Name> < 46 A8
09:59:59.6713 Tx: 09:59:59 <Set OSD Name> > 47 pulse4k [0x05]
09:59:59.6723 Rx: 09:59:59 <Give OSD Name> < 46 A8
09:59:59.6849 Tx: 09:59:59 <Set OSD Name> > 47 pulse4k [0x00]
09:59:59.7011 Rx: 09:59:59 <Set Stream Path> < 86 12
09:59:59.7022 [ ] streaming path has changed... to our address: True
09:59:59.7055 Tx: 09:59:59 <Active Source> > 82 12 00 [0x0F]
09:59:59.7441 Rx: 09:59:59 <Set System Audio Mode> < 72 01
09:59:59.7492 [ ] volume forwarding to device 05 enabled
09:59:59.8637 Rx: 09:59:59 <Set System Audio Mode> < 72 01
09:59:59.8642 [ ] volume forwarding to device 05 enabled
10:00:01.6819 Rx: 10:00:01 <Give OSD Name> < 46 00
10:00:01.8929 Tx: 10:00:01 <Set OSD Name> > 47 pulse4k [0x05]
10:00:01.8963 Rx: 10:00:01 <Give OSD Name> < 46 B6
10:00:01.9066 Tx: 10:00:01 <Set OSD Name> > 47 pulse4k [0x05]
10:00:01.9085 Rx: 10:00:01 <Give OSD Name> < 46 02
10:00:01.9093 Tx: 10:00:01 <Set OSD Name> > 47 pulse4k [0x05]
10:00:01.9106 Rx: 10:00:01 <Give OSD Name> < 46 02
10:00:01.9114 Tx: 10:00:01 <Set OSD Name> > 47 pulse4k [0x00]
10:00:01.9127 Rx: 10:00:01 <Give OSD Name> < 46 02
10:00:01.9136 Tx: 10:00:01 <Set OSD Name> > 47 pulse4k [0x00]
10:00:01.9153 Rx: 10:00:01 <Give OSD Name> < 46 02
10:00:01.9163 Tx: 10:00:01 <Set OSD Name> > 47 pulse4k [0x00]
10:00:03.5277 Tx: 10:00:03 <Routing Information> > 81 12 00 [0x0F]
10:00:06.5270 [ ] timeout for check TV state!
10:00:06.5286 Tx: 10:00:06 <Give Device Power Status> > 8F [0x00]
10:00:06.8470 Rx: 10:00:06 <Set Stream Path> < 86 12
10:00:06.8476 [ ] our receiver is active source: True
10:00:07.1877 Rx: 10:00:07 <Report Power Status> < 90 00
10:00:44.6196 Rx: 10:00:44 <Set System Audio Mode> < 72 01
10:00:44.6210 [ ] volume forwarding to device 05 enabled
10:00:44.8619 Rx: 10:00:44 <Set System Audio Mode> < 72 01
10:00:44.8627 [ ] volume forwarding to device 05 enabled
10:00:45.0273 Rx: 10:00:45 <Set Stream Path> < 86 11
10:00:45.0279 [ ] streaming path has changed... to our address: False
10:00:45.0285 [ ] go into standby...
10:00:45.0543 [ ] Skip turning off TV
10:00:45.1365 Rx: 10:00:45 <Active Source> < 82 11
10:00:45.3126 Rx: 10:00:45 <Routing Information> < 81 11
10:00:45.5039 Rx: 10:00:45 <Set Stream Path> < 86 11
10:00:46.2036 Rx: 10:00:46 <Set Stream Path> < 86 11
10:00:46.3136 Rx: 10:00:46 <Active Source> < 82 11 

 

[s3n0]

And with which device are you trying to wake up your set top box ?

 

Maybe it would be better to use a set-top box to wake up all devices. Or what do you actually want to achieve, I don't know. Anyway, Linux is installed on the set-top box and there are many options in terms of linux shell. You can directly send some CEC commands or read them in the linux shell if you turn on debugging mode in the HDMI-CEC plugin / configuration.

Edited by s3n0, 15 January 2023 - 12:23.

[tulok]

I want pulse 4k to wake up from standby. I've already tried every option!

[WanWizard]

Hence my question many posts back: does the Pulse4K receive a CEC command from the TV to wake up?

 

If yes, it is an issue in our code that we must fix. If not, there is nothing we can do about it.

[Frenske]

Hence my question many posts back: does the Pulse4K receive a CEC command from the TV to wake up?

 

If yes, it is an issue in our code that we must fix. If not, there is nothing we can do about it.

 

I’ll test the PULSe4K on my new 4K TV which handles HDMI-CEC properly so far.

[WanWizard]

Did a bit of testing with my test box (an HD66SE):

 

When I put the TV in standby, Enigma reports

[eHdmiCEC] send message 8F
[eHdmiCEC] send message 36

and the box goes into standby.

 

When the box is in standby, and I switch the TV on, no CEC message is reported.

Edited by WanWizard, 15 January 2023 - 17:19.
update, used incorrect CEC settings

[WanWizard]

I’ll test the PULSe4K on my new 4K TV which handles HDMI-CEC properly so far.

 

How?

 

The problem is not box -> tv (so using the box remote, box in standby = tv in standby), but tv -> box (switch the TV off or to another HDMI input, box goes into standby).
 

[WanWizard]

My test TV has a CEC test option in the tools menu.

 

If I ask it to search for devices, it says "No device found", but I see no CEC commands arrive on the box when the box is in standby.

 

I've been playing a bit with the CEC settings on the box, and now have another challenge: if I switch the box on, the TV goes on, box immediately goes back into standby, TV goes of again .

[Frenske]

Hence my question many posts back: does the Pulse4K receive a CEC command from the TV to wake up?

 

If yes, it is an issue in our code that we must fix. If not, there is nothing we can do about it.

This is what I intended to test.

[tulok]

Hence my question many posts back: does the Pulse4K receive a CEC command from the TV to wake up?

 

If yes, it is an issue in our code that we must fix. If not, there is nothing we can do about it.

Yes.  In reverse, it receives the Pulse4K CEC command from the TV to wake up.  Thank you very much in advance for the fix!

[tulok]

My test TV has a CEC test option in the tools menu.

 

If I ask it to search for devices, it says "No device found", but I see no CEC commands arrive on the box when the box is in standby.

 

I've been playing a bit with the CEC settings on the box, and now have another challenge: if I switch the box on, the TV goes on, box immediately goes back into standby, TV goes of again .

When I turn on the box, the TV turns on, the box immediately goes back to standby, the TV turns off again and won't wake up from standby.  The hdmi cec doesn't work as it should!

[Pr2]

 

I’ll test the PULSe4K on my new 4K TV which handles HDMI-CEC properly so far.

 

How?

 

The problem is not box -> tv (so using the box remote, box in standby = tv in standby), but tv -> box (switch the TV off or to another HDMI input, box goes into standby).
 

 

 

You should try these settings:

config.hdmicec.minimum_send_interval=50
config.hdmicec.repeat_wakeup_timer=0

Do not repeat wakeup timer and set a delay of 50 ms

 

But the HDMI CEC iimplementation s far from being perfect in the Pulse4K. :-)  But trust me turning TV ON/OFF from the Pulse4K RCU only so with HDMI-CEC is working fine I use it on my parents TV.

Edited by Pr2, 15 January 2023 - 18:39.