Jump to content


Photo

VU+ Ultimo 4K with DVB-S2x (45308X FBC), DVB-T2 MTSIF (BCM3466) and DVB-S2 (AVL6222)


  • Please log in to reply
107 replies to this topic

Re: VU+ Ultimo 4K with DVB-S2x (45308X FBC), DVB-T2 MTSIF (BCM3466) and DVB-S2 (AVL6222) #41 nemosince1996

  • Senior Member
  • 73 posts

0
Neutral

Posted 27 July 2019 - 12:19

OFF TOPIC: I don't know whether it is necessary to create a new one

 

When I copied NimManager and earlier some other files it seems to me that from OpenPLI 7.1 image all copied file names using ftp are converted to lowercase. It causes problems and I have to carefully check everything what I copied. Samba does not do it.



Re: VU+ Ultimo 4K with DVB-S2x (45308X FBC), DVB-T2 MTSIF (BCM3466) and DVB-S2 (AVL6222) #42 littlesat

  • PLi® Core member
  • 49,505 posts

+533
Excellent

Posted 27 July 2019 - 12:22

Never use ftp to transfer files! Totally not needed at all and that!!!! Just use explorer and type in the address bar \\ip.from.the.box!!!!

Edited by littlesat, 27 July 2019 - 12:24.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: VU+ Ultimo 4K with DVB-S2x (45308X FBC), DVB-T2 MTSIF (BCM3466) and DVB-S2 (AVL6222) #43 nemosince1996

  • Senior Member
  • 73 posts

0
Neutral

Posted 27 July 2019 - 12:30

For years it worked to the full satisfaction. I thought and I think it's a mistake of image. However, I can change what I was used to.



Re: VU+ Ultimo 4K with DVB-S2x (45308X FBC), DVB-T2 MTSIF (BCM3466) and DVB-S2 (AVL6222) #44 WanWizard

  • Forum Moderator
    PLi® Core member
  • 48,879 posts

+836
Excellent

Posted 27 July 2019 - 12:43

FTP might be an issue when you use it from Windows, as file names in Windows are case-insensitive, while in Linux they are case-sensitive.

 

FTP in itself will not convert filenames (but it might touch the content, so always transfer in binary mode), but it could well be that the file was created in the wrong case.


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: VU+ Ultimo 4K with DVB-S2x (45308X FBC), DVB-T2 MTSIF (BCM3466) and DVB-S2 (AVL6222) #45 nemosince1996

  • Senior Member
  • 73 posts

0
Neutral

Posted 27 July 2019 - 12:56

I use Windows but on this side nothing has changed. I use ftp mainly for copying bouquets from one box to another. Source box is linked via samba and another via ftp. I have never had problems with lowercase and capitols in names as well as file attributes. I accept your way of work and explanation. ... Howgh



Re: VU+ Ultimo 4K with DVB-S2x (45308X FBC), DVB-T2 MTSIF (BCM3466) and DVB-S2 (AVL6222) #46 littlesat

  • PLi® Core member
  • 49,505 posts

+533
Excellent

Posted 27 July 2019 - 13:18

Use explorer instead of FTP and your issue is solved... nothing special required!!!!!!! Even for putting bouquets on your box this is better.

Edited by littlesat, 27 July 2019 - 13:19.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: VU+ Ultimo 4K with DVB-S2x (45308X FBC), DVB-T2 MTSIF (BCM3466) and DVB-S2 (AVL6222) #47 WanWizard

  • Forum Moderator
    PLi® Core member
  • 48,879 posts

+836
Excellent

Posted 27 July 2019 - 14:15

If the file is created in the wrong case, using a CIFS connection won't solve the problem.

 

I've never heard of an FTP client that decides on his own to change the case of filenames...


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: VU+ Ultimo 4K with DVB-S2x (45308X FBC), DVB-T2 MTSIF (BCM3466) and DVB-S2 (AVL6222) #48 nemosince1996

  • Senior Member
  • 73 posts

0
Neutral

Posted 27 July 2019 - 15:30

