|Mike - there is a debugging option. Turn logging on in NRIRServ and you can look at the log and see what NRIRServ and the slinke driver are doing.
Ben, thanks for the quick reply. I can't believe I forgot about that - I had had it set for some debugging last week but forgot about it.
The log file is interesting. One thing that would help would be timestamps for the events in the file, so I could match them against specific tests done.
Also, showing the TCP connects (from what Ip and what time, and the IR code sent) would be great. Maybe I'm not reading the info properly, but the log info is focused on the ir signals being sent and not on the network side of the request.
I do see some signals sent at 58 Khz, which is matches the replaytv's IR frequency, so that probably means the codes I got from remotecentral were accurate. I'm also trying sending signals to my Sony DVD player, but that doesn't respond either... :-( So I think there is some IR issue here that the IR Linc will correct.
|Is the ocelot plugged into the computer or something else?
Well, now I have to tell you more about what I'm doing. :-) Yes, the Ocelot is currently plugged into the same system. But that won't be the case permanently. I have an old Dell PC that runs the HAL 2000 automation package. It controls a bunch of X-10 controlled lights, and will also control a couple RCS thermostats once I get the time to install them. It also runs slink-e server for CDJ access (I rewired my house with some fairly extensive CAT5 and RG6 wiring that I use for sending data, serial info, IR, and CATV around). Even though the SLink-e is in the A/V rack in the family room, I have very good luck with remoting the Slink-e RS232 over the a CAT5 path from my office upstairs where the automation system is.
I'm getting ready to build an HTPC soon that will sit in the A/V rack, and then I'll move the Slink-e connection to it. It'll also be connected to the Pioneer HDTV RPTV I have, and will eventually have an HDTV reciever card in it (I already have an off-air antenna mounted in my attic and patched downstairs in the A/V rack through the RG-6 network waiting for it). The new lower cost HDTV cards that can output directly through the systems AGP card through a software HDTV decoder seem to be the best approach to feeding an RPTV to me. This system will also run girder and NRIRserv as well.
I have been waiting for a good case (looks like the new Antec Fusion will fit the bill), and the new dual DDR400 P4 chipsets to come out so I can free up the guts of my current primary workstation to go into the HTPC. This way I always have the fastest system for my desktop.
The Ocelot is plugged into the HAL2000 system and I use it now as an X-10 interface. I find it very reliable, and it will eventually also control sprinklers, outside lights, and a bunch of other things. The reason I want have the Ocelot tied into the xantech system is a crude way of communicating between the A/V systems and Hal 2000. So for example, if HAL detects no one is at home, it can send an IR signal to girder to power down the A/V stuff. Likewise, when Netremote wakes up the A/V system and selects TV or DVD viewing is about to commence, it can send an IR signal to HAL 2000 that will command the X-10 light controls to a specific mode. Also, when I tell Hal 2000 to operate the house in "party mode", it can send an IR command to the Russsound system to lock out the keypads in the house.
I find the approach to integration a lot cleaner than having every control system send IR commands directly to equipment and to the X-10 devices. This allows each system to maintain a context of what's going on and act accordingly rather than trying to coordinate a discrete set of lower levels commands. At least that's where I'm going - it may not work as neatly as I've described it after it's built. :-)
Sorry for the verbage, but I think you can see why I think Netremote is such a powerful addition to my systems! Particularly with multiple PPC's in different parts of the house...