NRIRServ bug

[MikeM]

Folks, does anyone have this running under windows 2000 professional? I am having a lot of trouble making this work with my Slink-E. I did get it to work once for a few keys, but nothing works after that one session ( I had tried a lot before that one working session).

First off, NRIRServ won't exit without generating a windows fault (not a system crash, just a process exception). And most of the time, it won't save any changes to the flags (logging, start with windows) when exiting.

I have both a windows XP win32 client as well as a pocketpc 2002 client (both version .98) trying to connect with no success. I can ping the server just fine, but no data gets through. Because I can't figure out if logging is actually working (I set the flag, but can't restart it with the flag set because of the error on exit problem - and it doesn't log anything (not even creating the log file when it's still running).

Since I am using a Slink-E with Slink-E server, I can fire up the diagnostics on the Slink-E and watch for data traffic sent, and I don't see any, but don't know whether the NRIRServ daemon isn't seeing the requests, or that it's an invalid IR code, etc... I have played with the timeouts with no sucess as well.

Anyone have any ideas as to what to do next? I don't think I have missed anything obvious, and I have cleared the registry entries to try and make sure nothing there is messing stuff up.

Thanks,
Mike

[Ben S]

Hi Mike,

I believe there is a problem with the NRIRDriver under NetRemote. This doesn't account for NRIRServer bombing when exiting, but it does account for why data might not be getting through.

I'm prepping some other changes for 0.983, which includes a big fix for the NRIRDriver.

Sorry for the hassle.

-Ben

[MikeM]

Ben, thanks for all your efforts here! It's a great piece of work.

Are you sure this is my problem? I'm running version .98 of the code, and I though IR passthrough worked fine in that version?

Thanks,
Mike

[Ben S]

Unfortunately I believe it has been broken since 0.98. I reworked the way events were being handled at that time, and slipped in a bug regarding IR transmission.

You should be able to download 0.972 (for Win32) here (http://www.netremote.org/dl/archive/NetRemote-Win32-0.972.zip), which should work for testing until I release 0.983 (in a few days).

[ezamora]

Hi Ben,

First of all, I like to thank you for all your efforts, this is a great tool! It is exactly what I was looking for months.

I'm having the same effect explained here. I'm running W2K-Server (P-IV, 256MB, 23GB Free) Slink-E, PPC2002 and Homeseer to control basically all my Sony devices (11) through Control-S, IR and/or S-Link using my PocketPC (which is a great idea!).

My first approach was to install Slinke Server v1.32 (Nirvis), NetRemote 0.982, PCC2002 NetRemote 0.982 and NRIRServ (12-May-2003) knowing that Slinke is working fine because homeseer is able to send all kind of commands through it.

NRNIServer seems to connect fine as a Client of SlinkServ (The SlinkServ shows another client connected), however, when a I click a command from NetRemote or from PPC2002NetRemote I cannot see a command received>sent at SlinkServ from NRIRServer.

2 days later, after seeking for a posted solution, re-installing my server and installing just what it is necessary, the problem persisted. In my search, I found Mike's post so I decided to install NetRemote 0.972 as you suggested, same results.

I also found a post saying that he cannot control which port will be used to send a command, NRIRServer seems to send every command to every port, may I suggest to include in further releases the option to send a command over a specific port pre-defined in the "data section" of the button?

At this point I don't know how to handle the communication problem between NRIRServ and SlinkServ, could you help me? 8) I'm thinking that maybe is a NRIRServ problem, can be? Do you have an older version?

Thanks,

Henry

[Ben S]

Hi Henry,

0.99 release candidate 5 is pretty darn stable. Stable enough that I won't say "press your luck" with it.

You can download it from the General Discussion Forum, 1st thread. Could you please try that version and let me know what you find?

Regarding specifying which port to send it to: Yes, I should do that. If it can wait a few weeks, I have some other ideas for NRIRServ that will benefit Jon and the UIRT-USB stuff, as well as make for better IR performance.

Thanks Henry!
-Ben

[ezamora]

Hi Ben,

Thanks for your quick response. I follow your suggestions last weekend and I found the same result. Using some sniffer utility I found that if you change the tcp/ip port (from 8081 to another) NRIRServ will use 8081. I had to use another port because one of my services was using this one. If is possible don't forget to remark this hardcoded line..! I use to forgot this when I'm programming :)

Now, everything works very well and I'm using your last version. Thanks again for all your help.

BTW, when NRIRServ send a command to Sline Server, sends it through all IR, Slink and Control-S ports?

Thx. Henry

[ezamora]

Hi Ben,

What do I have to do to send Control-S (IR unmodulated) and/or S-link (bi-directional) commands?

I know you are busy. If is something do you have to change in the code, would you like me to help you with it?

Thx,

Henry

[Ben S]

Hi Henry,
Unfortunately NRIRServ does send IR through all the ports, and I'll need to check the code to see if it's sticking to 8081 for some reason.

Regarding s-link and control-s, it might be better to handle that through Girder using cde files?

-Ben

[ezamora]

Thanks for your reply...

Yes, I'm using Girder to control my devices, I was just thinkig to use one program instead of two different. I'm looking foward to use NRIRServ, I think is just very nice.

Thanks again,

Henry

[Ben S]

I am in the midst of cleaning up the NRIRServ code. I'm adding the ability to use the variable IP.PortNumber to figure out what port to send to. I thought this would be better than having to put a port number as the IR name in for a large number of buttons.

This is especially needed with the way I'm doing passthrough for the GlobalCache, as it doesn't have a "Blast to all ports" option.