usuals available?

[Gastone]

is it possible to have usals (gotox) working on neutrino?
neutrino looks good (and thanks to all the developpers) and i don't understand because a feature as important as that is not added to it

thanks in advance for every answer
and thanks to all the cvs (enigma and neutrino) developpers
regards

[seife]

Send me hardware (usals rotor, dish and LNB), then I can implement / test it.

It is no fun to implement something you have no use for

[Gastone]

yep yep yep, that's right!

thanks for the reply (and your additions in cvs)
i hope that some developpers has that hw, and add, in the future that protocol

best regards

[rhabarber1848]

If I am reading the changelogs of the Coolstream firmware correctly
they already seem to have some kind of usals support

There some DiseqC changes too as few usals rotor types
wasnt work proper.

So why reinvent the wheel? Just wait for their sourcecode

[Gastone]

i tried a search about the gotox protocol
here : http://www.eutelsat.com/satellites/4_5_5.html in the bus specification.pdf page 17
i found that MAYBE is enough send a 5 byte positioning target ( i dunno the format) in the address 6E, with the "switch channel" command and wait a channel lock (without lock must be possible a new switch), a good idea can be a "moving dish" message on the screen, better if with the target satellite position

i think that the positioning target is (sat position, from the satellites list) - (recevier longitude * a unknow little calculation with latitude, both setup in the netrino gui interface)
according to the stab site http://www.stab-italia.com/mostradivisione.php?id=2 :
here as an example
rome
lat 41,9
long 12,5

19.2E=+7.5°
13E=+0.6°
30W=-46.9°

i try to give some input, maybe someone can add it




edit:
from http://www.eutelsat.com/satellites/4_5_5.html Positioner Application Note (PDF, 245 KB) page 11

3.10. “Goto Angular Position (degrees)”
Command byte ‘6E’ is not yet fully defined, but will normally use two data
parameter bytes. At present the command is defined for control of a terrestrial
antenna rotator, e.g. for the azimuth of a horizontally-directed Yagi or
microwave antenna.
The high nibble of the first data byte indicates how the remainder of the
angular data is to be interpreted. The values ‘F’, ‘0’ and ‘1’ are allocated to
support full rotation in a horizontal plane (e.g. for terrestrial sources). The
nibble ‘0’ references the angle defined in the remainder of the data to
North (0°), ‘1’ adds 256° clockwise to the angle and ‘F’ subtracts 256°. The
low nibble of the first data byte indicates the clockwise rotation angle in
increments of 16°. Thus a first data byte of ‘00’ defines due North, ‘01’
defines an azimuth of 16° Εast, ‘0A’ (hexadecimal) an azimuth of 160°, and
‘10’ (hexadecimal) a rotation of 256° clockwise from north.
The high nibble of the second data byte defines the angle in degrees, and the
low nibble indicates the fractional part of a degree, if required. Note that the
low nibble is a true binary fraction, and is not Binary Coded Decimal. Thus
the most significant bit (of the low nibble) defines half a degree, the next bit
a quarter degree and the least significant bit a sixteenth. If the Tuner-receiver
User-interface is to show a decimal value, then the ten closest fractional
values can be employed, as given in the following table.

[Gastone]

IF someone want to try a test, without any gui/automation, only using and executing a manually configured script, i'm available

[seife]

Well, I'm usually not implementing stuff that I don't have any use for. Or good friends of mine. Or that my boss wants me to implement. Or which is at least an interesting problem.

the gotoxy spec does not meet any of those criteria, so sorry, you will probably have to do that by yourself ;-)

[Gastone]

bad reply but thx the same for it

[Gastone]

i found this link, http://www.coolstreamtech.de/support/sv ... ublic_svn/
someone can add that usuals protocol to the neutrino cvs?

i really don't understand why a so used protocol isn't supported at this time

thanks to any developpers, even if they doesn't add it too

ps: i see that the quote text was not correct in the previous post, i try to re-send it:

Code: Alles auswählen

