This content has been marked as final. Show 5 replies
Edge Server tries to decode tags when inserting them into the database: hex/binary to company id, class, serial, ... . This is based on a file named encodings.xml. If the header (first 8 bits for epc gen2) cannot be found as defined in this file, the automatic decode fails. Decode e.g. works for sgtin, sscc and grai with 64 and 96 bit length.
So, to get an exception here is not nice, but uncritical. You could add your custom coding to your encode.xml...
Thank you very much for the information. This whole process of running and configuring a ses is really frustrating. Which leads to another question....Where did you get your information about how to run and config the ses? I don't remember reading about the encode.xml file. Maybe I just missed it, I dunno. I can setup and get it to read tags but I am at a loss on how to use the ses properly.
Send me you mail address and I´ll send you a hands-on tutorial we´re using in partner trainings...
ses doesn't distinguish between antennea ids at this point. You have to use a reader per location.
fyi all...Sorry , wrong thread. I meant to reply to this one Mercury4 ThingMagic Antenna identification
ses doesn't distinguish between antennea ids at this
point. You have to use a reader per location.