neumoDVB

[satesco]

I managed thanks to Deeptho (my gratitude) to activate terrestrial reception with neumoDVB. I should point out that the 6590 card test was done on a DVB-T2 frequency and 8 steps.
I can now say that all 3 standards (satellite, cable, terrestrial) work well with neumoDVB, and Llew's Ka-band tests complete and underline once again that Deeptho's neumoDVB project is a great success for those-in special Dxers- who want to use DVB cards under Linux.
Being a work in progress project, I expect it to bring new features and improvements that will be on the same level as DVB applications under Windows.
And when you think that it is done by one man and not by a team,all I can say is, Congratulations and Hats off

Many consider publicly expressing admiration for someone a sign of, at best, childishness.Yes, I prefer to be seen that way when I think of the creative minds we have among us. I think of CrazyCat and Deeptho. Two brilliant minds that make our lives and passions more beautiful. They have proven that they have a creative intelligence in this field of DVB applications, and if I add that all their creation is offered for free to anyone who wants to use them, my gratitude is immense, without words.
I wish both of them good health

 

[Llew]

I wish both of them good health

I echo that. At the very least, neumoDVB is keeping my brain active these days in my senescence

I'm rebuilding neumoDVB in Ubuntu again because of problems with my existing install. Amongst other things, I never got T/T2 to work in it. I couldn't input anything into the list.

Llew's Ka-band tests

You can choose a KA LOF in the LNB list?

 

[satesco]

I echo that. At the very least, neumoDVB is keeping my brain active these days in my senescence

I'm rebuilding neumoDVB in Ubuntu again because of problems with my existing install. Amongst other things, I never got T/T2 to work in it. I couldn't input anything into the list.


You can choose a KA LOF in the LNB list?

Indeed neumoDVB keeps us in a mental grip as long as we accept Deeptho's challenge, which forces us to accept his challenge. Because, as we see, new things appear along the way as long as the project is in the works. And we see the changes it brings, forcing us to "learn" all the time, and for us, coming from the Windows environment, it is a more considerable intellectual effort. And I think I'm in the same boat as you
I have not yet tested the Ka-band with neumoDVB because I have not installed the Ka lnb. I still don't know if I can choose the Ka-band in the app. I will look into this when I install the lnb. Soon I will do this test and then I will post the results.
Regards

 

[deeptho]

I echo that. At the very least, neumoDVB is keeping my brain active these days in my senescence

I'm rebuilding neumoDVB in Ubuntu again because of problems with my existing install. Amongst other things, I never got T/T2 to work in it. I couldn't input anything into the list.

Well Llew, ... report the error in detail. It could depend on the card as well and/or on the need to provide voltage for an antenna
amplifier (not supported yet)

You can choose a KA LOF in the LNB list?

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)

 

[Llew]

DVB-T muxes fine now deeptho with a fresh install of Ubuntu 20.04.4. Same kernel 5.9.0-rc7-tbs+

To do - DVB-S muxes.

Thanks for your guidance

 

[satesco]

I'm happy for you, Llew, that you managed to fix the terrestrial reception
But I'm also glad you finally decided to use neumoDVB on Ubuntu. Now I'm not the only user who has the app on Ubuntu. It's one more reason, although he doesn't need much reason, for Deeptho to take us, ubuntu-tisti, into account when updating his drivers and application. Although this involves him more because, as he confessed, it's a system he doesn't have a friendly relationship with for his application.
Regards

 

[Llew]

On to DVB-S configuration. Here lies a similar problem that I had in my previous Ubuntu installation. The adapter screen was changed in the frontend list a week or two ago, so here's my adapter choice in the new list -


- and then, as usual, adding an entry in the LNB list. All this is basic stuff of course that I've been doing many times before.


Then it's to the DBS mux llst to add my chosen sat and frequency -


Nothing to see. Nothing scanned in.

Back to check the LNB entry. Just as I expected. Zilch. Nada.





I can only think that the configurated LNB has not been saved. Where can I find the saved LNB? which file?

Here's my log for this session. What should I be looking for?

2022-08-14 13:40:41,171 DEBUG: [receiver ] new frontend adap=0 fe=0 wd=9
 ceiver/devmanager.cc:436
