Carlos Prados wrote:
I was wondering if it is any way of passing the CT-API interface some
serial port parameters, such as baudrate, parity, number of stop bits and
byte size.
The ctapi.h interface does not allow passing none of these parameters, and
there is *no* way to send serial port
Gregor,
Would it be against OSI model if we put the IO parameters in a config
file? I think this is better from a practical point of view than having
two diferent shared libraries for two identical (except the IO
initialization parameters) readers.
This config file could be the same we use to
From: Gregor [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
X-Mailer: Mozilla 4.03 [de] (WinNT; I)
MIME-Version: 1.0
To: [EMAIL PROTECTED]
Subject: Re: MUSCLE serial.h ctapi.h question
References: Pine.LNX.3.95.980928134912.20836B-10@radius
Content-Type: text/plain; charset=us-ascii
Hi,
I am just going through the code for the Reflex driver. Some of
questions:
1) It seems to me that this is basically a CTAPI but not CTBCS compliant
driver.
2) In the skeleton driver, why not defining a set of refence header
files (like a ctbcs.h file, a driver -specific header file and so
You should notice if you have the latest ctapi driver for the Reflex that
in the Ct_data function most of the CTBCS functions are interpreted. I
have masked off some of the bytes mainly due to the fact for example in a
Reset, I always return the ATR no matter what. I realize it is not fully
