PowerVu Chat [only chat, don‘t post keys here]

nautilus7

VIP
Messages
607
@chk8210 what you say is not possible. With the new method you tell oscam-emu what group id to use for your channels. What are the group directives that you added in your softcam.key for the new pvu method?

@m35istan, with the new method is not needed to have unique emm keys.
 

m35istan

Registered
Messages
696
@chk8210 what you say is not possible. With the new method you tell oscam-emu what group id to use for your channels. What are the group directives that you added in your softcam.key for the new pvu method?

@m35istan, with the new method is not needed to have unique emm keys.

I can not try with new method. But i can try and write here if i found same emm key. :)
 

jdavid22

Registered
Messages
167
I have a very similar problem, for the tps 4100H (105w) and 4120H (058w) with the old method you find the key ecm, but with the new method, you never find the key, this same problem was exposed here ... https: / /www.sat-universe.com/showpost.php?p=2037006499&postcount=95
 

m35istan

Registered
Messages
696
@m35istan, with the new method is not needed to have unique emm keys.

Firstly i do not understand what means "not needed to have unique emm keys."

I try to 4 same emm keys for 12303 & 12322

When I write thor group keys added thor section.

Code:
P 0008FFFF 00 F8CB6A9F56E5A9 ; added by Emu Tue Jun 11 23:18:16 2019 UA: 00623773
P 0008FFFF 01 E2801E35FF20D5 ; added by Emu Tue Jun 11 23:18:16 2019 UA: 00623773

When I write astra group keys added astra section.

Code:
P 005EFFFF 00 2CAF14DA76F715 ; added by Emu Tue Jun 11 23:57:33 2019 UA: 00623773
P 005EFFFF 01 DC0452CBAB850A ; added by Emu Tue Jun 11 23:57:33 2019 UA: 00623773

When I write thor section and if i watch astra not write any key

Code:
2019/06/11 23:25:06   0050494E00000000   82309B1099010E
2019/06/11 23:25:37   0050C38300000000   82309B1099010E
2019/06/11 23:26:38   0052ACB300000000   82309B1099010E
2019/06/11 23:26:50   0052F2B200000000   82309B1099010E
2019/06/11 23:27:31   00535D6400000000   82309B1099010E
2019/06/11 23:28:58   00561A8F00000000   82309B1099010E
2019/06/11 23:29:07   005636AB00000000   82309B1099010E
2019/06/11 23:30:30   0059155200000000   82309B1099010E
2019/06/11 23:32:25   006019B600000000   82309B1099010E
2019/06/11 23:33:03   0060DA4600000000   82309B1099010E


2019/06/11 23:44:41   0050494E00000000   82309B1099010E
2019/06/11 23:45:13   0050C38300000000   82309B1099010E
2019/06/11 23:46:16   0052ACB300000000   82309B1099010E
2019/06/11 23:46:28   0052F2B200000000   82309B1099010E
2019/06/11 23:47:06   00535D6400000000   82309B1099010E
 

m35istan

Registered
Messages
696
P ACE05CA0 GROUP 0008 ; 4.8°E 12360 V
P BF175115 GROUP 0008 ; 0.8°W 12303 V
P 0008FFFF 00 00000000000000 ;ecm key
P 0008FFFF 01 00000000000000 ;ecm key

P 0008 0057FB98 XXXXXXXXXXXXXX ; EMM Key 12303 & 12322
P 0008 005FB5AF XXXXXXXXXXXXXX ; EMM Key 12303 & 12322
P 0008 006A1FAA XXXXXXXXXXXXXX ; EMM Key 12303 & 12322
P 0008 00623773 XXXXXXXXXXXXXX ; EMM Key 12303 & 12322

P 0008FFFF 00 F8XXXXXXXXXXA9 ; added by Emu Wed Jun 12 00:44:55 2019 UA: 00623773
P 0008FFFF 01 E2XXXXXXXXXXD5 ; added by Emu Wed Jun 12 00:44:55 2019 UA: 00623773


