search

unixer / vtuner

Automatically exported from code.google.com/p/vtuner
0 stars 0 forks source link

FE_DISEQC_SEND_MASTER_CMD failed Connection timeout #6

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Dreambox DM800se -> Dm800HD
2. Use diseqc with channel scan
3. Look at the Console

What is the expected output? What do you see instead?
When its sending diseqc I get "FE_DISEQC_SEND_MASTER_CMD failed Connection 
timeout" and no channels are found

What version of the product are you using? On what operating system?
Tried latest, and some other versions with same output.

Please provide any additional information below.
using DM800se -> ARM works
using x86_64 -> DM800HD works
using DM800se -> DM800HD does not work.

Also tried many different images on the dm800se

LOG:

vtunerd: [3596 ../../vtunerd-service.c:351] debug: control message received
vtunerd: [3596 ../../vtunerd-service.c:400] debug: MSG_SET_VOLTAGE: 0x1
vtunerd: [3596 ../../vtunerd-service.c:351] debug: control message received
vtunerd: [3596 ../../vtuner-dmm-3.c:334] warn: FE_DISEQC_SEND_MASTER_CMD failed 
- Connection timed out
vtunerd: [3596 ../../vtunerd-service.c:408] debug: MSG_SEND_DISEQC_MSG:
vtunerd: [3596 ../../vtunerd-service.c:439] warn: vtuner call failed, type:11 
reason:-1
vtunerd: [3596 ../../vtunerd-service.c:351] debug: control message received
vtunerd: [3596 ../../vtuner-dmm-3.c:334] warn: FE_DISEQC_SEND_MASTER_CMD failed 
- Connection timed out
vtunerd: [3596 ../../vtunerd-service.c:408] debug: MSG_SEND_DISEQC_MSG:
vtunerd: [3596 ../../vtunerd-service.c:439] warn: vtuner call failed, type:11 
reason:-1
vtunerd: [3596 ../../vtunerd-service.c:351] debug: control message received
vtunerd: [3596 ../../vtuner-dmm-3.c:334] warn: FE_DISEQC_SEND_MASTER_CMD failed 
- Connection timed out
vtunerd: [3596 ../../vtunerd-service.c:408] debug: MSG_SEND_DISEQC_MSG:
vtunerd: [3596 ../../vtunerd-service.c:439] warn: vtuner call failed, type:11 
reason:-1

Original issue reported on code.google.com by kriss...@gmail.com on 18 Oct 2011 at 8:11

GoogleCodeExporter commented 9 years ago 
Can you check if DM800HD -> DM800se works? 

My problem is that I don't have DM800se, the only Dreambox I have is DM800HD.

/Honza

Original comment by jpetrous on 19 Oct 2011 at 1:09

GoogleCodeExporter commented 9 years ago 
Sorry I cant as I dont get a picture on my dm800hd (that is why it has been 
used as vtuner reciever).

This is what happens when I try to change channels 

erd: [31569 ../../vtunerd-service.c:392] debug: MSG_READ_SIGNAL_STRENGTH: 0
vtunerd: [31569 ../../vtunerd-service.c:359] debug: control message received
vtunerd: [31569 ../../vtunerd-service.c:433] debug: MSG_GET_PROPERTY: 0 4225560
vtunerd: [31569 ../../vtunerd-service.c:447] warn: vtuner call failed, type:17 
reason:4225560
vtunerd: [31569 ../../vtunerd-service.c:359] debug: control message received
vtunerd: [31569 ../../vtunerd-service.c:433] debug: MSG_GET_PROPERTY: 0 4225560
vtunerd: [31569 ../../vtunerd-service.c:447] warn: vtuner call failed, type:17 
reason:4225560
vtunerd: [31569 ../../vtunerd-service.c:359] debug: control message received
vtunerd: [31569 ../../vtunerd-service.c:433] debug: MSG_GET_PROPERTY: 0 4225560
vtunerd: [31569 ../../vtunerd-service.c:447] warn: vtuner call failed, type:17 
reason:4225560
vtunerd: [31569 ../../vtunerd-service.c:359] debug: control message received
vtunerd: [31569 ../../vtunerd-service.c:433] debug: MSG_GET_PROPERTY: 0 4225560
vtunerd: [31569 ../../vtunerd-service.c:447] warn: vtuner call failed, type:17 
reason:4225560
vtunerd: [31569 ../../vtunerd-service.c:359] debug: control message received
vtunerd: [31569 ../../vtunerd-service.c:380] debug: MSG_GET_FRONTEND

Im using an ARM board right now

Original comment by kriss...@gmail.com on 25 Oct 2011 at 1:48

GoogleCodeExporter commented 9 years ago 
The most strange thing is that after upgrading dm800hd. dm800hd -> dm800se 
works. strange as dm800hd -> vdr, dm800hd -> dm800hd worked.

Original comment by kriss...@gmail.com on 2 Nov 2011 at 10:05

GoogleCodeExporter commented 9 years ago 
As far as I can see, the main issue may be the empty body of hw_get_property() 
function in vtuner-dmm-3.c. Can you apply the following patch and recheck again:

