Re: Telnet app with no UI
From: LowlyEngineer (charles_at_linquist.net)
Date: 04/01/05
- Next message: Frank Saxton: "Dump question"
- Previous message: J.O. Aho: "Re: Telnet app with no UI"
- In reply to: J.O. Aho: "Re: Telnet app with no UI"
- Next in thread: Walter Mautner: "Re: Telnet app with no UI"
- Reply: Walter Mautner: "Re: Telnet app with no UI"
- Reply: Dmitriy M: "Re: Telnet app with no UI"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 01 Apr 2005 07:15:01 -0800
Unfortunately, I only know microcontroller Assembly language - not 'C'
or Linux, so I can't help them very much.
Right now, you can use ANY standard telnet program (Hyperterm,
TerraTerm, even DOS telnet) to communicate/control our machine. As
soon as a connection is made, our machine announces itself. It
outputs its ip, machine name, serial number and status. Any
characters sent to it through telnet are interpreted and
acted upon by that machine.
It was initially thought that a human would be able to view the status
and control the machine from anywhere in the world (passwords can be
turned on, if desired).
Now, the customer wants to parse the data and look for certain
character strings ("ERROR" for example), and send a response back
("OFF", for example). There will be no human or display screen
involved. What is desired is -
1. The customer's application will send the IP of the machine to the
Linux telnet "mini-application", which will initiate the telnet
session to the specified IP, and report back only if a connection
cannot be established.
2. All incoming characters (from the telnet session) will be directed
to the customers application.
3. The customers application will send ASCII responses to the
"mini-telnet" Linux application.
I don't know if I have explained this in the right way.
TIA
On Fri, 01 Apr 2005 16:50:04 +0200, "J.O. Aho" <user@example.net>
wrote:
>LowlyEngineer wrote:
>> Sorry about the lack of specifics. This is a machine monitoring and
>> control application where data formatted in ASCII strings will be
>> autonomously sent from a machine (produced by my company) then parsed
>> and acted upon by the customer's code. Upon reception of certain
>> codes, the customer's application will respond (again in ASCII) with
>> one of 4 simple commands.
>
>So it's really not questiuon about telnet, but a simple protocol that your
>company have made itself.
>
>
>> There will normally be no human interaction of any kind.
>> The customer's code be responsible for establishing the telnet
>> session.
> > My impression is that the only time a human will be notified is if a
> > telnet session cannot be initiated by the customer's application.
>
>telnet will requier human interaction.
>
>
>
>So what do yoiu really want to ask?
>How to make a small tool that knows your communication protocol?
>
>
> //Aho
- Next message: Frank Saxton: "Dump question"
- Previous message: J.O. Aho: "Re: Telnet app with no UI"
- In reply to: J.O. Aho: "Re: Telnet app with no UI"
- Next in thread: Walter Mautner: "Re: Telnet app with no UI"
- Reply: Walter Mautner: "Re: Telnet app with no UI"
- Reply: Dmitriy M: "Re: Telnet app with no UI"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|