neumoDVB

[moonbase]

11200 might be a beacon. What is the promax scan resolution?

It depends on the model of the Promax.
The Ranger Neo + model I have can scan down to 10MHz per full screen display. each square of the grid representing 1MHz

 

[Llew]

11200 might be a beacon. What is the promax scan resolution?

11.200.80 is a beacon. Also 11699.20, 12500V and 20401H.

​

 

[Llew]

It depends on the model of the Promax.
The Ranger Neo + model I have can scan down to 10MHz per full screen display. each square of the grid representing 1MHz

My Promax Ranger HD can do 20MHz. 10MHz would be nice, I suppose there may be rare occasions I might need to measure bandwidths down to that level.

 

[tom55]

A resolution would be the distance between two points in graph. The specifications on their website mention values 100, 200khz, 1mhz etc.
Not sure those spikes were more narrow than that so they'd be visible on promax...

 

[Llew]

Just checked my Promax. It does go down to 10 MHz. I'm sure it used to be 20 MHz - maybe it changed with a software update, if that was possible.

 

[tom55]

I made a scan with premium PLL directly attached to card. The spikes are quite visible

 

[Llew]

A resolution would be the distance between two points in graph. The specifications on their website mention values 100, 200khz, 1mhz etc.
Not sure those spikes were more narrow than that so they'd be visible on promax...

The Promax resolves the spikes, for instance the one at 11110 MHz at 10 MHz resolution. I make that at ~750 KHz B/W.

 

[tom55]

From that screenshot it can be seen promax resolution is about 10khz or slightly more.
So this was a signal generated on purpose to see if promax captures it, or it's interference generated by LNB?

 

[satesco]

I updated neumoDVB, so both muxes 11221 H and 11261 H did not crash.

 

[deeptho]

I'm sure I'm up-to-date on the drivers, but I'll check anyway.

Your neumoDVB is obviously far too sensitive for my old equipment ( but in a good way - it keeps us on our toes )

I am just curious what the problem might be. You can check the installed driver version with
cat /sys/module/dvb_core/info/version
type = "neumo";
version = "1.5";

and in more detail with
git branch -v|grep deepth
(in .../media/)

 

[Llew]

I am just curious what the problem might be. You can check the installed driver version with
cat /sys/module/dvb_core/info/version
type = "neumo";
version = "1.5";

and in more detail with
git branch -v|grep deepth
(in .../media/)

It is version 1.5 deeptho.

 

[deeptho]

It is version 1.5 deeptho.

That should be the right one.

 

[sat-tv-fan]

Just recently found out about this software. Is it likely to work fairly OK on a Pi 4 8gb ?

 

[deeptho]

Just recently found out about this software. Is it likely to work fairly OK on a Pi 4 8gb ?

Until somebody tries, we will not know, but there is no reason that it wouldn't.
Note that it will require a 64-bit version of the OS.

 

[Llew]

Just recently found out about this software. Is it likely to work fairly OK on a Pi 4 8gb ?

Works OK (mostly) for me with an arm64 Ubuntu on the SD card in an RPi 4 with 8Gb. That's with the TBS5957 for S/S2 and a T/T2 USB stick.

Channels and muxes found, installed and video displayed. A problem for me at the moment is to get spectrum scan working with the 5927 without it shutting down neumodvb occasionally.

 

[deeptho]

Works OK (mostly) for me with an arm64 Ubuntu on the SD card in an RPi 4 with 8Gb. That's with the TBS5957 for S/S2 and a T/T2 USB stick.

Channels and muxes found, installed and video displayed. A problem for me at the moment is to get spectrum scan working with the 5927 without it shutting down neumodvb occasionally.

Llew,

so what happens then? What exactly is "shutting down" and what are the error messages in /tmp/neumo.log and/or on the console?

 

[Llew]

Llew,

so what happens then? What exactly is "shutting down" and what are the error messages in /tmp/neumo.log and/or on the console?

I'll check that out tomorrow to find what's happening. If I can find the SD card, I haven't used it for some time.

 

[tom55]

Well: if you modified the driver code, then the problem might be in those modifications?

I did set resolution to 187,5khz instead of 187, and the samples in .dat are increased by 187, then next 188, 187, 188 and so on. Does this need driver conversion to hz in order to work properly? I suspect it might be a reason, cannot be sure.
There are times when the scan finish just fine, and times when it constantly crash at the same point

 

[deeptho]

I did set resolution to 187,5khz instead of 187, and the samples in .dat are increased by 187, then next 188, 187, 188 and so on. Does this need driver conversion to hz in order to work properly? I suspect it might be a reason, cannot be sure.
There are times when the scan finish just fine, and times when it constantly crash at the same point

That could be the problem. I do not think this was ever tested (and it may not be possible to change)

 

[tom55]

I have 2 cards, one attached to H and another to V port of LNB. While at 7e, V scan usually crashes, while H scan completes. Just moving dish to another position is enough for both cards to complete scan without problem.
For that reason i was convinced the problem is due to RF level parsing, just few days ago accidentaly noticed in spectrum window x is actually frequency related.
Is there a way to obtain samples from memory somehow, because during the window when crash happens only zeroes are written into .dat file?