This Article Applies From:
CVI Fusion 7.10.3 | Infinity Client 7.10.3 | Infinity Module 7.10.3 | Core Services 7.10.3 |
Introduction
The following guide is designed to give instructions on how to integrate a Card Reader asset in PivotWare.
A number of compatible card readers are also listed for your consideration.
1 - Pre-requisites
We recommend to first read through the following articles if you are either new to PivotWare, or unfamiliar with the software suite:
- PivotWare architecture overview.
- Station and process creation overview.
- Asset creation overview.
- Creating and managing users.
2 - Card reader asset overview
2.1 - Generic overview
Any user profile can be setup to be automatically logged in when presenting a card on a supported card reader connected to an Infinity Client.
Depending on the options, the card need only to be presented once, or must stay on the card reader at all time for the operator to remain logged in.
2.2 - Choosing a Card Reader model
Several Card Reader models are officially supported:
Card reader manufacturer | Card Reader Model | Communication type | Supported Cards | Configuration Article link |
ACS | ACR122S | Serial | Mifare® Classic Cards | Integrating wih an ACR122S |
ACS | ACR122U | USB | Mifare® Classic Cards | Integrating with an ACR122U |
ELATEC | TWN4 | USB or RS-232 | 125K tags | |
ELATEC | TWN3 | USB or RS-232 | 125K tags |
These card readers can directly be selected from the Card Reader asset selection drop down menu. Their respective configuration is detailed in the corresponding articles.
If none of the card readers listed above offers you the solution you are looking for, PivotWare also offers you, as an alternate solution, the possibility to use generic card readers, providing they support either of the following protocols:
- RS232 plain text.
- USB CCID: in this category, the ACR1252U from ACS has been known to have been successfully integrated with PivotWare.
2.3 - MIFARE® Classic Cards overview
All card readers officially supported by PivotWare operate with Mifare® Classic cards.
These cards are structured around sectors, each containing a number of blocks (the exact number, as well as each sector size, depends on the card storage capacity). However, a number of fields are standard, or recommended:
- Block 0 (Mandatory): the first block of Sector 0 is the Manufacturer of the card data. As a result, it is not usable to write an identification code, and must not be tempered with.
- Block 1 and Block 2 of Sector 0 (Suggested): may hold some specific information about the application the card is intended for. Depending on the on- site use, said sectors cannot be used either to hold the operator's identification code.
- The last block (Mandatory) of each sector encodes the badge Authentication Key. Two keys can be encoded in any MiFare® card (Key A - Key B) and either one must be provided via CVIFusion to the Infinity Client software. Failing to provide the proper code will prevent the system from reading the associated fields.
For further details, please consult the official MIFARE® documentation.
3 - Configuring the Asset in PivotWare
Navigate to the Asset Manager panel then select the project you wish your Asset to be included in.
Set the Asset Type to Card Reader.
3.1 - Settings overview
The permitted settings for any card reader depend both on the Asset Vendor and the selected Card Reader Type. Find below the list of possible Card Reader Properties fields:
Property name | Possible settings | Description | Asset Vendor(s) | Card Reader Type(s) |
Reading mode | Continuous | The card associated to the operator must remain on the card reader at all times. | ACS | ACR122S ACR122U Other CCID |
Other Card Reader | Other CCID | |||
Single Shot | The operator is logged in when the card is presented once to the card reader. The operator can then remove the card. The operator needs to present the card a second time to log out. This mode allows for two different users to be simultaneously logged to the station using only the card reader for identification. | ACS | ACR122U Other CCID | |
Other Card Reader | RS232 Plain Text Other CCID | |||
Authentication Required? | Unchecked / Checked | This option needs to be checked if the identification field written in the card is protected by a specific code (MIFARE® classic cards). The Authentication code can be filled as soon as the option is checked: see 2.3 - MIFARE® Classic Cards overview . | ACS | ACS122S ACR122U Other CCID |
Other Card Reader | Other CCID | |||
Block Number | Value starts at 1 | Specifies the data block the identification field is written to (MIFARE® classic cards See also 2.3 - MIFARE® Classic Cards overview). Infinity Client will retrieve the information from said field to check whether an operator matches the identification value stored in said block. | ACS | ACS122S ACR122U Other CCID |
Other Card Reader | Other CCID | |||
COM Port | Value starts at 1 | The serial com port the asset is connected to. | ACS | ACS122S |
Other Card Reader | RS232 Plain Text | |||
Message segmentation | EOL / Fixed size | Data frames formating. | Other Card Reader | RS232 Plain Text |
EOL Suffix | EOL data frame. | Other Card Reader | RS232 Plain Text |
3.2 - Configuring your Asset in CVIFusion
In order to create your asset:
- Select the Asset Vendor.
- Select the Card Reader Type: note that this option is restricted by your choice of Asset Vendor.
- Select in the Card Reader Properties the Reading Mode.
- Fill in the remaining details of the Card Reader properties.
Note: the baud rate for serial devices is configured at the station level. Please refer to Creating Stations, Steps and Processes article for further details.
You will find further details for integrating with ACR 122S (link) and ACR122U (link) in the corresponding articles.
Find also attached to this article an Asset Configuration File with an example for Other Card Reader / Other CCID devices.
To have more information about integrating with a generic Card Reader, please contact our remote support team. |
Once the settings are complete, click Save Asset then Save Asset Project.
3.3 - Attaching then using the asset in a process
The Card Reader Asset must be associated to the station it is connected to via CVIFusion's Station Manager panel.
Please refer to Desoutter Industrial Tools : Creating and Associating Assets (desouttertools.com) for further details.
Once the Card Reader asset has been attached to the station, navigate to the Process Configuration panel then expand the System Access Logon Types menu.
To allow the operators to login using a card at any specific station, check the Card Reader option is active then click Save Process Configuration to update your station settings.
At this stage, it is already possible to transfer the configuration to the target station.
3.4 - Card code association and Card reader test
To associate users to a station, refer to Creating and managing users article on our support portal.
Once your users have been created and associated to a station, navigate back to the User Manager project.
Select a user for whom you wish to add a Card Code as explained in Creating and managing users then fill in the required information.
If you are unsure about the Card Code, CVIFusion lets you check data written to a card on the Card Reader (providing the device is an ACR122S, ACR122U or an Other CCID). To achieve this:
- Connect the target Card Reader to the computer running the CVIFusion software.
- Click on Card Reader Settings.
- Select the card reader model from the menu that has opened.
- Provide the details to allow CVIFusion to retrieve the Card Code details. The details must be identical to the information filled in the Asset Manager panel. Click Ok.
- Click Read Card from the User Creation pane.
The code will, as a result, appear in the Card Code field and let you save it directly for the current user. Once this is done, you can simply move to another user.
If no data appears:
- Either the Card Reader is not recognised by your computer. This can be checked by displaying the system diagnostics for the station.
Then check whether a card reader is detected:
This solution is only valid when the card reader is either an ACR122S, an ACR122U or any other CCID Card Reader (serial card reader are therefore not taken into account). - No data has been written to the selected Block.
- The Card Reader is not recognised by the operating system: open the Device Manager window and check whether a card reader is detected.
- The service allowing card data to be read is not started: open task manager window, then check whether the SCardSvr service has correctly started.
To further investigate similar issues, please contact our remote support team. |
4 - Further Readings
The following articles can provide with further information: