CNelson03

In a previous post, the discussion morphed to using the iTach IR Node server for other Global Cache products, so I decided to create this new post. In its current state, the iTach IR Node Server is designed to work primarily with the Global Cache iTach IP2IR device. I'm migrating from an iRule/ISY/GC environment that also has other Global Cache boxes, namely older GC-100-12 all-in-one boxes and a couple iTach IP2SL232's -- both not officially supported by the iTach IR Node Server, so I decide to investigate/test further. Per the GC-100, it doesn't work now, but I think the existing Node Server may work for IR, provided the Module Address can be changed to 4 or 5. Not sure how easy this is to do, but it appears modules 4 and 5 are needed for the GC-100-12: (diagram from the GC-100 API Specification Version 1.0d) For iTach IP2SL RS-232 support, it requires a different code set (ASCII?). iRule handled this with it's Gateway/Devices infrastructure (which is all no longer available as the servers were shutdown). Fortunately, I had created a couple Network Resources to do some scheduled activities like a nightly sweep to power down devices. I tried re-creating these as a iTach IR Node Server with a similar command structure except the "setstate" command: function, code1, hexcode1, code2, hexcode2 "Power ON","setstate,1:1,@PWR:2\r\n",, "Power OFF","setstate,1:1,@PWR:1\r\n",, OR "Power ON","setstate,1:1,@PWR:2",, "Power OFF","setstate,1:1,@PWR:1",, Neither of these works (at least in my system). Perhaps this is due to other differences such as being "C-Escaped", ports, etc? While the Network Resources approach does work for some of my devices, others I created do not seem to work (not sure why yet). The Node Server approach is recommended anyway (and slicker than creating lots of Network Resources), so I'm wondering if others have found ways to get these to work via a Node Server? For the Network Resources approach, have others found things (config, etc) that are needed to get them to work with various devices?

I will try playing around with the GC-100 as well, I mostly use them for their RS232 ports as well so the IR may not be an issue (primarly use the new iTach for the IR control but do have a couple IR devices on a GC100). I think one issue may be that they use different ports for the different connections (e.g., 4999, 5000, etc). So instead (or in addition?) to specifying the connector, you must specify the port (e.g., RS232 Connector 1 = 4999, 2= 5000) and I think each grouping (IR, RS232, On/off triggers) is another module. I had done a few commands in Network Resources prior, here's a sample of a Power Off: For some reason, some of these existing calls work on eisy, but some don't (did work on 994). More investigation needed (unless I'm just missing a setup step or something.) Overall, I'm just getting started in the migration and can no longer get into iRule to see all the codes I setup so it's going to be a project to convert and have been trying the UD Mobile interface. Now that I have the ITach IR Node Server commands setup, is a Program the easiest way to call them from a UD Mobile button in Favorites? Or can the node be called from the "Devices and Scenes" like in the Admin Console? I don't see the node server in the list of Devices and Scenes when I use the "Command" type but I did setup a Program with the "Then" being 'ON' and the Else being 'OFF' and that worked. Just don't want to create a lot of programs if there's an easier way.

Javi: Thanks, I found two problems: Pinging the iTach showed inconsistent returns, sometimes all packets would return, other times only 25% or 75% would come back. I swapped out the Ethernet cable and this seemed to help. This probably caused the initial inconsistent operation -- sometimes the packets would make it through, but other times not. When I re-installed the node server, I forgot to change the third digit in the IP from ".0" to ".1 (oops!) and subsequently the unit wouldn't work at all. Changing the URL, restarting the node server and Admin Console did change the Module Type to "3 IR" and it seems to be working consistently now (or at least as consistently as IR typically is) So problem solved there. Any ideas on the "rwood receiver" name in Admin Console? Not a major deal but curious why it did that. Another related question: this node server is for the iTach IP2IR box and I also have Global Cache IP2SL-232 and GC-100 units in my system. Does this Node Server work with them? Do you need to use hex codes or do Global Cache or network commands also work? I'm migrating over from ISY-994i/iRule and want to re-use as much as possible. I've done some calls in Network Resources but those seem a bit more inconsistent (some work, some not) on eisy.

I setup the iTach-IR Node Server in eisy but it is not working reliably -- sometimes the commands work, but other times not, even when I set the 'repeat' higher. In looking at the node server, I see the Module Type is "UNKNOWN" instead of "3IR" as noted in a previous post. When trying to run the commands, I get an error of "-2" One other thing I noticed is the node that I created had a value of "Sherwood Receiver" in the key field, but shows up in the Admin Console as "rwood receiver" I tried deleting and then re-installing the iTach-IR node server in Polygot but it didn't fix the problem. Something I am missing? How do I get the Module Type to be 3IR?