New Edision OS nino Pro Grey 1x DVB-S2X + 1x DVB-C/T2 Linux Enigma 2 Combo Tuner Digital Multi-Stream Receiver H.265 HEVC HD 1080p

[Huevos]

The El Nino is indicating Left circular polarised signals as Horizontal linear polarised signals, this is not accurate. The SF8008 correctly recognises the circular polarity. Is this issue a setting in the satellites.xml file or some other configuration setting? The El Nino needs to correctly report circular and linear polarity before it can be considered precise.

As there is no difference on the cable between a horizontal polarised signal and a left-hand polarised signal how do you suggest the receiver differenciate between the two? Same with right-hand polarised and vertical polarised.

 

[Huevos]

It actually says both: L and R and V and H.
It would have been necessary before completely removing the satellites.xml of "ninoPro "to know what it indicates of itselfView attachment 120586

Did you correctly set the search parameters. e.g. search circular?

 

[el bandido]

What does the infobar say in the skin?
Is the polarization and other transponder parameters correct in the infobar?

 

[scopus]

After that scan I did posted earlier I did another scan this time selecting 'clear before scan'
Just scanned 40W again and they are now showing correctly as L and R??

 

[Huevos]

Guys you don't seem to get it. No point slating the box. The binary has no way to know if a signal is circular or linear polarised. So it just returns the polarisation YOU fed it. So if YOU enter the wrong polarisation, the output will reflect the wrong polarisation that YOU entered.

After all, how is the receiver supposed to know whether YOU have the dielectric plate inserted or removed from the LNBF.

Only way around this is to read the SI tables on every found transponder and make corrections accordingly. But that is really nothing to do with a blindscan.

 

[scopus]

Guys you don't seem to get it. No point slating the box. The binary has no way to know if a signal is circular or linear polarised. So it just returns the polarisation YOU fed it. So if YOU enter the wrong polarisation, the output will reflect the wrong polarisation that YOU entered.

I'm not slating it, more that happy with my nino..

 

[Pierangelo]

@ scopus.
Please a comparison of the sensitivity of the Tuner.
Thanks

 

[moonbase]

As there is no difference on the cable between a horizontal polarised signal and a left-hand polarised signal how do you suggest the receiver differenciate between the two? Same with right-hand polarised and vertical polarised.

Image menu setting with default value of H/V that can be changed to L/R by the end user per satellite. However, it looks like it is resolved in El Nino based on the last scan from "scopus" where the list was cleared before the scan.

 

[el bandido]

There is a problem.
It really looks like Scanned Transponder values may be changed or altered when "syncWithKnownTransponders" is ran in the blindscan plugin. This issue can be fixed. This issue is easy to duplicate or replicate. First time I have seen an enigma2 receiver do this.

I doubt this issue bothers the scanned channels or the ability to watch tv. Some of the transponder values will appear wrong or altered, but nothing more drastic than that.

 

[Huevos]

There is a problem.
It really looks like Scanned Transponder values may be changed or altered when "syncWithKnownTransponders" is ran in the blindscan plugin. This issue can be fixed. This issue is easy to duplicate or replicate. First time I have seen an enigma2 receiver do this.

That is the whole point of syncWithKnownTransponders. That is desired behaviour. It is correcting for very minor differences in the output of the binary compared to the content of satellites.xml. What did you think it did? Please explain the issue.

 

[el bandido]

Satellites.xml is pretty useless here because some of our satellite transponders change a lot.

During syncWithKnownTransponders, The Nino is taking fec and other wrong values from similar transponder(s) in the .xml file and applying them to what it scanned. It seems to be all cosmetic and does not hurt reception of channels. But it can be confusing.

The skin infobar usually shows the correct FEC for the channel regardless of what the blindscan logged, but the bogus FEC will show in positioner setup and in other places.

Then you also have the Nino Pro assigning bad DVB-S fec's on its own - without any transponders being in satellites.xml for the satellite, and without the aid of syncWithKnownTransponders.

So there are two little issues, both cosmetic.

 

[stephan94]

Another question, if I can afford

Can we currently change the LOF in the "Edision OS Nino Pro" to adapt it to the KA band.?
Can a blindscan be made in KA band and have good frequency values?
I know that on the 8008 this is not possible, the frequencies found by bindscan are indicated with KU values.

 

