Article View: borland.public.cppbuilder.nativeapi
Article #6062Re: help me with ACK/ ENQ protocol please
From: N. Karademir
Date: Mon, 13 Jun 2005 22:34
Date: Mon, 13 Jun 2005 22:34
76 lines
3285 bytes
3285 bytes
thanx "Colin B Maharaj" <noreply@myhost.com> schreef in bericht news:42a8bed6$1@newsgroups.borland.com... > Hi N. :) > Serial communications uses the ASCII character set and they were probably > designed hand-in-hand > the letter 'T' is at position 84 in the ASCII table and the letters 'A' to > 'Z' runs from 65 to 90. I hope you get this. > > Now, there are what is called non printable characters or control > characters that were / are used primarily for Serial Communications > These run from position 0 = NULL CHARACTER to 31. > When doing software flow control in Serial comms you will need to design > your app to recognise and send these characters for flow control. > Here is the list - I hope this helps.... > > Dec Hex ASCII Description ^Key > > 0 0 NUL (null) Ctrl-@ > 1 1 SOH (start of heading) Ctrl-A > 2 2 STX (start of text) Ctrl-B > 3 3 ETX (end of text) Ctrl-C > 4 4 EOT (end of transmission) Ctrl-D > 5 5 ENQ (enquiry) Ctrl-E > 6 6 ACK (acknowledge) Ctrl-F > 7 7 BEL (bell) Ctrl-G > 8 8 BS (backspace) Ctrl-H > 9 9 HT (horizontal tab) Ctrl-I > 10 A LF (line feed) Ctrl-J > 11 B VT (vertical tab) Ctrl-K > 12 C FF (form feed) Ctrl-L > 13 D CR (carriage return) Ctrl-M > 14 E SO (shift out) Ctrl-N > 15 F SI (shift in) Ctrl-O > 16 10 DLE (data link escape) Ctrl-P > 17 11 DC1 (device control 1) XON Ctrl-Q > 18 12 DC2 (device control 2) Ctrl-R > 19 13 DC3 (device control 3) XOFF Ctrl-S > 20 14 DC4 (device control 4) Ctrl-T > 21 15 NAK (negative acknowledge) Ctrl-U > 22 16 SYN (synchronous idle) Ctrl-V > 23 17 ETB (end of trans. block) Ctrl-W > 24 18 CAN (cancel) Ctrl-X > 25 19 EM (end of medium) Ctrl-Y > 26 1A SUB (substitute) Ctrl-Z > 27 1B ESC (escape) Ctrl-[ > 28 1C FS (file separator) Ctrl-\ > 29 1D GS (group separator) Ctrl-] > 30 1E RS (record separator) Ctrl-^ > 31 1F US (unit separator) Ctrl-_ > > > > N. Karademir wrote: >> Hello, >> >> can someone give me some info about ack/enq protocol? >> >> i f i am right, the rs232 device sends me ENQ, then i send ACK back, then >> it >> sends data, finally i'll sent ACK.? >> >> How do i send ACK? >> >> is this just the letters "ACK" ? >> or is it a dec / hex value i have to send? >> >> >> >> thanks >> >> >> N. Karademir >> >> >>
Technical Details
Message-ID:
<42adeea7$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news2.google.com!proxad.net!gatel-ffm!gatel-ffm!194.25.134.126.MISMATCH!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<42a4b193@newsgroups.borland.com> <42a8bed6$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 10cc67,30f067a42f010330 X-Google-Attributes: gid10cc67,public X-Google-Language: ENGLISH,ASCII-7-bit From: "N. Karademir" <n.karademir@smart-software.org> Newsgroups: borland.public.cppbuilder.nativeapi References: <42a4b193@newsgroups.borland.com> <42a8bed6$1@newsgroups.borland.com> Subject: Re: help me with ACK/ ENQ protocol please Date: Mon, 13 Jun 2005 22:34:54 -0000 Lines: 77 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-RFC2646: Format=Flowed; Response NNTP-Posting-Host: 84.84.63.230 Message-ID: <42adeea7$1@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1118695079 84.84.63.230 (13 Jun 2005 13:37:59 -0700) Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news2.google.com!proxad.net!gatel-ffm!gatel-ffm!194.25.134.126.MISMATCH!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail