neumoDVB

[satesco]

As you know now, I come from a Windows environment, which forces me to learn and adapt to the trend imposed by Deeptho, which, as he rightly said,his app is a work in progress. What I recognize is that it is difficult for a Windows-ist to learn quickly and work easily on Linux.
If it wasn't for him helping me, maybe I would be in the same situation as you. But because he wants neumoDVB to do what on Windows you can't, say, with the 6903x card, it forces me to try to understand how our developer thinks about his application.
I think this is the reason for the difficulties that you or I have, or anyone who wants to use his application. Now after using neumoDVB for a long time, I can say that using it does not pose as many problems as we think, but bugs are the ones that create difficulties. And it all starts from those conditions that Deeptho talked about many times to eliminate the existing conflict between files left over from previous use and to update them with the updated ones. And this can only be detected by Linux insiders.
I know that what I am saying now is obvious and does not help the average user at all, but if one really wants to use neumoDVB, then one should take heed of what I am saying, and I am convinced that one will not be disappointed.
Of course what I am saying now is not for you, who doesn't help you to configure the application anyway, but for those who will try to install it but who don't have a deep knowledge of Linux.
Anyway Deeptho has raised the standard of dvb application use in Linux far above what has been achieved so far on this system.
And it's a good thing he's a trailblazer

 

[Llew]

Having got things reasonably back to normal after remembering to choose a satellite in the USALS column in the LNB list I can do a spectrum scan for, in this instance, 14w vertical with the TBS6903X. No problem locking individual TPs - here, 11634V.



The problem I have is with the adapter for the TBS6903X. the blindscan column is not ticked. It must have some bearing on the adapters not being found during the blindscans.



A blindscan of the previous spectrum is so rapid (4s), it barely stops at each TP to lock anything (the sole lock of 11634V is that which I had locked after the spectrum scan).
I don't know why it says 130 locked (?)


Another spectrum scan, this time H and V, shows the result of a blindscan. Nothing locked and an individual check of 11634 again yields no lock this time - the reason being no suitable adapter found.



A section of the log for the 59 TPs scanned. No adapter found for any.

[/CODE]

2022-08-16 14:36:40,160 DEBUG: [neumodvb ] SelectRecord D1A[0x000002]Ku 32767 14.0W: V 2022-08-16 14:36 neumolist.py:1200
2022-08-16 14:37:01,382 DEBUG: [neumodvb ] Blindscan start spectrum_dialog.py:253
2022-08-16 14:37:01,382 DEBUG: [neumodvb ] starting blindscan all spectrum_dialog.py:261
2022-08-16 14:37:01,383 DEBUG: [neumodvb ] scanning 11493.500H 1126.25kS/s; 59 tps left to scan spectrum_dialog.py:303
2022-08-16 14:37:01,384 DEBUG: [neumodvb ] set current_tp: spec=14.0W H dish 1 tp=11493.500H 1126.25kS/s neumoplot.py:925
2022-08-16 14:37:01,554 DEBUG: [neumodvb ] Tuning - BLIND scan: 14.0W 11493H pls_search_range=None positioner_dialog.py:346
2022-08-16 14:37:01,554 DEBUG: [receiver  RECEIVER-CMD SUB[-1] 14.0W 11493H] LNB D1A[0x000002]Ku 3276714.0W Ku 32767 cannot be used ceiver/devmanager.cc:1336
2022-08-16 14:37:01,554 ERROR: [receiver  RECEIVER-CMD SUB[-1] 14.0W 11493H] Subscribe 14.0W 11493H: no suitable adapter found receiver/receiver.cc:523
2022-08-16 14:37:01,555 DEBUG: [neumodvb ] Tuning failed Subscribe 14.0W 11493H: no suitable adapter found positioner_dialog.py:354
2022-08-16 14:37:01,558 DEBUG: [neumodvb ] Moving on after tuning failed spectrum_dialog.py:315
2022-08-16 14:37:01,558 DEBUG: [neumodvb ] TUNE DONE mux=14.0W 11493H ERROR spectrum_dialog.py:384
2

[...]

