Jump to content


Photo

VuZero problem openpli 4.0

Started by Rudi1, 21 Feb 2017 20:04

  • Please log in to reply
27 replies to this topic

#1 Rudi1

  • Senior Member
  • 162 posts

+1
Neutral

Posted 21 February 2017 - 20:04

I have this problem only with  openpli image.I try several images but all is working fine except openpli.Here is my problem.

I flash the box with latest openpli.Setup all settings and install only few plugins(epgimport,iptv player)

Also I edit epgcache path to save dat files on usb (config.misc.epgcache_filename=/media/usb/epg.dat) and start watching tv but after some time the box 

becomes unresponsive and in the end the box crash itself. I do not know what caused this (maybe the epgimport save files somewhere....)

I try to flash the box several times but always the results is the same.

Can anyone know why this is happening to me and how to solve this problem?


VU+Zero

Osmio4K

Re: VuZero problem openpli 4.0 #2 Frenske

  • Forum Moderator
    PLi® Core member
  • 27,396 posts

+394
Excellent

Posted 21 February 2017 - 22:54

It might be usefull if you create an enigma log with putty and hope that this issue occurs when the logfile is being created.
The only proper way is to start a telnet session with putty, be sure the logfile is saved, stop enigma with init 4 and start enigma again with enigma2 and hope for the best. As soon as the issue occurs stop the logging and post the log here.

Mijn schotel is een T90 met 10 LNB's. Daarnaast voor de fun nog een draaibaar systeem met een Triax TD 78.

Dreamboxen heb ik niet meer echt actief. Verder heb ik ook nog een een VU+ duo2 met 500Gb harddisk + een VU+ Uno, Zero, Solo 4K, Ultimo 4K, Zero 4K, Uno 4Kse. + ook nog een Xtrend ET7x00. Daarnaast heb ik ook nog diverse andere modellen w.o. een Formuler F4, ET8500, ET7500, Mut@nt 2400HD, Xsarius Fusion HD se en verder nog wel het e.e.a. waarmee op verzoek vanalles wordt getest. Iemand moet het tenslotte doen. ;) :)
Los van de eerder genoemde modellen heb ik nog wel een rits aan testsamples als Mut@nt 2400HD, HD60, GB UE4K, GB Trio4K, Maxitec Multibox combo en Twin, Octagon sf8008, sf8008 mini en last but nog least enkele modellen van het Grieks Duitse Edision.

Voor centrale opslag van media gebruik ik een Qnap 219P met tweemaal 2 Tb harddisks + een Synology DS414 met 12 Tb Totale opslag.

-------------------------------------------------------------------------------------------
Many answers to your question can be found in our wiki: Just one click away from this "solutioncentre".

Als ik alles al wist hoefde ik ook niets te vragen. If I had all the knowledge I had no questions at all.

Re: VuZero problem openpli 4.0 #3 WanWizard

  • PLi® Core member
  • 68,612 posts

+1,739
Excellent

Posted 21 February 2017 - 22:57

Enigma only uses the epgcache on startup, to reload the epg data cached on restart. It doesn't use it while running, so that can't be the cause.

 

If it becomes unresponsive, do you get a spinner in the upper-left corner? If it crashes, do you get a green screen and a crash mesage? If not, what do you mean by crash?


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

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

Re: VuZero problem openpli 4.0 #4 Rudi1

  • Senior Member
  • 162 posts

+1
Neutral

Posted 21 February 2017 - 23:11

Well,I get a spinner in the upper-left corner and then image restart.no crash log and after some time he image becomes slow again.

 

VU+Zero

Osmio4K

Re: VuZero problem openpli 4.0 #5 WanWizard

  • PLi® Core member
  • 68,612 posts

+1,739
Excellent

Posted 21 February 2017 - 23:17

The enitre box restarts, or only Enigma restarts? If Enigma, it could be a segfault somewhere, which would be easy to find using the method Frenske posted.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

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

Re: VuZero problem openpli 4.0 #6 Rudi1

  • Senior Member
  • 162 posts

+1
Neutral

Posted 21 February 2017 - 23:30

not enigma the enitre box restarts.


VU+Zero

Osmio4K

Re: VuZero problem openpli 4.0 #7 WanWizard

  • PLi® Core member
  • 68,612 posts

+1,739
Excellent

Posted 21 February 2017 - 23:32

Never seen this, something that could cause the complete OS to crash. Normally that could be buggy drivers, but no other Zero owner (including myself) has reported a similar issue.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

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

