Posts by joeuser

It seems there is no simple solution to your dilemma. If I understand your configuration correctly, you have a single motorized dish with the main being a twin lnb with one output connected to the motor, then to your tuner A. The second output and a second and third lnb connected through a switch to tuner B? After you tune to something on 23, the dish has moved, but when you then try to tune to something on 28, the "logic" of enigma is that tuner A is on 23 and 28 is available on tuner B, so it tries to use tuner B, which of course does not work because it is now also pointed at 23.

If you make tuner A preferred, then if you try to tune something from sats 19 or 13, it will use tuner A and move the dish, which will limit you to that one sat. (All lnbs for tuner B will be pointed at wrong sats relative to your config.)

If you make tuner B preferred, then when you tune something from 28, it will use tuner B, which will basically create the same situation you currently have.

A few possible workarounds:

Change setup so tuner A is "positioner, selecting satellites" then select all sats you watch except 19 and 13 (do not delete!) Then set preferred tuner to tuner A. Only downside is you won't be able to watch/record two things on 19 and or 13 at the same time - maybe not a big deal for you??

If you do not record often from 19 or 13, you can try setting the preferred tuner to auto and set preferred recording tuner to tuner A. Then if the sat is "stuck" at 23, if you try to record something to on 28, it "should" try to use tuner A and move the dish back to 28. Downside is if you record from 19 or 13 it will move the dish, making 28 unusable until the recording finishes. One workaround for this is to always start a recording on 28 just before recording something on 19 or 13 - this will lock the dish on 28 and force the recordings for 19 and 13 to use tuner B. After the recording on 19/13 starts, the recording on 28 can be stopped, freeing up the dish.

If you leave your setup as is, when "stuck" on 23, choose a channel on 28 and start an instant recording, then immediately choose another channel on 28. This "should" lock tuner B for recording on 28 and force the second 28 channel to use tuner A, causing the dish to move back to 28.

There may be a way to use the advanced setup on tuner B, but I can't think of one off the top of my head....

Is the IP address of the duo2 conflicting with another stb/pc/phone/tablet/etc??? Or even the router itself??

Quote from biggest1d

I can push it to £800 and just satellite only. Not interested in the bits n bobs as long as it's stay with and new tech coming out in the next few years.
Thanks

Just a few thoughts...

You did not mention what you have now and why you want to upgrade.

Do you watch/record multiple channels at the same time? Makes a difference on the number of tuners. Also, depends on sat setup - multiple LNBs / multiple LNB outputs? To take real advantage of multiple tuners, you need at least one of the above.

Single TV, multiple TVs? (possibly using existing stb on another TV and sharing with new receiver..)

Streaming to PC/tablet/phone? - affects how many tuners you will need for simultaneous use.

Do you do lots of recording (and keeping for some time?) HD or SD? Makes a difference on what size disk you will need.

As far as, "new tech coming out" that is 4k, but really no sense in trying to plan for that now.

With my basic setup, it is just stored in the file (not folder) /etc/enigma2/settings. But I certainly never tried to setup 26 lnbs. :)

Have you tried powering it on from the back while holding the "menu" button on the front? It is strange that the numbers on the front would change without anything being sent to the rs-232 port.

Quote from stevejo

As far as im aware you wont get any image stable on an amiko not even the original image but its the box thats the issue not the software

No, it is the software, not the box. The problem is the developers concentrate on the higher end boxes and spend very little time making sure their images/plugins work on sh4 based boxes. A good example was the "judder" problem that was largely ignored because it was a "hardware" problem and in the end a "software" fix solved it. More recently the problem with the multi-tuners was a problem with pti.ko, not the hardware. I have had an HDMU image (with a modded pti.ko) running for almost two months now without and problems and without any reboots. Although, I do not use many plugins, which definitely helps. So, the only "issue" with the box is the lack of good developer support. I am not necessarily criticizing all the developers, I completely understand they have limited time to work for free. But blaming hardware for software problems only makes them look foolish when a software fix comes around.

I posted an hour ago and there was some brief message saying "your post will be available....?????" didn't catch the rest. Guessing the post is gone, will post again later tonight if it doesn't show up....

- - - Updated - - -

Actually, I found an old upgrade guide for the spark7111 which will work the same for the 7162. It covers upgrading by USB or TFTP for spark AND enigma2. Also included is how to upgrade the uboot from the serial port if it turns out you need to do that. In the spark rescue image there is an update uboot image.

- - - Updated - - -

Also see this post: http://linuxsat-support.com/showthread.php?t=20313

paul, TFTP can be used to flash any image. While for spark it can be done through the front panel buttons, enigma2 requires using the serial interface. The example I gave was for spark - and the reason I suggested "rescue" is that he complained that he thinks the image is preventing him from re-flashing. If the image changed some of the environment variables, flashing a rescue image may help.

tommybo, can you boot to spark? If not, your environment has probably been corrupted (or changed purposely by some image.)

What image do you have loaded?

Can you telnet to the box? If so, you can try the following commands to see what has been done:

Quote

SPARK7162:~# fw_printenv
Can't open /dev/mtd7: No such device
SPARK7162:~# insmod i2s
SPARK7162:~# fw_printenv
bootdelay=3
baudrate=115200
yw_version=YW_1.1.005
board=pdk7105
monitor_base=0
monitor_len=0x00100000
load_addr=0x80000000
HOSTNAME=LINUX7167
ethaddr=00:80:E1:12:06:38
netmask=255.255.255.0
bootcmd_spark=nboot.i 0x80000000 0 0x00100000 ;bootm 0x80000000
bootcmd_enigma2=nboot.i 0x80000000 0 0x18000000 ;bootm 0x80000000
kernel_base_spark= 0x00100000
kernel_base_enigma2= 0x18000000
kernel_len_spark= 0x00a00000
kernel_len_enigma2= 0x00800000
erase_env=mw.b $load_addr 0 0x20000;eeprom write $load_addr 0x000a0000 0x20000
.
.
.
.

Display More

You can post the results here.

It is also possible by TFTP - there are some tutorials out there on how. A quick search for "alien tftp rescue" found this:

Quote

1.Install TFTP tools [csicotftp11.rar] to your PC

2.Set your PC IP addr to [192.168.40.19]

3.connect your PC to STB by LAN, now we only support LAN, do not support WLAN

4.Set default booting system to [spark]

Upgrade Step:
1.copy [mImage] and [userfsub.img] to a folder called spark of your PC, for example [C:/spark]

2.select folder in TFTP tools

3.Keep Pressing [OK] Button in Front Panel, then power on STB.

4.After 5 seconds you will see [Forc] in LED, release [OK] button and press [align=right] Button.

5.If everything OK, You will see [T LD] shining in LED and you will see some debug information in TFTP Server, like “Mon Oct 25 14:02:36 2010: Sending 'mImage' file to 192.168.40.19 in binary mode Mon Oct 25 14:02:39 2010: Successful. Mon Oct 25 14:02:50 2010: Sending 'userfsub.img' file to 192.168.40.19 in binary mode Mon Oct 25 14:03:33 2010: Successful.”

6.if upgrade success, You will see [SUCC] and STB reboot automatically.
If upgrade not finishes in 5 minutes, then there must be something wrong, please check your configuration and re-try.

Display More

I have not tried it myself, but I have heard it works well.

You may also need to connect a serial cable to further debug your problems - also lots of tutorials out there for this.