Jump to content


Photo

[Satfinder] Add multitype tuner support


  • Please log in to reply
35 replies to this topic

Re: [Satfinder] Add multitype tuner support #21 athoik

  • PLi® Core member
  • 8,458 posts

+327
Excellent

Posted 5 November 2016 - 06:43

On cable there is an transponder?

Edited by athoik, 5 November 2016 - 06:44.

Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916

Re: [Satfinder] Add multitype tuner support #22 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 5 November 2016 - 09:06

Well, not literally, but a frequency = a transponder (or in fact the other way around).



Re: [Satfinder] Add multitype tuner support #23 Huevos

  • PLi® Contributor
  • 4,644 posts

+161
Excellent

Posted 5 November 2016 - 10:02

It's just terminology. It is a multiplex or transport stream. Lots of people call it a transponder, but in reality that is a piece of hardware onboard a satellite.

Re: [Satfinder] Add multitype tuner support #24 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+541
Excellent

Posted 5 November 2016 - 10:55

Yeah the name transponder is really a misnomer. On both S, T and C it should be called a stream or a frequency, inho. In NL it's called a "complex" on C, I don't know in other countries.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: [Satfinder] Add multitype tuner support #25 littlesat

  • PLi® Core member
  • 57,120 posts

+698
Excellent

Posted 5 November 2016 - 11:58

That is why I thought about Signal Finder....


WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: [Satfinder] Add multitype tuner support #26 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 5 November 2016 - 12:01

Problem is that it doesn't 'find' a signal; it shows all details of 'the signal' (both receiving-quality/quantity and details). Plus it has a scan option.

 

'Signal details'?

'Signal details & scan'?



Re: [Satfinder] Add multitype tuner support #27 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+541
Excellent

Posted 5 November 2016 - 12:15

Signal status

Signal monitor

Reception status

Signal debug

 

Just a few suggestions.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: [Satfinder] Add multitype tuner support #28 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 5 November 2016 - 12:23

'Signal status' & 'Signal monitor' aren't bad at all.

Re: [Satfinder] Add multitype tuner support #29 littlesat

  • PLi® Core member
  • 57,120 posts

+698
Excellent

Posted 5 November 2016 - 12:40

In het nederlands staat daar Signaalzoeker.... Signal Finder... Wat is daar mis mee???


WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: [Satfinder] Add multitype tuner support #30 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+541
Excellent

Posted 5 November 2016 - 12:47

http://forums.openpl...e-2#entry611125


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: [Satfinder] Add multitype tuner support #31 Huevos

  • PLi® Contributor
  • 4,644 posts

+161
Excellent

Posted 5 November 2016 - 17:15

No, it is the person moving the dish that finds the signal.

 

But I still think "Signal Finder" is best.

 

Before I converted this plugin to display Terrestrial and Cable it was called  "Sat Finder" so I don't see why "Signal Finder is not appropriate. Or maybe PLi just want to use something different from all the other images that changed the name more than a year ago.

 

https://github.com/O...bb8fbe87b17f745


Edited by Huevos, 5 November 2016 - 17:16.


Re: [Satfinder] Add multitype tuner support #32 Huevos

  • PLi® Contributor
  • 4,644 posts

+161
Excellent

Posted 6 November 2016 - 03:07

Do you trust DVB API?

If yes then you do not afraid of the following patch.

 First victim is Vu+ Hybrid DVB-C/DVB-T twin tuner (TT3L10).

 

https://github.com/O...d7b1fa54cc1b0dc

 

TT3L10 reports:

<    27.535> [NIM] get types from delsys ['DVB-C']


Edited by Huevos, 6 November 2016 - 03:08.


Re: [Satfinder] Add multitype tuner support #33 littlesat

  • PLi® Core member
  • 57,120 posts

+698
Excellent

Posted 6 November 2016 - 10:02

I'm afraid basically a vu problem... So another vu work-a-round consideration discussion :(

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: [Satfinder] Add multitype tuner support #34 Huevos

  • PLi® Contributor
  • 4,644 posts

+161
Excellent

Posted 6 November 2016 - 11:23

It is reported to Vu months ago that their drivers are not DVB API 5 compliant. So no surprise. This is just another example.

If it works in the factory image thats good enough for them.

Right now it only works because it falls back to the proc values.

Re: [Satfinder] Add multitype tuner support #35 littlesat

  • PLi® Core member
  • 57,120 posts

+698
Excellent

Posted 6 November 2016 - 13:15

Thrn we should consider to keep it on proc values....

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: [Satfinder] Add multitype tuner support #36 Huevos

  • PLi® Contributor
  • 4,644 posts

+161
Excellent

Posted 6 November 2016 - 13:36

It should follow DVB API 5. Anyway there are other boxes where DVB API 5 is correct and proc values are wrong.

 

Right now we are using DVB API 5, and proc as fallback.

 

But anyway proc values don't help in the example given by Athoik.


Edited by Huevos, 6 November 2016 - 13:37.



2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users