Replies to This Discussion

Permalink Reply by WW on June 6, 2016 at 8:31

Sorry but I have no idea . . . I'm merely a careful instruction follower who doesn't give up easily. :)

ZinwellPermalink Reply by Graham Wilson on June 8, 2016 at 14:09

v1.23 was the last software release.  I have copies of this and earlier versions if anyone wants to try them.  v1.23 was to enable the receiver to collect channels from other TPs, so it is unlikely that an earlier version will be better.

Here is a summary of what I have found so far:

1. The HSMX200 doesn’t automatically collect the 3 channels: Four+1, Prime and Edge, during a re-scan, since these 3 channels were moved to the new TP frequency of 12519 on the 25^th of May
2. The channels can be manually added (using a Full Scan instead of Auto Scan) as long as the receiver is connected to a 11300 LNB
3. I haven’t been able to find any way to add these channels when the receiver is connected to a 10750 LNB.
4. The new channels are retained ok, if they are first added while the receiver is connected to a 11300 LNB and then the receiver is moved to operate on a 10750 LNB (with a change of the LNB local oscillator frequency in the settings).   

Permalink Reply by willis on June 9, 2016 at 0:53

can g wilson take a flash dump of his working hsmx 200 and make the file available?

ZinwellPermalink Reply by Graham Wilson on June 9, 2016 at 23:39

Great suggestion. I'm away from home for a couple of days but will look to see if this is possible when I get back

Permalink Reply by nzdtv.com on June 11, 2016 at 7:51

I have theory that the ISSUE is with the NIT info on SKY home transponder 12519 H

If someone with pci or usb satellite tuner card can take a look at the NIT info data, quite often NIT info is junk or full of errors. As in wrong freqs

Its probably screwing up where it needs to look for D3 12707 H!

ZinwellPermalink Reply by Graham Wilson on June 11, 2016 at 10:31

I have attached a log file taken from the internal serial port of the HSMX200, if anyone wants to analyse this and see if they can spot a problem:

1. Starts after a Set Defaults
2. Starts with a log of a normal scan, using Auckland as the region
3. Second scan included is a Full Scan, where all channels are collected again and  Four+1, Prime & Edge are included (on 11300 LNB)
4. Final part of log.    Starts on TV1, Change to 9 then 10 then 11 to verify the 3 channels are working

Attachments:

• 2016_06_11 HSMX200.log, 61 KB

ZinwellPermalink Reply by Graham Wilson on June 11, 2016 at 13:05

Just looking thru the log, I've noticed the following (by adding the IF output frequency and the LNB local oscillator frequency)

During the initial scan, the frequencies 12456, 12483, 12644 & 12707 work out correctly when adding the IF & LNB frequencies together from the log.     

When the Sky TPs are scanned the addition of the IF output frequency shown and the LNB frequency range from 480 to 1200 KHz higher than it should be.    Could this difference in frequency be the cause of failing to collect the new channels?

I don't have easy access to a 10750 installation to compare a log but as the resulting IF output from a 10750 is much higher in frequency than with a 11300 this difference may be contributing to non collection of the 3 channels. 

Permalink Reply by nzdtv.com on June 11, 2016 at 13:34

 it shouldnt be looking at those frequencys and symbolrates, are they listed in the transponder menu itself?

if you delete all transponder  data except 12456 H 12483 H and 12519 H does it still look for them?

those look to be the verticals for SBS abc etc

