See attached photo. Install that jumper on the pins. Connect Ethernet cable between board and your computer, then power up the board. This will force the Ethernet module to a static IP address of 192.168.1.88
If you run the NCD 5500 Ethernet configuration utility you should see the module appear. Let me know what you find.
The answer for the LED is, yes it comes on green and stays on.
As for the connection issue, as I have noted in a prior post, I have set the static IP jumper and then ran the NCD 5500 Ethernet Configuration Utility and received the results as shown in the 12th post of this thread. After selecting the Apply Settings button on the top menu bar I exit the program.
I just now repeated the same steps to verify the results, and they turned out to be identical.
After exiting the 5500 Ethernet Configuration Utility, I kill the power to the controller, wait 2 seconds and then remove the static IP address jumper before turning it back on.
I start the NCD Base software and the Select Connection window appears. I select the Network radio button and set the IP Address to 192.168.1. 88 and the Listen Port to 2101. The Select Connection window now looks as followsâŚ
I proceed to select the OK button and after a short delay the Base Station Software window is displayed as followsâŚ
Those are the exact steps I take, and the results that I receive. Iâm trusting you can tell me what Iâm doing wrong. If not, then hopefully you can tell me what I need to do to make this work (other than using a DHCP enabled router instead of using a dumb switch which is a mandatory requirement for the project).
Thanks for your assistance to date on this matter.
Hi David,
On the screenshot that you shared, the first picture specifically, the NCD5500 should broadcast a discovery packet, the IP address will show up in the lower windows. Does the ip address ever show up in the lower window (that says IP/Mac/ZigBee Address, etc) or does it stay blank as shown in your screen shot. It will take up to 30 seconds to appear, but this is an important step. If the IP address does not appear in this box, there is likely a problem with the network connection/router/cabling. We have several customers who use this device exclusively in static IP mode, so network connection hardware will need to be examined carefully.
Ryan
If it does not show up in the window, there is a problem with general network communications, it sounds like its hardware related as UDP is generally supported by about everything. For testing purposes, please plug the computer and the ethernet module into a standard router that supports DHCP. Even though this may not be required, this is helpful for troubleshooting. @TravisE_NCD_Technica is our expert on this, I have tagged him so he can suggest further troubleshooting steps.
I would concur that the next step of troubleshooting is to plug the board and your computer into a standard network router that supports DHCP. Let us know if this works or not. Make sure the Jumper is not installed on the Ethernet module also.
It took a while, but I finally located a router that supported DHCP that I could use.
After setting up the router, the IP address for the laptop used to communicate with the NCD5500 needed to have its IP address changed to be on the same network number that the NCD5500 was using as the default (192.168.1.xx). Once that was accomplished, the NCD Base software was able to identify the NCD5500 card and I was able to communicate with both relays on the NCD5500 board successfully using the ProXR Enhanced Command Set. The IP address of the NCD5500 was shown to be set with the expected default values of 192.168.1.88. I was also able to access the Device Identification and the Device Configuration functions. However, I believe our âtrial periodâ for the COMM Operator program has expired because even though I could at one time, I no longer could access that program.
For clarity purposes, at this point the hardware configuration simply consisted of an Ethernet cable running from the laptop to the DHCP enabled router, and another from the router to the Ethernet Module on the NCD5500.
At this point the NCD5500 was powered down and a static IP jumper was installed over the 2 pins on the Ethernet Module to allow the IP address for the NCD5500 to be set as a static value. When the board was powered back up, the NCD5500 Config Tool was executed. The software appeared to recognize that the NCD5500 was on the network as it was listed in the window on the left side of the display. The IP values in the Network Settings section were changed from the default to the following.
IP Address: 172.20.1.110
Subnet Mask: 255.255.255.0
Gateway: 172.20.1.1
DNS Server: 8.8.8.8
Then the apply settings button was selected and the NCD Config Tool was exited. The NCD5500 was then powered down and after more than 10 seconds, the static IP jumper was removed from the Ethernet Module.
Before swapping out the router with the switch, the NCD5500 was powered up once again to check if the IP address change had taken affect or not. However, when the NCD Base program was started and the Select Connection window was showing that the NCD5500 was recognized, the display indicated that it still retained the default IP address of 192.168.1.88. Running the NCD Config Tool again also disclosed that the IP address had not changed.
It appears to me that the Ethernet Module or something on the NCD5500, is not providing the capability to change the static IP address and maintain it.
What would be your thoughts on the next step I should take?