Quote:
Originally Posted by bill190
...
I found the location in the Mercury II channel file where the diseqc positioner numbers are stored for positioners such as the VBox II.
The location in the channel file is (hex) 0xE200.
Note that I am using Mercury firmware version V0145. It is possible that this data is in a different location for other firmware versions or that it may be moved/changed with future versions. |
THanks! That seems to work for firmware 133 also. Wish I knew this a few weeks ago. My motor was already set up with sat locations from another receiver, and I wanted to have a way to just move those locations over to the Mercury, rather than searching for each sat again. This would have saved me some time.
I didn't bother looking for this data in the downloaded .bin file, because it didn't appear in the channel editor program, so I assumed that it wasn't being downloaded, but apparently it downloads (upload in Fortec speak) it, but doesn't use it.
Anyway THANKS, that will be useful.
Quote:
Originally Posted by bill190
The stored satellite position numbers on my Vbox II appear on the VBox display as.
P01, P02, P03, ... P09, P10, P11, etc.
The above is decimal.
The positioner numbers stored at 0xE200 are hex...
P01, P02, P03, ... P09, P0A, P0B, etc.
The hex number stored at location 0xE200 corresponds to the first satellite in the satellite list on the Mercury with the listing set to default (not sort by position). So...
1st satellite in list = location 0xE200
2nd satellite in list = location 0xE201
3rd satellite in list = location 0xE202
etc.
So for example I could store 01 to location 0xE200. Then I could download the modified channel file to the Mercury and go to the first satellite in the default (unsorted) list and it would move the dish to Vbox position P01. Or store 1E to the same location and it would move the dish to Vbox position P30. (Assuming that these positions have already been stored in the Vbox.)
|
I think you're saying the same thing that I observed, but just to clarify. What I saw, is that when I saved DiseqC1.2 positions via the remote, the Mercury just starts at 1, and then the next sat I save becomes 2, and the third sat I save becomes 3, etc, etc. These positions aren't in any order, it's just a matter of where those sats are in the default list.
One thing I was interested in, was what would happen when you try to assign 2 satellites to the same DiseqC1.2 position. Ie, for example if you have G11 and Nimiq-1 both at 91 deg, I was guessing that the Mercury will waste a DiseqC1.2 sat position, and store 2 different numbers for that one position, and sure enough, I just tested that, and it does. Ie I just saved the same sat location for two different sats, and it used two different sat location numbers, which is a waste. Ie it would be better to be able to save the two sats both with the same location number, if they are at the same longitude. With the Lifetime and Ultra, you can do this. I'm a bit nervous to try putting the same number in this data file just yet, ie it might really mix it up when it goes to try finding the next available number to save the next sat in. Perhaps it saves somewhere else, the last number it used. Also might be interesting to see what happens when you delete a sat already saved, and then save another. Ie say you have 20 sats saved, and delete number 10, then save another. Ie does the new one become 10 or 21.
Anyway, this is a nice discovery, and it will be interesting to investigate this further.
Thanks!