Final words: I used to use Total Commander built-in ftp for several devices - 2 pc's, several satellite and several linux-based boxes - not only on lan with full success for many years until now. You told me your opinion and advised me what to do. Thanks guys. But I am not so young to change easily my way of doing things. :(



Re: VU+ Ultimo 4K with DVB-S2x (45308X FBC), DVB-T2 MTSIF (BCM3466) and DVB-S2 (AVL6222) #49 WanWizard

  • Forum Moderator
    PLi® Core member
  • 48,879 posts

+836
Excellent

Posted 27 July 2019 - 15:35

I'm not saying you should.

 

I am only intriged as to why you see a filename change case during transfer, when that never happened before, and FTP has nothing in the protocol to perform such action.


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: VU+ Ultimo 4K with DVB-S2x (45308X FBC), DVB-T2 MTSIF (BCM3466) and DVB-S2 (AVL6222) #50 nemosince1996

  • Senior Member
  • 73 posts

0
Neutral

Posted 27 July 2019 - 15:54

Ok, for example: I copied one plugin directory from my old Ultimo 4K (OpenPLI 7.1) to new Ultimo 4K (7.1 built from scratch) the way I described above because .ipk refused to install. I did something similar several times in past but from now all directory and file names are lowercase. It means that these files were created correctly and run in old box. After copy they should be correct as well. Where can they be changed?



Re: VU+ Ultimo 4K with DVB-S2x (45308X FBC), DVB-T2 MTSIF (BCM3466) and DVB-S2 (AVL6222) #51 littlesat

  • PLi® Core member
  • 49,505 posts

+533
Excellent

Posted 27 July 2019 - 16:10

Must be a setting into total commander... again use the standard explorer... no total commander required.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: VU+ Ultimo 4K with DVB-S2x (45308X FBC), DVB-T2 MTSIF (BCM3466) and DVB-S2 (AVL6222) #52 WanWizard

  • Forum Moderator
    PLi® Core member
  • 48,879 posts

+836
Excellent

Posted 27 July 2019 - 16:30

I doublechecked: vsftpd doesn't have a feature to convert filenames to lower (or any other) case. So it must indeed be a client-side issue.

 

Maybe this problem? https://www.ghisler....opic.php?t=8363


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: VU+ Ultimo 4K with DVB-S2x (45308X FBC), DVB-T2 MTSIF (BCM3466) and DVB-S2 (AVL6222) #53 nemosince1996

  • Senior Member
  • 73 posts

0
Neutral

Posted 27 July 2019 - 20:06

@WanWizard - thank you very much. You were quicker and more successfull than me. That's it. I have already started checking everything on my side but because I knowingly have not changed anything in Total Commander it would take more time for me to find the reason. Thanks again. I like how you try to help common user and try to fight for the reputation of OpenPLi. And it is really good for me.



Re: VU+ Ultimo 4K with DVB-S2x (45308X FBC), DVB-T2 MTSIF (BCM3466) and DVB-S2 (AVL6222) #54 WanWizard

  • Forum Moderator
    PLi® Core member
  • 48,879 posts

+836
Excellent

Posted 27 July 2019 - 20:10

:thumbs-up:


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: VU+ Ultimo 4K with DVB-S2x (45308X FBC), DVB-T2 MTSIF (BCM3466) and DVB-S2 (AVL6222) #55 nemosince1996

  • Senior Member
  • 73 posts

0
Neutral

Posted 29 July 2019 - 07:42

I have made update today. Configuration of tuners is OK. Great.



Re: VU+ Ultimo 4K with DVB-S2x (45308X FBC), DVB-T2 MTSIF (BCM3466) and DVB-S2 (AVL6222) #56 littlesat

  • PLi® Core member
  • 49,505 posts

+533
Excellent

Posted 29 July 2019 - 08:34

And I'm also 'afraid' we're currently the only image that solves it... Even in VUs image (+likely VTi, but I cannot verify that on code because they illegally do share their sources) it will not work  when you put something additional in the 3rd legacy tuner slot... It took me also a lot of thoughts for the best solution, which still can be optimized (later).