Re: VuZero problem openpli 4.0 #8 Rudi1

  • Senior Member
  • 162 posts

+1
Neutral

Posted 21 February 2017 - 23:38

Really strange that this is happening only to me,I'm not expert so just write what's going on with my box.


VU+Zero

Osmio4K

Re: VuZero problem openpli 4.0 #9 WanWizard

  • PLi® Core member
  • 68,612 posts

+1,739
Excellent

Posted 21 February 2017 - 23:52

I understand that, but if we don't have any debug info, and can't reproduce it, we're as clueless as you. ;)

 

I can only say try to do what Frenske suggested. Use a client that maintains console history (like a linux terminal, or PuTTY on Windows), telnet into the box, start Enigma on the commandline, and wait until it happens again. And then post the last 50 or so lines of output in the terminal here.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

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

Re: VuZero problem openpli 4.0 #10 Rudi1

  • Senior Member
  • 162 posts

+1
Neutral

Posted 22 February 2017 - 00:01

I have to apologize because I'm not sure or box do a full restart  or just an enigma, so I will try what you propose to do as soon as I had a little more time.:)

.Thank you for help!


VU+Zero

Osmio4K

Re: VuZero problem openpli 4.0 #11 WanWizard

  • PLi® Core member
  • 68,612 posts

+1,739
Excellent

Posted 22 February 2017 - 00:10

In both cases, running Enigma from the commandline will show you the error.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

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

Re: VuZero problem openpli 4.0 #12 zeros

  • PLi® Contributor
  • 1,635 posts

+61
Good

Posted 22 February 2017 - 05:33

Exactly the same happened here with Sundtek usb stick and the solution was to use the Turbo tuner instead of Sundtek. No crash log, box just hangs at some time during the watching. The back button only helped to restart the box. The other software is not tried, so I can't tell if it was only for the PLi software so.

Edited by zeros, 22 February 2017 - 05:34.

DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB

Vertex 4K60 4:4:4 600MHz

Re: VuZero problem openpli 4.0 #13 Cofybreak

  • Senior Member
  • 115 posts

0
Neutral

Posted 22 February 2017 - 07:25

Really strange that this is happening only to me,I'm not expert so just write what's going on with my box.

 

Welcom to the club.

Same here, but box is osmini.

For now no solution - see in this topic.


Re: VuZero problem openpli 4.0 #14 WanWizard

  • PLi® Core member
  • 68,612 posts

+1,739
Excellent

Posted 22 February 2017 - 11:14

Also using some USB device?


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

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

Re: VuZero problem openpli 4.0 #15 Erik Slagter

  • PLi® Core member
  • 46,960 posts

+541
Excellent

Posted 22 February 2017 - 17:56

dmesg.

 

I think it's the ol' memory fragmentation problem.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.

Re: VuZero problem openpli 4.0 #16 Rudi1

  • Senior Member
  • 162 posts

+1
Neutral

Posted 22 February 2017 - 23:04

Is it any solution for this yet?


VU+Zero

Osmio4K

Re: VuZero problem openpli 4.0 #17 WanWizard

  • PLi® Core member
  • 68,612 posts

+1,739
Excellent

Posted 22 February 2017 - 23:14

Is it any solution for this yet?

 

As long as there is no cause known, there will not be a solution.

 

So when it happens again, someone needs to telnet into the box, issue the "dmesg" command like Erik asked, and post the result here.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

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

Re: VuZero problem openpli 4.0 #18 Rudi1

  • Senior Member
  • 162 posts

+1
Neutral

Posted 24 February 2017 - 12:58

Today I flash the image again and after few hour the same problem.here is the first log when the image becomes unstable:

PYTHONPATH: /usr/lib/enigma2/python
DVB_API_VERSION 5 DVB_API_VERSION_MINOR 10
ENIGMA_DEBUG_LVL=3
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
[MAIN] executing main
TuxTxt cache cleared
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
cleaning up
TuxTxt cache cleared
TuxTxt cache cleared
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] ERROR reading PES (fd=56): Value too large for defined data type
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
cleaning up
TuxTxt cache cleared
TuxTxt cache cleared
cleaning up
TuxTxt cache cleared
TuxTxt cache cleared
TuxTxt cache cleared
TuxTxt: initialized
TuxTxt service started 20
TuxTxt running thread...(020)
TuxTxt stopped service 20
cleaning up
TuxTxt cache cleared
TuxTxt cache cleared
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
cleaning up
TuxTxt cache cleared
TuxTxt cache cleared
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
[eDVBAudio] /dev/dvb/adapter0/audio0: Device or resource busy
[eDVBVideo] /dev/dvb/adapter0/video0: Device or resource busy
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] ERROR reading PES (fd=49): Value too large for defined data type
[eDVBPESReader] ERROR reading PES (fd=49): Value too large for defined data type
[eDVBPESReader] ERROR reading PES (fd=49): Value too large for defined data type
Killed

