HVS-2 PID(s)


James Brown
 

Good day all.
With David’s help again my system is almost running successfully on my new settings using TBS dual mode for basic and HVS-1.

The SR-1 is also back in business on the new HVS-2.

But the tellicast is not seeing data so I’m wondering if there is any change in the hvs2 channel ini that needs to be made for the new transponder and perhaps more importantly which PID and MODCOD for single reception.

I have currently set the MODCODS to 0x00041000 and in the filter table PID 610 as per a Eumetsat doc but tc is still waiting to connect.

Any thoughts gratefully received.

All the best,
James.


James Brown
 

On 29 Nov 2022, at 11:15, James Brown <satellite@...> wrote:

Good day all.
With David’s help again my system is almost running successfully on my new settings using TBS dual mode for basic and HVS-1.

The SR-1 is also back in business on the new HVS-2.
I can now report all is well and apologies for bothering the group.

Over the weekend I’d done a reset to factory settings on the SR-1 and thought I’d changed everything.

Erm, I possibly hadn’t set the LAN multicast to ON, just possibly ;-)

James.


Ernst Lobsiger
 

James,

IIRC MODCODS 0x00041000 is BAS+HVS-1 or HVS-2 and PID 610 is O.K. Maybe your SNR is marginal and the SR1
switches off HVS modcodes. You could probably run without MODCOD filter or set the limit for cutoff low. My 2 cents.

Ernst


David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺
 

On 29/11/2022 11:14, James Brown wrote:
Good day all.
With David’s help again my system is almost running successfully on my new settings using TBS dual mode for basic and HVS-1.
The SR-1 is also back in business on the new HVS-2.
But the tellicast is not seeing data so I’m wondering if there is any change in the hvs2 channel ini that needs to be made for the new transponder and perhaps more importantly which PID and MODCOD for single reception.
I have currently set the MODCODS to 0x00041000 and in the filter table PID 610 as per a Eumetsat doc but tc is still waiting to connect.
Any thoughts gratefully received.
All the best,
James.
James,

I'm still thinking 600 and 601, but no harm in adding 610.

It's a pity that the EUMETSAT Ayecka SR1 documentation hasn't been kept up to date, in spite of the latest being dated 2022.

Cheers,
David
--
SatSignal Software - Quality software for you
Web: https://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv


Ernst Lobsiger
 

On Tue, Nov 29, 2022 at 04:17 AM, David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺 wrote:
I'm still thinking 600 and 601, but no harm in adding 610.
600 and 601 is for HVS-1, 610 for HVS-2.


David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺
 

On 29/11/2022 12:24, Ernst Lobsiger via groups.io wrote:
600 and 601 is for HVS-1, 610 for HVS-2.
Thanks, Ernst.

Cheers,
David
--
SatSignal Software - Quality software for you
Web: https://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv


Ernst Lobsiger
 

On Tue, Nov 29, 2022 at 04:17 AM, David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺 wrote:
I have currently set the MODCODS to 0x00041000 and in the filter table PID 610 as per a Eumetsat doc but tc is still waiting to connect.
David and James,

above modcods IIRC are for the combined BS+HVS-1 and allow for switching off HVS-1 if the SNR  goes below settable numbers.
I never had a SR1 with this feature but assume it should work for HVS-2 as well. Maybe double check the V polarization (13Volts)?

Ernst


geojohnt@...
 

Hello All,

OK, the PID for (all) HVS-2 is 601.

Now I was never licenced for HVS-2 data.
Switching the BS/HVS-1 setup SR! to V and running TC HVS-2 (or not) shows SNR and Power but no data flow.
TC remains yellow and 'connecting.'

And you will see from the attached SR1 status screen shots, HVS-2 shows Transport Status Not Locked - whereas it is for BS/HVS-1.

I've not set any HVS-2 channel .ini yet - really need to know the best channel with the least data just to show everything is working.

???

Regards,
John
 


-----Original Message-----
From: Ernst Lobsiger via groups.io <ernst.lobsiger@...>
To: MSG-1@groups.io
Sent: Tue, 29 Nov 2022 12:42
Subject: Re: [MSG-1] HVS-2 PID(s)

On Tue, Nov 29, 2022 at 04:17 AM, David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺 wrote:
I have currently set the MODCODS to 0x00041000 and in the filter table PID 610 as per a Eumetsat doc but tc is still waiting to connect.
David and James,

above modcods IIRC are for the combined BS+HVS-1 and allow for switching off HVS-1 if the SNR  goes below settable numbers.
I never had a SR1 with this feature but assume it should work for HVS-2 as well. Maybe double check the V polarization (13Volts)?

Ernst


James Brown
 

On 29 Nov 2022, at 17:12, geojohnt via groups.io <geojohnt@...> wrote:


Hello All,

OK, the PID for (all) HVS-2 is 601.

Now I was never licenced for HVS-2 data.
Switching the BS/HVS-1 setup SR! to V and running TC HVS-2 (or not) shows SNR and Power but no data flow.
TC remains yellow and 'connecting.'

And you will see from the attached SR1 status screen shots, HVS-2 shows Transport Status Not Locked - whereas it is for BS/HVS-1.

I've not set any HVS-2 channel .ini yet - really need to know the best channel with the least data just to show everything is working.

???

Regards,
John
 


-----Original Message-----
From: Ernst Lobsiger via groups.io <ernst.lobsiger@...>
To: MSG-1@groups.io
Sent: Tue, 29 Nov 2022 12:42
Subject: Re: [MSG-1] HVS-2 PID(s)

On Tue, Nov 29, 2022 at 04:17 AM, David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺 wrote:
I have currently set the MODCODS to 0x00041000 and in the filter table PID 610 as per a Eumetsat doc but tc is still waiting to connect.
David and James,

above modcods IIRC are for the combined BS+HVS-1 and allow for switching off HVS-1 if the SNR  goes below settable numbers.
I never had a SR1 with this feature but assume it should work for HVS-2 as well. Maybe double check the V polarization (13Volts)?

Ernst
<HVS-1.jpg>
<HVS-2 new.jpg>