2022-08-16 14:37:21,280 DEBUG: [neumodvb ] scanning 12718.200V 13500.0kS/s; 1 tps left to scan spectrum_dialog.py:303
2022-08-16 14:37:21,280 DEBUG: [neumodvb ] set current_tp: spec=14.0W V dish 1 tp=12718.200V 13500.0kS/s neumoplot.py:925
2022-08-16 14:37:21,451 DEBUG: [neumodvb ] Tuning - BLIND scan: 14.0W 12718V pls_search_range=None positioner_dialog.py:346
2022-08-16 14:37:21,451 DEBUG: [receiver  RECEIVER-CMD SUB[-1] 14.0W 12718V] LNB D1A[0x000002]Ku 3276714.0W Ku 32767 cannot be used ceiver/devmanager.cc:1336
2022-08-16 14:37:21,451 ERROR: [receiver  RECEIVER-CMD SUB[-1] 14.0W 12718V] Subscribe 14.0W 12718V: no suitable adapter found receiver/receiver.cc:523
2022-08-16 14:37:21,451 DEBUG: [neumodvb ] Tuning failed Subscribe 14.0W 12718V: no suitable adapter found positioner_dialog.py:354
2022-08-16 14:37:21,454 DEBUG: [neumodvb ] Moving on after tuning failed spectrum_dialog.py:315
2022-08-16 14:37:21,455 DEBUG: [neumodvb ] TUNE DONE mux=14.0W 12718V ERROR spectrum_dialog.py:384
2022-08-16 14:37:21,627 DEBUG: [neumodvb ] scanning 12737.000V 13375.0kS/s; 0 tps left to scan spectrum_dialog.py:303
2

More work needs to be done to try and find the problem.

Deeptho,the full log file runs to thousands of lines. If it would help I can post it.

 

[deeptho]

Having got things reasonably back to normal after remembering to choose a satellite in the USALS column in the LNB list I can do a spectrum scan for, in this instance, 14w vertical with the TBS6903X. No problem locking individual TPs - here, 11634V.

View attachment 144577

The problem I have is with the adapter for the TBS6903X. the blindscan column is not ticked. It must have some bearing on the adapters not being found during the blindscans.

View attachment 144579

A blindscan of the previous spectrum is so rapid (4s), it barely stops at each TP to lock anything (the sole lock of 11634V is that which I had locked after the spectrum scan).
I don't know why it says 130 locked (?)

View attachment 144580
Another spectrum scan, this time H and V, shows the result of a blindscan. Nothing locked and an individual check of 11634 again yields no lock this time - the reason being no suitable adapter found.

View attachment 144581

A section of the log for the 59 TPs scanned. No adapter found for any.

[/CODE]

2022-08-16 14:36:40,160 DEBUG: [neumodvb ] SelectRecord D1A[0x000002]Ku 32767 14.0W: V 2022-08-16 14:36 neumolist.py:1200
2022-08-16 14:37:01,382 DEBUG: [neumodvb ] Blindscan start spectrum_dialog.py:253
2022-08-16 14:37:01,382 DEBUG: [neumodvb ] starting blindscan all spectrum_dialog.py:261
2022-08-16 14:37:01,383 DEBUG: [neumodvb ] scanning 11493.500H 1126.25kS/s; 59 tps left to scan spectrum_dialog.py:303
2022-08-16 14:37:01,384 DEBUG: [neumodvb ] set current_tp: spec=14.0W H dish 1 tp=11493.500H 1126.25kS/s neumoplot.py:925
2022-08-16 14:37:01,554 DEBUG: [neumodvb ] Tuning - BLIND scan: 14.0W 11493H pls_search_range=None positioner_dialog.py:346
2022-08-16 14:37:01,554 DEBUG: [receiver  RECEIVER-CMD SUB[-1] 14.0W 11493H] LNB D1A[0x000002]Ku 3276714.0W Ku 32767 cannot be used ceiver/devmanager.cc:1336
2022-08-16 14:37:01,554 ERROR: [receiver  RECEIVER-CMD SUB[-1] 14.0W 11493H] Subscribe 14.0W 11493H: no suitable adapter found receiver/receiver.cc:523
2022-08-16 14:37:01,555 DEBUG: [neumodvb ] Tuning failed Subscribe 14.0W 11493H: no suitable adapter found positioner_dialog.py:354
2022-08-16 14:37:01,558 DEBUG: [neumodvb ] Moving on after tuning failed spectrum_dialog.py:315
2022-08-16 14:37:01,558 DEBUG: [neumodvb ] TUNE DONE mux=14.0W 11493H ERROR spectrum_dialog.py:384
2