Code:
2019/06/12 00:47:59 44434FA0 r      (emu) Key found in EMM: P 0008**** 00 Fxxxxxxxxxxxx9 ; UA: 006A1FAA
2019/06/12 00:47:59 44434FA0 r      (emu) Key found in EMM: P 0008**** 01 Exxxxxxxxxxxx5 ; UA: 006A1FAA
2019/06/12 00:47:59 44434FA0 r   (reader) emu1 [emu] solo2 emmtype=unique, len=155 (hex: 0x9B), cnt=1: written (12 ms)
2019/06/12 00:47:59 26623DFD c   (reader) emu1 [emu] Successfully added EMM to /etc/tuxbox/config/emu1_unique_emm.log
2019/06/12 00:48:00 69D2A25C h    (webif) all debug_level=2
2019/06/12 00:48:00 26623DFD c      (ecm) get cw for ecm:
2019/06/12 00:48:00 26623DFD c      (ecm)   81 30 3D 30 37 20 0E 00 00 00 00 E8 B0 00 5D 5E 
2019/06/12 00:48:00 26623DFD c      (ecm)   2D F8 87 9E B4 A9 FC CE 88 BC 75 2B 00 A2 C0 00 
2019/06/12 00:48:00 26623DFD c      (ecm)   00 76 56 51 E8 55 85 E2 F6 40 02 5C 2D 89 24 82 
2019/06/12 00:48:00 26623DFD c      (ecm)   75 0C 07 88 CA B5 9A 7D 28 1E D1 36 5F 55 13 8E 
2019/06/12 00:48:00 44434FA0 r      (emu) csaUsed: 0, xorMode: 0, ecmSrvid: 0A2C, hashModeCw: 0, modeCW: 0
2019/06/12 00:48:00 44434FA0 r      (emu) channel hash: BF175115, group id: 0008
2019/06/12 00:48:00 44434FA0 r      (emu) calculated cw 0: BCD3D92C6B43DADC
2019/06/12 00:48:00 44434FA0 r      (emu) calculated cw 1: 5B209731B57C4FAD
2019/06/12 00:48:00 44434FA0 r      (emu) calculated cw 2: 3B252585EA9BCDDA
2019/06/12 00:48:00 44434FA0 r      (emu) calculated cw 3: 3B252585EA9BCDDA
2019/06/12 00:48:00 44434FA0 r      (emu) calculated cw 4: 1A7FDCA1E025499B
2019/06/12 00:48:00 44434FA0 r      (emu) calculated cw 5: 1A7FDCA1E025499B
2019/06/12 00:48:00 44434FA0 r      (emu) calculated cw 6: 31E9FB25922008CD
2019/06/12 00:48:00 44434FA0 r      (emu) calculated cw 7: CE6E04C46DD93732

P 0045BED1 GROUP 005E ; 4.8°E, 12322 V
P 005EFFFF 00 00000000000000 ;ecm key
P 005EFFFF 01 00000000000000 ;ecm key

P 005E 0057FB98 XXXXXXXXXXXXXX ; EMM Key 12303 & 12322
P 005E 005FB5AF XXXXXXXXXXXXXX ; EMM Key 12303 & 12322
P 005E 006A1FAA XXXXXXXXXXXXXX ; EMM Key 12303 & 12322
P 005E 00623773 XXXXXXXXXXXXXX ; EMM Key 12303 & 12322

P 005EFFFF 00 2CXXXXXXXXXX15 ; added by Emu Wed Jun 12 00:56:25 2019 UA: 00623773
P 005EFFFF 01 DCXXXXXXXXXX0A ; added by Emu Wed Jun 12 00:56:25 2019 UA: 00623773

