So the error came when i use or via the core.py or with this simple
row when you call the function of the frontend.pxy:
set_frontend(params)
frequency = 11977
feparams = {
"inversion" : dvb3.frontend.INVERSION_AUTO,
"symbol_rate" : 27500,
"fec_inner" : dvb3.frontend.FEC_AUTO,
}
scheda
loocking the frontend.pyx hoe i can call the function __dealloc__ from
class Frontend:
def __dealloc__(self):
close(self.fd)
Luca
On 23 Nov, 15:29, luca72 wrote:
> test reply
>
> On 23 Nov, 14:37, Michael Sparks wrote:
>
> > Luca,
>
> > On Friday 20 November 2009 09:36:20 Michael
test reply
On 23 Nov, 14:37, Michael Sparks wrote:
> Luca,
>
> On Friday 20 November 2009 09:36:20 Michael Sparks wrote:
>
> > until I see the full file you're *currently*
> > editting and the *current* sourcefile, I have no chance of reconstructing
> > exactly what's happening.
>
> Third time lu
Luca,
On Friday 20 November 2009 09:36:20 Michael Sparks wrote:
> until I see the full file you're *currently*
> editting and the *current* sourcefile, I have no chance of reconstructing
> exactly what's happening.
Third time lucky, hopefully.
Please can you post:
* The code that you have t
I'm not sure I'm afraid - that code is old, so might no longer be fully
compatible with the dvb3 bindings that kamaelia now uses.
My suggestion would be to take the source code for DVB_Multiplex:
http://code.google.com/p/kamaelia/source/browse/trunk/Code/Python/Kamaelia/Kamaelia.Device/DVB/Core
Hello
I try to post in the ng but i get error , i know something.
Luca
>
Messaggio originale
>Da: spark...@gmail.com
>Data: 20/11/2009 10.36
>A:
>Cc: "luca72"
>Ogg: Re:
[kamaelia-list] Re: Tuning
>
>Hi Luca,
>
>On Friday 20 November 2009 07:39:
Maybe better to look at a layer closer to the python. See:
http://code.google.com/p/kamaelia/source/browse/trunk/Code/Python/Bindings/python-dvb3/dvb3/frontend.pyx#126
Teh QPSKParameters class is filled from the 'frequency' parameter and the
'feparams' you provide. You therefore need to s
Thanks
I try to explain what i need to do using python.
The base data are:
DVB-S
Frequency 11977
pid 1296 Sky Italy ECM pid
Polarization Horizontal
symbol rate 27500
If i understand right at first i have to setup the front end is it
correct?
Locking dvb-3 api for dvb-s frontend i have the follow
Hi Luca,
On Friday 20 November 2009 07:39:12 luca72 wrote:
> now i can't test it
>
> Many thanks i will inform you.
> PS:I think that i'm your nightmare (sorry)
No, not nightmare. Someone testing current code in a scenario we haven't tried
since that code was written is actually a dream scenario
> I think you are try-ing to record the ECM data stream from Sky Italy
> on the Hotbird on 13E correct?
Yes i need to do it
So tonight i try to use szap, or maybe i try to find where caffeine
store it's channel.conf file i and try to get some data fro it.
I have no deseq installed.
so maybe the d
Luca,
I think you are try-ing to record the ECM data stream from Sky Italy
on the Hotbird on 13E correct?
According the the data that I can find you need to supply a FEC of 3/4
so you are missing some frontend parameters.
The frequency should be 11977 Mhz so that looks correct (because
core.py in
> The file frontend.pyx could not be opened.
> The debugged program raised the exception unhandled IOError
> "(22, 'Invalid argument')"
> File: frontend.pyx, Line: 364
I think these two errors are becuase the wrong set of parameters are being
specified. See my email from about half an hour ago.
Thanks
I have no more code this is just the beginning:
I confirm 27500 is the simbol rate, Frequency is 11977, ECM pid
1296 ,Horizontal means the horizontal polarization,
Now i get no parameters error but leke before i get :
The file frontend.pyx could not be opened.
and after i get :
The debug
On Thursday 19 November 2009 21:41:15 luca72 wrote:
> i make a little change but i get another error:
Could you post the whole file into a pastebin ?
eg http://pastebin.com/
Along with the full trace back?
One thing that does look wrong to me is given this:
* Frequency 11977
* pid 1296
Just found this link:
http://www.bbc.co.uk/reception/info/sat_frequencies.shtml
Confirms that the FEC value should be FEC_5_6 - leaving only the three
inversion options to try.
Also noticed that the symbol rate that page specifies is different to the
one you're using: 22 Msymbol/s, not 27.5 Ksym
I'm not hugely familiar with DVB-S so anything I'm about to suggest might
be wrong(!) ...
If I remember right, DVB-S is QPSK modulation based.
Looking at:
http://code.google.com/p/kamaelia/source/browse/trunk/Code/Python/Bindings/python-dvb3/dvb3/cfrontend.pxd#169
...I reckon the feparams you n
i make a little change but i get another error:
from Kamaelia.Device.DVB.Core import DVB_Multiplex
from Kamaelia.Chassis.Pipeline import Pipeline
from Kamaelia.File.Writing import SimpleFileWriter
import dvb3
freq = 119.77
feparams = {"symbol_rate" : 27500,
}
and i get the following
Thanks Michael for your help, but at my first test i get problems
usual:
so i explain my test
i have this data i have to log ECM and store it in file:
Frequency 11977
pid 1296
Horizzontal
27500
So i start just to write :
from Kamaelia.Device.DVB.Core import DVB_Multiplex
from Kamaelia.Chassi
On Thursday 19 November 2009 07:25:56 luca72 wrote:
> Thanks for the linkd page, in the example there are dvb-t example but
> i con also use for dvb-s making some change is it correct?
You'll be pleased to hear that the dvb bindings were first used with a DVB-S
card. Most current testing has been
Thanks for the linkd page, in the example there are dvb-t example but
i con also use for dvb-s making some change is it correct?
Thanks
Luca
On 18 Nov, 23:58, Michael Sparks wrote:
> On Wednesday 18 November 2009 20:31:34 luca72 wrote:
>
> > Where i can find a tuning example
>
> The component
20 matches
Mail list logo
