Barracuda09 / SATPI

SATIP server for linux, suitable to run on an Raspberry Pi, Vu+, GigaBlue or any other linux box. currently supporting DVB-S/S2/T/C and transform DVB-S requests to DVB-C
http://barracuda09.github.io/SATPI
GNU General Public License v2.0
151 stars 32 forks source link

Request: Unicable/SCR static and dynamic support #151

Open lars18th opened 2 years ago

lars18th commented 2 years ago

Hi @Barracuda09 ,

I feel you're doing some new development to improve the wire management (based on #150). So I want to add this request:

I feel this could be done with the current unicable API. As the static frequencies could correspond to regular (free) SCR slots. And futhermore, if you really need to send the unicable commands, then you could send to a "fake" position (i.e.64?). And then all the real SCR LNBs will not process the command and don't use the slot assigned to the static frequency requested. Futhermore, from the tuner client side this will be like changing from one slot to another. Therefore, I think this could be feasible and it will work fast without troubles.

You could try to implement this, please? Thank you, and please continue with this great project.

Barracuda09 commented 2 years ago

So as I understand it now, it is only the frontend that tunes to a requested freq. so now DiSEqC or 'real' LNB connected

lars18th commented 2 years ago

Hi @Barracuda09 ,

I'm not sure about your comment. The 5th LNB is an another programable SCR/Unicable LNB that is configured to not listen for any JESS/SCR command. Just to pass a fixed transponder/frequency to a fixed slot all the time. That's corresponds to the "static" frequencies that I want to tune with the unicable tuners. Then for each unicable tuner, not only the slot frequency will be in use, but also the static ones (plus some small difference, to round the frequency). This list of static frequencies will be similar to the remapping frequency list. But in this case they are not remapping to anything else. They're only changing the method to "tune" to the target frequency: instead of sending a command to the LNB to center it in the listening frequency, the tuner will change the listening frequency from the current slot to a "new" slot (the static one).

You could implement this, please?

Barracuda09 commented 2 years ago

So the 'static' frequency should be a input in the Unicable settings, and if the frontend receives this frequency it should not send DiSEqC command and/or setup the LNB only tune to this frequency

lars18th commented 2 years ago

So the 'static' frequency should be a input in the Unicable settings, and if the frontend receives this frequency it should not send DiSEqC command and/or setup the LNB only tune to this frequency

YES!

Example of the configuration:

So if the client request this:

I feel it's simple to implement, right? Regards.

Barracuda09 commented 2 years ago

I feel it's simple to implement, right?

Yes, I feel it should not be to much trouble as well.