[...]

2022-08-16 14:37:21,280 DEBUG: [neumodvb ] scanning 12718.200V 13500.0kS/s; 1 tps left to scan spectrum_dialog.py:303
2022-08-16 14:37:21,280 DEBUG: [neumodvb ] set current_tp: spec=14.0W V dish 1 tp=12718.200V 13500.0kS/s neumoplot.py:925
2022-08-16 14:37:21,451 DEBUG: [neumodvb ] Tuning - BLIND scan: 14.0W 12718V pls_search_range=None positioner_dialog.py:346
2022-08-16 14:37:21,451 DEBUG: [receiver  RECEIVER-CMD SUB[-1] 14.0W 12718V] LNB D1A[0x000002]Ku 3276714.0W Ku 32767 cannot be used ceiver/devmanager.cc:1336
2022-08-16 14:37:21,451 ERROR: [receiver  RECEIVER-CMD SUB[-1] 14.0W 12718V] Subscribe 14.0W 12718V: no suitable adapter found receiver/receiver.cc:523
2022-08-16 14:37:21,451 DEBUG: [neumodvb ] Tuning failed Subscribe 14.0W 12718V: no suitable adapter found positioner_dialog.py:354
2022-08-16 14:37:21,454 DEBUG: [neumodvb ] Moving on after tuning failed spectrum_dialog.py:315
2022-08-16 14:37:21,455 DEBUG: [neumodvb ] TUNE DONE mux=14.0W 12718V ERROR spectrum_dialog.py:384
2022-08-16 14:37:21,627 DEBUG: [neumodvb ] scanning 12737.000V 13375.0kS/s; 0 tps left to scan spectrum_dialog.py:303
2

More work needs to be done to try and find the problem.

Deeptho,the full log file runs to thousands of lines. If it would help I can post it.

Llew,

you are running outdated drivers. That could be part of the problem. This card is fully supported and should cause few problems. What is
happening is that you are blindscanning, but as you noticed, the code thinks that blindscanning is not supported, so the only proble is that the code tries again instead of stopping after this error. This is because of some incompatibility between kernel and program.


Earlier you made a working kernel for satesco. Perhaps now is the time to get the latest kernel from satesco?
You need everyting in /lib/modules/working_kernel and a corresponding official kernel. I spent a lot of time on satesco's computer
fixing various bugs unrelated to neumo, but in the end it worked.

 

[Llew]

deeptho, I had no problem with neumoDVB before recent changes. Everything worked fine - a check back of my earlier posts show that.

So a change of kernel might be needed if any updates don't happen to be compatible with a kernel we might be using at any time?

 

[deeptho]

deeptho, I had no problem with neumoDVB before recent changes. Everything worked fine - a check back of my earlier posts show that.

So a change of kernel might be needed if any updates don't happen to be compatible with a kernel we might be using at any time?

Basically: yes. I try to avoid such incompatibilities, but from time to time they occur and it is too much work checking all combinations.
I still consider all the software beta quality.

In any case upgrading the kernel will give you all sorts of benefits, such as much faster spectrum scan.

 

[deeptho]

By the way: if you compiled the kernel successfully in the past and you did not delete the sources, upgrading should not be difficult:

cd ~/blindscan_kernel/media
git reset --hard
git pull
cd ../media_build
make -j `nproc`
sudo make install
sudo reboot

 

[Llew]

@deeptho

While I continue hunting for a suitable kernel/mediabuild combination to have blindscan working again with the TBS6903X, I am at present using my TBS 5927 in a Raspberry Pi.

