If a supported Baltech RFID stand-alone device is used, the TwinCAT PLC library can be used as interface.
Alternatively certain Beckhoff Control Panels or Panel PCs can be used. In these devices a RFID reader can be integrated as an option.
In this case an SDK containing the proprietary documentation is provided.
The functionality if the TwinCAT library is the same in both cases.
RFID reader settings
Quality Equipment for the Recycling Industry. Main Promo Images. Quality You Can Depend On. For over 19 years, Baletech® Recycling Equipment (a Division of J.M. Hydraulics, Inc.) has built products with the highest quality steel and components.
For smooth communication between controller and RFID readers, some settings need to be made before the system startup. These include, for example, the baud rate for the serial communication. The proprietary tool 'Baltech id-engine explorer' provided by the RFID reader manufacturer can be used to transfer these settings to the RFID reader. The tool can be used to carry out a function test to check whether the RFID device is recognised and whether the transponder cards are detected.
- The BALTECH Expert software is designed for database management and is compatible with the BALTECH VP-3470 vibration analyzer, infrared cameras and alignment systems. The software enables to: Create measurement routes on vibration diagnostics.
- Phillips Driver Bits. Starting at $3.60. 3M Aqua Pure 3MFF100 Full Flow Drinking Water Filtration System. Starting at $267.89. Jamestown Distributors #2-56 S/S.
The following default settings are recommended for the data communication:
| Setting | Value |
|---|---|
| Baud rate | 115200 baud |
| Parity Bit | none |
| Data bits | 8 |
| Stop bit | 1 |
This matches the factory setting of the supported Baltech RFID devices. Other parameters can be set, if required. These must then also be adopted into the reader connection on the software side.
The baud rate of the reading devices can be changed with the tool 'Baltech id-engine explorer'. (See Baltech documentation: IdEngineExplorer.pdf)
Note: The tool 'Baltech id-engine explorer' only runs under Windows XP. It is not available for Windows CE. The baud rate is therefore not configurable under Windows CE.
Note: In the PLC a fast task is required for processing the incoming data. If the RFID device is connected to a COM port with a baud rate of 115,200 a cycle time of 1 ms is required (see section Reader interfacing)
Note: In order to configure the baud rate from the PLC, the following byte sequence can be transferred as a raw data block [ 0x 1C 00 09 06 00 01 03 00 02 xx xx - with xx xx representing the baud rate, e.g. 9600 baud: 96 units at 100 baud -> 0x 00 60 ]. Further information can be found in section 'Low level communication'. This is also possible under Windows CE, if a transfer with the currently set baud rate is possible.
Usage of virtual serial COM ports (USB)
If the device is connected via USB the corresponding Usb-To-Virtual-Com-Port driver has to be installed. This driver is already installed if it is about a Beckhoff Panel-PC. The SDK of the RFID device contains the driver too. The virtual COM port is displayed in the Windows device manager.
The Beckhoff TwinCAT 'Serial Communication' is used for the communication to driver. But neither a device is added to TwinCAT System Manager nor a mapping is done. Further information is to be found in the Documentation for the PLC library serial Communication.
Handling of the RFID reader
The library supports the standard settings for the Baltech communication. 'Host Operation' mode is supported. Other modes are not supported. The BRP (Baltech Reader Protocol) is used for internal access in 'Communication Mode' 'Normal Mode'. If raw data are sent via the low level communication option it is important to ensure that the above settings are correctly specified within the frame.
Note: It must be pointed out here that not all peculiarities of every supported RFID reader model can be named here. Therefore you are referred to the manufacturer’s own documentation for more detailed information.
Configuration
If encrypted transponder cards are used, the same key must be available in the RFID device. The Baltech RFID reader is configured once, i.e. the key only has to be specified once. For security reasons the key cannot be read from the device configuration. In line with the encryption of a transponder card a VHL file is stored in the device configuration. Several VHL files can be stored in order to be able to access different cards access without reconfiguration.
There are three options for transferring VHL file into the configuration of a RFID device.
| Configuration type | Description |
| Configuration card | A configuration can be transferred via a configuration card. This is the preferred option. |
| 'Baltech id-engine explorer' tool | This tool can be used to transfer a configuration into the memory of the Baltech RFID device. (See Baltech documentation: IdEngineExplorer.pdf) In simple cases the specific configuration can be created directly in the tool. Alternative Baltech offers technical support and can provide a file containing the configuration.
|
| from the PLC | For Mifare Classic cards the transfer of a VHL file configuration can be programmed in the PLC program code. The command SetConfig transfers the configuration specified at the input in ST_RFID_ConfigIn. The structure of a Mifare card and the possible settings for key allocation are explained in ST_RFID_CfgStruct_BaltechMifVHLFile. (More detailed information about Mifare cards can be found in the Baltech document entitled Mifare.pdf) |
Transponders
Suitable transponder cards for Baltech RFID devices are available from several manufacturers. If cards with encryption are to be used, Baltech offers preconfigured cards for this purpose.
Manufacturer contact
Driver installation under Windows XP/Vista/7 (32/64-bit)
The Elektor RFID Reader comes with the Élektor-Vendor ID (0x0C7D) and a Product ID (0x0005). Because the Elektor RFID reader uses a modified Vendor ID and Product ID, it’s not possible to use the original FTDI CMD driver from the FTDI website.
Note: This driver is not certified and cannot be installed on Windows 8 x64.
Driver installation under Windows 8.
Windows 8 x64 will only allow the installation of certified drivers. The certified driver supplied by FTDI (http://www.ftdichip.com/Drivers/D2XX.htm) will work with the FDTI-Vendor ID (0x0403) and the Product ID (0x6001) for their respective devices.
For this driver it is necessary that the Elektor Ventor ID (0x0C7D) and the Elektor Product ID (0x0005) is replaced by the FDTI-Ventor ID (0x403) and the FDTI -Product ID (0x6001). This is done by changing the FDTI chip configuration.
For changing the FDTI-chip configuration, FTDI provides the free software tool 'FT_PROG'(www.ftdichip.com/Support/Utilities.htm).
Important: The following steps must be running under Windows XP or WIN7.
1. Start FT_PROG
2. Read the FDTI-chip configuration with the menu command Device | Scan and Parse.
3. Select in the dialog 'USB Device Descriptor' for the custom VID / PID option the value 'FDTI Default '..
4. Download the modified configuration with the menu command Device | Program in FDTI chip.
Now you can use the original certified FDTI USB driver for the Elektor-RFID-Reader under XP / Vista / WIN 7 / WIN 8.
The FT232R USB/RS-232 Converter
FTDI's FT232R (IC1) was selected as a USB-to-serial converter for the reader circuit.
- USB 2.0 Full-speed compatible.
- The entire USB protocol is integrated on the chip.
- RS232, RS422 and RS485 with a data rate of between 300 baud and 3 Mbaud.
- Different bit bang modes.
- Integrated 1024-bit configuration EEPROM.
- Integrated USB termination resistors.
- Built-in clock generation requiring no external crystal.
- Configurable Control Bus (CBUS) I/O pins.
- Unique identification number (FTDIChip-ID).
- Free driver for Windows, Windows CE.NET, Linux und Mac.
USB-Treiber Architektur
Future Technology Device International (FTDI) provides two different versions of the PC drivers. Tge Virtuelle COM-Port (VCP) driver emulate a traditional RS-232 interface (COM port). Auf In this way, existing PC software, such as a terminal emulator, can be used.
Baltech Usb Reader Driver
The second driver variant, Direct Driver (D2XX), consists of a proprietary DLL (FTD2XX.DLL). This has a lot more features available that the VCP driver. Reading and writing the EEPROM configuration requires the use of the D2XX driver. Data communication is much more efficient with this driver, as it uses the Direct Block Transfer and Bulk Mode USB feature.
Baltech Driver Jobs
For Windows, the installation of the VCP and D2XX drivers is done from a single package, in the Combined Driver Model (CDM). This has only been the case since 2006. Until then, it was not possible to install both drivers together on a Windows system.
Bel Tec Driver
For the Elektor-RFID-Reader, both drivers are needed. The Virtual COM Port driver is used mainly for programming the P89LPC936. The current C# reader library uses the D2XX driver DLL, due of its expanded features.