Gigablue & motor issues

icz999

Newbie
Hi all,

I"ve moved back to my e2 box today. Thanks to help on this forum I got everything setup and working this AM

This AM

- Latest version of OSCAM was installed and working
- Sorted my WebIF issues and the latest version of Oscam allowed me gain access to the webif of Oscam - something that never worked prior.
- Installed the latest Oscam via putty
- Motor was moving freely across 28.2, 16e and 42e = no issue

Problem

I did a manual scan on 42.e which worked and brought around 500 channels. I cleared picture on some channels. Since then, it won't move the motor to any sat.

I've done a factory reset, resubmitted my long/lat and no matter what I can't get the dish moving. I think it got stuck and some commands did something weird and it didn't know where the dish was.

Some notes

- I'm in Tuner B as the gigablue for some reason since day dot didn't move the motor on tuner A
- I've done a factory reset, and I believe that the dish has gone to 0 (stuck on 0)
Doesn't appear to move on GotoX or goto0 commands

My long and lat appear to be fine...

A bit of a loss on this one!

Any help would be much appreciated

Thanks as always!
 
Stop doing factory resets as can have issues on some boxes.
The question will be how did you setup the tuners for multiple sats as even i have forgotten but did have a list of sats .
Might have to do screenshots so others can say you missed this or that.
 
I had this problem with a technomate Tm motor but with my Xtrend ET8500, It did not like going all the way to 42 east. I can not remember which but either a H or V channel on 28.2 east got it moving again but would eventually get stuck again. In the end i just got another motor. I think when you Factory reset the box it wipes the enigma2 folder. Maybe reflash and try different Horizontal and Vertical channels on 39 east and 28 east to get it moving again.

 
Why not just flash a new image and install a channel list from the settings menu in the plugins menu.

Could do that. It's got OpenVIX on it today. What would you recommend?

I do think that I may have an issue with the motor. The Viark had issues and it would get stuck relatively often and it appears to be the same with the e2.
 
With regards to the mention of tuner letters, if your motor is physically attached to tuner A, why would tuner B move it?

For tuner configuration to be correct, software config must match hardware config.

It may be beneficial to draw a sketch of your dish/LNB/wiring and describe it. As well as describe the tuner configuration for each tuner.
 
With regards to the mention of tuner letters, if your motor is physically attached to tuner A, why would tuner B move it?

For tuner configuration to be correct, software config must match hardware config.

It may be beneficial to draw a sketch of your dish/LNB/wiring and describe it. As well as describe the tuner configuration for each tuner.

We had this issue when the installer did the installation a couple of years back

Apparently it appears the gigabit UE has issues with tuner A and Tuner B only moves the motor at least in my case…
 
With regards to the mention of tuner letters, if your motor is physically attached to tuner A, why would tuner B move it?

For tuner configuration to be correct, software config must match hardware config.

It may be beneficial to draw a sketch of your dish/LNB/wiring and describe it. As well as describe the tuner configuration for each tuner.
Sure if i remember correctly there is something about tuner a and tuner b on the gigablue ue that the motorised dish needs to be connected to tuner b. I think there is something in the manual about it. I know the guy who fitted the system and he has years of experience but this receiver was giving odd results until the motor was connected to slot b. That's if i can remember correctly. Out of interest @icz999 what motor did you buy for him to install?
 
If the motor is unresponsive, a user on another forum used a non-enigma2 receiver to move it. Or the buttons on the motor.

I presume f-plug has been double checked for loose strands causing a short etc.
 
If the motor is unresponsive, a user on another forum used a non-enigma2 receiver to move it. Or the buttons on the motor.

I presume f-plug has been double checked for loose strands causing a short etc.
He has a viark sat 4k he could use that to try drive the dish and free it off.
 
Sure if i remember correctly there is something about tuner an and tuner b on the gigablue ue that the motorised dish needs to be connected to tuner b. I think there is something in the manual about it. I know the guy who fitted the system and he has years of experience but this receiver was giving odd results until the motor was connected to slot b. That's if i can remember correctly. Out of interest @icz999 what motor did you buy for him to install?
He supplied a new motor. TM. I’ll get the exact model shortly it was brand new.
 
Morning folks,

Some additional info that (hopefully) will help as I've thought about this

The e2 box was on 16e clearing channels
I went into positioner setup and asked it to move to 28.2 east (not scan, but on e2 positioner setup)
The dish moved - but it moved to an incorrect location (I've found out this morning) that the location it moved to is 19.2e


Current state

I've plugged the viark in - and it's not moving it from 19.2e i.e. i tried to move it to 16e but it's not moved
I've scanned in 19.2e and channels are opening - so confirms that 19.2e is where the dish landed
I could probably do a factory reset and re-insert my long/lat and i'm sure it will eventually move and lock into some sat's although this wash/rinse repeat makes me feel that something deeper is wrong
I had setup the e2 box yesterday and it is working and moving absolutely fine - it was only when I moved it to turksat that it seemed to get confused and not move back to 16e

Photos

My Gallery — Postimages

- Dish lockoed on 19.2e
- Motor photos

Next steps

I looked behind the motor but can't see any colours/lights?
As I'm locked in at 19.2e and I want to watch the United game at noon I may just keep it there...
Considering when the dish was at 16e and I asked it to move to 28.2 in the positioner setup - does this make anyone feel that my long lat etc is wrong?

Photo of my e2 setup (does this directionally look correct?)

I've added my dishpointer coordinates as a FYI

Photo of e2 setup & what dishpointer says for long/lat

My Gallery — Postimages
 
Morning folks,

Some additional info that (hopefully) will help as I've thought about this

The e2 box was on 16e clearing channels
I went into positioner setup and asked it to move to 28.2 east (not scan, but on e2 positioner setup)
The dish moved - but it moved to an incorrect location (I've found out this morning) that the location it moved to is 19.2e


Current state

I've plugged the viark in - and it's not moving it from 19.2e i.e. i tried to move it to 16e but it's not moved
I've scanned in 19.2e and channels are opening - so confirms that 19.2e is where the dish landed
I could probably do a factory reset and re-insert my long/lat and i'm sure it will eventually move and lock into some sat's although this wash/rinse repeat makes me feel that something deeper is wrong
I had setup the e2 box yesterday and it is working and moving absolutely fine - it was only when I moved it to turksat that it seemed to get confused and not move back to 16e

Photos

My Gallery — Postimages

- Dish lockoed on 19.2e
- Motor photos

Next steps

I looked behind the motor but can't see any colours/lights?
As I'm locked in at 19.2e and I want to watch the United game at noon I may just keep it there...
Considering when the dish was at 16e and I asked it to move to 28.2 in the positioner setup - does this make anyone feel that my long lat etc is wrong?

Photo of my e2 setup (does this directionally look correct?)

I've added my dishpointer coordinates as a FYI

Photo of e2 setup & what dishpointer says for long/lat

My Gallery — Postimages
You might have problems watching utd on 19.2 because there unwatchable at the moment, on Sky anyway
 
Back
Top