Everything working well with various Ubuntu OS's (Mate, Mint etc), except for a problem with overscanning of the screen on the spectrum page. It means I can't access the spectrum scan button at the bottom of the page!
Can it be altered by the user, or is it defined in wxWidgets when you build the app (i.e., can't be changed for an individual installation)?

Also, when I go to choose a channel in the Service List,There's no channels. Perhaps this is because in this case the screen is overscanned too? Just a guess.

I've only seen these problems with neumoDVB on the RPi, but the section on overscanning in the RPi's config file doesn't change anything for me. I just wondered if anything can be changed in neumoDVB's configs.

 

[deeptho]

@deeptho

While I continue hunting for a suitable kernel/mediabuild combination to have blindscan working again with the TBS6903X, I am at present using my TBS 5927 in a Raspberry Pi.

LLew why don't you try the media_build on my githutb page. I updated it recently for people in your situation. It seems that it really is media_build that is broken from time to time. So the trick is to not
update it, unless your current version stops working. No updates means no new bugs.

My version is here:

GitHub - deeptho/media_build_old: media_build for compiling the neumoDVB media_tree on this site

media_build for compiling the neumoDVB media_tree on this site - deeptho/media_build_old

github.com

About raspberri pi: note that the software may have problems on a 32bit os. So a 64bit rpi version (which is rare) is best. a 32bit could be made to work, but may require software changes.

Everything working well with various Ubuntu OS's (Mate, Mint etc), except for a problem with overscanning of the screen on the spectrum page. It means I can't access the spectrum scan button at the bottom of the page!
Can it be altered by the user, or is it defined in wxWidgets when you build the app (i.e., can't be changed for an individual installation)?

What is your screen resolution? The software assumes a big screen screen. Sizes can be adjusted by editing the code. Not an end-user solution, but not very difficult either

Also, when I go to choose a channel in the Service List,There's no channels. Perhaps this is because in this case the screen is overscanned too? Just a guess.

I've only seen these problems with neumoDVB on the RPi, but the section on overscanning in the RPi's config file doesn't change anything for me. I just wondered if anything can be changed in neumoDVB's configs.

Not sure what you are talking about. An empty service list could mean things are not working at all (no services found, or database code does not work on 32 bit os), or ...

View attachment 144709

 

[satesco]

...


You can enter LOF values (one for a low band and one for a high band; for KA use only the low band) in
the fields lof_low and lof_high. You als need to set freq_low to the bottom most frequency that can be tuned
and freq_mid to the top most. Totally untested. I can add KA band definitions if you send me the parameters
(upper and lowe frequency, LOF and if the spectrum is inverted)

Tried lnb Ka 21.4 GHz ~ 22.0 GHz with neumoDVB. I guess I didn't choose well when configuring the lnb, probably because I didn't see any options for Ka, only Unknown, Ku, C, WDB, and WDBUK. And yet I chose the local oscillator for WDB, of course to no avail.
What are the last two?

 

[Llew]

An empty service list could mean things are not working at all (no services found, or database code does not work on 32 bit os)

Sorry, should have been clearer. I meant there were no channels showing in the View -> Channels list.

The RPi image is aarch64.

No problem with services -



Resolution on my monitor is fine (1600x800).All neumoDVB lists resolve perfectly OK. It's just the spectrum screen that's causing the problem.

 

[Llew]

Tried lnb Ka 21.4 GHz ~ 22.0 GHz with neumoDVB. I guess I didn't choose well when configuring the lnb, probably because I didn't see any options for Ka, only Unknown, Ku, C, WDB, and WDBUK. And yet I chose the local oscillator for WDB, of course to no avail.
What are the last two?

I tried those LNB options on the lowest LOF 17.250 GHz and the Astra 1L frequencies (NewsNet) but neumoDVB promptly shut down every time I tried them

satesco, out of interest, are you still using the 5.13.0-39 kernel? It's not worked for me during my attempts recently to get my TBS6903X to blindscan in neumoDVB.

 

[satesco]

-What type of lnb did you choose when you set the local oscillator?
-Yes, with all DVB cards installed on my pc I work fine with 5.13.0-39 kernel. So far I have had no problems with blindscan with 6903X, and I can say that it does fast. I would say it works the best of all cards. And no wonder we think that Deeptho,(maybe I am wrong), created neumoDVB because of this card(?).

 

[Llew]

-What type of lnb did you choose when you set the local oscillator?

The Hughes, on the 1M Triax. I should have said the LO is 17350 GHz.

Yes, with all DVB cards installed on my pc I work fine with 5.13.0-39 kernel.

OK, I'll try again with that kernel, and use deeptho's media_build, although I'm sure I've used that already.

I just wanted to confirm that you are still on that kernel. Thanks.

 

[satesco]

Not LO I wanted to know, but what type of lnb did you choose in neumoDVB (LNB type column): Unknown, Ku, C, WDB, or WDBUK?
I'm not sure, but I think the application crashed because of the chosen lnb type and LO setting.
Thanks

 

[Llew]

I tried all four with that LOF, each on the two Astra 1L data frequencies (18561 and 18567, as they are always present and strong here).

Each time I tried, neumoDVB closed down.

 

[deeptho]

Tried lnb Ka 21.4 GHz ~ 22.0 GHz with neumoDVB. I guess I didn't choose well when configuring the lnb, probably because I didn't see any options for Ka, only Unknown, Ku, C, WDB, and WDBUK. And yet I chose the local oscillator for WDB, of course to no avail.
What are the last two?

There is no entry for Ka lnb yet, but you can (probably) use a Ku LNB entry instead and change
all the frequencies (2 oscillator frequencies and low/mid/high frequencies). I think mid and high should
be the same (only 1 band, not 2?) and the second oscillator frequency probably does not matter.

This is unless any of the Ka LNBS use an oscillator frequency above the band. In that case it
would be better to select a C-band lnb to fake a Kaband one.


If you send me the list of those frequencies and the names for KaA, kaB... then I can add the lnb types

The wideband lnbs are the ones used by skyuk. They require tuner support (and I have no card supporting them)

 

[deeptho]

I tried those LNB options on the lowest LOF 17.250 GHz and the Astra 1L frequencies (NewsNet) but neumoDVB promptly shut down every time I tried them

You could send me the neumo.log file?

satesco, out of interest, are you still using the 5.13.0-39 kernel? It's not worked for me during my attempts recently to get my TBS6903X to blindscan in neumoDVB.

 

[satesco]

At the moment I only use a KaD. I hope to "trick" C-band or Ku lnb for Ka, as you recommend.
At 7.0E, I lock a few active frequencies with Crazyscan and IQmonitor.
Here they are in the screenshot:

 

[Llew]

LLew why don't you try the media_build on my githutb page. I updated it recently for people in your situation. It seems that it really is media_build that is broken from time to time. So the trick is to not
update it, unless your current version stops working. No updates means no new bugs.

My version is here:

GitHub - deeptho/media_build_old: media_build for compiling the neumoDVB media_tree on this site

media_build for compiling the neumoDVB media_tree on this site - deeptho/media_build_old

github.com

That's the one one I wanted deeptho. Thanks. Blindscan is now ticked in the frontend list.

However, that list arrangement is unfamiliar to me - there's two mac addresses to each TBS tuner. If I choose the TBS6903X that shows as available to me, and go to the LNB in the list, its availability is unticked, hence I cannot tune anything in the spectrum list.

I can show the logfile, but I was hoping you might give me a clue as to where I might be missing something obvious before I do? As I say, I'm not familiar the layout of the adapters in the frontend list.

(I've highlighted adapter2, but obviously I chose A2 TBS 6903X when I went to the LNB list).

 

[deeptho]

That's the one one I wanted deeptho. Thanks. Blindscan is now ticked in the frontend list.

However, that list arrangement is unfamiliar to me - there's two mac addresses to each TBS tuner. If I choose the TBS6903X that shows as available to me, and go to the LNB in the list, its availability is unticked, hence I cannot tune anything in the spectrum list.

I can show the logfile, but I was hoping you might give me a clue as to where I might be missing something obvious before I do? As I say, I'm not familiar the layout of the adapters in the frontend list.

(I've highlighted adapter2, but obviously I chose A2 TBS 6903X when I went to the LNB list).

View attachment 144729

View attachment 144728