Edited by littlesat, 29 July 2019 - 08:35.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: VU+ Ultimo 4K with DVB-S2x (45308X FBC), DVB-T2 MTSIF (BCM3466) and DVB-S2 (AVL6222) #57 nemosince1996

  • Senior Member
  • 73 posts

0
Neutral

Posted 29 July 2019 - 09:31

@littlesat - look at #17, probably the second but I appreciate that you were able to solve it in OpenPLI image quickly and for the first try. Of course there is really room for tuning and improvement. But for me it is important that it is running reliably. I have checked it also in QuadPIP plugin for all four positions in several sets with different tuners and lnb's. It runs very well.



Re: VU+ Ultimo 4K with DVB-S2x (45308X FBC), DVB-T2 MTSIF (BCM3466) and DVB-S2 (AVL6222) #58 littlesat

  • PLi® Core member
  • 49,505 posts

+533
Excellent

Posted 29 July 2019 - 09:48

Or OE-A did something wierd in their BSP, they use a different (older?) drivers.... Then in OpenATV the first 16 tuners do not have fixed fbc_id in their procs.

 

With the latest drivers we get from the BSP from it cannot work as all first 16 tuners in any ARM VU box are indicated as FBC tuners...At least the 3rd tuner should be recognized as fbc leave tuner... It might also be OE-A does not have proper leave tuner handling or do it differently in cpp code for DVB-C tuners so they do not get an issue by chance. I only see they check for fbc tuners functions are equal to our. In addition they do a lot of 'if box x then do y' in their code which we think is not done which might mask it.


Edited by littlesat, 29 July 2019 - 09:50.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: VU+ Ultimo 4K with DVB-S2x (45308X FBC), DVB-T2 MTSIF (BCM3466) and DVB-S2 (AVL6222) #59 twol

  • Senior Member
  • 275 posts

+8
Neutral

Posted 29 July 2019 - 09:54

Or OE-A did something wierd in their BSP, they use a different (older?) drivers.... Then in OpenATV the first 16 tuners do not have fixed fbc_id in their procs.

 

With the latest drivers we get from the BSP from it cannot work as all first 16 tuners in any ARM VU box are indicated as FBC tuners...At least the 3rd tuner should be recognized as fbc leave tuner... It might also be OE-A does not have proper leave tuner handling or do it differently in cpp code for DVB-C tuners so they do not get an issue by chance. I only see they check for fbc tuners functions are equal to our. In addition they do a lot of 'if box x then do y' in their code which we think is not done which might mask it.

OpenATV FBC tuner implementation is different from OpenPli/OpenViX - OE-A drivers are latest from vendor...... 


Edited by twol, 29 July 2019 - 09:55.

Gigablue Quad 4K & UE 4K
.........FBC Tuners:
------------------> DUR-Line DCR 5-1-8-L4 Multiswitch to 1.5M dish(28.2E)
------------------> Spaun SUS 5581/33 NFA Multiswitch to 80 cm dish(19.2E)
.........DVB-S2X into 90cm dish (27.5W)

Octagon SF8008 DVB-S2X tuner using Legacy ports on multiswitches
Edision Osmio 4K+, Zgemma H9Combo and Multibox using Legacy ports on multiswitches
Zgemma H9twin & Zgemma H9 C/S mode into Giga4K
 


Re: VU+ Ultimo 4K with DVB-S2x (45308X FBC), DVB-T2 MTSIF (BCM3466) and DVB-S2 (AVL6222) #60 littlesat

  • PLi® Core member
  • 49,505 posts

+533
Excellent

Posted 29 July 2019 - 10:01

I just checked their SatConfig.py and NimManager.py and as far I can see they solved it by accident by only creating FBC-'links' on DVB-S....As the kast tuner is DVB-S also they will see the third tuner as FBC tuner with only having two 'root' tuners and without any leave tuners. The wierd thing is that it does not have real side-effects.

At least our code does now not recognize them as FBC tuner at all...


WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users