Beeps from the ACR-1255U-J1

[MartyParticipant]

The device seems to beep when the tag is readable and when the tag is no longer readable. Is there a way to generate different beeps based on the event: one sound if its within range of the tag, and a different sound when its no longer in range.

[MartyParticipant]

Also – the reader seems to be most sensitive when I place the diagonal corner (next the the BATT and COMM lights) closest to the tag. Is that accurate based on where the NFC chip reader is? Is there any way to get the NFC reader (on this device) to be even more sensitive? It was able to read the tag when held about 1/4 inch above the tag, but not 3/4 of an inch.

• This reply was modified 5 years, 11 months ago by  Marty.

[ScottKeymaster]

Hi Marty,

Glad to hear you’ve got it working.

|| Is there a way to generate different beeps based on the event:

It’s not possible to configure the beep when entering and exiting the field.

|| Is there any way to get the NFC reader (on this device) to be even more sensitive?

The only way to configuration this strength is to use the configuration of highPower(kHighPower in Obj-C) for transmitPower in your FmConfiguration.

https://docs.flomio.com/#transmitpower

Looking at the code you sent this week, it’s already configured that way.

Scott

[MartyParticipant]

1. You didn’t answer this question: the reader seems to be most sensitive when I place the diagonal corner (next the the BATT and COMM lights) closest to the tag. Is that accurate based on where the NFC chip reader is?

2. If I wanted the firmware modified for the beeps to change for tag nearby vs. out of range, is that possible?

3. If I wanted the firmware modified to increase power even higher, is that possible?

4. Does the scan period configuration setting have any effect when using it with bluetooth instead of the audio port?

[RichardKeymaster]

@Marty

1. That’s not accurate, the NFC scan surface is in the bottom portion of the FloBLE face, below the Flomio Spark logo (circle).

2. I sent you a text message today about the firmware change. We estimate it’ll be $2000 of NRE effort to implement this.

3. The power is currently set to the max on the NFC reader chip. That being said improved range can be achieved by choosing the best tag geometry for your tags. More info here.

4. Yes, bluetooth is much faster than the audio jack interface so scanning is faster.

best,
Richard

[MartyParticipant]

Thanks. The videos were helpful.

We need labels that are about 30mm circular (or square). Which ones, in your experience, give the maximum signal? The ones we experimented with, purchased from Amazon for about $0.08 each, probably would only make it through one of the square stone blocks you show in the video.

[MartyParticipant]

One more question. Assume we have a line of 10 tags spaced about 1.5 inches apart – roughly 40cm, and want to move the flomio device over the tags so that we can read each and every tag in that line.

1. How slowly would we have to move the reader?

2. The device beeps when the tag is in range, but it takes another second or so to read the tag. Is there any information send from the reader, available to the SDK, when the reader is first in range? If not, can this change be made, and what information could be collected (for an NRE fee).

[RichardKeymaster]

> Which ones, in your experience, give the maximum signal?

35mm round. Copper coil. Best are from Smartrac or HID

> How slowly would we have to move the reader?

About an inch per second for best results.

> Is there any information send from the reader, available to the SDK, when the reader is first in range?

Only the tag type, make and model. This is known as the ATR and is non-unique information. Tag read times are sub second. If it’s taking longer then the issue may be you are using poor quality tags. We can run benchmarks on your tags of choice to recommend best ways of improvement at $150/hr contract rate. Since end result is subjective, it’s hard to estimate effort. I suggest we start with purchasing a Flomio Service package and we go from there.

best,
Richard

[Author]

Posts