Difference between revisions of "ThingMagic"
From RifidiWiki
| Line 4: | Line 4: | ||
;Model Number: | ;Model Number: | ||
| − | + | 4 | |
;Network Protocol: | ;Network Protocol: | ||
| − | + | SQL like protocol that may be wrapped in ssh, web interface, RCP, and Linux shell login. | |
;Communication: | ;Communication: | ||
10/100 BaseT Ethernet – RJ45 | 10/100 BaseT Ethernet – RJ45 | ||
| Line 12: | Line 12: | ||
4 read points (4 transmit points, 4 receive points) | 4 read points (4 transmit points, 4 receive points) | ||
;General Purpose I/O: | ;General Purpose I/O: | ||
| − | + | (To Do) | |
==Basis of Virtual Reader== | ==Basis of Virtual Reader== | ||
| Line 29: | Line 29: | ||
===Memory Model=== | ===Memory Model=== | ||
| − | + | The memory model is like a state based database. | |
===Getting Tags=== | ===Getting Tags=== | ||
| + | Getting tags is fairly simple just execute: | ||
| + | <pre><nowiki> | ||
| + | telnet [reader ip address] 8080 | ||
| + | </nowiki></pre> | ||
| + | Then type: | ||
| + | <pre><nowiki> | ||
| + | select id from tag_id set time_out=[milliseconds]; | ||
| + | </nowiki></pre> | ||
| + | Note: the semicolon at the end of each command is necessary. | ||
| + | <br /><br /> | ||
| + | One can also return multiple items: | ||
| + | <pre><nowiki> | ||
| + | select id, protocol_id from tag_id set time_out=[milliseconds]; | ||
| + | </nowiki></pre> | ||
| + | |||
| + | Also add filters or conditionals: | ||
| + | <pre><nowiki> | ||
| + | select id from tag_id where [condition or filter] set time_out=[milliseconds]; | ||
| + | </nowiki></pre> | ||
| + | |||
| + | In addition more than one statement can be put on more than one line. | ||
| + | <pre><nowiki> | ||
| + | select id from tag_id set time_out=[milliseconds]; select protocol from tag_id set time_out=[milliseconds]; | ||
| + | </nowiki></pre> | ||
| + | |||
====On Demand==== | ====On Demand==== | ||
Revision as of 23:46, 9 February 2008
Contents
Introduction
- Model Number
4
- Network Protocol
SQL like protocol that may be wrapped in ssh, web interface, RCP, and Linux shell login.
- Communication
10/100 BaseT Ethernet – RJ45
- Antennas
4 read points (4 transmit points, 4 receive points)
- General Purpose I/O
(To Do)
Basis of Virtual Reader
Documentation
Client Tools
Reader Design
This section will give a brief overview of how the hardware reader operates for the purposes of emulation.
Communication
Protocols
The main method for communicating with the reader is via TCP, TCP+SSH on port 8080, web interface, and RCP.
Memory Model
The memory model is like a state based database.
Getting Tags
Getting tags is fairly simple just execute:
telnet [reader ip address] 8080
Then type:
select id from tag_id set time_out=[milliseconds];
Note: the semicolon at the end of each command is necessary.
One can also return multiple items:
select id, protocol_id from tag_id set time_out=[milliseconds];
Also add filters or conditionals:
select id from tag_id where [condition or filter] set time_out=[milliseconds];
In addition more than one statement can be put on more than one line.
select id from tag_id set time_out=[milliseconds]; select protocol from tag_id set time_out=[milliseconds];
On Demand
Autonomous Mode
Login
Supported Features
[To do.]
Unsupported Features & Bugs
Linux shell access to reader. This is fairly complex and require to emulate the entire hardware infrastructure of the reader and an ARM possessor. Also the web and RCP interface might be developed at a later time.
