[VU-Solo BH 1.6.3] Difficulties remembering Rotor settings

[Robbedoesje]

Hi all,

I'm new to VU+ and this community, though I'm pretty familiar with the Enigma2 engine's as I've had experiences with serval Dreamboxes in the past.

I managed to flash Black Hole 1.6.3. a week go when I got my Vu+ Solo, but took me like 24 hours to setup my motorized installation . Both USALS and DiSEqC 1.2 are working outstanding now, though I experience one problem.

When I put my Solo in standby and turn it on again, the box seems confused, it doesn't "find" any signal although the dish is pointed to the same satellite as before standby and even on the same channel. One time the SNR indicator will show 0%, one time 99%. The only way to fix this, as I found out, is to go to the Rotor settings menu, reset the rotor (GOTO 0) and choose Restart STB from the Shutdown menu. After it boots up it then goes to the remembered satellite / channel again and signal is back. This also occures after I opened for example the YouTube Plugin, Mediaplayer etc.

What I think happens if I reason this problem logical is that the Box, after standby etc, forgot where it is and continuous tries to send the same GOTO command to the rotor (99%), while the rotor doesn't move because it's already in this position. So the box doesn't remember it's settings or recognize the rotor is already in the correct position.

Long story, my question is, is this image related? Is this a common issue for VU+ devices? How can I solve this? I searched this forum and many other forums about this, but I can't find a satisfying solution....

My setup:

Vu+ Solo
Stab HH90 Rotor
Selfsat flat satellite dish

DiSEqC 1.2 settings (positions) from the Rotor (Stab has 29 positions stored in its memory)

Hope someone can help me.

 

[Robbedoesje]

Really? Nobody? Dev's? Or I posted this in the wrong place?

 

[Dzoni]

Hmmm... You must to start testing of all elements of Your installation.

1. LNB (maybe is in conflict with vu+ tuner)
2. Cable connection (cable and F connectors)
3. Make a one fresh installation of BH 1.6.4
4. Set up Your settings and reboot.


You must to work step by step to find a problems. I think that problem is in installation not in box.

 

[Robbedoesje]

Hmmm... You must to start testing of all elements of Your installation.

1. LNB (maybe is in conflict with vu+ tuner)
2. Cable connection (cable and F connectors)
3. Make a one fresh installation of BH 1.6.4
4. Set up Your settings and reboot.


You must to work step by step to find a problems. I think that problem is in installation not in box.

Dzoni,

Thank you for your reply and advice. I walked thru these steps many times already. The LNB can't be defect as the SelfSat Dish (LNB integrated) is just 7 months old and was working correctly with my previous decoder. Same with the cable, it's renewed 4 months ago for Belden H126 Duobond high end cable (not more than 10mtr).

I re-flashed the BH 1.6.4 image I think four or five times now including a fresh set up of the satsettings (so no copying from the previous installation). During these re-flashes I also tried different satsetting files to be found in this forum. So in total I tried:
- fresh installation with USALS configuration
- fresh installation with DiSEqC1.2 using prestored sat positions of the rotor table
- fresh installation with DiSEqC1.2 pointing the sat to the different sat by myself
- fresh installation with USALS configuration and satsettings from this forum
- fresh installation with DiSEqC1.2 configuration and satsettings form this forum

With my "old" Homecast device all different configurations worked without problem, USALS, DiSEqC1.2 and "Motor".

If I don't put the device in Standby, there is no issue, it starts AFTER Standby. I could left the device turned on, but I think it won't be healthy for the box life expectations

