autobiss not working

[fusillo]

since few days the autobiss is not properly working...if the key is known it takes few seconds otherwise we can wait for ever and ever. Is there any issue with the AUbiss server?

[STRETCH]

Maybe the transponder details within the server, are not the same as your receiver.

Den

[fusillo]

how can I know which tp is known on server side? it should be all automatic.....maybe it's just overloaded by requests

[Feralkiwi]

I have found that the BISS server is now using 4MHz spacing.
This seamed to happen 3 weeks ago.

A friend rolls a code on 12703 and my LNB / scan finds the same feed on 12699 and the code is not returned from the server.
I change the TP frequency to 12702 and the code is returned.

You will see what frequencies your satellite LNB is returning and can compare them to sites like lyngsat dot com.
You can then see if your LNB has drifted lower or higher.
Knowing this you can then change the frequency for your scanned feed lower or higher by 2MHz and see if you get a code returned.
Here in NZ / Auzz the feeds only include a CW at the start, so if you find the feed some time after it first came up, you may not find any usable CW to get a code from.
Some feeds don't have any CW, ever so never roll.

Note if you change the frequency too far you will loose lock and the server will not be asked.

Owen

[fusillo]

Thanks! Your explanation definitely makes sense, i will focus on frequencies.

[naif]

I have found that the BISS server is now using 4MHz spacing.
This seamed to happen 3 weeks ago.

A friend rolls a code on 12703 and my LNB / scan finds the same feed on 12699 and the code is not returned from the server.
I change the TP frequency to 12702 and the code is returned.

You will see what frequencies your satellite LNB is returning and can compare them to sites like lyngsat dot com.
You can then see if your LNB has drifted lower or higher.
Knowing this you can then change the frequency for your scanned feed lower or higher by 2MHz and see if you get a code returned.
Here in NZ / Auzz the feeds only include a CW at the start, so if you find the feed some time after it first came up, you may not find any usable CW to get a code from.
Some feeds don't have any CW, ever so never roll.

Note if you change the frequency too far you will loose lock and the server will not be asked.

Owen

We did not need this solution for the device one day, but the device was performing its duties to the fullest, always bringing the code in a smooth and fast way until about a month ago, things changed, it seems that it is from your side

[cpr43]

I have found that the BISS server is now using 4MHz spacing.
This seamed to happen 3 weeks ago.

A friend rolls a code on 12703 and my LNB / scan finds the same feed on 12699 and the code is not returned from the server.
I change the TP frequency to 12702 and the code is returned.

You will see what frequencies your satellite LNB is returning and can compare them to sites like lyngsat dot com.
You can then see if your LNB has drifted lower or higher.
Knowing this you can then change the frequency for your scanned feed lower or higher by 2MHz and see if you get a code returned.
Here in NZ / Auzz the feeds only include a CW at the start, so if you find the feed some time after it first came up, you may not find any usable CW to get a code from.
Some feeds don't have any CW, ever so never roll.

Note if you change the frequency too far you will loose lock and the server will not be asked.

Owen

We did not need this solution for the device one day, but the device was performing its duties to the fullest, always bringing the code in a smooth and fast way until about a month ago, things changed, it seems that it is from your side

Why will you updated if everything was working fine?? You need to keep looking and find the way to roll back to your previous firmware

[fusillo]

I have found that the BISS server is now using 4MHz spacing.
This seamed to happen 3 weeks ago.

A friend rolls a code on 12703 and my LNB / scan finds the same feed on 12699 and the code is not returned from the server.
I change the TP frequency to 12702 and the code is returned.

You will see what frequencies your satellite LNB is returning and can compare them to sites like lyngsat dot com.
You can then see if your LNB has drifted lower or higher.
Knowing this you can then change the frequency for your scanned feed lower or higher by 2MHz and see if you get a code returned.
Here in NZ / Auzz the feeds only include a CW at the start, so if you find the feed some time after it first came up, you may not find any usable CW to get a code from.
Some feeds don't have any CW, ever so never roll.

Note if you change the frequency too far you will loose lock and the server will not be asked.

Owen

We did not need this solution for the device one day, but the device was performing its duties to the fullest, always bringing the code in a smooth and fast way until about a month ago, things changed, it seems that it is from your side

Why will you updated if everything was working fine?? You need to keep looking and find the way to roll back to your previous firmware

what kind of answer is this one? first of all the upgrade popup cannot be removed...second there were so many bugs that we hope the upgrade will fix them but them we realize that not only bugs are not solved but new ones are introduced.

[STRETCH]

What software did you have on you receiver, when autoroll biss was working.
Is it in the download section.

Den