News:

Latest versions:
Server plugin: 0.5.1
MVP dongle: 0.5.2
Raspberry Pi client: 0.5.2
Windows client: 0.5.2-1

Main Menu

No signal from MLD vomp after TV power off

Started by svalavuo, August 07, 2013, 11:38:06

Previous topic - Next topic

svalavuo

Hi,
Is it just me or does someone else suffer from following error:
1) When I turn on my TV and Raspberry Pi with vompclient on MLD, everything works flawlessly (well, except the ui is in english and I'm from Finland) :)
2) When I turn my TV off, it (the TV shuts down as it should)
3) When I turn my TV on, it turns on and gives me "No Signal" -message.

Raspberry Pi is on (I have ssh connection to it online), but I can't get vompserver (or RPi) to send picture to TV.

RPi: Linux MLD 3.6.11.158 #1 PREEMPT
       vompclient      2013.02.25_50

VDR: 1.7.33-1yavdr0~precise
Vompserver: 0.4.0-1
Samuli
vdr 2.0.3-3 + vompserver 0.4.0 + MediaMVP H4 + Raspberry Pi with vompclient

MartenR

You should be able to switch the language to finish in the properties menu, if not the l10n folder is not in the right place at the server side.

For the second problem, it depends a bit wether you are using CEC or not. If you are using cec it is likely that the switch off of the tv also turned the vompserver off. (switvhing the TV signal off).
Then you have to turn vomp on after the TV is powered on again (with the key of your remote control of the tv designed to turn on the selected cec device).

Marten

svalavuo

Quote from: MartenR on August 08, 2013, 07:17:44
You should be able to switch the language to finish in the properties menu, if not the l10n folder is not in the right place at the server side.
Ok, I'll have to check this then.

Quote from: MartenR on August 08, 2013, 07:17:44For the second problem, it depends a bit wether you are using CEC or not. If you are using cec it is likely that the switch off of the tv also turned the vompserver off. (switvhing the TV signal off).
Then you have to turn vomp on after the TV is powered on again (with the key of your remote control of the tv designed to turn on the selected cec device).
I use CEC. How come CEC could switch my vompserver off? Vompserver is on my VDR -machine (not on RPi). Seems more likely that CEC switches something off from RPi. I haven't tried if reboot of RPi would bring signal again. RPi is in my kitchen and WAF (Wife Acceptance Factor) suffers a lot when RPi needs to be disconnected from power and connected again to gain picture. :)
Samuli
vdr 2.0.3-3 + vompserver 0.4.0 + MediaMVP H4 + Raspberry Pi with vompclient

svalavuo

#3
Quote from: svalavuo on August 08, 2013, 07:29:34
Quote from: MartenR on August 08, 2013, 07:17:44
You should be able to switch the language to finish in the properties menu, if not the l10n folder is not in the right place at the server side.
Ok, I'll have to check this then.
This helped! Some text is in germany, but...

Quote from: MartenR on August 08, 2013, 07:17:44For the second problem, it depends a bit wether you are using CEC or not. If you are using cec it is likely that the switch off of the tv also turned the vompserver off. (switvhing the TV signal off).
Then you have to turn vomp on after the TV is powered on again (with the key of your remote control of the tv designed to turn on the selected cec device).
OK. Seems like RPi informs vompserver that it's off.
10:07:56.864180 [debug]  RRProc - Config save: General Last Power State Off
10:07:56.864583 [debug]  RRProc - threadMethod waiting
10:07:56.865122 [debug]  Client - Received chan=3 kats=1375945675
10:07:56.865154 [debug]  Client - Waiting
10:07:56.866521 [debug]  TCP - TCP has closed socket
10:07:56.866541 [debug]  Client - Disconnection detected
10:07:56.866570 [debug]  Client - Vomp client destructor
10:07:56.866611 [info]   RRProc - threadMethod err 2 or quit

How come it doesn't inform that TV is on again? My TV is a cheap one (Logik) and it doesn't seem to have a separate key for attached cec equipment :(
Can I somehow make vompclient (or RPi) to learn one of my remotes keys to work as power -key or something?
Or can I somehow disable this functionality (turning off)?

Reboot helped after TV was on again.

I know this isn't vompserver problem, but how do I save settings in RPi MLD?
For some reason every boot changes localtime to point to Berlin, but I would like it to be Helsinki. Is there a way to save this setting or do I make the change in wrong place?
Samuli
vdr 2.0.3-3 + vompserver 0.4.0 + MediaMVP H4 + Raspberry Pi with vompclient

MartenR

Well, I would suggest, that you try different configurations for CEC on your TV. (What kind of TV do you have?)

Of course you can uncomment the power related switch  cases in "TranslateHWCFixed(ULLONG code)" in RemoteLinux.
This will disable the power key, but these change is only a dirty fix and thus will not go into the main development tree. (POWER is a special signal in CEC and is hardcoded in vomp).

Anyway the client side log with the CEC Messages will help.

Marten


svalavuo

As I mentioned earlier, TV is cheap one (Logik) and there is no settings for CEC.

Basically best solution would be that RPi sends PowerOn -message to vompserver when I turn my TV on :)
Maybe this works for other TV:s, but mine stays blank (only this "No Signal" -message appears on screen).