I managed to obtain the crashlog as of 22/07/11. Maybe the problem is to be found in here? I have no idea what to read out of this except:
RemovePopup, id = ZapError
[eDVBCAService] remove channel 0x1a8f420
[eDVBCAService] write leave transponder failed!!
[eDVBLocalTimerHandler] remove channel 0x1a8f420
[eEPGCache] remove channel 0x1a8f420
[EPGC] abort caching events !!
allocate channel.. 0c99:0003
[eDVBCAService] new channel 0x1a8f420!
(0)tune
Entry for 23,5? not in Rotor Table found... i try gotoXX?
siteLatitude = 52.007999, siteLongitude = 4.746000, 23.500000 degrees
PolarmountHourAngle=159.368829
RotorCmd = e14a
RotorCmd e14a, lastRotorCmd e14a
prepare_sat System 1 Freq 12187000 Pol 0 SR 27500000 INV 2 FEC 4 orbpos 235 system 1 modulation 1 pilot 2, rolloff 0
tuning to 1587 mhz
OURSTATE: tuning
allocate Channel: res 0

But what is this referring to? Which Rotor Table does the device mean? If I remember correctly this log was while using USALS settings.

Thanks in advance....



+- 1/2 TID 4e
sdt update done!
[AutoRes] determineContent
[AutoRes] switch deinterlacer mode to auto
[AutoRes] new content is 1920x1080i25
[AutoRes] determined videomode 1080i
++ 2/2 TID 4e
done!
doing version filtering
0012: 4e 51 d6 2f 00 00
mask: ff ff ff 3f 00 00
mode: 00 00 00 3e 00 00
It's now Fri Jul 22 00:36:27 2011
[timer.py] next activation: 1311287887 (in 99997 ms)
It's now Fri Jul 22 00:36:27 2011
[timer.py] next activation: 1311287887 (in 99995 ms)
[EPGC] start caching events(1311287787)
[eDVBLocalTimerHandler] diff is 1
[eDVBLocalTimerHandler] diff < 120 .. use Transponder Time
[eDVBLocalTimerHandler] update RTC
[eDVBLocalTimerHandler] time update to 00:36:29
[eDVBLocalTimerHandler] m_time_difference is 1
[eDVBLocalTimerHandler] set Linux Time
[EPGC] start cleanloop
[EPGC] stop cleanloop
[EPGC] 584772 bytes for cache used
playing 1:0:19:5217:C99:3:EB0000:0:0:0:
[eDVBCAService] free slot 0 demux 0 for service 1:0:19:51D6:C96:3:EB0000:0:0:0:
[eDVBCAService] free service 1:0:19:51D6:C96:3:EB0000:0:0:0:
[eDVBCIInterfaces] remove last pmt handler for service 1:0:19:51D6:C96:3:EB0000:0:0:0: send empty capmt
eDVBCIInterfaces->setInputSource(0, 0)
(3) slot 1 usecount is now 0
decoder state: play, vpid=-1, apid=-1
DEMUX_STOP - pcr - ok
DEMUX_STOP - video - ok
VIDEO_STOP - ok
AUDIO_STOP - ok
DEMUX_STOP - audio - ok
AUDIO_CONTINUE - ok
DEMUX_STOP - ttx - ok
start release channel timer
not pauseable.
RemovePopup, id = ZapError
[eDVBCAService] remove channel 0x1a8f420
[eDVBCAService] write leave transponder failed!!
[eDVBLocalTimerHandler] remove channel 0x1a8f420
[eEPGCache] remove channel 0x1a8f420
[EPGC] abort caching events !!
allocate channel.. 0c99:0003
[eDVBCAService] new channel 0x1a8f420!
(0)tune
Entry for 23,5? not in Rotor Table found... i try gotoXX?
siteLatitude = 52.007999, siteLongitude = 4.746000, 23.500000 degrees
PolarmountHourAngle=159.368829
RotorCmd = e14a
RotorCmd e14a, lastRotorCmd e14a
prepare_sat System 1 Freq 12187000 Pol 0 SR 27500000 INV 2 FEC 4 orbpos 235 system 1 modulation 1 pilot 2, rolloff 0
tuning to 1587 mhz
OURSTATE: tuning
allocate Channel: res 0
[eDVBCIInterfaces] addPMTHandler 1:0:19:5217:C99:3:EB0000:0:0:0:
caid '0100' is in caid list of slot 1... so use it
(1)CISlot 1, usecount now 1
eDVBCIInterfaces->setInputSource(0, 5)
CI Slot 1 setSource(0)
[eDVBCIInterfaces] gotPMT
allocate demux
resolve: resolve ${sysconfdir}/scan_tp_valid_check.py
resolve: -> /etc/scan_tp_valid_check.py
[SEC] set static current limiting
[SEC] setVoltage 2
[SEC] sleep 10ms
set sequence pos 3
[SEC] update current switch params
[SEC] startTuneTimeout 5000
[SEC] setFrontend 1
setting frontend 0
[SEC] sleep 500ms
(0)fe event: status 0, inversion off, m_tuning 1
BlackHoleapi: popclose,
(0)fe event: status 1f, inversion on, m_tuning 2
OURSTATE: ok
[eDVBCAService] channel 0x1a8f420 running
[eDVBLocalTimerHandler] channel 0x1a8f420 running
no version filtering
0014: 70 00 00 00 00 00
mask: fc 00 00 00 00 00
mode: 00 00 00 00 00 00
[eEPGCache] channel 0x1a8f420 running
stop release channel timer
no version filtering
0012: 4e 52 17 00 00 00
mask: ff ff ff 00 00 00
mode: 00 00 00 00 00 00
ok ... now we start!!
no version filtering
0000: 00 00 00 00 00 00
mask: ff 00 00 00 00 00
mode: 00 00 00 00 00 00
eventNewProgramInfo 0 0
have 1 video stream(s) (0201), and 1 audio stream(s) (0065), and the pcr pid is 0201, and the text pid is 0021
allocate demux
disable teletext subtitles
decoder state: play, vpid=513, apid=101
DMX_SET_PES_FILTER(0x201) - pcr - ok
DEMUX_START - pcr - ok
DMX_SET_PES_FILTER(0x65) - audio - ok
DEMUX_START - audio - ok
AUDIO_SET_BYPASS(0) - ok
AUDIO_PAUSE - ok
AUDIO_PLAY - ok
Video Device: /dev/dvb/adapter0/video0
demux device: /dev/dvb/adapter0/demux0
VIDEO_SET_STREAMTYPE 1 - ok
DMX_SET_PES_FILTER(0x201) - video - ok
DEMUX_START - video - ok
VIDEO_FREEZE - ok
VIDEO_PLAY - [EPGC] next update in 2 sec
ok
DMX_SET_PES_FILTER(0x21) - ttx - ok
DEMUX_START - ttx - ok
VIDEO_SLOWMOTION(0) - ok
VIDEO_FAST_FORWARD(0) - ok
VIDEO_CONTINUE - ok
AUDIO_CONTINUE - ok
not pauseable.
[AutoRes] service changed
+ 1/1 TID 00
done!
PATready
use pmtpid 0a9b for service_id 5217
no version filtering
0a9b: 02 52 17 00 00 00
mask: ff ff ff 00 00 00
mode: 00 00 00 00 00 00
doing version filtering
0000: 00 00 00 05 00 00
mask: ff 00 00 3f 00 00
mode: 00 00 00 3e 00 00
[SEC] set dynamic current limiting
+ 1/1 TID 02
done!
eventNewProgramInfo 0 0
have 1 video stream(s) (0201), and 1 audio stream(s) (0065), and the pcr pid is 0201, and the text pid is 0021
decoder state: play, vpid=513, apid=101
[eDVBCAService] new service 1:0:19:5217:C99:3:EB0000:0:0:0:
[eDVBCAService] add demux 0 to slot 0 service 1:0:19:5217:C99:3:EB0000:0:0:0:
caid '0100' is in caid list of slot 1... so use it
[eDVBCIInterfaces] gotPMT
demux 0 mask 01 prevhash 00000000
doing version filtering
0a9b: 02 52 17 11 00 00
mask: ff ff ff 3f 00 00
mode: 00 00 00 3e 00 00
action -> InfobarShowHideActions toggleShow
+- 1/2 TID 4e
sdt update done!
[AutoRes] determineContent
[AutoRes] switch deinterlacer mode to auto
[AutoRes] new content is 1920x1080i25
[AutoRes] determined videomode 1080i
++ 2/2 TID 4e
done!
doing version filtering
0012: 4e 52 17 17 00 00
mask: ff ff ff 3f 00 00
mode: 00 00 00 3e 00 00
[EPGC] start caching events(1311287794)
[eDVBLocalTimerHandler] diff is 0
[eDVBLocalTimerHandler] diff < 120 .. use Transponder Time
[eDVBLocalTimerHandler] not changed
[EPGC] abort non avail schedule other reading
[EPGC] abort non avail viasat reading
[EPGC] abort non avail mhw reading
nr_read 120 nr_write 421
sum 541 prev_sum 108
hdd was accessed since previous check!
[IDLE] 0 600 False
[EPGC] nownext finished(1311287809)
no ancillary data in audio stream... abort radiotext pes parser
action -> InfobarInstantRecord instantRecord
self.recording: []
action -> WizardActions back
pre:
[]
action -> InfobarSubserviceSelectionActions DeliteGpshow
allocating new converter!
action -> WizardActions down
unknown action WizardActions/down! typo in keymap?
action -> WizardActions down
unknown action WizardActions/down! typo in keymap?
action -> WizardActions ok
Looking for embedded skin
screen cleanup!
screen cleanup!
action -> ColorActions yellow
Looking for embedded skin
Traceback (most recent call last):
File "/usr/lib/enigma2/python/Plugins/Extensions/FanControl2/plugin.py", line 325, in DoTest
setVoltage(self.id,SaveAktVLT)
File "/usr/lib/enigma2/python/Plugins/Extensions/FanControl2/plugin.py", line 115, in setVoltage
f = open("/proc/stb/fp/fan_vlt", "w")
IOError: [Errno 2] No such file or directory: '/proc/stb/fp/fan_vlt'
(PyObject_CallObject(<bound method FanControl2Test.DoTest of <class 'Plugins.Extensions.FanControl2.plugin.FanControl2Test'>>,()) failed)
getResolvedKey config.plugins.crashlogautosubmit.sendAnonCrashlog failed !! (Typo??)
resolve: resolve ${sysconfdir}/enigma2/settings
resolve: -> /etc/enigma2/settings
getResolvedKey config.plugins.crashlogautosubmit.addNetwork failed !! (Typo??)
resolve: resolve ${sysconfdir}/enigma2/settings
resolve: -> /etc/enigma2/settings
getResolvedKey config.plugins.crashlogautosubmit.addWlan failed !! (Typo??)
resolve: resolve ${sysconfdir}/enigma2/settings
resolve: -> /etc/enigma2/settings
]]>
</enigma2crashlog>

 

