File: README

package info (click to toggle)
slbreflex 2.2.0-6
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 200 kB
  • ctags: 200
  • sloc: ansic: 1,523; makefile: 79; sh: 73
file content (59 lines) | stat: -rw-r--r-- 1,971 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
MUSCLE CT-API Reader API / PCSC Driver for Reflex 62/64.

Author: David Corcoran
License: See LICENSE

Note: You must set your COM port under main.c for CT_init().

This is a compatible API with the German CT-API Health Card Standard for
the Schlumberger Reflex 62/64 readers.  Please look out for more readers
to come supported under the CT-API.  This is the lowest level API for 
MUSCLE smartcard readers.  This also supports the basic CT-BCS
command set.  This also works with the PC/SC infrastructure.

Here are the CT-API available functions:

CT_init( unsigned int Ctn, unsigned int pn )

   Ctn: Terminal Number (not used)
   pn : Port number, PORT_COM1, PORT_COM2, PORT_LPT1, etc.


CT_data( unsigned int cn, unsigned char *dad, unsigned char *sad,
         unsigned int lc, unsigned char *cmd, unsigned int *lr
         unsigned char *rsp )

   cn : Terminal Number (not used)
   dad: Destination Address (See Below)
   sad: Source Address (See Below)
   lc : Length of command
   cmd: Command Data Buffer
   lr : Length of return
   rsp: Response

CT_close( unsigned int Ctn );
   Ctn: Terminal number (Not used)


  What is sad and dad ?????  This allows you to distinguish between
talking to the card or the reader. Basically here are the available
values:

   0    Smart Card 
   1    Reader
   2    Host

So if your sad (Source Address) is 2 and your dad (Destination Address) is
0 you want to send a command from the host to the smartcard such as a Get
Response. If your sad is 2 and your dad is 1 then you want to send a
command from the host to the reader such as a Card Power Off.

If you are looking to support your reader under the Linux Smart Card
Resource manager and Open Card Framework I would suggest creating a
CT-API driver like this one and fitting into the two frameworks will
be simple with the code that will sit on top that is being written.

Please let me know if you have any questions.

Thanks,
Dave Corcoran   (corcordt@cs.purdue.edu)