**CHAT ONLY** ECM KEY COLLECTION IN REGION AMERICA PowerVu

[greatgatsby]

No, those don't seem valid. This mux has always been trickier to get working keys for. I've used pvuhome to get the keys for most every other mux up there, but this one, and 101W 4020 have always caused issues. I left pvuhome running last night with 1.4MB of ecm from the mux, and it came up with nothing. Can't remember now, maybe I used to collect 10MB of ecm? Like I said, it's been quite a while since I mucked with this (and lots of the old keys from before are still valid, but not all)

 

[Satsurfer00]

No, those don't seem valid. This mux has always been trickier to get working keys for. I've used pvuhome to get the keys for most every other mux up there, but this one, and 101W 4020 have always caused issues. I left pvuhome running last night with 1.4MB of ecm from the mux, and it came up with nothing. Can't remember now, maybe I used to collect 10MB of ecm? Like I said, it's been quite a while since I mucked with this (and lots of the old keys from before are still valid, but not all)

101 W 4020 Rolls the keys often. You need the EMM key and it rolls pretty fast.

 

[greatgatsby]

101 W 4020 Rolls the keys often. You need the EMM key and it rolls pretty fast.

That's kindof what I suspected. It seemed like I could find keys, but they were never valid by the time I went to use them. Never had luck getting the EMM there either.

 

[greatgatsby]

On a mux like 101w 4020 where there are 2 emm pids, do you record and process both of them? Just one? How do you know?

 

[kebien]

On a mux like 101w 4020 where there are 2 emm pids, do you record and process both of them? Just one? How do you know?

What you mean 2 EMM pids?
Does the CAT says that??
Can you post it?

Generally,CA id 0E01 is not EMM information and have no EMM packets in there,if that is what you trying to point to.

 

[greatgatsby]

Yes, I was referring to CA id 0x0e01. It shows up in TSR in the CAT table, and in PVUEMU (because it's also showing you the same CAT table)

 

[greatgatsby]

Wow, pvh actually ground out the emm key for 101W 4020! Maybe I just wasn't patient enough before. Now I can watch the canookistanies play this hookey they're always going on and on aboot.

 

[acuaroyale]

Hi, does anyone have G15 133W/4166V? Thank you.

 

[ro_54]

Hi, does anyone have G15 133W/4166V? Thank you.

pm sent.

 

[hoffmann]

ECM KEY COLLECTION IN REGION AMERICA

I would appreciate the powervu keys for 58W satellite tp 3960V30000.
Thank you!
att
hoffmann

 

[hoffmann]

ECM KEY COLLECTION IN REGION AMERICA

got it was emulator problem. thanks

 

[jdavid22]

I could put your final configuration of your softcam

 

[Rickk]

softcam.keys are written in hexadecimal

https://www.lyngsat.com/muxes/Intelsat-21_West-hemi_3920-H.html

your oscam settings are the total garbage

 

[jdavid22]

Thanks SatEze

I read some times that wiki, but i do not have documentation to transform from the old format to the new one.

For instance this working ECMs how to move them to the new one?


I wonder how can work this keys just with 0000 instead of <group><srvid>

Thanks

You do not need to make any transformation from that old format (which works and works well) to the new format but you should read the url just provided ...

P <hash> GROUP <groupid>

This part is the only difficult since you must obtain it for each of the tps(hash) ..

I spent everything served friend, just add your emmkey is everything.

Now I asked you to upload your softcamkey for that tp you want to configure, not the Oscam configuration.

 

[lojasyst]

jdavid22

According to the documentation:
hash (4 bytes) : Transponder hash calculated automatically by OSCam-Emu. Use debug level 2 to display it


tail -f /var/log/oscam.log | grep hash shows only
(emu) csaUsed: 0, xorMode: 0, ecmSrvid: 0065, hashModeCw: 1, modeCW: 3
(emu) channel hash: 00000000, group id: 0000

So I never get the hash to put that line with debug level 2.

Am i missing something?

 

[jdavid22]

I think it is confusing what is needed, if you use any new version of oscam the hash of the tp you see it in the log.


Watch this video if you could, I could help you.

https://www.youtube.com/watch?v=D96Gvki3bZk

 

[antrabe]

anyone knows if something change on tp 3966h 22500 , 43W

 

[jdavid22]

You came asking for the 3920h, the 4120h is another roll ... that tp and the 3960v use the same emmkey, correct your softcam accordingly. Obviously you must also be sure that the emmkey are still valid. You should also wait a while until you get the keys

 

[lojasyst]

Jdavid22, Sorry if I confused you.

Neither 3720V nor 3920H and 4120H/3960V does not work. Just the same message not found

I think it is a config problem because you reported the keys still work

(ecm) get cw for ecm:
(ecm) 80 30 45 50 3F 20 0E 00 73 08 92 53 3D 09 7F 09
(ecm) 06 0C 00 A6 A0 00 34 3E 7B BC 2A 4D 7D DC A4 65
(ecm) BB DB 48 03 E5 03 70 00 00 BC 36 AB 8F 89 ED 69
(ecm) 95 C9 0C 05 51 43 EE A0 62 D3 0D 8B 7B 16 59 B3
(ecm) 53 8A EC A7 0E 7E 21 D9
(ecm) linuxsatsupport (0E00@000000/0000/0037/48:CF5A0A738DB060D00AF6F580AAEE492B): not found (1 ms) by emulator
​

 

[lojasyst]

I changed log level and now I see
(reader) emulator [emu] Error processing ecm for caid 0E00, provid 000000, srvid 0026, servicename: 0E00@000000:0026 unknown

But i do have in services provid/srvid