#150: Diseqc 1.1 support

Support forum for minisatip
TheTroll

Post by TheTroll »

you mean src=4 for diseqc position 1 ?

TheTroll

Post by TheTroll »

I get this with src=4

[30/07 07:49:55.124477]: send_diseqc fd 8, pos = 3, pol = 0, hiband = 0, com => e0 10 38 fc 00, uncom => e0 10 39 f0 00

TheTroll

Post by TheTroll »

Can you take a look at e2 implementation please ?
When I log what enigma2 does, I get the following when changing diseqc input:

The first time, it goes on input 3:

[eDVBFrontend] (0)tune [64/48097]
[eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
[eDVBFrontend] prepare_sat System 1 Freq 10729000 Pol 1 SR 22000000 INV 2 FEC 2 orbpos 192 system 1 modulation 2 pilot 2, rolloff 0
[eDVBFrontend] tuning to 979 mhz
[eDVBChannel] OURSTATE: tuning
[eDVBFrontend] set static current limiting
[eDVBFrontend] set sequence pos 3
[eDVBFrontend] set sequence pos 4
[eDVBFrontend] setVoltage 1
[eDVBFrontend] sleep 200ms
[eDVBFrontend] invalidate current switch params
[eDVBFrontend] sendDiseqc: e00000(DiSEqC reset)
[eDVBFrontend] sleep 50ms
[eDVBFrontend] sendDiseqc: e00003(DiSEqC peripherial power on)
[eDVBFrontend] sleep 150ms
[eDVBFrontend] sendDiseqc: e01039f2(?)
[eDVBFrontend] sleep 50ms
[eDVBFrontend] set sequence pos 3
[eDVBFrontend] set sequence pos 3
[eDVBFrontend] update current switch params
[eDVBFrontend] startTuneTimeout 5000
[eDVBFrontend] setFrontend 1
[eDVBFrontend] setting frontend 0
[eDVBFrontend] (0)fe event: status 0, inversion off, m_tuning 1
[eDVBFrontend] sleep 500ms
[eDVBFrontend] (0)fe event: status 7, inversion off, m_tuning 2
[eDVBFrontend] (0)fe event: status 1f, inversion off, m_tuning 3
[eDVBChannel] OURSTATE: ok
[eDVBFrontend] set dynamic current limiting

Then changing to input 2:

action -> SetupActions right
unknown action SetupActions/right! typo in keymap?
action -> SetupActions right
[TuneTest] tuning to transponder with data (11459, 6666, 1, 5, 2, 235, 0, 1, 0, 2)
[eDVBFrontend] (0)tune
[eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
[eDVBFrontend] prepare_sat System 0 Freq 11459000 Pol 1 SR 6666000 INV 2 FEC 5 orbpos 235 system 0 modulation 1 pilot 2, rolloff 0
[eDVBFrontend] tuning to 1709 mhz
[eDVBChannel] OURSTATE: tuning
[eDVBFrontend] set static current limiting
[eDVBFrontend] set sequence pos 3
[eDVBFrontend] set sequence pos 7
[eDVBFrontend] invalidate current switch params
[eDVBFrontend] sendDiseqc: e01039f1(?)
[eDVBFrontend] sleep 50ms
[eDVBFrontend] set sequence pos 3
[eDVBFrontend] set sequence pos 3
[eDVBFrontend] update current switch params
[eDVBFrontend] startTuneTimeout 20000
[eDVBFrontend] setFrontend 1
[eDVBFrontend] setting frontend 0
[eDVBFrontend] (0)fe event: status 0, inversion off, m_tuning 1
[eDVBFrontend] sleep 500ms
[eDVBFrontend] (0)fe event: status 7, inversion off, m_tuning 2
[eDVBFrontend] set dynamic current limiting

TheTroll

Post by TheTroll »

I think that what you implemented actually is diseqc 1.0 + 1.1
In my case, its pure diseqc 1.1 with 1->8 commands ...

I hope you can sort something out :)

Thx

catalinii
Posts: 0
Joined: Wed Nov 18, 2015 5:41 am

Post by catalinii »

Hi,

I forgot that src gets decremented so you can try src=5

I looked previously to tvheadend and the sources above and it is all about uncommitted and committed.

As I said
(src-1) / 4 --> uncommitted index
(src -1) % 4 --> committed index

Thanks

TheTroll

Post by TheTroll »

Yes I tried this.
i changed my diseqc working mode to 1.0+1.1 but same issue.

BTw are you sure of your uncommited command:
- is the pol and hi/low really necessary?
- my diseqc doc says that it should be set to even value for 1-4 and odd value for 5-8, ( with commited value A B C D)

TheTroll

Post by TheTroll »

By the way, i can code and compile for my vu+, so if you have some debugging ideas, please let
me know!
Maybe its the a diseqc problem after all.. maybe a tuning issue.

Aso the tone burst should be configuration enalbe/disable i think

thx!!

TheTroll

Post by TheTroll »

Hi,

after more investigation it seems that the problem now comes from the pid filtering.
After we setup a pid filter (0 fo instance), no data comes back from dvr0 as expected.
Femon says that the tp is tuned though.
Is there a chance that the pid filtering has a problem on the vu+ solo2 with minisatip ?

What is very strange, is that it looks like that when using the frontend0, it is only possible to scan channels using demux1 and not demux0...
EDIT: this came from satipclient running on the box...

So it could be one of the problems

Thanks

catalinii
Posts: 0
Joined: Wed Nov 18, 2015 5:41 am

Post by catalinii »

Hi,

just to understand, what was the solution for the diseqc problem ?
Is there something that needs to be done additionally to resolve tuning problems ?

About demux, if I understand correctly, you have multiple (2?) demux devices?
If yes you can change in dvb_set_pid (dvc.c) and see if you get something out of dvr0.

Thanks

TheTroll

Post by TheTroll »

Hi,

to be honest it does not work very well..
I made it send only the 0x39 command and it helped.

About the demuxes and fe, its still unclear to me how it works, but using fe0 and dmx0 was ok.

Though, the pid filtering was very slow to start.

Post Reply