[Dzoni]

I did not think that Your LNB is not correct, I said that is in conflict with vu+box. I had many sitation like Your. All workeed ok on my dm500,when I bought dm800 that wasn't work.... How much cm is Your satellite dish ?

 

[ab9adr]

Same problem in my vuplus robbedoesje tried also different images and different dishs :s

 

[Robbedoesje]

The dimensions of the dish are 47,5 cm, 26 cm, 7,5 cm. (LxWxD) Yes its a square dish which equals a 60cm dish http://i-do-it.co.kr/
This in combination with a Stab HH90 Rotor which is equal to a Stab HH90s (special for Selfsat because of a smaller pole to attach)

I think its not the dish as everything worked without problems on the Homecast. Also it works perfectly smooth, as long as my VU Solo is turn on.

Attached the full specs of the dish/lnb.

 

[Robbedoesje]

Same problem in my vuplus robbedoesje tried also different images and different dishs :s

And you have a motorized installation as well? If so, perhaps it is a bug in Enigma 2? I have to confess I never tried my installation on another Linuxbox running Enigma 2. I had a WaveFrontier dish before so no motor.

 

[ab9adr]

And you have a motorized installation as well? If so, perhaps it is a bug in Enigma 2? I have to confess I never tried my installation on another Linuxbox running Enigma 2. I had a WaveFrontier dish before so no motor.

