[VU+ Solo2] Tuner not available error

[Andy_Hazza]

I have a Vu+ Solo2, on ViX 3.2-006, using ViX's ABM with no such issues. If I record 2 channels at the same time, all my non viewable channels are greyed as that shows they are on different transponders, which is correct.


Sent from my iPhone using Tapatalk

 

[breomckillian]

I'll give the builtin ABM a go when the family is not watching the TV instead of the E2 one to try in case its an issue with the plugin.

 

[abu baniaz]

Thids is Kill Bill's thread. To avoid ncofusion, please start your own thread. Post a link to this thread if similar issue.

@Kill Bill,
Upload a debug log whcih captures the issue.
Also post an excerpt of your settings file whch deals with the tuner config. It will be like the following:

config.Nims.1.diseqcMode=positioner
config.Nims.0.diseqcA=282

The settings file is located in /etc/enigma2

 

[kill_bill]

Something wierd is going on and im not sure it's tuner related, but something running accessing the other tuner.

Was getting a freeze every 5 seconds (timed it!), restarted Enigma then OK. Started freezing again after a hour or so.

Changed default ports for remote streaming incase, really not sure!

 

[harryoz]

When is someone going to admit this is 3.2 image problem, when I go back to Hades then no tuner problems.
Extend Et8000 with 007 updated today still same problems.

 

[scouse645]

Iv'e had the same problems as above, in my opinion i have fixed it by turning off the ABM from scanning at a set time during the night, doing it manually myself, no problem since. i'm not saying i know why this worked, it just did.

 

[judge]

When is someone going to admit this is 3.2 image problem

It's not though.

 

[kill_bill]

Iv'e had the same problems as above, in my opinion i have fixed it by turning off the ABM from scanning at a set time during the night, doing it manually myself, no problem since. i'm not saying i know why this worked, it just did.

I'll give this a blast, or go back to Hades!

 

[scouse645]

I'm sad to report that i put my box on this morning and tuner B shows recording but it isn't

 

[Rob van der Does]

1) Sometimes when streaming to another device (E2-box, mobile) the tuner won't be freed when the streaming stops. That depends on the client box. Powering off the client box completely (i.e. powerless, or deep sleep) fixes this.
2) When a port to the box has been forwarded in the router, the STB may be accessed from the outside world. The telnet command 'netstat' will tell you who it is, and disconnecting the LAN-connector will fix it for sure. Worth a try.

ANyway: there is no issue with ViX 3.2 causing tuners to show busy while they aren't.

 

[Andy_Hazza]

When is someone going to admit this is 3.2 image problem, when I go back to Hades then no tuner problems.
Extend Et8000 with 007 updated today still same problems.

No such issues on all my boxes running ViX 3.2-007.


Sent from my iPhone using Tapatalk

 

[bbbuk]

I haven't noticed this neither on my Solo2 running a clean/fresh usb install (with no restore of settings) of 3.2 006 with just $ky uk (no multisat).

 

[Rob van der Does]

I have a range of boxes on ViX 3.2 and none of them has such an issue. And if there was a real problem in this area, the forum would be overloaded with complaints.

So best is to try to find the culprit instead of walking away. There must be a suer setting that causes this. Best way would be to start with a flash without restore (only use ABM or any other means to get your bouquets on board) and a softcam.
Also disconnect the LAN-cable whenever you experience an issue like this and see if that stops it.

 

[scouse645]

Morning all, i am still having this problem, done all i can to find out why, including all suggestions above, a new box was purchased also, a mutant2400, i have also done fresh flash without restore, i have also tried every setting in recording settings, i have now put Hades 018 back on the box as of yesterday, no problem since with respect i would ask if the members who have tried to address this problem actually record on a daily basis as i do, not sure there is a problem if you don't record.

 

[gabbism]

Good afternoon Guys,

I have just bought a VU+ duo2 but i can't find anyway to add softcam plugin i have contacted the people i bought it from cos i couldnot add Cline or Nline to it. Plus i am quite new to all this.

thanks for your help.

 

[Peterj]

@gabbism:
Don't hijack someones thread and no card sharing talk on the board.
Read the rules again

 

[Andy_Hazza]

Good afternoon Guys,

I have just bought a VU+ duo2 but i can't find anyway to add softcam plugin i have contacted the people i bought it from cos i couldnot add Cline or Nline to it. Plus i am quite new to all this.

thanks for your help.

You didn't read the forum rules when you signed up then?........


Sent from my iPhone using Tapatalk

 

[harryoz]

Morning all, i am still having this problem, done all i can to find out why, including all suggestions above, a new box was purchased also, a mutant2400, i have also done fresh flash without restore, i have also tried every setting in recording settings, i have now put Hades 018 back on the box as of yesterday, no problem since with respect i would ask if the members who have tried to address this problem actually record on a daily basis as i do, not sure there is a problem if you don't record.

I second all you have done, I have extrend et8000 and Xpeed lx3, on the 8000 i dont record and dont use ABM, on the LX3 I dont use ABM but do record, and as I too said before when I go back to Hades 018 no problems, also Hades has samba installed, and In customise i can disable auto scanning of channels, I find Hades much more user friendly.

 

[Rob van der Does]

...also Hades has samba installed, and In customise i can disable auto scanning of channels, I find Hades much more user friendly.

You can install Samba on 3.2 without any problem. It has been left out, as many people don't use it, so it would be a waste of resources.
As you may have read (in an other thread) the disabling of backgroundscanning will be back in the next build; it wasn't in the last one due to an error.

 

[Rob van der Does]

And as the issue mentioned in this thread can't be reproduced by any one in our team, I can only suggest it's due to a setup error. And even if it is a bug, we can't fix it without reproducing it.