Code:
2019/06/12 00:56:25 44434FA0 r      (emu) Writing key file: /etc/tuxbox/config3/SoftCam.Key
2019/06/12 00:56:25 44434FA0 r      (emu) Key written: P 005EFFFF 00 2CXXXXXXXXXX15
2019/06/12 00:56:25 44434FA0 r      (emu) Key found in EMM: P 005E**** 00 2CXXXXXXXXXX15 ; UA: 00623773
2019/06/12 00:56:25 44434FA0 r      (emu) Writing key file: /etc/tuxbox/config3/SoftCam.Key
2019/06/12 00:56:25 44434FA0 r      (emu) Key written: P 005EFFFF 01 DCXXXXXXXXXXX0A
2019/06/12 00:56:25 44434FA0 r      (emu) Key found in EMM: P 005E**** 01 DCXXXXXXXXXX0A ; UA: 00623773
2019/06/12 00:56:25 6DB849DE c   (reader) emu1 [emu] Successfully added EMM to /etc/tuxbox/config/emu1_unique_emm.log
2019/06/12 00:56:25 44434FA0 r   (reader) emu1 [emu] solo2 emmtype=unique, len=155 (hex: 0x9B), cnt=1: written (18 ms)
2019/06/12 00:56:26 6DB849DE c      (ecm) get cw for ecm:
2019/06/12 00:56:26 6DB849DE c      (ecm)   80 30 3D 30 37 20 0E 00 00 00 00 B3 A0 00 36 15 
2019/06/12 00:56:26 6DB849DE c      (ecm)   E7 BD 50 90 90 E3 3A F3 13 F6 53 31 00 51 40 00 
2019/06/12 00:56:26 6DB849DE c      (ecm)   00 32 BB 78 0D B2 31 47 41 02 F8 0F E8 E6 32 BD 
2019/06/12 00:56:26 6DB849DE c      (ecm)   F5 99 E7 BC 7C 49 DB 23 70 A1 DF 68 67 90 C3 F4 
2019/06/12 00:56:26 44434FA0 r      (emu) csaUsed: 0, xorMode: 0, ecmSrvid: 0514, hashModeCw: 0, modeCW: 0
2019/06/12 00:56:26 44434FA0 r      (emu) channel hash: 0045BED1, group id: 005E
2019/06/12 00:56:26 44434FA0 r      (emu) calculated cw 0: BAC894AB3851EC32
2019/06/12 00:56:26 44434FA0 r      (emu) calculated cw 1: 38C7A7CDE0409EA4
2019/06/12 00:56:26 44434FA0 r      (emu) calculated cw 2: FD6738263845612A
2019/06/12 00:56:26 44434FA0 r      (emu) calculated cw 3: FD6738263845612A
2019/06/12 00:56:26 44434FA0 r      (emu) calculated cw 4: FD6738263845612A
2019/06/12 00:56:26 44434FA0 r      (emu) calculated cw 5: 45EF3170A8C4EA58
2019/06/12 00:56:26 44434FA0 r      (emu) calculated cw 6: 4634F87A16BF0B5E
2019/06/12 00:56:26 44434FA0 r      (emu) calculated cw 7: A1834097F885B091
 
Last edited:

iq180

Registered
Messages
235
I have a very similar problem, for the tps 4100H (105w) and 4120H (058w) with the old method you find the key ecm, but with the new method, you never find the key, this same problem was exposed here ... https: / /www.sat-universe.com/showpost.php?p=2037006499&postcount=95

I have no problem with these 2 sats, my 50 usd china box works perfect on this, I have old logs for finding EMM keys, just load the EMM key, put it on the sat tp/ Ch and let it sit and it opens.
 

m35istan

Registered
Messages
696
@m35istan, explain in better English what the problem, because I don't see anything wrong.

Same emm key work without problem with new method.
If i write emm key thor group oscam add key thor group,
If i write same emm key astra group oscam emu add key astra group.
 

jdavid22

Registered
Messages
167
I have no problem with these 2 sats, my 50 usd china box works perfect on this, I have old logs for finding EMM keys, just load the EMM key, put it on the sat tp/ Ch and let it sit and it opens.

