Did you first read the top-level page of this section in the menu? Is called: Our Chip is Different!
Technical data of our NFC Sensor Chip Platform:
ISO-15693 based, but doing SO MUCH MORE:
- Our NFC Platform is 100% compatible with the widely spread ISO-15693 standard.
- Can be read by all modern NFC Phones, NFC Tablets, NFC Wrist (Phone) Watches, NFC Data Hubs and all ISO-15693 readers that may provide more output power and then can read at much larger distances.
- The chip supports Anti-Collision (reading multiple tags in the field).
- Two Data Encoding Modes (1 of 256 or 1 of 4).
System On Chip (SOC):
- The controller is an On-Chip Computer and it can be programmed by us to provide almost ANY function to the chip.
- Almost ANY type of Sensor or external Circuit can be controlled and its data computed by this programmable internal Micro-Controller.
- Interface Ports can be given a variety of functions.
- Custom Data Encryption could (optionally) be supported.
Internal RFC (Resistance-to-Frequency Converter) for Resistive Sensors:
- 4 x 14-bit RFC ports. This is a very sensitive (very accurate) type of Analogue-to-Digital Converter (ADC) that can distinct extremely small differences (increments) of roughly 120 Ohm.
Effective Temperature Sensing results are ± 0.1 °C accurate (depending on the intrinsic accuracy of the sensor that is selected and on the measurement range).
Mentioned Accuracy is same for tags without any battery or with battery (for Automatic Data Logging).
Temperature measurements are not falsely affected by any RF heating: some other chip designs do suffer from this undesired energy influence.
- The same RFC interface could be used for ANY other resistive type of sensor: either as separate 3rd party component or as printed sensor (where the accuracy depends on the requirement and printing technology that is applied by you or by us for you!).
Very low Power Consumption (3 modes):
- Full Operation mode: On average roughly 300 micro Ampere (depending on the project specifications).
This is only active during a very short time (roughly 1 second only) when the actual measurements are calculated (RFC and Controller active) and data are stored to EEPROM, Real Time Clock is also active.
Immediately after such action the Chip will automatically switch to Standby mode.
- Standby mode: 11 micro Ampere (only with a battery connected for the Real Time Clock: otherwise the standby mode consumes zero).
In this mode only the internal Real Time Clock is running; the Controller and Interfaces are readily waiting for action (standby).
On average the Chip is running roughly 99% of the time in this low power Standby mode.
- Transport mode: 600 nano Ampere (0.6 micro Ampere).
If the tag is connected to a battery, this connection can be switched On and Off anytime by command.
If the battery is switched off, the Real Time Clock will not work. Then the battery leakage is 600 nano Ampere.
Very few external components (BOM):
- Depending on the sensor type and memory configuration a maximum of 2 ~ 5 very tiny capacitors would be needed and 1 Reference Resistor for the RFC Interface. In some cases you maybe wish to add a crystal for an even higher accuracy of the internal Real Time Clock function.
Internal Real Time Clock (relevant for Automatic Data Logging, and so only with battery attached):
- No need for any external crystal. The accuracy of the Real Time Clock without external crystal is almost 99%.
Its accuracy is automatically re-calibrated each time the tag is being read from an NFC - RFID reader.
- In case a higher time accuracy is required (for Data Loggers that are not in any RF Reader field for a long time), an external 100% accurate crystal can optionally be connected: the interface for that option is available. Adding an external crystal does not increase the power consumption.
- SRAM is a kind of internal volatile (temporary) memory that the system uses to temporarily store its function settings and calculated Sensor data to, before it is stored to the optional non-volatile (permanent) EEPROM.
That means that even if the Chip configuration is without any such non-volatile data storage memory, it can still communicate its UID#, optional NDEF string and the real time Sensor measurement results to the NFC Reader.
Its capacity is 2 banks of 128 Byte each. Net available is 192 Byte.
- The need for any permanent Data Storage Memory differs per application and per project.
- Our NFC Chip Platform design allows for zero data storage in case that is not needed, or in case our NFC Chip is connected to another circuit.
For example Bluetooth, or a Controller with its own EEPROM that may already be used in an electronic 3rd party device that we add our NFC functions to, to make it "connected" to the Internet of Things.
- In most configurations though there will be the requirement for permanent data storage (for Data Logging on Chip).
Then we offer a choice of standard EEPROM or optionally for FRAM (which is much more expensive, but much bigger in capacity, very fast in writing speed and less sensitive for Gamma Irradiation as applied in some sterilization processes).
- The data storage capacity can be chosen, depending on the project requirement. Available are EEPROM capacities such as 1, 2, 8, 16, 32 or 64 kb.
- The internal Watchdog circuit checks if the system is running OK. In case of a hiccup, it will automatically reset the circuit, so that it will continue to run well.
LVD and LVR:
- Low Voltage Detect and Low Voltage Reset circuits are implemented.
- The controller can be set to warn if the battery falls under a certain Voltage. So that the user is warned to replace the battery on time for the automatic Data Logging, if needed.
External Voltage (Vext):
- Our Chip can provide 1.8 Volt to any external ciruit that might need power from our Chip.
- An internal LDO (Low Drop-Out) circuit takes care of regulating the output voltage.
- Even if no battery is applied, the energy that is provided to the NFC Chip from the RF Field of the NFC - RFID Reader is sufficient to supply such power to external circuit(s).
- The electrical current from Vext can be up to 4 milli Ampere, depending on the strength of the received RF power.
- Our NFC Sensor Chip can provide many interfaces and other connections. In a maximum configuration as many as 32 pins may need to be reliably connected to a flexible or hard printed circuit.
In most manufacturing facilities SMT chip mounting is a very standard process: SMT offers very fast and reliable connections and very accurate position alignment.
For such most extensive configurations including the integrated permanent data storage we offer SMT mountable QFN32 packaging (5 x 5 mm) with 32 ports. If less ports and lower specifications are needed, we may step down to 4 x 4 mm QFNxx packaging with less ports. All depends on the Custom Chip requirement.
- However: the NFC Chip itself can also be "wire bonded" direct to any circuit or optionally be "glued". Then no packaging is needed, but most factories do not have the machines in place for this type of mounting technology.
For such requests we can provide the Chip as "Die on Wafer". The standard die size is only 2.3 x 2.2 mm.
Optional EEPROM dies can be as small as 0.7 x 1.1 mm (8 kb), depending on the selected storage capacity.