4 Replies Latest reply on Dec 8, 2016 10:21 AM by Edward Correia

Behavior of scanner after setting decoderParams.i2of5.length

Markus Balschbach Dec 8, 2016 2:24 AM

Hi all,

in our applications we need to scan different lengths of I2of5-barcodes.

Today we have three different lengths in 2of5:

plombage - length 8 digits
parcel - length 24 digits
dock receipt - length 26 digits

We also use different lengths of Code128...

In our WindowsMobile-Applications we used the settings for MinimumLength and MaximumLength in DecoderAPI.dpI2OF5 of EMDK for .Net.

Within the EMDK for Android there are settings named length1 and length2; althought we thought this has the same meaning it has not...

Using Length1 and Length2 in EMDK for Android (V5.0) the scanner only reads barcodes with that specific lengths, we can't define a length-range any more.

Is this a bug or a feature ?

What do we need to do to tell the scanner to scan all barcodes in range 8 to 26 digits ?

Kind regards

Markus

Re: Behavior of scanner after setting decoderParams.i2of5.length

Markus Balschbach Dec 8, 2016 6:57 AM (in response to Markus Balschbach)
Sorry, problem is solved after telephone call

Here's the result for those who have same problem:

Default config for 2of5 is
length1 = 14
length2 = 10

This means you're able to scan barcodes having a length of 10 and 14, nothing else.

I thought - because of these default-values - length1 is the upper bound and length2 the lower bound for the range.
Turning my lengths around solved the problem.

If you need a range, then use length1 as lower bound and length2 as upper bound
If you need two fixed lengths use length2 for the lower length and length1 for the higher one.

@Moto:
Would be nice to have an short hint in the help-file for the EMDK

Kind regards
Markus
Like Show 0 Likes(0)

Actions
Re: Behavior of scanner after setting decoderParams.i2of5.length

Darryn Campbell Dec 8, 2016 6:57 AM (in response to Markus Balschbach)

Hi Markus,

My understanding of these lengths was that length1 was the minimum length and length2 was the maximum length, though the documentation does not spell this out explicitly.

Can you please confirm you tried with length1 as 8 and length2 as 26?

Darryn.
Like Show 0 Likes(0)

Actions
- Re: Behavior of scanner after setting decoderParams.i2of5.length
  
  Darryn Campbell Dec 8, 2016 7:00 AM (in response to Darryn Campbell)
  
  Ah, replied at the same time
  
  USER09527, is it possible to have the documentation updated as suggested?
  
  Thanks.
  
  Like Show 0 Likes(0)
  
  Actions
  - Re: Behavior of scanner after setting decoderParams.i2of5.length
    
    Edward Correia Dec 8, 2016 10:21 AM (in response to Darryn Campbell)
    
    absolutely Darryn. thanks for letting me know. ps...I moved the "correct answer" designator to the solution Marcus got from support. I hope you don't mind.
    
    Like Show 0 Likes(0)
    
    Actions

Go to original post