Things not going well with my new HD200 - FIXED

[Madz]

I'm having all sorts of problems with this - have a separate thread (http://forums.sagetv.com/forums/showthread.php?t=38063) because I can't access shared media - now trying to get the extender working and am having problems there too.

When I start the extender it says it's connecting the the server, then the screen goes black, the red activity light turns off and that's where the action stops. It appears as though it has switched itself off - pressing the power button at this point causes the HD200 to turn back on and comes up with the standalone main menu.

I've tried everything I can think of - deleting the properties file in the clients folder on the sage server, restarting the sage server service, doing the full reset procedure in the manual for the HD200. Nothing seems to help.

Background Info:I was able to connect the extender once and when I saw it worked I tried to load the SageMC stv. This worked and I chose my theme. I then closed it down and went to edit the properties file in \clients on the sage server manually to transfer across the SageMC settings from my normal client.properties file. When I started things back up it hasn't worked since and I can't get it to work again.

Here is the telnet log:

STP-HD200[/client]# sh runclient.sh 10.1.1.3
kill: you need to specify whom to kill
STVCFG0: not found
720p: not found
1080i: not found
1080p: not found
Using 1920x1080p@50|standard=HDMI_1080p50 Digital
Starting SageTVMini Client
Connecting to 10.1.1.3
Starting GFX thread
Trying to connect to server at 10.1.1.3:31099
before memset
before connect
before reply
Connection accepted by server
Connected to gfx server
Sending ui size 960X540
Opened /dev/ir on 6
Opened /dev/fip on -1
before memset
before connect
before reply
Starting main loop
Connection has been terminated by server
Error processing GFX Command
Connection accepted by server
Connection error 1, exiting
Joining gfx thread
Joining input thread
Input Thread is done
Joining media thread
Deinit GFX
Exiting
STP-HD200[/client]#

Any ideas?

Other question is after telnet'ing in, doing the above then typing exit and closing hyperterminal, the red activity light doesn't go out on the HD200 and I have to pull out the plug to turn it off.

[Brent]

I'd try the configuration reset procedure described in the HD200 manual:

If none of the other troubleshooting suggestions have solved the problem, then you can try this
Configuration Reset Procedure:
1. Turn the player off by unplugging the power cable.
2. Press the Delete button on the remote and continue holding it as you plug the power cable
back in. Continue holding the Delete button until the Active light blinks twice.
3. Note that you may need to use the Video Out button on the remote to change the video
output resolution.
4. After the reset procedure, check the above troubleshooting tips again.
If the player is still not functioning properly after the Configuration Reset and rechecking the
troubleshooting tips, then contact SageTV technical support via www.sagetv.com/support.html.

[Madz]

Yep, tried that (above). Appreciate the reply though. I was sure that would have got me running again. I'm a bit worried I've really screwed it up somehow.

[iammike]

To test if it's the SageMC stv, you could temporarily rename it to something else. That would keep the extender, or any other client for that matter, from finding it. When the extender starts up I think it would revert back to the default stv. Not a solution, but it would at least help to isolate the problem.

[Madz]

That's a good idea iammike - will try it out now...

[Madz]

Well thanks mainly to iammike's push in the right direction, I've got this sorted out - I changed things on the server end and found things started working, so that did indeed help to isolate the problem to something on the server rather than it being a problem with the HD200.

Of course it all ended up being my fault - two mistakes actually:

1) I wasnt stopping and restarting the sage service either side of modifying the extender properties file in the clients folder - this it seems is not necessary if the extender disconnects properly, but when it was crashing, I was putting back the original file and then when I tried to restart the extender, the server was overwriting this with the old bad file again, so the extender again didn't work and I mistakenly thought the reverted file hadn't had any effect. Anyway, golden rule- always ensure the sage service is stopped when playing with any of the config files

2) In being lazy wanting to copy over my existing PC client profile rather than set everything up from scratch, I'd just merged most of the settings from the SageClients.properties file into the extender properties file. However it turns out that they are not all compatible with the HD200. In particular, you need to ensure that these are set to True for the HD200:

ui/windowless=true
ui/remote_render=true

With that done, all is working fine now on the extender front!!