FAQ

Frequently Asked Questions

  • 1. What is the difference between App and Firmware?

    The firmware occupies most space in flash memory. It provides functions for accessing IO or doing RFID operations. Furthermore, the execution of an app is controlled by the firmware. The firmware cannot be read back from a TWN4.
    A firmware image has the extension .bix.

    The app is the part of flash memory, which specifies the behaviourof a TWN4. Due to this, the programmer of the app has full control over the behaviour of the final application. An app can be programmed by the customer. In order to do so, an appropriate developer pack is provided.

  • 2. Why do we need the folder Driver?

    Our readers can work as Keyboard device and Serial device. When reader with the USB cable is used, we provide firmware with the CDC USB Stack, in order to have a reader as a Virtual Serial Device. For this CDC USB stack additional driver is needed, which we provide in our development pack as a part of the Driver folder.

  • 3. Why do we need the folder Tools?

    In this folder our compiler and libraries used by it are stored. AppBlasteris using files from this folder and it would not be able to work without this.

  • 4. Why do we need the folder Templates?

    In this folder we store templates that customers can use in the AppBlasterinteractive configuration to adjust for example standard App only to technologies that they will use. Also it can be used as a starting point for creating a new image, which contains Firmware + App.

  • 5. Why do we need the folder Projects?

    AppBlasterin older development packsused this folder to store new image that is created through it. In new development packs after 1.64 this folder is not used anymore and firmware image will be created in the same folder where the App is sorted, or in the Appsfolder.

  • 6. Why do we need the folder NFC?

    Here we have our NFCP2PDemo.apk Android application and also our Windows application that can be used for demonstration of NFC Peer-To-Peer communication.

  • 7. Why do we need the Director?

    Customers can use Director tool for some testing of the functionality, which will be later implemented into their own application. Also it can be easily used for reading/writing data into the transponders memory.

  • 8. Why do we need the AppBlaster?

    We need the AppBlasterfor loading new firmware images and new configurations into the reader.

  • 9. What is inside the Manual TWN4 API Reference?

    Here all our functions are explained in details. So every programmer can refer to this document in order to make their own application, which would run on our reader.

  • 10. What is inside the Manual TWN4 AppBlaster (ConfigCards) User Guide?

    Here we have a small guide on how to use the AppBlastertool.

  • 11. What is inside the Manual TWN4 Director User Guide?

    Here we have a small guide on how to use the Director tool. The Director is a powerful tool used to easily test all the internal firmware functions and APIs of Elatec's TWN4 RFID reader. The behavior of TWN4 can be controlled by the user with so called apps which are small programs. They have access to several APIs which makes it easy to develop complex RFID applications. The Director can be used to test the firmware functions and APIs of TWN4 without writing a single line of code.

  • 12. What is inside the Manual TWN4 Simple Protocol?

    Here all our commands for Simple Protocol communication are explained. These commands could be directly used from some third party application in order to control our reader from the Host side.
    Example of the third party application is Terminal program, like PicoTerm, PuTTY, etc..

  • 13. What is inside the Manual TWN4 System Overview?

    Here we have information about the TWN4 devices itself. It includes information about memory layout, pins, communication protocols, history of changes (firmware, tools), etc..

  • 14. Can I export any TWN4 firmware or App from the reader?

    Both firmware and App cannot be read back from a TWN4.
    This allows to store secret keys and other cryptographicfunctionality as part of an App. Furthermore, the possibility to clone a device is avoided and the intellectualproperty is protected.

  • 15. Can I export any TWN3 firmware or Script from the reader?

    Yes, this is possible. There is a button in the TWNConfigtool called “Export”, which can be used for exporting an HEX file. This file later can be loaded to another TWN3 reader.

  • 16. What is the standard firmware we are shipping?

    HID Keyboard Mode

  • 17. Do you know the different USB stacks ?

    ‘K’: USB HID device (keyboard)
    ’C’: USB CDC device class (virtual COM port)
    ’H’: USB HID device (reports)
    ??: CCID

  • 18. What are our standard Apps ?

    “STD": Standard App, TWN4 is searching for transponder and forwarding the ID to thehost
    "PRS": Simple Protocol, TWN4 is running under the control by a host. TWN4 executes
    commands, sent by the host and returns response. In this way, nearly all TWN4 system
    functions can be execute remotely by the host.

  • 19. What means direct chips commands support?

    Direct communication, using native manufacturer‘s commands, is possible.

  • 20. What means T commands?

    Direct communication with Transponder using low level 14443-3 or 14443-4 commands.

  • 21. What is the usage of this 18kB flash inside the TWN4 for?

    To store any kind of user data ,i.e. UIDs

  • 22. How many I/Os has TWN4?

    8 GPIOs for Core, from which 2GPIOs are on the OEM PCBalso.

  • 23. What are Step Data?

    Standard for the Exchange of Product model data for CAD systems.

  • 24. How to program Firmware on TWN3/TWN4?

    Please follow next procedure to update firmwareon TWN3:

    1. Connect TWN3 reader to host
    2. Start TWNConfigtool
    3. Click button Connect
    4. Click on tab Firmware, and select latest firmware for reader.
    5. Click Program, please detect that Protocol window does not show any error
    6. When process is finished start to test it
    7. Start Notepad
    8. Put the card on the reader, there should be some data on Notepad
    9. Remove the card


    Please use AppBlastertool and following procedure to update firmwareon TWN4:

    1. Connect TWN4 reader to host
    2. Start AppBlastertool (from standard DevPack)
    3. Click on “Program Apps & Firmware Images” tab
    4. Click on “Select Image” and select firmware image from DevPack
    5. Click on Program Image button
    6. Start Notepad
    7. Put the card on the reader, there should be some data on Notepad
    8. Remove the card
  • 25. How to program App/script to TWN3?

    If you are not familiar how to set script fileon TWN3, follow next procedure:

    1. Connect TWN3 reader to host
    2. Start TWNConfigtool
    3. Click button Connect
    4. Click on tab Scripting, click on Select Script and select last script
    5. Click Compile, please detect that Protocol window does not show any error
    6. Click button Write Configto store information on TWN3
    7. Click button Restart
    8. Start Notepad
    9. Put the card on the reader, there should be some data on Notepad
    10. Remove the card
  • 26. How to program App/script to TWN4?

    If you are not familiar how to set App script fileon TWN4 , follow next procedure:

    1. Connect TWN4 reader to host
    2. Start AppBlastertool
    3. Click on "Handle Project" tab and "Manage Project" tab.
    4. From "Project Template" select firmware (CDC or Keyboard)
    5. Select "Type of Project" (Create a project based on a given source code)
    6. Click on "Start New Project" will open "Source Code" tab
    7. Click on “Select Source" button and select script file
    8. Click on Blast! button
    9. Start Notepad or Terminal application
    10. Put the card on the reader, there should be some data on Notepad/Terminal
    11. Remove the card
  • 27. What is Interactive Configuration?

    Easy way to configure reader without any knowledge of programming script.

  • 28. Reader is not outputting the requested number, what to do?

    First of all, get output with ‚tracer‘ firmware on the reader to have more information about tag.
    Then you can try with simple output format conversions (hexadecima > decimal etc.)
    Contact support team for more information.

  • 29. How to have USB TWN3/TWN4 reader recognized as a serial device on a PC?

    You need to change mode of operation on TWN3 readers to Virtual COM Port with TWNConfig tool.
    On TWN4 you need to load firmware based on CDC with AppBlaster.

  • 30. How to connect TWN4 reader with the Director tool?

    You need to have Simple Protocol firmware loaded on the reader in order to work with Director testing tool.

  • 31. How can I read the firmware from the TWN4 reader?

    If firmware version is not defined on label of reader, firmware versions base on firmware 300 and higher are available in Device Manager, right click on TWN4 reader in Human Interface Device -> Properties -> Details tab -> Property: Bus reported device description.

  • 32. Can I read the firmware “.bixfile” and find out the configuration?

    It is not possible since it is read protected.

Contact

If you have any questions, please feel free to contact us. We are looking forward helping you with your request.

To contact form