Ultimo owner to be

[parkher]

Please don't laugh,
but what is this always blinking thing both on the Ultimo display and on the info bar? It looks like this (O) and is always blinking on all the channels, FTA or encrypted.
I would like it to stop blinking so that the RECORDING blinking is better noticeable, bad enough that it is not red on the Ultimo display.
I'm guessing it is ViX-specific.

[Rob van der Does]

Please don't laugh,
but what is this always blinking thing both on the Ultimo display and on the info bar? It looks like this (O) and is always blinking on all the channels, FTA or encrypted.
I would like it to stop blinking so that the RECORDING blinking is better noticeable, bad enough that it is not red on the Ultimo display.
I'm guessing it is ViX-specific.

If it looks like the attached icon: that means updates are available.

[parkher]

Yes, it looks exactly like this.
I see, from build 124 to 132.
Thanks.



Back to the remote: I think I somehow switched the Ultimo remote both to 1 and 2 simultaneously: even though Ultimo currently has code 2 and does not work with the Duo remote,
the Ultimo remote works with both Ultimo and Duo, and the Duo remote works with Duo only.
I did this: 2+7 then Help then 0002.
The same trick worked when switching the remote from 2 to 1.
So why is it interfering with Duo after converting back to 2.

[Rob van der Does]

Back to the remote: I think I somehow switched the Ultimo remote both to 1 and 2 simultaneously: even though Ultimo currently has code 2 and does not work with the Duo remote,
the Ultimo remote works with both Ultimo and Duo, and the Duo remote works with Duo only.
I did this: 2+7 then Help then 0002.
The same trick worked when switching the remote from 2 to 1.
So why is it interfering with Duo after converting back to 2.

Hmmm, this puzzles me. Looks like you did it all OK.
I can only suggest to try to set the R/C for the Ultimo to e.g. 3 (and the Ultimo itself as well of course) and see what happens.

[parkher]

with 3 - the same thing, also controls also Duo.
Maybe I just did not notice, maybe it was always interfering with Duo?
Maybe Duo accepts any codes?

[parkher]

I am running into new problems with Ultimo.

1. How to set up correctly a motorized system with two LNBs for the 2nd lnb?

Where diseqc 1.2 + diseqc 1.0 input 2 are used. I need this for circular polarization.
The only way it works is if I connect the dish to my old Octagon and then loop to Ultimo. Then I can switch to the channel with Octagon and Ultimo also sees it.
So Octagon has no problem with selecting that 2nd lnb.
Ultimo is ignoring the diseqc 1.0 command, it seems.
Or I don't know how to configure it correctly. It is not enough to use committed command Input 2 in diseqc 1.2 mode

Another thing: how to add some correction to USALS without saving the actual position and ignoring USALS altogether.
On Octagon it is very simple, you may change the position of the satellite, use 27.9 instead of 28.2, for example.
Here, I see only a possibility to change the position of the dish - which is not as clear.

[Larry-G]

Another thing: how to add some correction to USALS without saving the actual position and ignoring USALS altogether.
On Octagon it is very simple, you may change the position of the satellite, use 27.9 instead of 28.2, for example.
Here, I see only a possibility to change the position of the dish - which is not as clear.

you can ever so slightly adjust the co-ordinates ( longitude / latitude ) to achieve this.

[parkher]

Yes, and in order to adjust just for one satellite and not for all at once, it is necessary to use separate lnb numbers for each satellite.

I have a problem with diseqc 1.2 + 1.0 input 2. I guess, the correct command is AB, but still not working.
Ok, maybe AB is working, I finally was able to scan one transponder correctly without any help from Octagon.
Because the 2nd lnb is off center, it is even more difficult to tie it to USALS on Ultimo.

And I had another issue - still to investigate:
I see the results of MgCamd correctly working with tuner A but not with tuner B even on the same satellites and channels.

[Rob van der Does]

with 3 - the same thing, also controls also Duo.
Maybe I just did not notice, maybe it was always interfering with Duo?
Maybe Duo accepts any codes?

