R5000 problems

[gandalf]

I have finally decided to upgrade from V7 to V9 before the EPG expires.
I have a system with 2 HD Homeruns for OTA and Shaw cable service feeding a Moto DCX3200 into an HDPVR, a Moto 6700 feeding an analog capture card and an R5000 modified Moto box.
Everything updated fine except the R5000 unit which now behaves oddly. The driver screen normally shows 'waiting for connection' until it gets a ping from the SageTV service - then it connects and the icon goes green. Now it takes longer and goes through a phase of registering a STOP call from SageTV then connected. All looks fine but as soon as SageTV tries to use the device the connection drops and the R5000 goes back to 'waiting for connection'. With no IP network link obviously nothing works.
Apart from the tedious changeover of all the mapped channels to SD, all the other tuners seem to work fine.
Only other concern is that SageTV UI seems to run very slowly but perhaps it is juts settling in.
Am I missing something on the R5000?

[btrcp2000]

i can't help immediately, but on sunday am having dish network set up again and will be reconnecting my r5000 boxes. will let you know if mine works. Just sort of assumed that v9 would work with it, so I hope that's not the issue

[dgschoel]

I upgraded from v7 to v9 last week and my R5000 is working fine. I also upgraded my server hardware so I cannot comment on the slow UI loading as my system is much faster with the new hardware

[EnterNoEscape]

A slow UI is likely a symptom of the network encoder communication failing. There are many spots in the UI were SageTV wants to communicate with the capture device and when those interactions happen and the your capture device is a network encoder that's not responding, the UI will appear to be very slow.

[gandalf]

Interesting thought.
Is there a simple way to disable the network tuner without uninstalling it?
I have 2 R5000 tuners but only one is active. The other is not connected to the system but may still be in the configuration (Sage Properties - the tuner is no longer defined in SageTV itself). Could this be upsetting V9?

[EnterNoEscape]

Originally Posted by gandalf

Interesting thought.
Is there a simple way to disable the network tuner without uninstalling it?
I have 2 R5000 tuners but only one is active. The other is not connected to the system but may still be in the configuration (Sage Properties - the tuner is no longer defined in SageTV itself). Could this be upsetting V9?

If it's not set up, it shouldn't be causing any issues.

[pdermody]

I have (2) R5000 boxes on different machines, one on a Win7 host, and the other on a Win10 host. Both are running SageTV 9x without any issues (well the 10 box had some issues, but a clean install of 9 and dropping the wiz.bin and what not back in fixed that) and as of today both are now up and running with SD EPG.

-pd

[gandalf]

This is getting really frustrating.

My original installation licensed by Nextcom was for a pair of R5000 modified cable boxes. One was a DCT2224 and one a more modern DCT2524. Both were set up and worked fine under SageTV V7.

Then the older box developed a fault and had to be retired. I had added a newer DCX3200 with an HDPVR2 to get MPEG4 channels so the loss of one of the R5000s was not a disaster. SageTV v7 ran fine with both boxes defined in the Sage Properties file but the dead box removed from the source lineup. The r5000 software started before SageTV and identified the DCT2524 as the only box then went into 'waiting for SageTV' mode until the SageTV service started up - at which point it registered a ping and went green. All was well.

Then I upgraded to SageTV V9 and encountered two problems. Firstly the UI ran VERY slowly and secondly the DCT2524 was not found - hence my posts.
EnterNoEscape was quite correct and the slow UI issue was fixed by removing the R5000 tuner from the source lineup [thanks].

Then I noticed that the R5000 startup window was claiming to see the DCT2224 - which was no longer attached - and did not see the DCT2524. I have no idea why that changed - it is weird. I have reconfigured the R5000 driver with the right tuner and TCP port number but it still will not work. They match what is in the Sage Properties file so one would expect it to work.

Next step is to find the original details from Nextcom in my e-mail archive and see if the R5000 device ID matches the one in the DCT2524 box or if the gremlin changed that as well. I will report back when I have found that.
I am not sure where Nextcom stores the configuration data for the R5000s - probably the registry because no file in Program Files got changed from my backup.

I guess no option but to dig around for the original config data and possibly do a fresh install of the Nextcom R5000 software.

=====

Update - against all the odds my e-mail archive back to 2010 does work and I confirmed that the registration details that Nextcom supplied are the ones recorded in the registry - however nothing tells me which way round they go (I have 2 keys and had 2 devices) so I must assume they are correct. The registry only shows the active device and the TCP port matches what I had set up in SageTV so all looks fine.

Just to be sure I did a clean reboot and waited for the R5000 program to start.

The Nextcom R5000 window stays at 'SageTV: Waiting for connection on port 6968' - no comforting green light confirming connection after I start the SageTV service (as used to happen). As far as the R5000 is concerned, SageTV is not pinging it.

If I start the SageTV UI - it all works fine until I try to add the R5000 as a new source. It sees the R5000 as an option and all looks fine but if I try to add the new tuner the UI hangs with a spinning wheel. The only way out is to crash the UI by stopping the service.

So after an evening's work I am no further forward. The SD EPG works fine, SageTV v9 works fine (apart from the missing tuner), all recordings are fine. Just unable to make the R5000 network tuner work.

FYI (in case it makes a difference) the R5000 is on the same computer as the SageTV install and it is accessed via the loopback IP 127.0.0.1
[mmc/encoders/12347/encoding_host=127.0.0.1\:6968]

Any suggestions what to try next?

[KryptoNyte]

I'm sure there is a better way to do this, but as a workaround, do you still have the R5000 box with the fault, and does it run long enough to get SageTV to show both R5000 tuners, allowing you to choose 'the other one?'

[jusjoken]

Post the sagetv log after the hang and perhaps someone here can interpret the errors in the log.

[gandalf]

Thanks for these suggestions. I still have the old DCT unit that failed but it will take a while to dig it out. Although the STB part is dead, the R5000 board is, I think, USB powered so it should still work. Nice idea - however let's try the log suggestion first.

I have attached a ZIP file containing all the logs produced around my test time.

I can't say they make a lot of sense to me but one of the older logs shows a number of odd Java errors that might have something to do with the problem. The new logs cover me trying to attach the R5000 tuner and crashing the UI. The log has lots of blank lines in it but ends up with a loop of:
Sun 6/25 13:59:39.321 [MsgMgrSocket@167c318] MsgManager got socket connection from: Socket[addr=/127.0.0.1,port=58427,localport=6968]
- so it is trying to connect.

So - any gurus able to make sense of what is going on?

Thanks
'

[gandalf]

--- Just to be clear in my logged session above - what I did was:
turned on logging and restarted the UI
attempted to add the R5000 tuner
as before the UI went into a loop with just and endlessly spinning wheel of death
stopped the SageTV service to force the UI to stop
restarted the service and the UI
turned off logging

So the question is whether the log files show what is wrong and give a clue as to what needs fixing

[btrcp2000]

did you ever get this fixed? I have just tried to setup my second r5000 dish box, but sage only seems to recognize one. The other just sits there on "waiting for connection" while sage spins.

[gandalf]

No - not fixed yet. Temporarily abandoned switching over to the new Win 10 partition and still running on the old Win 8.1 that works.

When real world issues (like back tax problems) stop wasting my valuable free time I may be able to get back to this.

The issues are still active if someone finds a fix - but I can't update what has been said so far until I get more time.