My vompclient is ready package from MLD (their site is down btw) and thus I didin't compile that myself.
Samuli
vdr 2.0.3-3 + vompserver 0.4.0 + MediaMVP H4 + Raspberry Pi with vompclient

MartenR

QuoteBasically best solution would be that RPi sends PowerOn -message to vompserver when I turn my TV on
Yes sure, but I need the logs on the client side to see what is happening on the CEC side. E.g. if some message from the TV is not recognised.
You can  turn on in the client config on the server side network logging, then the client logging messages should appear on the server side.

If you can not provide the logs, I am not able to help.

Marten



svalavuo

Thanks! I'll do this.  Can you tell me how to turn client logging on from server side?
Sorry, but I really don't know.
Samuli
vdr 2.0.3-3 + vompserver 0.4.0 + MediaMVP H4 + Raspberry Pi with vompclient

MartenR

In the client config add to the section "Advanced", the option "Network logging" and set it to "On". 

Marten

svalavuo

Hi,

Now I feel stupid.

Where should this log go? On server location defined in vomp.conf?
my vomp.conf says:

[General]
Log file = /var/log/vdr/vompserver.log


Is that the location where vompclient will write it's data?
When I press Power Off for my TV, I'll get this to vompserve.log:
...
20:39:07.727752 [debug]  Client - Received chan=1, ser=122, op=11, edl=29
20:39:07.727768 [debug]  RRProc - recvReq
20:39:07.727784 [debug]  RRProc - recvReq set req and signalled
20:39:07.727800 [debug]  Client - Waiting
20:39:07.727804 [debug]  RRProc - thread woken with req, queue size: 1
20:39:07.727819 [debug]  Client - Received chan=4 loglen=57
20:39:07.727856 [debug]  RRProc - Config save: General Last Power State Off
20:39:07.727870 [debug]  Client - Waiting
20:39:07.728215 [debug]  RRProc - threadMethod waiting
20:39:07.728860 [debug]  Client - Received chan=4 loglen=54
20:39:07.728882 [debug]  Client - Waiting
20:39:07.730374 [debug]  Client - Received chan=3 kats=1376242746
20:39:07.730398 [debug]  Client - Waiting
20:39:07.730422 [debug]  Client - Received chan=4 loglen=80
20:39:07.730439 [debug]  Client - Waiting
20:39:07.730457 [debug]  Client - Received chan=4 loglen=47
20:39:07.730473 [debug]  Client - Waiting
20:39:07.730491 [debug]  Client - Received chan=4 loglen=75
20:39:07.730508 [debug]  Client - Waiting
20:39:07.730537 [debug]  TCP - TCP has closed socket
20:39:07.730551 [debug]  Client - Disconnection detected
20:39:07.730564 [debug]  Client - Vomp client destructor
20:39:07.730608 [info]   RRProc - threadMethod err 2 or quit

When I press Power button of TV remote (to switch it on), nothing happens in vompserver.log :(
Samuli
vdr 2.0.3-3 + vompserver 0.4.0 + MediaMVP H4 + Raspberry Pi with vompclient

MartenR

It looks like network logging is still switched off.


svalavuo

Hi,

I tried to put these:
[Advanced]
Network logging = On

to both vomp.conf and vomp-MAC.conf, but nothing seems to change. :(

I did restart my VDR and RPi too.
Samuli
vdr 2.0.3-3 + vompserver 0.4.0 + MediaMVP H4 + Raspberry Pi with vompclient

MartenR

I have unfortunetely no idea, why it does not work.
Anyway you can also start vomp locally on the rpi with "vompclient -d> debug.log" and you get a log file.

Marten

svalavuo

#13
hmmmm
When I run your command, I get this:
/usr/bin/vompclient: error while loading shared libraries: libOpenVG.so: cannot open shared object file: No such file or directory


I found out, that I was missing a config parameter.
15:47:38.735292 [debug]  Config - Config error: Key Network logging file not found

I added that, and now I get some data to my new log file :)

http://pastebin.com/96prYKLp
Samuli
vdr 2.0.3-3 + vompserver 0.4.0 + MediaMVP H4 + Raspberry Pi with vompclient

MartenR

Ok, this is in principle what I need, but for me it is a bit hard to interpret the result.
I need in some way to figure out, what happens, when you switch the tv off and what happens, if you switch it on again.
So please switch the TV off and note the time, then wait 5 minutes and switch it on (note also the time).
Then I need the log from the switch off to the switch off together with the correct times.

Marten