For example:
my PC is 120.120.120.1 and another PC is 198.222.234.4. I must send the
string "Hello" from my PC to second and wait the acknowledgement.
Have you a simple source?
Thanks in advance.
Roberto
Servizio Tecnico wrote in message <8ia2sp$p06$1...@news.mclink.it>...
kenmullins
"Servizio Tecnico" <soft...@gescart.com> wrote in message
news:8ia2sp$p06$1...@news.mclink.it...
"donald tees" <don...@willmack.com> ha scritto nel messaggio
news:8iafsp$qok$1...@news.igs.net...
> By far the easiest way to do this is to write it to a file on a server,
and
> then read it on the other machine.
>
> Servizio Tecnico wrote in message <8ia2sp$p06$1...@news.mclink.it>...
On Thu, 15 Jun 2000 10:28:34 +0200, "Servizio Tecnico"
<soft...@gescart.com> wrote:
>Hi,
>anybody know the API to send and receive a string from PC to another across
>the network.
>
>For example:
>
>my PC is 120.120.120.1 and another PC is 198.222.234.4. I must send the
>string "Hello" from my PC to second and wait the acknowledgement.
>
>
>Have you a simple source?
>Thanks in advance.
>Roberto
>
>
---
Try a better search engine: http://www.google.com
My personal web site: http://www.geocities.com/Eureka/2006/
Servizio Tecnico wrote in message <8iak5p$1sh$1...@news.mclink.it>...
>This way is not possible because inside the other PC (sorry PLC!) another
>program wait my call with a propetary ASCII protocol (like
>L001;A,12,12,<checksum>x"0d").
>
>
>"donald tees" <don...@willmack.com> ha scritto nel messaggio
>news:8iafsp$qok$1...@news.igs.net...
>> By far the easiest way to do this is to write it to a file on a server,
>and
>> then read it on the other machine.
>>
>> Servizio Tecnico wrote in message <8ia2sp$p06$1...@news.mclink.it>...
With the PING command I see the converter but I don't know the API to
communicate.
Roberto.
"donald tees" <don...@willmack.com> ha scritto nel messaggio
news:8iaspb$6t0$1...@news.igs.net...
How do you get the IP address set up? Device supplied software? The
supplier of than code may provide a subroutine library that would be easier
to use, since even after you get the correct API call you are still going to
be faced with protocol matching.
Servizio Tecnico wrote in message <8ib04h$6kr$1...@news.mclink.it>...
Servizio Tecnico wrote in message <8ib04h$6kr$1...@news.mclink.it>...
>Yes is true for the rs232 communication but this PLC is particular. The PLC
>is connected with a converter RS232-TCP/IP because the installation is done
>over 15 metres (limit of RS232) from the PC.
OTOH, you CAN use either a line driver, or even a pair of modems
back-to-back to extend past 15 metres (line drivers are available for up to
3 miles at 9600bps ... )
Would be much easier, I would bet.
RwP
kenmullins
"Ralph Wade Phillips" <ral...@techie.com> wrote in message
news:Fw7Ir...@news.boeing.com...
The line length limits on RS-232-C are also baud rate dependent, as the
primary problem is line capacitance. The 15 meter limit is at 19,200 baud,
lines well shielded. At 1200 baud, I have driven RS-232 800 metres with
no problem.
A PLC normally has I/O that conforms to standard wiring, so you can just
hook in a 660 volt motor starter, for example. The same thing is true for
various industrial meters and flow control valves, etc.
Programming one is done by ladder diagrams, almost like programming the old
patch boards for unit record equipment, but done on a screen. The program
is then flash blasted into ROM of some sort. Communication to a computer is
normally via a serial port, often the same one that you connect a PC to for
programming.
The effect of the entire PLC is to provide manual backup for the system, as
well as a complete industrial interface subsystem. Years ago, when I first
started in this industry, those functions were provided for by huge banks of
industrial relays. The PLC gives you a programmable firmware equivalent.
To run the entire thing by computer, you then ask the PLC to "turn on" a
motor. The PLC internal programming functions as the equivalent of a
dedicated channel controller, and ensures that you cannot override safety
requirements, for example. (a nice feature, BTW. Before the damned things
were invented, I once managed to get into an infinite loop that *filled* a
truck with the entire contents of a 250,000 ton silo of stone. We had to
dig it out with a front end loader. Even though I did ask the driver to get
out before the test, I was razzed about that for years)
Ken Mullins <**Ken**Mullins**@**mindspring.com** remove **'s> > wrote in
message <8ib7d8$4mm$1...@slb2.atl.mindspring.net>...
>What is a PLC?
>
>kenmullins
>
>"Ralph Wade Phillips" <ral...@techie.com> wrote in message
>news:Fw7Ir...@news.boeing.com...
Ken Mullins <**Ken**Mullins**@**mindspring.com** remove **'s> > wrote in
message <8ib7d8$4mm$1...@slb2.atl.mindspring.net>...
>What is a PLC?
>
Programmable Logic Controller.
RwP
Look up sockets. Thane has some cobol examples on his site from
memory.
One PC accepts the socket (server) and the other creates the link
using sockets (client).
Thanks
Ken Foskey
http://www.zipworld.com.au/~waratah/
For fast secure document delivery on the Net
http://www.themailxchange.com.au/
I must store this as the funniest bug I have ever heard :-}
Ken Foskey wrote:
>
> > To run the entire thing by computer, you then ask the PLC to "turn on" a
> > motor. The PLC internal programming functions as the equivalent of a
> > dedicated channel controller, and ensures that you cannot override safety
> > requirements, for example. (a nice feature, BTW. Before the damned things
> > were invented, I once managed to get into an infinite loop that *filled* a
> > truck with the entire contents of a 250,000 ton silo of stone. We had to
> > dig it out with a front end loader. Even though I did ask the driver to get
> > out before the test, I was razzed about that for years)
>
> I must store this as the funniest bug I have ever heard :-}
>
I agree. One omission by Don, he forgot to mention he was probably
'stoned'. <G>
Jimmy
Ken Foskey wrote in message <39496F4A...@zip.com.au>...
>> To run the entire thing by computer, you then ask the PLC to "turn on" a
>> motor. The PLC internal programming functions as the equivalent of a
>> dedicated channel controller, and ensures that you cannot override safety
>> requirements, for example. (a nice feature, BTW. Before the damned things
>> were invented, I once managed to get into an infinite loop that *filled*
a
>> truck with the entire contents of a 250,000 ton silo of stone. We had to
>> dig it out with a front end loader. Even though I did ask the driver to
get
>> out before the test, I was razzed about that for years)
>
>I must store this as the funniest bug I have ever heard :-}
>
Nope, Not a chance. Although a died-in-the-wool stoner, I cannot program
stoned. It affects short term memory too much, so I never even try to work
stoned, though I could as I am my own boss.
I have found, that I often get valuable insights when stoned, and often will
light a doobie in the evening to consider a problem, and often come up with
new algorithms then. However, I always wait until the next day to try to
code.