Yes, I reiterate, the old method works, I also have logs from 2015-2017 and I have released new emmkeys, with the new method these emmkeys do not work, but if they do it with the old method it works without any problem, the problem is solved by returning to the old method, what leaves me in doubt is because the new method does not work. I will continue with my tests ..

P.D: I currently have a Vu + Duo2 without stream relay
 

chk8210

Registered
Messages
60
@chk8210 what you say is not possible. With the new method you tell oscam-emu what group id to use for your channels. What are the group directives that you added in your softcam.key for the new pvu method?

Hi Nautilus7,

So for example 40W, below 2 package use same EMM key.
Code:
P F5885E47 GROUP 000A ;40W 4047R
P 000AFFFF 00 xxxxxxxxxxxxxx
P 000AFFFF 01 xxxxxxxxxxxxxx
P 000A 0061DD5D xxxxxxxxxxxxxx ; EMM Key

P 2CC4BB28 GROUP 0042 ; 40W 3728L
P 0042FFFF 00 xxxxxxxxxxxxxx
P 0042FFFF 01 xxxxxxxxxxxxxx
P 0042 0061DD5D xxxxxxxxxxxxxx ; EMM Key

With above setting 4047R updating well, but 3728L nothing.
If I delete EMM key from 4047R, 3728L updating and working.
AFN C vs. KU band same situation.
 

nautilus7

VIP
Messages
607
Yep, there is a bug. The emm algorithm finds new ecm keys but it writes them in the first group in the sofcam.key, the wrong one.

I will investigate the problem.
 
Last edited:

007.4

VIP
Messages
364
I may have missed something here as I've not followed the whole thread.
However, why not simply put the transponders with the same EMM key in the same group, as we do for discovery on 1W and 5E?
eg
Code:
P ACE05CA0 GROUP 0001 ;discovery networks 4.8°E 12360 V 
P BF175115 GROUP 0001 ;discovery networks 0.8°W 12303 V 
P 0001FFFF 00 xxxxxxxxxxxxxx
P 0001FFFF 01 yyyyyyyyyyyyyy
P 0001 EMMxEMMx zzzzzzzzzzzzzz; EMM

Thus for 40W you would have
Code:
P F5885E47 GROUP 000A ;40W 4047R
P 2CC4BB28 GROUP 000A ;40W 3728L
P 000AFFFF 00 xxxxxxxxxxxxxx
P 000AFFFF 01 xxxxxxxxxxxxxx
P 000A 0061DD5D xxxxxxxxxxxxxx ; EMM Key

If they are using the same EMM key they must be using the same ECM keys?
 

nautilus7

VIP
Messages
607
Yes, if the ecm keys are always the same, then this is the proper setup!

And probably this is why I didn't notice the bug before.


I had a quick look into the code and it not that easy to pass the necessary info (namespace, tsid and onid) to the emm algo, so it can calculate the channel hash and find the correct group id. The best/easiest solution would be to use the same group id, if the ecm keys are the same of course.
 
Last edited:

chk8210

Registered
Messages
60
Thus for 40W you would have
Code:
P F5885E47 GROUP 000A ;40W 4047R
P 2CC4BB28 GROUP 000A ;40W 3728L
P 000AFFFF 00 xxxxxxxxxxxxxx
P 000AFFFF 01 xxxxxxxxxxxxxx
P 000A 0061DD5D xxxxxxxxxxxxxx ; EMM Key

If they are using the same EMM key they must be using the same ECM keys?

I will try and send feedback about the result.
Thanks!
 

drhans

Registered
Messages
116
If they are using the same EMM key they must be using the same ECM keys?

not really, in theory providers should remove or expire unused UAs from their PNCs but often they don't, so it's reasonable to expect different ECM keys on 3728L and 4047R... they probably use different scramblers but the same IRD database
 
Top