All ControlSpace Devices not visible after changing the IP Address Subnet

Professional Installed
1

Hi Guys,

I was working on developing a training video today walking thru the steps of changing the IP Address subnet on an ESP-88 and CC-64. I went thru the steps as indicated on the ControlSpace help file, changing the IP address to 18.12.0.160 for the ESP-88 and 128.12.0 176 for the CC-64. When I was done, I changed my IP address on my computer to 128.12.0.88 and pushed the TAB key which gave me a new Subnet mask of 255.255.0.0. When I opened ControlSpace Designer and went to “System/Update Firmware”, only the ESP-88 with a CC-16 showed up in the window. When I pushed the Scan Button to find the CC-64, it showed up - and the ESP-88 disappeared.

I can “ping” both units from a command line and they respond as they should. If I disconnect power to the CC-64, the ESP-88 and CC-16 appear again. If I disconnect Power to the ESP-88, the CC-64 pops right up AND, if I change everything back to 192.168.0 160 and 176, all is well with the world - they both automatically show up. My question is, why isn’t all well with the world when I set it for the address in our help file?

Any help would be appreciated- I’d really like to get this video out the door and posted this week.

Thanks in advance for your help,

Bruce

2

Hello Bruce,

I ran into a similar issue at a project where I had to use the established network and assigned IP addresses at the site. I found that even though the IP address was 10.17.0.xxx, the subnet mask needed to be set at 255.255.255.0, in spite of what Windows XP suggested.

Unfortunately, I have no explanation why.

bk

3

Rob Brooks is travelling this week but he sent me a short response directly to my email. It is shown below;

"I found this myself a few months ago - It appears that ControlSpace is only really designed to function on a single subnet with a 255.255.255.0 mask. I don’t fully know the reason why yet but it’s on my list for some further testing. Both your devices were on the same subnet so I don’t really know why Windows was defaulting to 255.255.0.0 - but if you change the mask to 255.255.255.0 it should work just fine."

I’ll go back and try it again with the 255.255.255.0 mask. I think my computer did this to me because it knows I really want to be a MAC guy again <smile>

Thanks Brian & Rob for the quick response,

Bruce

4

Hi 

Similar experience, changed ip to 192.168.10.x, in project.

Was using CS 5.4, ESP-88, FW4.62, but it was not being discovered.

and once rebooted, came to same default 192.168.0.x .

Ant idea how to change the subnet ?