2022-08-14 13:40:41,172 DEBUG: [tuner ] Cleaned 1 muxes with PENDING/ACTIVE status b/chdb/chdb_extra.cc:1867
2022-08-14 13:40:41,172 DEBUG: [tuner ] Cleaned 0 muxes with PENDING/ACTIVE status b/chdb/chdb_extra.cc:1867
2022-08-14 13:40:41,172 DEBUG: [tuner ] Cleaned 0 muxes with PENDING/ACTIVE status b/chdb/chdb_extra.cc:1867
2022-08-14 13:40:41,187 DEBUG: [neumodvb ] ROW HEIGHT: 30 live.py:1327
2022-08-14 13:40:41,190 DEBUG: [tuner ] Cleaned epg: 18 milliseconds epgdb/epgdb_extra.cc:75
2022-08-14 13:40:41,236 DEBUG: [neumodvb ] CALL SetFocus live.py:1339
2022-08-14 13:40:41,582 DEBUG: [neumodvb ] Added glcanvas=<wx._glcanvas.GLCanvas object at 0x7f9e744a2b80> mpv_player=<pyneumompv.MpvPlayer object at 0x7f9ee8245130> focus_idx=0 l=1/1 live.py:1046
2022-08-14 13:40:41,588 DEBUG: [neumodvb ] CALL SetFocus live.py:2238
2022-08-14 13:40:41,589 DEBUG: [neumodvb ] CALL SetFocus live.py:303
2022-08-14 13:40:41,615 DEBUG: [neumodvb ] live selected service/chgm from [00000]  DVB-T 522MHz - BBC NEWS to [00000]  DVB-T 522MHz - BBC NEWS livescreen.py:74
2022-08-14 13:40:41,615 DEBUG: [neumodvb ] SET FOCUS ON row=0 <neumodvb.live.ServiceChannelPanel object at 0x7f9e74d2bdc0> live.py:307
2022-08-14 13:40:41,615 DEBUG: [neumodvb ] CREATE 0x18a4800 c/viewer/neumompv.cc:151
2022-08-14 13:40:41,615 DEBUG: [neumodvb ] Creating mpv 0x193a000 c/viewer/neumompv.cc:426
2022-08-14 13:40:50,674 DEBUG: [neumodvb ] menu command CmdLnbList neumomenu.py:242
2022-08-14 13:40:50,674 DEBUG: [neumodvb ] FIND menu command key=LnbList accel=Ctrl+Shift+L neumomenu.py:205
2022-08-14 13:40:50,676 DEBUG: [neumodvb ] run_menu_command CmdLnbList neumomenu.py:250
2022-08-14 13:40:50,676 DEBUG: [neumodvb ] CmdLnbList neumodvb.py:423
2022-08-14 13:40:50,681 DEBUG: [neumodvb ] OnCreateWindow rec_to_select=None neumolist.py:1192
2022-08-14 13:40:50,684 DEBUG: [neumodvb ] SHOW/HIDE <neumodvb.lnblist.LnbGrid object at 0x7f9e74f53670> True neumolist.py:923
2022-08-14 13:40:50,685 DEBUG: [neumodvb ] ACCEL OFF neumodvb.py:156
2022-08-14 13:40:55,652 DEBUG: [neumodvb ] menu command CmdDvbsMuxList neumomenu.py:242
2022-08-14 13:40:55,653 DEBUG: [neumodvb ] FIND menu command key=DvbsMuxList accel=Ctrl+Shift+M neumomenu.py:205
2022-08-14 13:40:55,654 DEBUG: [neumodvb ] run_menu_command CmdDvbsMuxList neumomenu.py:250
2022-08-14 13:40:55,654 DEBUG: [neumodvb ] CmdDvbsMuxList neumodvb.py:411
2022-08-14 13:40:55,681 DEBUG: [neumodvb ] CurrentSatAndMux None None dvbs_muxlist.py:204
2022-08-14 13:40:55,681 DEBUG: [neumodvb ] OnCreateWindow rec_to_select=None neumolist.py:1192
2022-08-14 13:40:55,685 DEBUG: [neumodvb ] SelectRecord 14.0W 11634V neumolist.py:1199
2022-08-14 13:40:55,686 DEBUG: [neumodvb ] SHOW/HIDE <neumodvb.dvbs_muxlist.DvbsMuxGrid object at 0x7f9e74f42790> True neumolist.py:923
2022-08-14 13:40:55,686 DEBUG: [neumodvb ] SHOW/HIDE <neumodvb.lnblist.LnbGrid object at 0x7f9e74f53670> False neumolist.py:923
2022-08-14 13:40:55,686 DEBUG: [neumodvb ] ACCEL OFF neumodvb.py:156

 

[deeptho]

Llew,
I cannot see an adapter name in the second screenshot. So we may be running older software. Again, version info is missing in your log file.
There is also no evidence of any tuning in your log file.

So in conclusion: you appear to removed all the interesting parts in the log file before posting. Why not send the complete log? \
Do any errors appear on the console?

 

[Llew]

I cannot see an adapter name in the second screenshot

That's because it disappears as soon as I go away from the LNB list. This is when I actually add the adaptor.

Ignore dish as 0. I just posted an example of how I add the adapter before it vanishes into the ether.



Sorry the log file was truncated. I'll post a full one (probably tomorrow now).

 

[Llew]

From log: ERROR: [receiver RECEIVER-CMD SCAN[0] 1 muxes] Subscribe 14.0W 11634V: no suitable adapter found receiver/receiver.cc:523

