Difference between revisions of "Engine Terms"
From RifidiWiki
(New page: category:developerDoccategory:engineDoc ====Formatter==== The formatter handles any reader specific parsing that needs to be done to a raw message coming into (using the decode met...) |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | [[category:developerDoc]][[category: | + | [[category:developerDoc]][[category:EmulatorDoc]] |
====Formatter==== | ====Formatter==== | ||
| − | The formatter handles any reader specific parsing that needs to be done to a raw message coming into (using the decode method) or going out of the reader (using the encode method). For example, | + | The formatter handles any reader specific parsing that needs to be done to a raw message coming into (using the decode method) or going out of the reader (using the encode method). For an example, see [[Formatter]]. |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
====Handler Method==== | ====Handler Method==== | ||
| Line 64: | Line 12: | ||
return arg; | return arg; | ||
}</pre></code> | }</pre></code> | ||
| + | |||
| + | ====Radio==== | ||
| + | The [[Radio|radio]] is the interface between the antennas and the TagMemory. | ||
| + | |||
| + | ====Tag Memory==== | ||
| + | The [[TagMemory|tag memory]] is the structure that holds tags in a specific reader. Each kind of reader should have its own TagMemory. | ||
| + | |||
| + | ====GPIO==== | ||
| + | [[GPIO]] (General Purpose input/output) is used to interface the reader with other PLC devices such as Light Stacks and Photo eyes. | ||
Latest revision as of 17:56, 29 November 2007
Contents
Formatter
The formatter handles any reader specific parsing that needs to be done to a raw message coming into (using the decode method) or going out of the reader (using the encode method). For an example, see Formatter.
Handler Method
- A method within a reader's project that handles a specific command for a reader. For example if a Rifidi Symbol reader receives a
Set System ParameterCommand, the following method handles the logic for that command:
public CommandObject setSystemParameter(CommandObject arg, AbstractReaderSharedResources asr) {
byte[] setSystemParam = { 0x04, 0x06, 0x27, 0x00 };
arg.getReturnValue().add(setSystemParam);
return arg;
}Radio
The radio is the interface between the antennas and the TagMemory.
Tag Memory
The tag memory is the structure that holds tags in a specific reader. Each kind of reader should have its own TagMemory.
GPIO
GPIO (General Purpose input/output) is used to interface the reader with other PLC devices such as Light Stacks and Photo eyes.
