Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £129! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £179! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...
[VU+ Solo4K] TBS 5925 USB Tuner
- Thread starter maxben
- Start date
ABM crash in writing lamedb…
@James save the xml file from both tuners. Xml files are in /tmp after scan completes. And debug log from both scans. Not sure why you have this trouble as scans work for el bandito.[/QUOTE]
@ Huevos,
I have done 2 vertical only scans the first was with the Solo2 tuner B single satellite with tuner A un-configured, that scan found 183 channels, I then disconnected and un-configured tuner B and connected the TBS again as a single satellite and it found 190 channels I can't upload these Xml files as they are in the wrong format but I have saved them.
BTW I did a STB restart before the TBS scan and checked before the scan if it would open any channels from the previous Solo2 scan or I could see a signal using the STB signal finder and I could not, the TBS scan took about 4 times longer than the Solo2 scan.
The good news is this time I was able to open the FTA channels scanned with the TBS, maybe it is because I used the "clear before scan parameter" on the blind scan page before the TBS scan, could that have been the problem?
Unfortunately the SNR and AGC levels using the TBS tuner are a considerable amount lower...in fact over 30% than with the Solo2 tuner which is surprising given the TBS found more transponders than the Solo2. Some of the weaker FTA channels from the TBS scan are showing pixilation so the Solo2s the higher SNR and SGC levels seems to indicate a more sensitive with a better lock than the TBS tuner, also the channels scanned by the TBS won't open with the Solo2 tuners.
I could only find one debug file and I think this is for the STB restart and not the scans but I have attached anyway.
Kind regards and thanks again for all your help and hard work,
James.
@ Huevos,
I have done 2 vertical only scans the first was with the Solo2 tuner B single satellite with tuner A un-configured, that scan found 183 channels, I then disconnected and un-configured tuner B and connected the TBS again as a single satellite and it found 190 channels I can't upload these Xml files as they are in the wrong format but I have saved them.
BTW I did a STB restart before the TBS scan and checked before the scan if it would open any channels from the previous Solo2 scan or I could see a signal using the STB signal finder and I could not, the TBS scan took about 4 times longer than the Solo2 scan.
The good news is this time I was able to open the FTA channels scanned with the TBS, maybe it is because I used the "clear before scan parameter" on the blind scan page before the TBS scan, could that have been the problem?
Unfortunately the SNR and AGC levels using the TBS tuner are a considerable amount lower...in fact over 30% than with the Solo2 tuner which is surprising given the TBS found more transponders than the Solo2. Some of the weaker FTA channels from the TBS scan are showing pixilation so the Solo2s the higher SNR and SGC levels seems to indicate a more sensitive with a better lock than the TBS tuner, also the channels scanned by the TBS won't open with the Solo2 tuners.
I could only find one debug file and I think this is for the STB restart and not the scans but I have attached anyway.
Kind regards and thanks again for all your help and hard work,
James.
I don't want to give priority to the TBS tuner, because then it will always be the first to be engaged, irrespective of whether the task involves a multistream transponder. If you subsequently want a multistream channel for something, the receiver won't be able to do it unless you cancel the first task.
It would be nice to have a modification to the system so that it stores and reads an additional attribute for each tuner, indicating whether it can receive multistream. Non-multistream transponders could then be handled automatically by the normal internal tuners, leaving the TBS tuner to do any difficult stuff.
Debug log.
el bandido
Forum Supporter
- Joined
- Dec 22, 2013
- Messages
- 245
- Reaction score
- 58
- Points
- 28
Receiver = Duo2, 4 Internal tuners, various usb tuners
Images = At least 4.2.005 and later (Problem also exist in other recent OE Alliance images)
Problem = Blindscan faling to complete
Post#95 = Failed blindscan log example.
I tested several images, and a few different blindscan plugins. The blindscan for internal tuners will start but not complete when any of my usb tuners are connected. The internal blindscan works fine IF the power is removed from the receiver, and the usb tuners are physically disconnected from the receiver. The blindscan works fine for usb tuner TBS5925, regardless of what other usb tuners are connected to the receiver.
Note: The latest blindscan plugin posted a few days ago at OE Alliance Git has been tested by me and seems to be OK. This does not seem to be a blindscan plugin problem.
Images = At least 4.2.005 and later (Problem also exist in other recent OE Alliance images)
Problem = Blindscan faling to complete
Post#95 = Failed blindscan log example.
I tested several images, and a few different blindscan plugins. The blindscan for internal tuners will start but not complete when any of my usb tuners are connected. The internal blindscan works fine IF the power is removed from the receiver, and the usb tuners are physically disconnected from the receiver. The blindscan works fine for usb tuner TBS5925, regardless of what other usb tuners are connected to the receiver.
Note: The latest blindscan plugin posted a few days ago at OE Alliance Git has been tested by me and seems to be OK. This does not seem to be a blindscan plugin problem.
The thing is we can only fix open source code, not closed source or hardware incompatibilities. Main point of the thread, multistream seems to work. And Blindscan too apart from this incompatibility. Blindscan was never bulletproof on the internal tuners anyway. Only real annoying issue is Enigma2 needs a way to select the correct tuner for multistream.
Sorry for the delay,i upload the debug error log.
After the crash lamedb is damage and i have lost all my channels…
PS: image = 4.2.006.006 (Multistream)
Receiver = Duo2, 4 internal(dual dvbs and dual dvbt) and TBS5925 external
@Tenten, your crash is caused by a dirty lamedb file. I'm going to commit a fix so this doesn't happen in future, but it is not the fault of ABM.
4.2.007.001 Multistream available. Either pull the software update or download the USB.zip from:
Fixes:
Code:
http://images.satellites-xml.org/multistream/Fixes:
- Select multistream tuner when channel is multistream.
- Give preference to non-multistream tuners when multistream tuner is not required.
- Clean dirty lamedb in ABM.
Last edited:
Are you getting as far as the spinner?
Should be fixed now.
abu baniaz
Moderator
Despite screen being blank, you can connect to it by putty and perform an update
Just update Duo2 with software update…all seems ok...
Ok, please test that multistream channels automatically go to correct tuner whereas normal S2 channels play on the internal tuner.
Not sure of the purpose of that test as my TBS just has a dedicated LNB on 5w and I've never had a problem with either MS channels from the TBS or normal S2 channels from other satellites on the internal tuners since the start of testing.
Similar threads
