G
Guest
I am new to both sockets and Netcf.
My task is to move an instrument controller module (called an ICE
implemented on a ICE.dll) down into a Pcb that supports Netcf. At present at
the Desktop level it uses Remoting to communicate with another application.
After reading various articles, the Msdn and this newsgroup I believe that
Sockets would be a good choice for us since Remoting is not supported on the
Netcf.
We manufacture analytical instruments for chemists (ICP's, Atomic Absorption
spectrometers, etc). Each will include a WinCe with an ICE to control it.
There can be 1 to N ICE's on each Pcb (though it will usually be 1). All
ICE's are controlled by a central component called the MIM (implemented as
MIM.dll).
The ICE's will only communicate with the MIM not with other ICE's.
I have created feasibility Apps that connect a desktop App to a Compact App
using sockets. When I do this I determine the Ip address manually. Since the
Ip on the setup I have is assigned by the local Lan box (a LinkSys box) it
may vary depending on startup sequence. Also the desktop will vary for the
same reason. Furthermore, in actual operation a User may not use a LinkSys
but have his desktop connected to a company Lan. In some other cases there
may be no Lan at all. Just the desktop and the instrument.
The question is how do I determine the Ip of the ICE running on a WinCe Pcb
from the desktop without privous knowledge? How does the destop and WinCe
pcb's intially connect up? Do you use a general broadcast of some sort. Is
there a way to set the ICE running on the WinCe Pcb from the desktop at power
on, keeping in mind that it can't be the same Ip for each Pcb since the MIM
could be connected to 1 to N ICE's on 1 to M WinCe Pcb's.
Also again how do you handle the situation where there is no Lan, just a
desktop, a hub and 1 to N ICE's on 1 to M WinCe Pcb's?
Appreciate any help, suggestions or code samples.
--John
My task is to move an instrument controller module (called an ICE
implemented on a ICE.dll) down into a Pcb that supports Netcf. At present at
the Desktop level it uses Remoting to communicate with another application.
After reading various articles, the Msdn and this newsgroup I believe that
Sockets would be a good choice for us since Remoting is not supported on the
Netcf.
We manufacture analytical instruments for chemists (ICP's, Atomic Absorption
spectrometers, etc). Each will include a WinCe with an ICE to control it.
There can be 1 to N ICE's on each Pcb (though it will usually be 1). All
ICE's are controlled by a central component called the MIM (implemented as
MIM.dll).
The ICE's will only communicate with the MIM not with other ICE's.
I have created feasibility Apps that connect a desktop App to a Compact App
using sockets. When I do this I determine the Ip address manually. Since the
Ip on the setup I have is assigned by the local Lan box (a LinkSys box) it
may vary depending on startup sequence. Also the desktop will vary for the
same reason. Furthermore, in actual operation a User may not use a LinkSys
but have his desktop connected to a company Lan. In some other cases there
may be no Lan at all. Just the desktop and the instrument.
The question is how do I determine the Ip of the ICE running on a WinCe Pcb
from the desktop without privous knowledge? How does the destop and WinCe
pcb's intially connect up? Do you use a general broadcast of some sort. Is
there a way to set the ICE running on the WinCe Pcb from the desktop at power
on, keeping in mind that it can't be the same Ip for each Pcb since the MIM
could be connected to 1 to N ICE's on 1 to M WinCe Pcb's.
Also again how do you handle the situation where there is no Lan, just a
desktop, a hub and 1 to N ICE's on 1 to M WinCe Pcb's?
Appreciate any help, suggestions or code samples.
--John