and here where almost I can't swith to anything and the spinner is almost always on


openpli 4 vuzero


vuzero login: root
root@vuzero:~# init 5
root@vuzero:~# enigma2.sh
/dev/dvb/adapter0/video0: Device or resource busy
PYTHONPATH: /usr/lib/enigma2/python
DVB_API_VERSION 5 DVB_API_VERSION_MINOR 10
ENIGMA_DEBUG_LVL=3
[MAIN] executing main
TuxTxt cache cleared
TuxTxt cache cleared
TuxTxt: initialized
TuxTxt service started 20
TuxTxt running thread...(020)
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
[eDVBSectionReader] ERROR reading section - Value too large for defined data type

TuxTxt stopped service 20
[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBPESReader] ERROR reading PES (fd=45): Value too large for defined data type
[eDVBPESReader] ERROR reading PES (fd=45): Value too large for defined data type
[eDVBPESReader] ERROR reading PES (fd=45): Value too large for defined data type
[eDVBPESReader] ERROR reading PES (fd=45): Value too large for defined data type
[eDVBPESReader] ERROR reading PES (fd=45): Value too large for defined data type
[eDVBPESReader] ERROR reading PES (fd=45): Value too large for defined data type
cleaning up
TuxTxt cache cleared
TuxTxt cache cleared
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

cleaning up
TuxTxt cache cleared
[eDVBSectionReader] ERROR reading section - Value too large for defined data type

TuxTxt cache cleared
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type


openpli 4 vuzero


vuzero login: root
root@vuzero:~# init 5
root@vuzero:~# enigma2.sh
/dev/dvb/adapter0/video0: Device or resource busy
PYTHONPATH: /usr/lib/enigma2/python
DVB_API_VERSION 5 DVB_API_VERSION_MINOR 10
ENIGMA_DEBUG_LVL=3
[MAIN] executing main
TuxTxt cache cleared
TuxTxt cache cleared
TuxTxt: initialized
TuxTxt service started 20
TuxTxt running thread...(020)
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
[eDVBSectionReader] ERROR reading section - Value too large for defined data type

TuxTxt stopped service 20
[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBPESReader] ERROR reading PES (fd=45): Value too large for defined data type
[eDVBPESReader] ERROR reading PES (fd=45): Value too large for defined data type
[eDVBPESReader] ERROR reading PES (fd=45): Value too large for defined data type
[eDVBPESReader] ERROR reading PES (fd=45): Value too large for defined data type
[eDVBPESReader] ERROR reading PES (fd=45): Value too large for defined data type
[eDVBPESReader] ERROR reading PES (fd=45): Value too large for defined data type
cleaning up
TuxTxt cache cleared
TuxTxt cache cleared
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section - Value too large for defined data type

cleaning up
TuxTxt cache cleared
[eDVBSectionReader] ERROR reading section - Value too large for defined data type

TuxTxt cache cleared
[eDVBPESReader] Created. Opening demux
[eDVBPESReader] Created. Opening demux
[eDVBSectionReader] ERROR reading section - Value too large for defined data type

[eDVBSectionReader] ERROR reading section -

VU+Zero

Osmio4K

Re: VuZero problem openpli 4.0 #19 WanWizard

  • PLi® Core member
  • 68,612 posts

+1,739
Excellent

Posted 24 February 2017 - 13:04

"init 5" may not be a good idea, perhaps you have two instances of Enigma running now?

 

You use "init 4" to stop Enigma, and "init 3" to start it again.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

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

Re: VuZero problem openpli 4.0 #20 Rudi1

  • Senior Member
  • 162 posts

+1
Neutral

Posted 24 February 2017 - 13:18

Now the image create the crash log too and then crash.

 

With these command:

 

openpli 4 vuzero


vuzero login: root
root@vuzero:~# init 4
root@vuzero:~# init 3
root@vuzero:~#

 not show the log.

Attached Files


VU+Zero

Osmio4K

Back to [EN] Enduser support

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

  1. Forums
  2. → PLi® Support
  3. → [EN] Enduser support