Which IPC should I use or where can I get some info about IPC

  • Thread starter Thread starter Anders Eriksson
  • Start date Start date
A

Anders Eriksson

I have a project where I have two hardware things (Lasers) that each are
controlled by a Windows PC. I need to control both of the lasers from
one of the PC's

This means that I need to communicate between the two programs that
controls the laser.

The communication will consist of a number of strings, about 30 with a
max lenght of 80 characters.

Anyone that can recommend a way to communicate?

Or maybe suggest somewhere I can read up on this?

// Anders
 
I have a project where I have two hardware things (Lasers) that each are
controlled by a Windows PC. I need to control both of the lasers from
one of the PC's

This means that I need to communicate between the two programs that
controls the laser.

The communication will consist of a number of strings, about 30 with a
max lenght of 80 characters.

Anyone that can recommend a way to communicate?
Click to expand...

TCP/IP more specifically TcpListener and TcpClient
seems as a good choice to me.

Arne
 
TCP/IP more specifically TcpListener and TcpClient
seems as a good choice to me.
Click to expand...

I have been thinking a bit and I think that I want to have three
programs. One master that communicates with the database and then sends
commands to a client that controls the hardware.

Hmmm.. I guess that I need to have two TcpListener, one for each
control program and one TcpClient for the database program.

If I do it that way I could add new hardware and just configure a new
ip-address for the TcpClient program.

Is this a good way of solving this?

// Anders
 
I have a project where I have two hardware things (Lasers) that each are
controlled by a Windows PC. I need to control both of the lasers from one
of the PC's
Click to expand...

PCs with frikkin' lasers on their heads!
 
I have been thinking a bit and I think that I want to have three
programs. One master that communicates with the database and then sends
commands to a client that controls the hardware.

Hmmm.. I guess that I need to have two TcpListener, one for each control
program and one TcpClient for the database program.

If I do it that way I could add new hardware and just configure a new
ip-address for the TcpClient program.

Is this a good way of solving this?
Click to expand...

I would have the server (master) have one TcpListener and Accept
a TcpClient per client and start a new thread for each, and the
clients use TcpClient to connect to the master.

Arne
 
Back
Top