3.10. “Goto Angular Position (degrees)”
      Command byte ‘6E’ is not yet fully defined, but will normally use two data
      parameter bytes. At present the command is defined for control of a terrestrial
      antenna rotator, e.g. for the azimuth of a horizontally-directed Yagi or
      microwave antenna.
      The high nibble of the first data byte indicates how the remainder of the
      angular data is to be interpreted. The values ‘F’, ‘0’ and ‘1’ are allocated to
      support full rotation in a horizontal plane (e.g. for terrestrial sources). The
      nibble ‘0’ references the angle defined in the remainder of the data to
      North (0°), ‘1’ adds 256° clockwise to the angle and ‘F’ subtracts 256°. The
      low nibble of the first data byte indicates the clockwise rotation angle in
      increments of 16°. Thus a first data byte of ‘00’ defines due North, ‘01’
      defines an azimuth of 16° Εast, ‘0A’ (hexadecimal) an azimuth of 160°, and
      ‘10’ (hexadecimal) a rotation of 256° clockwise from north.
      The high nibble of the second data byte defines the angle in degrees, and the
      low nibble indicates the fractional part of a degree, if required. Note that the
      low nibble is a true binary fraction, and is not Binary Coded Decimal. Thus
      the most significant bit (of the low nibble) defines half a degree, the next bit
      a quarter degree and the least significant bit a sixteenth. If the Tuner-receiver
      User-interface is to show a decimal value, then the ten closest fractional
      values can be employed, as given in the following table.

[seife]

i really don't understand why a so used protocol isn't supported at this time

I explained that in my first answer.

[Gastone]

not the rotor
but np for a little subscription, if it is possible
(i'm an enthusiast, nothing to do with the sat business)

[Gastone]

well, the enigma1 support seems to be, unlucky, ended (and like always, many thanks to all the developpers)
any chance to still use it with neutrino using a rotor?

thanks for every reply, better if with a rotor addition

regards

(seife please..)

[Gastone]

after some years, is it possible to have the usuals protocol available on a old dreambox using neutrino?

i cannot test the newest neutrino images until they are not compatibles with the only working usuals one (enigma)

thnaks in advance (and past ) for every answer
http://www.tuxbox-cvs.sourceforge.net/f ... 18&t=48900

[Gastone]

one year after:
so no chance until a rotor/sat/lnb gift?


(that protocol looks so simple to add... with a good knowledge of the neutrino "os")

[Renwich]

The UKCVS guys have got Usals implemented in Neutrino now for the DM500,

Change log https://www.assembla.com/code/ukcvs/sub ... ngesets/30

Discussion on ukcvs.org

http://www.ukcvs.org/Forums/neutrino/25 ... trino.html

[seife]

well, they backported it from neutrino-hd to be more precise...

[Renwich]

Yep admittedly, but its now in and working nicley

[Satsearching]

The point is, some complain that code and work is not made public by some groups.

We are amateurs, but we make public all work.

Shame tux don't help us

[rhabarber1848]

(merged both threads)

patch ported to Tuxbox CVS, only compile tested: EDIT: committed patch to CVS
Thanks to LraiZer.

[rhabarber1848]

38 downloads and no feedback I do not have a satellite dish so I can not test it...
It would also be interesting to know if Neutrino still works with non-usuals setups.

[rhabarber1848]

committed patch to CVS

Happy testing

[Gastone]

WOWWWWW
readed it just now in the cvs mailing
and promptly entered in the board for say thanks
a prob: in these days, very heavy work and really few time
but for sure, i'll give a look for how to compile the neutrino actually and i'll test it
(if i ask not too much, if possible to have a dm7000 "basic" cvs neutrino img somewhere it can speedup the test.. sorry for this really bad request..)

thx

[Gaucho316]

Mir ist aufgefallen, dass mit einem der Commits vom 01.08.2011 ein Speicherleck in der Klasse CScanSetup produziert wurde. Der folgende Patch berichtigt das.

Edit: Ach Mist, da fehlt noch etwas, weil toff zweimal benutzt wird. Ich aktualisiere den Patch gleich mal.

Edit: So, nun aber ...

Link entfernt, da Patch im CVS

[rhabarber1848]

ein Speicherleck in der Klasse CScanSetup produziert wurde. Der folgende Patch berichtigt das

committed: http://article.gmane.org/gmane.comp.vid ... x.scm/3050