Cisco D9800 connector has a issue: it does not read RF Status values. Version used: 1.5.04
Hi Jose,
Had a quick look in that connector and that table shows the result of a HTTP GET of ‘/ws/v2/status/input/rf’. Would you know if something has changed to that URL or the output of that command? Maybe you could also use the stream viewer to have a look at the response of the device or look in the logging to see if no exceptions are occurring.
In any case I would recommend to open a ticket in order to have this fixed.
Hi Tom.
here is the answer http get: /ws/v2/status/input/rf
<?xml version="1.0" encoding="ISO-8859-1" ?>
<input>
<rf>
<card>1</card>
<port>1</port>
<stream>1</stream>
<satlock>Lock+Sig</satlock>
<inputrate>80.376594</inputrate>
<netname>Turner Argentina</netname>
<netid>1</netid>
<transid>3</transid>
<lsttunerea>NIT_TS_Change</lsttunerea>
<tunereason>User->NIT</tunereason>
<freqmode>NIT</freqmode>
<svclstmode>Relaxed</svclstmode>
<baten>N/A</baten>
<niten>Yes</niten>
<sdten>Yes</sdten>
<paten>Yes</paten>
<act>Yes</act>
<pwr>Off</pwr>
<sel22khz>Off</sel22khz>
<lo1>5.15</lo1>
<lo2>0.0</lo2>
<xover>0.0</xover>
<pol>Horizontal</pol>
<orbpos>0.0</orbpos>
<ewflag>N/A</ewflag>
<afcrange>3.0</afcrange>
<dnlkfreq>3.92</dnlkfreq>
<symrate>30.0</symrate>
<fec>9/10</fec>
<mod>8PSK DVB-S2</mod>
<rolloff>.20</rolloff>
<iq>Normal</iq>
<siglevel> -36</siglevel>
<cndisp>16.6</cndisp>
<cnmargin>5.5</cnmargin>
<acqmode>Auto</acqmode>
</rf>
<rf>
<card>1</card>
<port>2</port>
<stream>1</stream>
<satlock>Lock+Sig</satlock>
<inputrate>80.376597</inputrate>
<netname>Turner Argentina</netname>
<netid>1</netid>
<transid>3</transid>
<lsttunerea>NIT_TS_Change</lsttunerea>
<tunereason>User->NIT</tunereason>
<freqmode>NIT</freqmode>
<svclstmode>Relaxed</svclstmode>
<baten>N/A</baten>
<niten>Yes</niten>
<sdten>Yes</sdten>
<paten>Yes</paten>
<act>No</act>
<pwr>Off</pwr>
<sel22khz>Off</sel22khz>
<lo1>5.15</lo1>
<lo2>0.0</lo2>
<xover>0.0</xover>
<pol>Horizontal</pol>
<orbpos>0.0</orbpos>
<ewflag>N/A</ewflag>
<afcrange>3.0</afcrange>
<acqmode>Basic</acqmode>
</rf>
<rf>
<card>1</card>
<port>3</port>
<stream>1</stream>
<satlock>Lock+Sig</satlock>
<inputrate>80.376597</inputrate>
<netname>Turner Argentina</netname>
<netid>1</netid>
<transid>3</transid>
<lsttunerea>NIT_TS_Change</lsttunerea>
<tunereason>User->NIT</tunereason>
<freqmode>NIT</freqmode>
<svclstmode>Relaxed</svclstmode>
<baten>N/A</baten>
<niten>Yes</niten>
<sdten>Yes</sdten>
<paten>Yes</paten>
<act>No</act>
<pwr>Off</pwr>
<sel22khz>Off</sel22khz>
<lo1>5.15</lo1>
<lo2>0.0</lo2>
<xover>0.0</xover>
<pol>Horizontal</pol>
<orbpos>0.0</orbpos>
<ewflag>N/A</ewflag>
<afcrange>3.0</afcrange>
<acqmode>Basic</acqmode>
</rf>
<rf>
<card>1</card>
<port>4</port>
<stream>1</stream>
<satlock>Lock+Sig</satlock>
<inputrate>80.376597</inputrate>
<netname>Turner Argentina</netname>
<netid>1</netid>
<transid>3</transid>
<lsttunerea>NIT_TS_Change</lsttunerea>
<tunereason>User->NIT</tunereason>
<freqmode>NIT</freqmode>
<svclstmode>Relaxed</svclstmode>
<baten>N/A</baten>
<niten>Yes</niten>
<sdten>Yes</sdten>
<paten>Yes</paten>
<act>No</act>
<pwr>Off</pwr>
<sel22khz>Off</sel22khz>
<lo1>5.15</lo1>
<lo2>0.0</lo2>
<xover>0.0</xover>
<pol>Horizontal</pol>
<orbpos>0.0</orbpos>
<ewflag>N/A</ewflag>
<afcrange>3.0</afcrange>
<acqmode>Basic</acqmode>
</rf>
</input>
Hi Jose. My appologies for the late answer. At first sight, the response seems to contain the necessary data to fill the table. Maybe something has changed in a new firmware version, which causes that the data cannot be parsed correctly anymore. Would recommend to contact techsupport@skyline.be, if you still have this problem.
The possible solution has been found: The problem is that your driver does not have the FEC 9/10 mapped. It would be ideal if in the new version of the driver it could be corrected by placing the non-conventional FECs.
If a conventional FEC such as 2/3 is placed, the values can be read.
Hi Jose,
As a more in-depth investigation is required for this issue than is possible here in the Q&A, I will close this question. If you still need help with this issue, it would be best to contact techsupport@skyline.be as Tom suggests below.