neumoDVB

[deeptho]

I agree, I first noticed the time problem when hitting a data TP in 30W earlier on. It would certainly speed things up to be able to move on to the next TP without waiting when blindscanning starts first sampling a data multistream, but I suppose doing that means we would lose the ability to check the rest of the stream to find possible useful information (as we can with the input stream checking facility in Crazyscan).

This has already been implemented.... Will be in next version

 

[deeptho]

I don't know if it happens only to me, but when I want to scan the polarities separately, the same color-blue-appears on both, although they should be different colours, blue for Horizontal and orange/yellow for Vertical.
Is this correct or is it an error?

Blue is used for the first graph, orange for the second, and so on. If there is only one graph it is blue.

 

[satesco]

I tried C-band reception at 40.0E with the 6903x and 6902se card, T2-MI muxes. The only regret I have is that almost every mux contains the same services.
Every PLP is decoded where the signal is good. Unfortunately in my area, there is massive interference in the C band.

 

[Llew]

@deeptho

Something weird has happened.

I did a git pull on neumodvb/build, and now I've lost the neumodvb.py. file in the gui folder. Hence I can't start neumodvb, and no log to check.

Can you figure out what's happened here? I've done a rebuild, and it compiles 100%.

 

[satesco]

I did simultaneous reception tests on several DVB cards with neumoDVB. Fortunately, they all work fine, with no problems as long as the computer has strong hardware support. Surely the app would work with all tuners if I used them and I would have had multiple signal sources
tbs6903x at 68.5E,
tbs6902se at 19.2E,
tbs6590 at 30.0W,
tbs6983 at 1.0W,
tbs6504 on Cable network

When can neumoDVB be used for terrestrial reception?
Regards

 

[Llew]

@deeptho

Something weird has happened.

I did a git pull on neumodvb/build, and now I've lost the neumodvb.py. file in the gui folder. Hence I can't start neumodvb, and no log to check.

Can you figure out what's happened here? I've done a rebuild, and it compiles 100%.

View attachment 144324

Back now after deleting neumoDVB and rebuilding from scratch.

Problem now is that I have lost all my LNB settings (blank LNB list), even though all my scanned sats are shown in my DVB-S Muxes list.

Looks as if I'll have to redo all my LNBs (dishes, adapters, diseqc etc. etc...

 

[deeptho]

@deeptho

Something weird has happened.

I did a git pull on neumodvb/build, and now I've lost the neumodvb.py. file in the gui folder. Hence I can't start neumodvb, and no log to check.

Can you figure out what's happened here? I've done a rebuild, and it compiles 100%.

View attachment 144324

LLew,
try "git reset --hard" (after cd-ing into the neumodvb folder)

 

[Llew]

LLew,
try "git reset --hard" (after cd-ing into the neumodvb folder) I have neumodvb.py back after adeleting

As I mentioned in my next post, I have neumodvb.py back after deleting neumodvb and reinstalling, but as I said, I have lost everything in my LNB list. Everything else is present in the Lists section (dvb-s muxes, services etc.)

 

[Llew]

Usually, when I do a rebuild of neumodvb, all my settings are retained, including my LNB setups. Now I have a blank LNB list. I assume I will have to do them again (adapters, LNB numbering etc).

 

[deeptho]

Back now after deleting neumoDVB and rebuilding from scratch.

Problem now is that I have lost all my LNB settings (blank LNB list), even though all my scanned sats are shown in my DVB-S Muxes list.

Looks as if I'll have to redo all my LNBs (dishes, adapters, diseqc etc. etc...

There have been some recent changes which indeed require editing the lnb list (but nothing else).

These changes have only been tested with the very latest kernel drivers. neumo automatically backs up your configuration (see the folder which contains your database). So you can always go back by restoring an older version of the software and of your database. Restoring the database is just copying the old files over the new ones (best make a backup first)

I have also written a script to convert the old database into a new one without loosing information, but that is not ready for general use. If you send me the old and the new files in ...db/chdb and ...db/statdb I can do the conversion for you

For instance, in my case, the database is stored in /mnt/neumo/db. chdb is the current one and chdb.mdb.20220722_22:19:53/
is a backup of an older version created by neumodvb.

