Reader to WISP Communication

Reader to WISP (downlink) communication is still in the prototype stages. Here's some info on the current state of things.
Questions? Head on over to the discussion board!

Link Layer Options


Select Command

Advantages:
  • Quick
  • Low Power
Disadvantages:
  • Reader may send infrequently - low rate, wisp may not catch command
  • No singulation to address particular WISPs

Read Command

Advantages:
  • Singulated tag
  • Tested firmware
Disadvantages:
  • High power consumption
  • Possibly not a lot of room for uplink data

Write Command

Advantages:
Disadvantages:
  • High power consumption
  • Not available in standard firmware release

Application Layer Options


Web App

Advantages:
  • Should be bug-free, see note below
  • Simple
Disadvantages:
  • No data logging
  • No automation
  • Not application-friendly

Polly's Note:
Word to the wise: I've been testing this code against the Impinj RFIDemo, using the InventoryFilter page. It appears to me that it only sends the first three bytes pattern fields (aka the mask field in the spec) correctly. So don't expect it to be able to look for (say) entire EPCs correctly. Also, when testing this code out in RFIDDemo, put your mask data in hex in the leftmost part of the pattern field.

Supported LLRP Reader Application

Advantages:
  • Framework is there
  • Intel-supported
  • Read support, but not totally fleshed out
Disadvantages:
  • Write are not yet implemented, should be similar to Read code

Impinj LLRP Application

Advantages:
  • Framework is lacking
  • Read and Write should work similar to web app
Disadvantages:
  • Spaghetti code

C++ Impinj-Proprietary Application

Advantages:
  • Solution may exist - contact Polly
Disadvantages:
  • Not supported by Impinj or Intel
  • No GUI






The last modification was made by - Changer119 Changer119 on Dec 2, 2009 4:49 am