Cannot get Netremote to communicate with Girder.

[SpineDoc]

OK I am having a bit of trouble here. I have set up Girder and it sends out my IR codes perfectly that I have programmed. Now I edit my .ccf file in Tonto and add the 5001 0000 0000 0002 ffff 0000 0001 0000 code to the IR section of a button, making sure to name the action the same as it is named in Girder ex: TV.ON. I save and load the .ccf into netremote, but nothing is happening.

Thanx much for the help. Version .996 Netremote. Hopefully version 1 will come out soon.

[SpineDoc]

I have checked also, and both the NR and girder passwords match.

[ebariaux]

making sure to name the action the same as it is named in Girder

The name in the CCF should be the same name as the "Internet Event Server" Event associated with your action on the Girder side, not the name of the Command.

Maybe that's what you meant, but just to be sure...

Eric.

[Jlee]

Also, open Girder and press one of your ccf buttons. If the girder action is getting through you will see it in the status bar on the bottom right of the girder window. That will help to establish where the problem is.

[Rob H]

And further to that, you can get Girder to learn the command names straight from your button presses.

Select the event in Girder, ensure that the top left combo box says 'All', press the learn button and then press the button in NetRemote. Saves a lot of typing IME

[SpineDoc]

Yes I am looking at the status of girder when I press the ccf key, and it looks as if nothing is happening. I did mean that I named the internet server event the same as the ccf/IR command.

rah99 thats a cool tip, thanks. Hopefully I can put it to use if I get this to work.

Anyone else have any ideas?

[Rob H]

Is NetRemote running on PPC or Win32?

If PPC then check the NetRemote.log file in the Program Files\NetRemote directory.

If Win32 then you can download DbgView from www.sysinternals.com to get at the debugging info. That might show what's going on.

Other possibilities include :-

1) You're using different ports - I use 1024 which I think is the default
2) You've got a firewall running that's blocking the port

[Mastiff]

Firewall?

[SpineDoc]

Hmm, yes I have a firewall, I will forward requests to that port to my HTPC.

Also I found that I need to obtain the USB-UIRT driver for Netremote server, I think its NRIR-USBUIR.dll. This way I can specify for NR server to use that device. I emailed the usbuirt vendor.

Can anyone email me the NR server driver so I can get it sooner? I am at quite a loss to understand why it is not posted as a download here and/or at the usbuirt site. My email is spinedoc777@hotmail.com.

I hope getting the driver in place solves this dilemma.

[SpineDoc]

Holy crap, this is complicated. Did not realize until I was just now browsing the forums that there are actually 2 different ways to send IR commands. You can use NR server to pass through the embedded IR commands in the ccf to the usb-uirt, or you can send a command to girder thru netremote and have girder send out the IR command. The latter does not require nr server, but I cannot get it to run!

I wish the usbuirt driver was included with nr server, even if its beta or has not been tested well. Now I have to sit around waiting for the usbuirt driver to be emailed to me, sigh.

[SpineDoc]

OK I finally got it to work, it looks like it was a firewall issue. Forwarded port 1024 to my HTPC and it worked!!!

I also hope to get the NR server working, as it seems like a LOT less trouble and typing to just output from NR directly instead of using girder. Currently I cannot learn codes in Tonto, but I am assuming that is because I dont have the NR server driver?

[Rob H]

See this post :-

http://www.netremote.org/phpBB2/viewtopic.php?p=6610#6610

[Jlee]

I don't think NRIRServ will be any use to you if you don't have the codes. I would use Girder and I've seen Ben (NR Creator) recommend this too. I believe that NRIRServ is recommended where you have no other reason to run Girder and you alredy have the codes.

[Rob H]

You can probably find suitable codes at www.remotecentral.com though.

[Mastiff]

You've got mail. And you'll probably find codes for just about everything you've got on the remotecentral website. If not, and you've got a PPC, you can download PDAWin's TV Remote Control here: http://www.pdawin.com/

Use that to learn the codes into a CCF, open that CCF in Tonto and get the codes from there. That's no problem to do in the shareware trial period. :wink:

[SpineDoc]

Thanks guys, much thanks for the file Mastiff. I guess I am confused with getting codes into the CCF thru Tonto. I see an option to learn IR codes in Tonto, but when it doesnt find any codes on any ports. Is this just a broken feature?

I also did look on remotecentral.com and could not find most of my components on there, seems most of the stuff on there is low end gear.

I am glad I dusted off Netremote and started using it again, forgot how cool it was. I cant wait for 1.0 to be released.

[Rob H]

It's not broken, but it only works if you have a Pronto (or lookalike) remote

[Jlee]

Learning codes in Girder with the USB-UIRT plug in is a piece of cake. If you are running girder then you don't need any other solution IMO.

[howie]

i too have everything working ok in girder but cant get any buttons in a ccf through netremote to work .i just cant seem to get a connection from girder to netremote i have spent hours reading the info and forums but im not getting anywhere. has anyone got any ideas or settings to try.

[Rob H]

Where are you running NetRemote? On a PPC or on Win32?

The simplest case is running it under Win32 on the same computer that Girder is running on.

Things to check :-

1) You are using the correct computer name or IP Address in the girder plugin properties.

2) You are using the same port and password in the girder plugin properties and in the property page for the Girder Internet Event Server (in Girder this can be found in File|Settings on the Plugins tab - make sure that there is a checkbox next to Internet Event Server and that the port & password match)

3) Have you got a firewall running that might be blocking port 1024

[Mastiff]

Hey, Rob! I've got the copyright on that firewall question! :wink: Another thing to try is "disable abuse protection". Sometimes that helps.

[howie]

im running on win32 on the same pc as girder and i have got the ports and passwords all the same etc. i am using jlees ccf.i have just tried the abuse thing as well and no joy. :cry:

[howie]

oh and i dont have a firewall.

[howie]

jlees ccf has a red dot in the bottom right hand corner that is supposed to turn green when it is connected to girder but it is always red.

[Rob H]

What do you have as the IP address? If you haven't already tried it then 127.0.0.1 or localhost should work.

Okay, download dbgView from www.sysinternals.com and let's see what the NetRemote log says.

It might also be worth downloading the Logger plugin for Girder (from www.girder.nl) to see what Girder thinks is happening.

[howie]

ok i got it to work by putting in localhost insead of an ip address. now for the big question. what do i need to change to use my pocket pc instead. i cant seem to get it to work by putting in the ip address is there anything else i need to do to get it to connect.

[Jlee]

To point your pocket pc at your pc running girder use the computer name rather than the ip address of your pc in the default host page / girder plug in properties within NR.

If that doesn't work then first of all check that you can successfully ping your pc from your pocket pc and vice versa. You'll need to download vxutil for your pocket pc to be able to find out the ip addres and ping from it. Sorry as I haven't read all of this thread but if you are using a wireless access point or similar device then that will also have an ip address (check the instructions) so try and ping that from everywhere else too. If any of these pings are unsuccessful then go back to your firewall settings.

Don't just rely on the red icon in my ccf to determine that girder is working as that needs other stuff that might be broken (i.e. feedback.lua) so you should also check it by initiating some sort of test command and opening girder to see if it's getting through.