[11Jun16 10:07:40:547] [SCAN] Search NIT: START...
[11Jun16 10:07:40:571] [ST0288_Tune] low = 11300000 high = 11300000
[11Jun16 10:07:40:598] [ST0288_Tune] Frequency_Khz= 1348000 , SymbolRate_Bds= 12600000, SearchRange_Hz= 10000000, Modulatio
[11Jun16 10:07:40:628] n= 1
[11Jun16 10:07:40:724] [ST0288_Tune]searchResult: Locked= 0 , Frequency_Khz= 670391172, SymbolRate_Bds= 561064836, Rate= 4
[11Jun16 10:07:40:787] [ST0288_Tune] low = 11300000 high = 11300000
[11Jun16 10:07:40:812] [ST0288_Tune] Frequency_Khz= 1348000 , SymbolRate_Bds= 12600000, SearchRange_Hz= 10000000, Modulatio
[11Jun16 10:07:40:838] n= 1
[11Jun16 10:07:41:096] [ST0288_Tune]searchResult: Locked= 0 , Frequency_Khz= 562592780, SymbolRate_Bds= 562595532, Rate= 16
[11Jun16 10:07:41:123] 10612767
[11Jun16 10:07:41:167] [AV] tune FE-1: f=12648000 V, symb=12600, satId=0, mod= 1, fec=12, ferr=-2000103
[11Jun16 10:07:41:195] [ST0288_Tune] low = 11300000 high = 11300000
[11Jun16 10:07:41:222] [ST0288_Tune] Frequency_Khz= 1348000 , SymbolRate_Bds= 12600000, SearchRange_Hz= 10000000, Modulatio
[11Jun16 10:07:41:247] n= 1
[11Jun16 10:07:41:478] [ST0288_Tune]searchResult: Locked= 0 , Frequency_Khz= 670391172, SymbolRate_Bds= 561064836, Rate= 4
[11Jun16 10:07:41:541] [ST0288_Tune] low = 11300000 high = 11300000
[11Jun16 10:07:41:565] [ST0288_Tune] Frequency_Khz= 1348000 , SymbolRate_Bds= 12600000, SearchRange_Hz= 10000000, Modulatio
[11Jun16 10:07:41:592] n= 1
[11Jun16 10:07:41:850] [ST0288_Tune]searchResult: Locked= 0 , Frequency_Khz= 50, SymbolRate_Bds= 562592780, Rate= 161061276

ZinwellPermalink Reply by Graham Wilson on June 11, 2016 at 15:55

Sorry the second sentence in my last post was incorrect (I confused scanned with locked frequencies) i.e. the initial locked frequencies of 12456, 12483, 12644, and 12707 are also offset by up to 1.2MHz

The transponder table lists the TP frequencies that we can pickup in NZ.    I have experimented with removing all TPs except 12456, 12483,  & 12519 then doing a full re-scan and Four+1, Prime and Edge are collected ok along with the regular channels (without all the Sky channel clutter as in the previous log file).     I have come to the conclusion that the variation in the locked frequencies is because my LNB is slightly off frequency.    I have tried changing the TP frequency from 12517 thru to 12520 but can't get the locked frequency any closer to what it should be.  (I can go +/- 5 either side of 12519 before I lose signal altogether).    I've also found that the LNB frequency can't be offset, although typing in say 11298 appears to work it goes back to 11300 during the re-scan, so I presume earlier trials with offsetting a 10750 LNB will have been the same

ZinwellPermalink Reply by Graham Wilson on June 11, 2016 at 16:19

If TP12456 & 12483 are removed from the TP table just leaving 12519, a Full Scan collects Four+1, Prime and Edge on LCN 001, 002 & 003 respectively instead of their allocated LCNs.

Permalink Reply by Greg blah blah on June 12, 2016 at 23:09

Hi everyone,
Back from my holiday, and my goodness you guys have been very busy trying to sort out this retuning issue!.

I have just retuned according to Pauls instructions and i now have all channels again. Fantastic!!.

I want to thank you all for your brilliant efforts and extremely helpful information and instructions. You guys are great . I am one truly grateful person.

I must say though, that i am very disappointed at the lack of information or efforts on the part of Hills themselves. They just didnt seem to give a damn, and the only help i got from them was a recorded message telling me to buy a new reciever. They didnt even have the courtesy to answer my email. Very bad customer service , if you could even call it customer service!.

But anyway, the real heros of this debacle are all the people who gave their time and efforts to help all of us having issues, thank you , thank you , thank you !.

Permalink Reply by Paul on June 12, 2016 at 23:31

Funny part is I don't even own a HILLS HSMX-200  had to borrow one, just have a few elderly neighbours that have these receivers.

• ‹ Previous
• 1
• 2
• 3
• 4
• 5
• Next ›
• Page