$ hg diff -p vtuner-dmm-3.c
diff -r c54cf92183e5 vtuner-dmm-3.c
--- a/vtuner-dmm-3.c    Tue Nov 01 15:30:43 2011 +0100
+++ b/vtuner-dmm-3.c    Thu Nov 03 21:08:51 2011 +0100
@@ -234,7 +234,8 @@ int hw_set_frontend(vtuner_hw_t* hw, str
 }

 int hw_get_property(vtuner_hw_t* hw, struct dtv_property* prop) {
-
+  WARN("FE_GET_PROPERTY: not implemented %d\n", prop->cmd);
+  return 0;
 }

 int hw_set_property(vtuner_hw_t* hw, struct dtv_property* prop) {

/Honza

Original comment by jpetrous on 3 Nov 2011 at 8:09

GoogleCodeExporter commented 9 years ago 
Seems that the problem is more complex than I thought of. 

When I do a scan (dm800se -> dm800hd) on 1w I get 10 channels on 1 transponder. 
Somehow it cannot switch transponder.

I tried to put lamedb from another box with channels, and still I could only 
watch on the first transponder.

After the scan on the transponder that actually works, I get these messages 
(Used an older version of vtuner, same error but better output)

vtunerd: [12719 ../../vtunerd-service.c:350] debug: control message received
vtunerd: [12719 ../../vtunerd-service.c:424] debug: MSG_GET_PROPERTY: 31 4222292
vtunerd: [12719 ../../vtunerd-service.c:438] warn: vtuner call failed, type:17 
reason:4222292
vtunerd: [12719 ../../vtunerd-service.c:350] debug: control message received
vtunerd: [12719 ../../vtunerd-service.c:424] debug: MSG_GET_PROPERTY: 31 4222292
vtunerd: [12719 ../../vtunerd-service.c:438] warn: vtuner call failed, type:17 
reason:4222292
vtunerd: [12719 ../../vtunerd-service.c:350] debug: control message received
vtunerd: [12719 ../../vtunerd-service.c:424] debug: MSG_GET_PROPERTY: 31 4222292
vtunerd: [12719 ../../vtunerd-service.c:438] warn: vtuner call failed, type:17 
reason:4222292
vtunerd: [12719 ../../vtunerd-service.c:350] debug: control message received
vtunerd: [12719 ../../vtunerd-service.c:424] debug: MSG_GET_PROPERTY: 31 4222292
vtunerd: [12719 ../../vtunerd-service.c:438] warn: vtuner call failed, type:17 
reason:4222292

The patch didnt do anything, same thing.

I also get many many 

vtunerc: [908 ../../vtunerc.c:97] info: less than 3 TS packets read 
(actually:188), 
vtunerc: [908 ../../vtunerc.c:97] info: less than 3 TS packets read 
(actually:188), 

This is somehow the only transponder that works

11216 V
tp C1
DVB-S
SR 24500
FEC 7/8

Original comment by kriss...@gmail.com on 4 Nov 2011 at 9:02

GoogleCodeExporter commented 9 years ago 
I dont know if this  helps, but this part is always missing when trying to scan 
with a dm800se (on dm800hd vtunerd)

tunerd: [1035 ../../vtunerd-service.c:375] debug: MSG_SET_FRONTEND 0
vtunerd: [1035 ../../vtunerd-service.c:360] debug: control message received
vtunerd: [1035 ../../vtunerd-service.c:385] debug: MSG_READ_STATUS: 0x1
vtunerd: [1035 ../../vtunerd-service.c:360] debug: control message received
vtunerd: [1035 ../../vtuner-dvb-3.c:146] info: FE_SET_FRONTEND parameters: 
freq:1517124 inversion:2 SR:24500000 FEC:7
vtunerd: [1035 ../../vtuner-dvb-3.c:217] debug: S2API tuning SYS:5 MOD:0 FEC:7 
INV:2 ROLLOFF:3 PILOT:2
vtunerd: [1035 ../../vtunerd-service.c:375] debug: MSG_SET_FRONTEND 0
vtunerd: [1035 ../../vtunerd-service.c:360] debug: control message received
vtunerd: [1035 ../../vtunerd-service.c:409] debug: MSG_SET_VOLTAGE: 0x2

Mostly just this is visible while scanning on dm800se (on dm800hd vtunerd)

vtunerd: [1035 ../../vtunerd-service.c:375] debug: MSG_SET_FRONTEND 0
vtunerd: [1035 ../../vtunerd-service.c:360] debug: control message received
vtunerd: [1035 ../../vtunerd-service.c:385] debug: MSG_READ_STATUS: 0x1
vtunerd: [1035 ../../vtunerd-service.c:360] debug: control message received

Original comment by kriss...@gmail.com on 7 Nov 2011 at 7:11

GoogleCodeExporter commented 9 years ago 
Ah, nice. Can you log me both variants? Working one and failed. Then I can 
compare them together. Please use highest logging values. And please send me 
logs for both sides - vtunerc (client) and vtunerd (server).

Thx

/Honza

Original comment by jpetrous on 7 Nov 2011 at 11:28

GoogleCodeExporter commented 9 years ago 
Here are the files,
Hope you'll se something in them :)

If you need anything more just say.

Original comment by kriss...@gmail.com on 8 Nov 2011 at 7:51

Attachments:

GoogleCodeExporter commented 9 years ago 
BTW, could this have anything to do with the new enigma2 versions?

Original comment by kriss...@gmail.com on 8 Nov 2011 at 2:16

GoogleCodeExporter commented 9 years ago 
Some new information.

When I comment out the if else on line 371 in vtunerd-service.c and just let 
the 

ret=hw_set_frontend(&hw,&fe_params);                                            
                      DEBUGSRV("MSG_SET_FRONTEND %d\n", skip_set_frontend); 

remain I can now search for channels (except HD?)

I've noticed some problemes with new images with vtuner even with dm800hd so 
this stuff above is something usefull?

Original comment by kriss...@gmail.com on 25 Nov 2011 at 11:29