skylink keep freezeng every two minutes

tajnyy · 04 December 2012, 20:33:03

hi there have anybody problems with skylink today?mine is keep freezeng every two minutes for about two minutes

xtruex · 04 December 2012, 22:35:49

Hi
No problem

suma · 05 December 2012, 05:35:58

Quote from: tajnyy on 04 December 2012, 20:33:03
hi there have anybody problems with skylink today?mine is keep freezeng every two minutes for about two minutes

1. Complete your signature
2. Show log-file

hypnox · 29 January 2013, 00:36:06

hi, skylink is still freezing to me, 5 to 10 times per day for a few second to minutes..
here is my log file, pls help..

Jan 28 21:11:36 192.168.100.105 000: 80 10 10 fb da 9a 6f 4f 14 66 c9 53 29 23 9f fe ......oO.f.S)#..
Jan 28 21:11:36 192.168.100.105 010: 8a 80 08 ...
Jan 28 21:11:36 192.168.100.105
Jan 28 21:11:36 192.168.100.105 [mg1] <- CW from newcamd serv1:XXX32 (148ms)
Jan 28 21:11:36 192.168.100.105 [mg1] 148 msec -- Mon Jan 28 20:11:35 2013
Jan 28 21:11:36 192.168.100.105 system: Cryptoworks caid: 0x0D96 pid: 0x0475
Jan 28 21:11:36 192.168.100.105 prov: 000004
Jan 28 21:11:36 192.168.100.105 cw0:1 FB DA 9A 6F 4F 14 66 C9
Jan 28 21:11:36 192.168.100.105 cw1:1 53 29 23 9F FE 8A 80 08
Jan 28 21:11:46 192.168.100.105 ECM to newcamd serv1:XXX32
Jan 28 21:11:46 192.168.100.105 Server: -- Mon Jan 28 20:11:45 2013
Jan 28 21:11:46 192.168.100.105 ----------------------------------------------------
Jan 28 21:11:46 192.168.100.105 000: 80 40 7d 81 ff 00 00 78 80 65 00 00 80 06 81 3d .@.....x.e.....=
Jan 28 21:11:46 192.168.100.105 010: ba dd 90 56 3a 36 9a 68 38 da d7 19 dd e7 6a 92 ...V:6.h8.....j.
Jan 28 21:11:46 192.168.100.105 020: 6a 5c 54 8f d3 89 e1 46 00 c9 57 2f 7c d1 9f 9e j\T....F..W/....
Jan 28 21:11:46 192.168.100.105 030: e2 34 dc af a6 16 97 3d f5 28 62 06 43 26 34 64 .4.....=.(b.C&4d
Jan 28 21:11:46 192.168.100.105 .G...
Jan 28 21:11:46 192.168.100.105 050: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
Jan 28 21:11:46 192.168.100.105 060: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 83 ................
Jan 28 21:11:46 192.168.100.105 070: 01 04 84 02 00 00 df 08 29 5d a0 c9 ab d3 2f 83 ........)]..../.
Jan 28 21:11:46 192.168.100.105
Jan 28 21:11:46 192.168.100.105 Client <- Server: -- Mon Jan 28 20:11:45 2013
Jan 28 21:11:46 192.168.100.105 ----------------------------------------------------
Jan 28 21:11:46 192.168.100.105 000: 80 10 10 fb da 9a 6f 4f 14 66 c9 e3 d0 88 3b 5e ......oO.f....;^
Jan 28 21:11:46 192.168.100.105 010: 14 83 f5 ...
Jan 28 21:11:46 192.168.100.105
Jan 28 21:11:46 192.168.100.105 [mg1] <- CW from newcamd serv1:XXX32 (160ms)
Jan 28 21:11:46 192.168.100.105 [mg1] 160 msec -- Mon Jan 28 20:11:45 2013
Jan 28 21:11:46 192.168.100.105 system: Cryptoworks caid: 0x0D96 pid: 0x0475
Jan 28 21:11:46 192.168.100.105 prov: 000004
Jan 28 21:11:46 192.168.100.105 cw0:1 FB DA 9A 6F 4F 14 66 C9
Jan 28 21:11:46 192.168.100.105 cw1:1 E3 D0 88 3B 5E 14 83 F5
Jan 28 21:11:56 192.168.100.105 ECM to newcamd serv1:XXX32
Jan 28 21:11:56 192.168.100.105 Server: -- Mon Jan 28 20:11:55 2013
Jan 28 21:11:56 192.168.100.105 ----------------------------------------------------
Jan 28 21:11:56 192.168.100.105 000: 81 40 7d 81 ff 00 00 78 80 65 00 00 80 06 81 3d .@.....x.e.....=
Jan 28 21:11:56 192.168.100.105 010: b5 36 ce e0 b0 1d 7c ed ae 8b e4 fd 8b 37 da 1f .6...........7..
Jan 28 21:11:56 192.168.100.105 :p.u
Jan 28 21:11:56 192.168.100.105 030: ab c1 c2 3f b9 e6 f4 89 7c 81 85 2a 43 25 75 69 ...?.......*C%ui
Jan 28 21:11:56 192.168.100.105 040: 47 31 3f ed 0a 73 0f 24 cc d4 c0 b3 fa ff ff ff G1?..s.$........
Jan 28 21:11:56 192.168.100.105 050: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
Jan 28 21:11:56 192.168.100.105 060: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 83 ................
Jan 28 21:11:56 192.168.100.105 070: 01 04 84 02 00 00 df 08 93 9b 6c 7b 32 bd 15 93 ..........l{2...
Jan 28 21:11:56 192.168.100.105
Jan 28 21:11:56 192.168.100.105 Client <- Server: -- Mon Jan 28 20:11:55 2013
Jan 28 21:11:56 192.168.100.105 ----------------------------------------------------
Jan 28 21:11:56 192.168.100.105 000: 80 10 10 ff 2d af db e4 12 43 39 e3 d0 88 3b 5e ....-....C9...;^
Jan 28 21:11:56 192.168.100.105 010: 14 83 f5 ...
Jan 28 21:11:56 192.168.100.105
Jan 28 21:11:56 192.168.100.105 [mg1] <- CW from newcamd serv1:XXX32 (178ms)
Jan 28 21:11:56 192.168.100.105 [mg1] 178 msec -- Mon Jan 28 20:11:55 2013
Jan 28 21:11:56 192.168.100.105 system: Cryptoworks caid: 0x0D96 pid: 0x0475
Jan 28 21:11:56 192.168.100.105 prov: 000004
Jan 28 21:11:56 192.168.100.105 cw0:1 FF 2D AF DB E4 12 43 39
Jan 28 21:11:56 192.168.100.105 cw1:1 E3 D0 88 3B 5E 14 83 F5
Jan 28 21:12:02 192.168.100.105 [mg1] stoping camd..
Jan 28 21:12:03 192.168.100.105 [mg1] service 13EF index 1 pmt pid 0 (1)
Jan 28 21:12:03 192.168.100.105 CaPID: 0x0459 ProvID: 000000
Jan 28 21:12:03 192.168.100.105 CaPID: 0x0463 ProvID: 000000
Jan 28 21:12:03 192.168.100.105 CaPID: 0x046D ProvID: 000000
Jan 28 21:12:03 192.168.100.105 CaPID: 0x0477 ProvID: 000000
Jan 28 21:12:03 192.168.100.105 CaPID: 0x048B ProvID: 000000
Jan 28 21:12:03 192.168.100.105 CaPID: 0x0495 ProvID: 000000
Jan 28 21:12:03 192.168.100.105 [mg1] Cryptoworks prov 4
Jan 28 21:12:03 192.168.100.105 [mgcamd] Cryptoworks key(s) not found for caid 0D03 provid 04 keynr 00
Jan 28 21:12:03 192.168.100.105 [mg1] network can't decode
Jan 28 21:12:03 192.168.100.105 [mg1] pid 0x0459 failed to decode.
Jan 28 21:12:03 192.168.100.105 [mg1] Cryptoworks prov 4
Jan 28 21:12:03 192.168.100.105 [mgcamd] Cryptoworks key(s) not found for caid 0D70 provid 04 keynr 00
Jan 28 21:12:03 192.168.100.105 [mg1] network can't decode
Jan 28 21:12:03 192.168.100.105 [mg1] pid 0x0463 failed to decode.
Jan 28 21:12:03 192.168.100.105 [mg1] Cryptoworks prov 4
Jan 28 21:13:27 192.168.100.105 [mg1] stoping camd..
Jan 28 21:13:28 192.168.100.105 [mg1] service 13ED index 1 pmt pid 0 (1)
Jan 28 21:13:28 192.168.100.105 CaPID: 0x0457 ProvID: 000000
Jan 28 21:13:28 192.168.100.105 CaPID: 0x0461 ProvID: 000000
Jan 28 21:13:28 192.168.100.105 CaPID: 0x046B ProvID: 000000
Jan 28 21:13:28 192.168.100.105 CaPID: 0x0475 ProvID: 000000
Jan 28 21:13:28 192.168.100.105 CaPID: 0x047F ProvID: 000000
Jan 28 21:13:28 192.168.100.105 CaPID: 0x0493 ProvID: 000000
Jan 28 21:13:28 192.168.100.105 [mg1] Cryptoworks prov 4
Jan 28 21:13:28 192.168.100.105 [mgcamd] Cryptoworks key(s) not found for caid 0D03 provid 04 keynr 00
Jan 28 21:13:28 192.168.100.105 [mg1] network can't decode
Jan 28 21:13:28 192.168.100.105 [mg1] pid 0x0457 failed to decode.
Jan 28 21:13:28 192.168.100.105 [mg1] Cryptoworks prov 4
Jan 28 21:13:28 192.168.100.105 [mgcamd] Cryptoworks key(s) not found for caid 0D70 provid 04 keynr 00
Jan 28 21:13:28 192.168.100.105 [mg1] network can't decode
Jan 28 21:13:28 192.168.100.105 [mg1] pid 0x0461 failed to decode.
Jan 28 21:13:28 192.168.100.105 [mg1] Cryptoworks prov 4
Jan 28 21:13:28 192.168.100.105 [mgcamd] Cryptoworks key(s) not found for caid 0D0F provid 04 keynr 01
Jan 28 21:13:28 192.168.100.105 [mg1] network can't decode
Jan 28 21:13:28 192.168.100.105 [mg1] pid 0x046B failed to decode.
Jan 28 21:13:28 192.168.100.105 [mg1] Cryptoworks prov 4
Jan 28 21:13:28 192.168.100.105 [mgcamd] Cryptoworks key(s) not found for caid 0D96 provid 04 keynr 00
Jan 28 21:13:28 192.168.100.105 ECM to newcamd serv1:XXX32
Jan 28 21:13:28 192.168.100.105 Server: -- Mon Jan 28 20:13:27 2013
Jan 28 21:13:28 192.168.100.105 ----------------------------------------------------

suma · 29 January 2013, 07:29:40

Quote from: hypnox on 29 January 2013, 00:36:06
hi, skylink is still freezing to me, 5 to 10 times per day for a few second to minutes..
here is my log file, pls help..

Hi, which particular channels are freezing for you? The whole package or just some channels? Name them pls, we'll check

hypnox · 29 January 2013, 11:02:35

hello, yesterday logging it was channel markiza, but its not a rule, the decoding error is random on any channel..

suma · 29 January 2013, 11:46:55

We have lost signal from SkyLink. Check the signal level, is it OK?

hypnox · 29 January 2013, 13:42:38

currently I dont know, but the signal strength usually dont falls below 86%.. if you think signal level from transponder..

suma · 29 January 2013, 19:14:27

Have you installed ignore.list, priority.list and replace.list from our server?
http://www.cardsharing.cc/index.php?topic=28611.0
Are you using softcam.key of emulator?

hypnox · 29 January 2013, 22:57:21

yes, I have installed, but I download them again..
softcam.key was erased, its mistake? Now I use firmware to octagon sf1008 because the factory firmware for Anaconda was unstable for my box and I found mgcamd to the octagon in this forum, do you think it is worth to try?
here: http://www.cardsharing.cc/index.php?topic=26566.msg71686#msg71686

suma · 30 January 2013, 07:01:36

Try mgcamd you found on the forum, erase softcam.key. You are doing right things.

hypnox · 30 January 2013, 22:06:05

Hi, I tried new mgcamd, sofcam.key was not found, but:

Jan 30 18:54:40 192.168.100.105 ===== Cryptoworks ECM on CaID 0x0D96, pid 0x0475 ======
Jan 30 18:54:40 192.168.100.105 prov: 000004
Jan 30 18:54:40 192.168.100.105 cw0:1 6C 98 BE C2 09 9E D9 80
Jan 30 18:54:40 192.168.100.105 cw1:1 F1 A9 3E D8 DD 8C 84 ED
Jan 30 18:54:43 192.168.100.105 [mg1] stoping camd..
Jan 30 18:54:44 192.168.100.105 [mg1] service 15ED index 1 pmt pid 0 (1)
Jan 30 18:54:44 192.168.100.105 CaPID: 0x0210 ProvID: 000000
Jan 30 18:54:44 192.168.100.105 CaPID: 0x020F ProvID: 000000
Jan 30 18:54:45 192.168.100.105 [mg1] No irdeto key(s) found for id 80 keynr 00
Jan 30 18:54:45 192.168.100.105 [mg1] network can't decode
Jan 30 18:54:45 192.168.100.105 [mg1] pid 0x0210 failed to decode.
Jan 30 18:54:45 192.168.100.105 [mgcamd] Cryptoworks key(s) not found for caid 0D96 provid 04 keynr 00
Jan 30 18:54:45 192.168.100.105 ECM to newcamd serv1:xxxxx
Jan 30 18:54:45 192.168.100.105 [mg1] <- CW from newcamd serv1:xxxxx (82ms)
Jan 30 18:54:45 192.168.100.105 [mg1] 82 msec -- Wed Jan 30 17:54:39 2013

for a few seconds channel encoded... so where is the problem, a weak connection to the internet or something like that?

suma · 31 January 2013, 05:24:02

Check your newly installed firmware. Seems that it is also unstable for your model of receiver. Re-flash your receiver again and try again. No other suggestion. The package is OK and there is no problem with it.

regards

hypnox · 31 January 2013, 15:54:33

ok, I know that the problem is on my side, try cleaning the receiver through RS232 cable, re-recording different versions of firmware may leave "rubbish.. "
Thanks for your patience..