Hi VI Guy,
In order to access your RT target you normally need to know its IP address. The example I linked earlier will help in situations where you need to connect to a specific RT target but for some reason do not know its IP address. This can happen if you configure your target to obtain an address from a DHCP server - which means that every time the controller boots it could potentially have a different address. When this happens, you could use this example to reestablish a communication with the RT engine.
The reason the serial number is required is that we need to know which of all the RT targets found on your network is the one you are interested in. So yes, in order to connect to an RT target you do need to know either the static IP addr
ess, or its serial number. You could figure out this serial number either from MAX or by looking at the sticker on the hardware.
The example is provided as an exe because it is meant as a programmatic connection tool, specifically in a situation like the one described above (where a connection is lost). At this time we can't provide the source code that provides this functionality (so I guess calling it an example is a bit of a misnomer.)
From your original post, I thought you were looking for a tool you could embed in your application that would find your controller. If this is not the case, please let me know. With your feedback, we can look at improving this utility or provide more effective ones.
Regards,
Dafna