My adapter and LNB list problems began after the upgrade (I'm currently up to date).

From the github neumodvb/src/stackstring -

"Major database change: identify adapters by their mac address and no longer
by adapter number. Limitations in the current database upgrade code result
in the loss of all defined lnbs. Also, old spectra will not show the adapter
on which they were captured."

So perhaps my upgrading hasn't removed exactly that which is causing my problem, namely loss of my LNB lists?

Probably I hadn't been aware that the previous upgrade was flawed, and perhaps it's causing my present woes.

As an aside deeptho, I commend you for authoring a great project, but I always seem several steps behind your work in progress. Maybe I need to give my brain a rest from it for a while

 

[deeptho]

That's because it disappears as soon as I go away from the LNB list. This is when I actually add the adaptor.

Ignore dish as 0. I just posted an example of how I add the adapter before it vanishes into the ether.

View attachment 144544

Sorry the log file was truncated. I'll post a full one (probably tomorrow now).

Press enter first and/or click into a different cell to finalize the edit. Or immediately add a second adapter.

 

[deeptho]

From log: ERROR: [receiver RECEIVER-CMD SCAN[0] 1 muxes] Subscribe 14.0W 11634V: no suitable adapter found receiver/receiver.cc:523

My adapter and LNB list problems began after the upgrade (I'm currently up to date).

From the github neumodvb/src/stackstring -

"Major database change: identify adapters by their mac address and no longer
by adapter number. Limitations in the current database upgrade code result
in the loss of all defined lnbs. Also, old spectra will not show the adapter
on which they were captured."

So perhaps my upgrading hasn't removed exactly that which is causing my problem, namely loss of my LNB lists?

Probably I hadn't been aware that the previous upgrade was flawed, and perhaps it's causing my present woes.

As an aside deeptho, I commend you for authoring a great project, but I always seem several steps behind your work in progress. Maybe I need to give my brain a rest from it for a while

Llew,

I think what happened is that you did not really add an LNB. For instance, you have not entered usals_pos, which is one of the ways of
adding a network. The LNB can only be used with a defined network. The documentation is not 100% uptodate, but on this point it should
be close enough...

 

[Llew]

you have not entered usals_pos,

deeptho, I don't use usals. I use diseqc 1.1, choosing the first port 0. for dish1. Isn't that enough to define the network?

As to adapters, choosing anything other than adapter 0 (of my four - two tuners of TBS6903, two tuners of TBS6903X) fails to even register in the LNB list - nothing appears in the adap column.

 

[Llew]

deeptho, I don't use usals. I use diseqc 1.1, choosing the first port 0. for dish1. Isn't that enough to define the network?

As to adapters, choosing anything other than adapter 0 (of my four - two tuners of TBS6903, two tuners of TBS6903X) fails to even register in the LNB list - nothing appears in the adap column.

OK, let's try adapter 2 with Dish2, using port 1 of diseqc 1.1(of course, I chose adapter 2, which is tuner 1 of my TBS6903x in the frontend list).

I chose adapter2 in the adapter column, which immediately disappears, leaving just the MAC address.

adap still showing 0.

Result -

 

[deeptho]

deeptho, I don't use usals. I use diseqc 1.1, choosing the first port 0. for dish1. Isn't that enough to define the network?

As to adapters, choosing anything other than adapter 0 (of my four - two tuners of TBS6903, two tuners of TBS6903X) fails to even register in the LNB list - nothing appears in the adap column.

Doesn't matter. The LNB needs to know where it is pointing at.

 

[Llew]

Doesn't matter. The LNB needs to know where it is pointing at.

May have cross posted. Check my post above yours.

 

[deeptho]

May have cross posted. Check my post above yours.

You still need to edit the usals-value. It is not nice that the adapter name disappears (will be fixed), but it is remembered once
you complete the missing steps: entering usals-value (e.g., 28.2E) and moving to another cell.

 

[deeptho]

LLew,
I also fixed the "adaptername does not show" bug in the newest version, which has just been uploaded

 

[satesco]

I don't know if it will help you, but I made a howto with card and lnb setting for Turksat 3A 42.0E. I chose to scan 5 muxes with low symbol rate of 400 Ks/s. Fortunately neumoDVB managed to find them with blindscan, and when it didn't find them, I managed manually to scan and locked them.
Forgive my clumsiness in preparing this video. I still need practice to work quickly with the application.
As you can see from the video, I scanned with the tbs6903x card. It is remarkable that it managed to locks those low symbol rate.
I hope it helps at least as a guide

https://youtu.be/zpdGyp4bURA

 

[Llew]

I don't know if it will help you, but I made a howto with card and lnb setting for Turksat 3A 42.0E. I chose to scan 5 muxes with low symbol rate of 400 Ks/s. Fortunately neumoDVB managed to find them with blindscan, and when it didn't find them, I managed manually to scan and locked them.
Forgive my clumsiness in preparing this video. I still need practice to work quickly with the application.
As you can see from the video, I scanned with the tbs6903x card. It is remarkable that it managed to locks those low symbol rate.
I hope it helps at least as a guide

https://youtu.be/zpdGyp4bURA

satesco, that's an excellent presentation showing neumodvb's verstatility in locking those low SRs. The video will almost certainly be helpful for anyone intending to try the project.

It's a couple of weeks since I've done any serious spectrum scanning with my cards, as I'm having a problem or two with the adapters in my neumodvb setup. When I've sorted things out, I'll try those myself - if I can see them with my dishes.