need EMM.bin of 123W

[strong5000]

who can send me emm.bin file (4020 H 30000) of Galaxy 18 at 123.0°W?

an friend record TP stream by box but nothing can get, he isn't have DVB card.

thanks

 

[iq180]

who can send me emm.bin file (4020 H 30000) of Galaxy 18 at 123.0°W?

an friend record TP stream by box but nothing can get, he isn't have DVB card.

thanks

This TP uses the Powervu default keys,they have never changed that I know of, I sent you a PM.

 

[strong5000]

thank you

 

[kebien]

And maybe there is no EMM packets sent for that same reason.
Never a key change mean there was never any packets sent to update their receivers,since keys are already in all receivers.

 

[iq180]

The fact of the matter is, they do send the packets in the data stream, the thing is you need to know when, it took me a very long time to find out when so I could get the EMM keys, that being said, the EMM key is of no use if your receiver is not on that TP & Ch when the packets are sent in the data stream.
I sent the OP the ECM & EMM keys, he has what he needs to open the CHs.

 

[strong5000]

The fact of the matter is, they do send the packets in the data stream, the thing is you need to know when, it took me a very long time to find out when so I could get the EMM keys, that being said, the EMM key is of no use if your receiver is not on that TP & Ch when the packets are sent in the data stream.
I sent the OP the ECM & EMM keys, he has what he needs to open the CHs.

maybe this package not use emm with stream more, have to put ECM key working now

 

[kebien]

maybe this package not use emm with stream more, have to put ECM key working now

iq180 is probably correct and the EMM spool is only sent once a week or month,so the only way to catch it is by recording for a full week or month,no other way around it.

I wonder why they even do that knowing the IRD's work right off the moment is turned on,since this keys are already there.
But we cannot really guess all their intentions.

 

[iq180]

iq180 is probably correct and the EMM spool is only sent once a week or month,so the only way to catch it is by recording for a full week or month,no other way around it.

I wonder why they even do that knowing the IRD's work right off the moment is turned on,since this keys are already there.
But we cannot really guess all their intentions.

I think the provider does this to add new receivers to the system or remove receivers, another odd thing about this one is I have never found but 1 EMM key, all stream recordings come up with the same EMM keys.
There are other TPs in the western ark that are odd as well, I found another one that only sends data in the stream for 10 seconds then nothing for the next 27 seconds then 10 seconds of data, I had to record 12 HRs just to get enough to run on PVH.

 

[kebien]

I think the provider does this to add new receivers to the system or remove receivers, another odd thing about this one is I have never found but 1 EMM key, all stream recordings come up with the same EMM keys.
There are other TPs in the western ark that are odd as well, I found another one that only sends data in the stream for 10 seconds then nothing for the next 27 seconds then 10 seconds of data, I had to record 12 HRs just to get enough to run on PVH.

The way I see it is those 10 seconds of data is actually the whole spool of UA,and since you also see only one EMM key,I would assume there is only one UA or just a few in the spool.Meaning they only have a few authorized IRDs.
PVHE would tell you how many UA it sees in the spool.
Other trasponders that use a pool of 4000 UA take a long time to go through the whole spool.
Now the restart of the spool I found no pattern,some trasponders send the spool again in few seconds,some of them pause for even hours.
The best way to see the behavior is in PVemu EMM monitor