[scopus]

Another question, if I can afford

Can we currently change the LOF in the "Edision OS Nino Pro" to adapt it to the KA band.?
Can a blindscan be made in KA band and have good frequency values?
I know that on the 8008 this is not possible, the frequencies found by bindscan are indicated with KU values.

No, I have tried to blindscan in Ka it does not work. It will not let you enter the Ka frequency range even if the LOF has been altered, it always asks for Ku values.
It looks like it may be possible blindcan in Ku, then alter the LOF and transponder values in Dreamblox edit to suit. I will try...

 

[stephan94]

So there is a problem to solve.
The possibility of entering the four LOFs for the KA band.
these are:

Ka (A) 18.2-19.2 LOF 17250
Ka (b) 19.2-20.2 LOF 18250
Ka (C) 20.2-21.2 LOF 19250
Ka (D) 21.2-22.2 LOF 20250

or while these four possibilities are already entering the different LNBs possible.
This is possible for the C band, there is no reason that this is impossible for the KA band.
I do not know if this is modifiable in the image or in the drivers.

 

[scopus]

Well the workaround is OK. I changed the LOF in the tuner settings then edited the transponder in Dreambox Edit, the ITN feeds are greyed out as I have not altered these yet, But Newsnet now shows the correct freq with the LOF at 17250
All these were found using the Ku blindscan first..

 

[Huevos]

Satellites.xml is pretty useless here because some of our satellite transponders change a lot.

During syncWithKnownTransponders, The Nino is taking fec and other wrong values from similar transponder(s) in the .xml file and applying them to what it scanned. It seems to be all cosmetic and does not hurt reception of channels. But it can be confusing.

Can you please post some examples of what is in satellites.xml and what the receiver is actually playing.

The skin infobar usually shows the correct FEC for the channel regardless of what the blindscan logged, but the bogus FEC will show in positioner setup and in other places.

Then you also have the Nino Pro assigning bad DVB-S fec's on its own - without any transponders being in satellites.xml for the satellite, and without the aid of syncWithKnownTransponders.

So there are two little issues, both cosmetic.

I thought I explained this above. A blindscan examines the signal to determine the parameters. Enigma uses the values returned by the drivers when tuned to the transport stream. If the drivers are good, these values will have been read from the SI tables.

 

[stephan94]

Guys you don't seem to get it. No point slating the box. The binary has no way to know if a signal is circular or linear polarised. So it just returns the polarisation YOU fed it. So if YOU enter the wrong polarisation, the output will reflect the wrong polarisation that YOU entered.
After all, how is the receiver supposed to know whether YOU have the dielectric plate inserted or removed from the LNBF.
Only way around this is to read the SI tables on every found transponder and make corrections accordingly. But that is really nothing to do with a blindscan.

I do not know of any hardware that can set itself whether it's H / V or L / R, even TBS cards do not know how to do it.
As Huevos says, you just need the user to indicate the polarization with which he works.
For me this is absolutely not a problem.

 

[Huevos]

So there is a problem to solve.
The possibility of entering the four LOFs for the KA band.
these are:

Ka (A) 18.2-19.2 LOF 17250
Ka (b) 19.2-20.2 LOF 18250
Ka (C) 20.2-21.2 LOF 19250
Ka (D) 21.2-22.2 LOF 20250

or while these four possibilities are already entering the different LNBs possible.
This is possible for the C band, there is no reason that this is impossible for the KA band.
I do not know if this is modifiable in the image or in the drivers.

So is this standard in Ka band. I have found LNBs with other combinations listed.

 

[Llew]

In Ka Band, the Inverto Saorsat LNBF uses a LOF of 21200 in Ka Band B (inverted spectrum as with C Band LNBs, to cover 19.7 - 20.2 GHz).

Among other Ka LNBs used in the USA that find their way to Europe for hobbyist use are the Hughes Band A LNB with a LOF of 17350. and the Hughes Band B with a LOF of 18500.

 

[Huevos]

Thanks Llew.

Sounds a right nightmare.

So if I stick to Stephan's numbers I get an IF range of 950-1950 MHz, identical to 10700-11700 MHz in Ku band, right?