[pabi]

Hi all,

I loaded the above binfile with a fix for Amazonas. I did a 8282 default key and used 73 11 as Provider ID. Result: did not work.
Added provider ID 73 06 with keys and box froze several times. When finally accepted new Id and keys it still does not function.

Anyone any ideas about solution?

Help appreciated.

Pabi

[DOWNLOWEZ]

dish n2 is gone.... n3 is king...

[beekermc]

No he's talking about Amazonas but that's down on all boxes right now. When a fix is released it will be here on AAAFTA.

[Ladybbird]

Originally Posted by pabi

Hi all,

I loaded the above binfile with a fix for Amazonas. I did a 8282 default key and used 73 11 as Provider ID. Result: did not work.
Added provider ID 73 06 with keys and box froze several times. When finally accepted new Id and keys it still does not function.

Anyone any ideas about solution?

Help appreciated.

Pabi

Pabi

You have asked the same question over and over again in the different threads you have started, including this one a couple of hours ago;

fix for Amazonas?

beekermc , I and others have answered you over and over. When a fix is issued it will be posted on the site. Please stop starting new threads for the same question.

[pabi]

Originally Posted by beekermc

No he's talking about Amazonas but that's down on all boxes right now. When a fix is released it will be here on AAAFTA.

Unless I am wrong, I found the fix for Pansat 250 SM posted by buddyjh, AAAFTA sitehelper, five days ago, so after the revision of N2 by Telefonica. The only problem I am having is that I do not know whether or not to change Provider ID from 73 11 into 73 06 or not. (see title above).

[beekermc]

It's because since that bin (today) all receivers are down on Amazonas.

[pabi]

Originally Posted by Ladybbird

Pabi

You have asked the same question over and over again in the different threads you have started, including this one a couple of hours ago;

fix for Amazonas?

beekermc , I and others have answered you over and over. When a fix is issued it will be posted on the site. Please stop starting new threads for the same question.

I started threads for different boxes in the correct sections as far as I am aware of. If not, please accept my appologies, Now I will wait and see what the answers will be in these forums.

[beekermc]

Here's the new BIN pabi:

X_250_150AMZ_090624_V525_api_amz (Amazonas Only)

[pabi]

Thank you very much for the new binfile!

Just for my information: Is this a fix for 73 11 or 73 06?
Next time I have to change keys I will know which provider id to use.
Thanks in advance for the info.

[beekermc]

Sometimes when they mess around with the satellite then a simple key change isn't enough. This and the ECM before this required bin files to fix. All the key inputting in the world wouldn't have brought it back up. So if it's a simple key change usually the keys will be posted along with the provider ID, if you don't see new keys wait for the new bins.

[pabi]

Originally Posted by beekermc

Sometimes when they mess around with the satellite then a simple key change isn't enough. This and the ECM before this required bin files to fix. All the key inputting in the world wouldn't have brought it back up. So if it's a simple key change usually the keys will be posted along with the provider ID, if you don't see new keys wait for the new bins.

I know what you mean. This binfile is working fine for now. What I meant was what provider id do I have to use for FUTURE keychanges? Is it still 7311 or will it be 7306 ? Before I start changing the wrong keys.

[beekermc]

When any keys are posted they will have the Provider you need to change right beside them.

[vietloan]

sorry to inturrupt, but i have a pansat 250sm, will this file( X_250_150AMZ_090624_V525_api_amz (Amazonas Only)work for my reciever?

[beekermc]

Only if your dish is pointed at Amazonas 61.0W.

[vietloan]

yeah, i don't think my dish is pointed at that, ty for the quick response