ls -alrt /mnt/neumo/db/chdb
chdb/                     
...
chdb.mdb.20211125_01:24:12/ chdb.mdb.20220128_01:23:25/ chdb.mdb.20220721_01:13:32/ chdb.mdb.20220722_22:15:40/
chdb.mdb.20211125_01:25:39/ chdb.mdb.20220128_01:45:06/ chdb.mdb.20220721_01:25:15/ chdb.mdb.20220722_22:19:53/

There will be some more changes next, but the internal autoconversion code will convert automatically without loss of data.

 

[deeptho]

When can neumoDVB be used for terrestrial reception?
Regards

Since last week.

 

[Llew]

There have been some recent changes which indeed require editing the lnb list (but nothing else).

Having restored to an earlier 'working' database, I still have a problem with the new LNB list and its adapter column(s).

With none of my previously chosen LNBs showing since using the updated neumodvb version, I'm attempting to set up a new LNB in the list.

Is my currently chosen adapter to show in the 'adap' column only when choosing my adaptor in the 'adapter' column, or should it show when I have highlighted it in the frontend list? (I can't manually add my adapter in the 'adap' column).

In any case as soon as I have filled a new field in the LNB list (as shown in the screengrab), highlighting it is useless as the field simply disappears when I move from the LNB list to anywhere else, e.g. spectrum or dvb-s mux list- it's vanished when checking back again.

 

[deeptho]

Llew,

this is not really a restored database, as it is not posisble to upgrade to the newest neumo version without either making manual
changes to the lnbs or running some script.

In the new code, you have to select an adapter from a list. For this you first need to activate edit mode (control-E)
then select the correct adapter and then move to some other field (otherwise the change is not saved).

In the next version it will change again. Then you will need to select a "card / rf input" combination. It may sound the same
but it is not. These changes are too complex to handle using auto upgrade. I guess users will have to "bite the bullet",
but the end result will be better

 

[Llew]

In the new code, you have to select an adapter from a list. For this you first need to activate edit mode (control-E)
then select the correct adapter and then move to some other field (otherwise the change is not saved).

I do that each time I have started neumodvb.

In the next version it will change again. Then you will need to select a "card / rf input" combination.

In the next version? I already select the card (highlighted). I don't know what #RF is supposed to do. Forgive my ignorance but It's currently not selectable - whatever is it supposed to select? Or is that for a future version?

Why is blindscan not ticked for my TBS 6903X? It used to be in my last neumodvb version.

What's adapter#1 in the first field? It doesn't show as present, yet blindscan is enabled and ticked. Perhaps it's a leftover from when I attempted to use my USB DVB-T/T2 tuner in the earlier neumodvb version? Checking frontends in Terminal correctly show my four adaptors in the correct order, with no other adapter present. That USB tuner was unplugged a while ago.

 

[Llew]

I do that each time I have started neumodvb.


In the next version? I already select the card (highlighted). I don't know what #RF is supposed to do. Forgive my ignorance but It's currently not selectable - whatever is it supposed to select? Or is that for a future version?

Why is blindscan not ticked for my TBS 6903X? It used to be in my last neumodvb version.

What's adapter#1 in the first field? It doesn't show as present, yet blindscan is enabled and ticked. Perhaps it's a leftover from when I attempted to use my USB DVB-T/T2 tuner in the earlier neumodvb version? Checking frontends in Terminal correctly show my four adaptors in the correct order, with no other adapter present. That USB tuner was unplugged a while ago.

View attachment 144351

With USB T/T2 Tuner plugged in, so adapter#1 doesn't seem to be anything to do with the USB tuner.

DVB-T/T2 muxes in List doesn't work still incidentally. There's still no way of creating a field.

 

[deeptho]

I do that each time I have started neumodvb.

No, I mean: instead of entering an adapter number for an lnb, you need to pick the adapter from a list. Adapter numbers
are rather depending on all klnds of unwanted issues such as the order in which cards are detected. The latest code
uses the MAC address of the adapter instead, so it will always know the correct "number" even if you put the card in a different pci-express
slot.

The next code (not ready yet) will rather use a mac address per card and the "RF input" number, which is the number of the connector on the card.
So it uniquely identifies a cable going to a dish. This is because of cards like tbs6909x and tbs6903x, all adapters can reach all cables. The current
drivers do not use the flexibility. The next ones will be more flexible. For instance, you will be able to tune 8 muxes in the same band
(e.g, vertical-Hight) simultaneously on the same LNB, even if there is only one cable to that LNB.

For the user it will be simple: you specify lnbs per physical connector instead of per adapter. It will also be less work to configure.

So in conclusion: It is work in progress and for all of this to work best, the latest kernel is needed. The goal is to keep everything
compatible in a way that older -non supported - devices can still be used in a reasonably easy fashion.

The current kernel is fine even for older code (minus bugs)

In the next version? I already select the card (highlighted). I don't know what #RF is supposed to do. Forgive my ignorance but It's currently not selectable - whatever is it supposed to select? Or is that for a future version?

#RF is the number of the RF connector at the back. Currently this is readonly. That will change.
There will be documentation as well.

Why is blindscan not ticked for my TBS 6903X? It used to be in my last neumodvb version.

Don't know. I have such a card plugged in right now, and blindscan shows up.

What's adapter#1 in the first field? It doesn't show as present, yet blindscan is enabled and ticked. Perhaps it's a leftover from when I

#1 is the adapter number, corresponding to /dev/dvb/adapter1

attempted to use my USB DVB-T/T2 tuner in the earlier neumodvb version? Checking frontends in Terminal correctly show my four adaptors in the correct order, with no other adapter present. That USB tuner was unplugged a while ago.

That is why it is listed as not available.

Its name is missing (blank) because it is some unsupported device and you are
not running the latest neumo kernel drivers, which attempt to report meaningful values for unsupported devices.

Note that the driver code for some popular devices like hauppage is full of bugs which cause the kernel to crash if you remove the
USB device. After that expect serious problems unless you reboot. I fixed this for hauppage wintv dual hd in the latest kernel code.

I would recommend running the latest kernel. It has some bugs fixed.

With USB T/T2 Tuner plugged in, so adapter#1 doesn't seem to be anything to do with the USB tuner.

DVB-T/T2 muxes in List doesn't work still incidentally. There's still no way of creating a field.

There is no LNB for DVB/T. You should bring up the "DVB-T muxes" list which will be empty and then use the add new command
(Control-N) and enter frequency, bandwidth and some more data. Then press control-M to scan the mux and the services should appear.
See below. I only entered frequency, system, modulation and bandwidth.

I was only able to test this with my own DVB-T transmitter. I cannot receive anything here (no signal). So DVB-T2 has not been tested.
If it doesn't work, show me the log files

View attachment 144351

 

[Llew]

I was only able to test this with my own DVB-T transmitter. I cannot receive anything here (no signal). So DVB-T2 has not been tested.
If it doesn't work, show me the log files

deeptho, the latest kernel hasn't helped with either my adapter problems or attempting to fill details into the DVB-T list.

I'm afraid the log file doesn't tell me anything if it doesn't have any error warnings Perhaps you can see something amiss there?

The only way I can enter any DVB-T mux info is placing it in the Filter list. Edit/New doesn't do anything. Grid remains blank.

Checking a DVB-S transponder in 14W previously chosen and known to be working (highlighted in the DVB-S Mux and Services lists), as expected it reports an absent adapter when trying it in the Channel list. I expect it's my odd adapter listings that is causing it.

This problem has occured since pulling the latest changes in github. No doubt it's something to do with my setup - I expect I'll have to make some changes somewhere.








View attachment 144396

 

[deeptho]

I think you are doing something wrong. Not sure what. The code is the right version (but there is newer one
in the mean time). Probably you are trying to add a dvb-t mux in the dvb-s list? That is not going to work.

 

[Llew]

I think you are doing something wrong. Not sure what. The code is the right version (but there is newer one
in the mean time). Probably you are trying to add a dvb-t mux in the dvb-s list? That is not going to work.

No I would never do that. Perhaps it's because the default screen when starting neumodvb is the channels (View>C), so that would be in the log irrespective of if you go to the DVB-T Mux List as the first list of your choice?

 

[deeptho]

Llew, I was refering to the screenshot. Together with Satesco we verified that DVB-T2 is working. His problem
was related to not installing the latest version: git pull can give errors if for some reason local changes have been made.
There were other problems as well, related to the specific nvidia graphics card problems. Even teamviewer stopped working at some pint.

I fixed a few minor bugs bugs in the mean time as well, but these do not prevent operation.