No: I definitely don't have this problem. I have a DUO (code1), UNO (code 2), Ultimo 1 (code 3) and Ultimo 2 (code 4): there's no interference at all. That's the whole point of having different codes.

In short: I have no clue why your DUO obeys all codes.

[parkher]

I also thought that initially everything was ok. Only after I did 2+7 -> Help -> 0001 and then 2+7 -> Help 0002 - only after that the remote began to interfere with Duo.
So I need to reprogram the remote somehow better.
There is no question, though, that it is sending code 2 (now 3) to Ultimo, and it seems, also code 1 to Duo....

[Rob van der Does]

I also thought that initially everything was ok. Only after I did 2+7 -> Help -> 0001 and then 2+7 -> Help 0002 - only after that the remote began to interfere with Duo.
So I need to reprogram the remote somehow better.
There is no question, though, that it is sending code 2 (now 3) to Ultimo, and it seems, also code 1 to Duo....

You can try:
In case you want to reset the RCU,
Press Sequence: <<1 + 6>>, <9>, <9>, <6>

1. Press 1and 6 for three seconds until LED is on.
2. Press <9>, <9>, <6>.
3. This will reverse the RCU into no configuration state.

[Larry-G]

I'm the same as rob here.
I have 3 receivers stacked on top of each other.

Uno ( running on code 4 )
Duo ( using default code 1 )
Ultimo ( using default code 2 ).

I use a harmony 650 for the Duo and Ultimo ( not really a fan of the ultimo remote so i took the batteries out and re-boxed it ). Using the default Uno remote ( This is the one Vu now ship with all Duo's, Solo's and is sold individually as a universal remote ).

I also have x2 Duo remote's both the later black one and the earlier white one, and none of these remote's interferes with the other units when set up for a specific machine.

[parkher]

No, 1-6 9 9 6 did not help either. Still working with Duo.
Maybe Duo somehow accepts all the codes?

Maybe it was fixed in later drivers of Duo?
I see that my OpenPLi image on Duo is from 2010.
I think I will switch to the latest ViX and see what happens with the remote then.

As to switching to ViX:

- I understand that I need a new bootloader?
Flashing it on Duo is exactly the same as flashing an image?

- I hope that all the recorded stuff on the hard drive will not be destroyed.
Had there been such cases when the contents of the hard drive disappeared after flashing a new image?

[Huevos]

Where diseqc 1.2 + diseqc 1.0 input 2 are used. I need this for circular polarization.
The only way it works is if I connect the dish to my old Octagon and then loop to Ultimo. Then I can switch to the channel with Octagon and Ultimo also sees it.
So Octagon has no problem with selecting that 2nd lnb.
Ultimo is ignoring the diseqc 1.0 command, it seems.
Or I don't know how to configure it correctly. It is not enough to use committed command Input 2 in diseqc 1.2 mode

Another thing: how to add some correction to USALS without saving the actual position and ignoring USALS altogether.
On Octagon it is very simple, you may change the position of the satellite, use 27.9 instead of 28.2, for example.
Here, I see only a possibility to change the position of the dish - which is not as clear.

Just clarify... You have a fixed universal linear LNB in the breach of a USALS controlled dish, and on the same dish you have a second LNB for circular polarisation in offset configuration. Is that correct? This is more or less how I have my C-band LNBs set up. If you are having trouble configuring this I can run you through it.

On the DiSEqC 1.0 switch. Inputs 1-16 in the tuner menu are for DiSEqC 1.1 uncommitted switches. Committed AA, AB, BA, & BB correspond to ports 1-4 on your DiSEqC 1.0 switch. For use with a positioner set DiSEqC mode to 1.2.

[Rob van der Does]

I see that my OpenPLi image on Duo is from 2010.

That could be the case indeed. No idea what images & drivers were so long ago!
Update!

As to switching to ViX:

- I understand that I need a new bootloader?
Flashing it on Duo is exactly the same as flashing an image?

Yes, but is ready in a split second.

- I hope that all the recorded stuff on the hard drive will not be destroyed.
Had there been such cases when the contents of the hard drive disappeared after flashing a new image?

Nope; as long as you dont manually initialize the HDD in any stage.