Yes it is and I use a vbox. Didn't try too with a linux box just when I use my old receiver it works great

 

[Robbedoesje]

Yes it is and I use a vbox. Didn't try too with a linux box just when I use my old receiver it works great

Hmmm, maybe VU+ isn't fully supporting motorized configurations? All I can do is speculate as I tried as far as I know everything.... I hope one of the experts here on the forum can shine their lights on our issue....

 

[ab9adr]

Hmmm, maybe VU+ isn't fully supporting motorized configurations? All I can do is speculate as I tried as far as I know everything.... I hope one of the experts here on the forum can shine their lights on our issue....

I don't think so because when I don't use my vbox and connect my lnb directly to the stb the problem is the same. Did you try to do the same ? I think that is a hardware problem.

 

[Dzoni]

Hmmm, maybe VU+ isn't fully supporting motorized configurations? All I can do is speculate as I tried as far as I know everything.... I hope one of the experts here on the forum can shine their lights on our issue....

The easiest answer you get if You test Your vu+ box on other sattelite motor configuration (some friend...) and if it work on other installation,the answer comes by itself where is a problem...

 

[tobler]

with a duo (for sure the same as the solo for the rotor setup/use) np with a usals setup, never a prob

the "drive to zero" and all the rest setup is useless if you using usals: it must works
with the right setup, is enough to setup correctly lat long (and dish correctl mounted), no other devices that use the same motor, and the motor must be in a fully working state
no need to use further setup/tests

 

