EAN8 to EPC and EPC to EAN8 produces different results about epc-tds HOT 7 CLOSED

Got it, thank you so much for the library and for the information!)

from epc-tds.

Hello Dmitry,
The EAN codes you are using have the wrong control code. For example, the ean 0000007401802(4) has 4 as check digit.
Greetings.

from epc-tds.

I checked all the above eans here https://www.gs1.ch/en/home/offer/barcode/check-digit-calculator-and-ean-13-barcode-generator and yes all of them have the wrong check digit. Thank you so much for pointing it out!)

from epc-tds.

Hi Dmitry,

Thanks for your input.

GS1 documentation indicates that a GTIN must have 14 digits, so the user must fill in with leading zeros.

Try this:

console.log('eanToEpc -> epcToEan:', epcToEan(eanToEpc('00000060573421')));

Or modify your eanToEpc method, like this:

const eanToEpc = (ean: string): string => {
const epc = new tds.Sgtin96().setGtin(ean.padStart(14,"0"));
return epc.toHexString();
}

You can also use this GS1 web app to perform checks:

https://www.gs1.org/services/epc-encoderdecoder

Best regards.

Sergi

from epc-tds.

Aha, and then when I receive a result from RFID device (which is EPC) and extract EAN from it, I can safely remove all leading zeros from this EAN?

from epc-tds.

Yes, you can remove them, but if you want to use a standard later (GTIN-8, GTIN-12, GTIN-14), you will have to control the number of digits.

from epc-tds.

Hello,

I use the same logic ean -> epc -> ean and seems like there is something wrong with some ean numbers:

original ean: 00000074018029. decoded ean: 00000074018024. epc: 30000001C3C5280000000000
original ean: 00000045214445. decoded ean: 00000045214448. epc: 3000000113F7900000000000
original ean: 00000028225773. decoded ean: 00000028225775. epc: 30000000AC46C40000000000

The last digit in decoded ean differs from the original ean number.

What could be the reason for such behavior?

from epc-tds.