David,
>Go for it.. I see no problem with that. Also, I had no problem with the
>little chipdrive. It seemed to work fine with the same interface.
The IO initialization parameers of Chipdrive extern and the little
Chipdrive micro is the same: 8 bits/byte Even parity and 2 stop bits. The
Tow
It could feasably fit well. I don't know how we would specify which reader to
use in the CT-API though. Although int ctn is the Card Terminal number. Isn't
this only if you have multiple readers on the same device ? We would have to
come up with a numbering convention.
Thanks
Dave
On Mon, 28
Go for it.. I see no problem with that. Also, I had no problem with the
little chipdrive. It seemed to work fine with the same interface.
Thanks
Dave
On Mon, 28 Sep 1998, you wrote:
>I was wondering if it is any way of passing the CT-API interface some
>serial port parameters, such as baudra
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 te
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
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
the serial.h does not allow passing the number of stop bits.
I
