Skip to main content
Visitor II
June 18, 2021
Solved

Causes and solutions for reading performance degradation

  • June 18, 2021
  • 3 replies
  • 1012 views

We made a prototype, but the reading performance is worse than EVAL.

It was confirmed that the value of Ext.signal sourse in the "normal with RF on" state was large.

Therefore, it is presumed that the large reception noise is the cause of the deterioration of reading performance.

Is this guess correct?

When measured with a certain antenna,

both "Refrected Power" values are -20dBm or less.

However, the value of Ext.signal sourse in the "normal with RF on" state is about -70 dBm for EVAL, and about -60 dBm for our prototype.

What is the cause of this difference?

How can we improve read performance?

    This topic has been closed for replies.
    Best answer by Bart Herse

    Hi Mizum.1

    We made a prototype, but the reading performance is worse than EVAL.

    --> how exactly is the performance lower?

    --> is it read range or read speed, etc...?

    --> please quantify the lower performance.

    --> details about the performance test would be very helpful (reader antenna, which tag, reader settings, TX power, etc...)

    It was confirmed that the value of Ext.signal sourse in the "normal with RF on" state was large.

    --> Ext.signal Source: I am assuming you are referring to the Diagnostic Sweep Function available in the GUI.

    --> So an external signal source is used, maybe a RF signal generator, and the reader is swept across the frequency band using the

    Ext. Signal Source function in order to detect it?

    --> I believe that there is a limited value in this kind of measurement.

    --> In order to measure the reader sensitivity I recommend to use dedicated measurement equipment. If you PM me your email address I can point you to two well known companies - one from Austria the other from Finland.

    Therefore, it is presumed that the large reception noise is the cause of the deterioration of reading performance.

    Is this guess correct?

    --> At this point, without additional information, it is difficult to say what the root cause of the experienced lower performance might be.

    --> How was the reception noise measured?

    When measured with a certain antenna,

    both "Refrected Power" values are -20dBm or less.

    However, the value of Ext.signal sourse in the "normal with RF on" state is about -70 dBm for EVAL, and about -60 dBm for our prototype.

    What is the cause of this difference?

    --> There is a number of potential causes for this difference.

    --> I would start at looking at the component choices and the layout

    How can we improve read performance?

    --> As I mentioned above, additional inputs are needed to provide a specific recommendation.

    --> In general:

    + Check output power - compare tests with max. power and reduced power (-6 dB),

    + Layout and components,

    + Reader settings - are they the same for both readers?

    Cheers,

    B

    3 replies

    Visitor II
    June 30, 2021

    Hi Mizum.1

    We made a prototype, but the reading performance is worse than EVAL.

    --> how exactly is the performance lower?

    --> is it read range or read speed, etc...?

    --> please quantify the lower performance.

    --> details about the performance test would be very helpful (reader antenna, which tag, reader settings, TX power, etc...)

    It was confirmed that the value of Ext.signal sourse in the "normal with RF on" state was large.

    --> Ext.signal Source: I am assuming you are referring to the Diagnostic Sweep Function available in the GUI.

    --> So an external signal source is used, maybe a RF signal generator, and the reader is swept across the frequency band using the

    Ext. Signal Source function in order to detect it?

    --> I believe that there is a limited value in this kind of measurement.

    --> In order to measure the reader sensitivity I recommend to use dedicated measurement equipment. If you PM me your email address I can point you to two well known companies - one from Austria the other from Finland.

    Therefore, it is presumed that the large reception noise is the cause of the deterioration of reading performance.

    Is this guess correct?

    --> At this point, without additional information, it is difficult to say what the root cause of the experienced lower performance might be.

    --> How was the reception noise measured?

    When measured with a certain antenna,

    both "Refrected Power" values are -20dBm or less.

    However, the value of Ext.signal sourse in the "normal with RF on" state is about -70 dBm for EVAL, and about -60 dBm for our prototype.

    What is the cause of this difference?

    --> There is a number of potential causes for this difference.

    --> I would start at looking at the component choices and the layout

    How can we improve read performance?

    --> As I mentioned above, additional inputs are needed to provide a specific recommendation.

    --> In general:

    + Check output power - compare tests with max. power and reduced power (-6 dB),

    + Layout and components,

    + Reader settings - are they the same for both readers?

    Cheers,

    B

    Mizum.1Author
    Visitor II
    July 14, 2021

    @Bart Herse​ 

    Hi Bart Herse

    We made a prototype, but the reading performance is worse than EVAL.

    --> how exactly is the performance lower?

    --> is it read range or read speed, etc...?

    --> please quantify the lower performance.

    --> details about the performance test would be very helpful (reader antenna, which tag, reader settings, TX power, etc...)

    When using EVAL, the reading range is about 4-5m. 

    When using our prototype, the reading range is about 1-2m. 

    Read speed is about 220 tag/s using EVAL, 140 tag/s using our prototype at the range of 2m.

    Antenna is Advantenna-p12 made by Keonn.

    Tag is ALN-9840 made by Alien.

    It was confirmed that the value of Ext.signal sourse in the "normal with RF on" state was large.

    --> Ext.signal Source: I am assuming you are referring to the Diagnostic Sweep Function available in the GUI.

    --> So an external signal source is used, maybe a RF signal generator, and the reader is swept across the frequency band using the Ext. Signal Source function in order to detect it?

    --> I believe that there is a limited value in this kind of measurement.

    --> In order to measure the reader sensitivity I recommend to use dedicated measurement equipment. If you PM me your email address I can point you to two well known companies - one from Austria the other from Finland.

    I set "Reader settings" -> "settings" -> "Device power mode" -> "normall with RF on" in the GUI.

    and I measure Ext.signal Source: Diagnostic Sweep Function available in the GUI.

    We recognize that this state is simulating the receiving state. 

    Therefore, it is presumed that the large reception noise is the cause of the deterioration of reading performance.

    Is this guess correct?

    --> At this point, without additional information, it is difficult to say what the root cause of the experienced lower performance might be.

    --> How was the reception noise measured?

    I measure Ext.signal Source in the GUI.

    How can we improve read performance?

    --> As I mentioned above, additional inputs are needed to provide a specific recommendation.

    --> In general:

    + Check output power - compare tests with max. power and reduced power (-6 dB),

    + Layout and components,

    + Reader settings - are they the same for both readers?

    Max. output power is 29.0dBm.

    Reduced power (-6dB) is 26.0dBm.

    We using AMP -TQP9107- and 10dB Directional Coupler same with EVAL board.

    Reader settings are the same for both readers.

    Visitor II
    July 14, 2021

    Dear Mizum.1,

    I suspect the cause for the lower performance to be a specific issue for which this community forum might not be the best place to solve it.

    Therefore I suggest that you PM me your email address and company info so that regional support can help you clearing this issue.

    I would be glad, that once the issue is solved, we post any insights and "lessons learnt" here in this thread to provide a closure to this topic.

    Cheers,

    B