From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,cc65ab136f46904d
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news3.google.com!proxad.net!feeder1-2.proxad.net!newsfeed.straub-nv.de!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From: Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP>
Newsgroups: comp.lang.ada
Subject: Re: GNAT.Serial_Communications
Date: Fri, 15 Apr 2011 17:12:56 +0000 (UTC)
Organization: A noiseless patient Spider
Message-ID: <io9uan$4ej$1@dont-email.me>
References: 
 <d79ca03a-af82-410f-9add-6f6a817b9512@l30g2000vbn.googlegroups.com>
 <inunk9$beu$2@dont-email.me>
 <de88c5f4-ad8e-49d4-96fb-8e665b75c8cf@18g2000prd.googlegroups.com>
 <io4b08$vqq$1@dont-email.me>
 <da0564e5-e856-4080-970a-329d066563d6@f31g2000pri.googlegroups.com>
 <MvGpp.8526$bI3.7652@newsfe15.ams2>
 <9af0087d-9637-40d9-8c30-2e06c2d1e4f4@o26g2000vby.googlegroups.com>
 <d4dc0334-8b72-4c16-84df-a02d99f18cd9@e26g2000vbz.googlegroups.com>
Injection-Date: Fri, 15 Apr 2011 17:12:56 +0000 (UTC)
Injection-Info: mx02.eternal-september.org;
 posting-host="4pjzwDT2MPp9AkNxUo/C4Q";
	logging-data="4563"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX18D28XFfQ0FSPwjTEvctdUoWCQY0zpI814="
User-Agent: slrn/0.9.8.1 (VMS/Multinet)
Cancel-Lock: sha1:ZFp0hJZcnZHX51I3EBlr574hWtw=
Xref: g2news2.google.com comp.lang.ada:19772
Date: 2011-04-15T17:12:56+00:00
List-Id: <comp.lang.ada>

On 2011-04-15, tonyg <tonythegair@gmail.com> wrote:
>
> Actually this is not the problem I spoke too soon. Minicom will talk
> and read the correct values.
> However gnat will read correctly but not write to the port properly,
> but its not hanging anymore so thats a plus. I just cannot see why
> minicom would write the string correctly to the port but when I write
> the string to the port through gnat.serial_communication it does not
> work!!
>

With the Minicom reference, I assume this is a Linux/Unix system (I have
not been following this thread in detail).

The obvious place to start looking are the flow control signals and if
they are been set (and used) correctly.

Have you looked at a full stty output when Minicom is running and compared
it to the settings when your program is running and made sure that the
flow control modes are been setup correctly ?

What flow control is expected by the device receiving your output ?

If hardware flow control is expected by the other device, is your program
asserting the flow control signals (either directly or indirectly)
correctly ?

Simon.

-- 
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Microsoft: Bringing you 1980s technology to a 21st century world