[Robbedoesje]

with a duo (for sure the same as the solo for the rotor setup/use) np with a usals setup, never a prob

the "drive to zero" and all the rest setup is useless if you using usals: it must works
with the right setup, is enough to setup correctly lat long (and dish correctl mounted), no other devices that use the same motor, and the motor must be in a fully working state
no need to use further setup/tests

Well the setup is working in a fully state. Except when coming out of standby, with USALS and disecq.

 

[Robbedoesje]

The easiest answer you get if You test Your vu+ box on other sattelite motor configuration (some friend...) and if it work on other installation,the answer comes by itself where is a problem...

unfortunately I don't have any friends with a sat installation as Holland has cheap ass cable tv offering large channel packages. Even fiberglass in many regions....

 

[ab9adr]

The easiest answer you get if You test Your vu+ box on other sattelite motor configuration (some friend...) and if it work on other installation,the answer comes by itself where is a problem...

I tried it with an other sattelite motor configuration which I have and it's the same problem

 

[Robbedoesje]

with a duo (for sure the same as the solo for the rotor setup/use) np with a usals setup, never a prob

the "drive to zero" and all the rest setup is useless if you using usals: it must works
with the right setup, is enough to setup correctly lat long (and dish correctl mounted), no other devices that use the same motor, and the motor must be in a fully working state
no need to use further setup/tests

May I ask which rotor ur using?

Sent from my GT-I9100 using Tapatalk

 

[tobler]

since the old stab 120 was broken (goes crazy with positioning), in the last years i'm using a sm3d22 (not sure at 100% i need to verify it in the dish location)

looks perfect as this:

 

[Robbedoesje]

since the old stab 120 was broken (goes crazy with positioning), in the last years i'm using a sm3d22 (not sure at 100% i need to verify it in the dish location)

looks perfect as this:
View attachment 3917

So in my case, what could be the cause if we look at my crashlog? Failing settings in the VU or in the Rotor? As it says, 23,5 not to be found in table. Rotor is new as of 7 months old, works perfect on other device.......

Sent from my GT-I9100 using Tapatalk

 

[tobler]

just tested on my
and i have the same warning, so it is normal:

Entry for 19,2? not in Rotor Table found... i try gotoXX?