I'm looking for some advice on dealing with a quirk in the Net2 access control system at my workplace. We frequently order UID cards for our door access system, but a recent batch of 750+ cards has a leading zero in their 10-digit UIDs. Unfortunately, when we input these into Net2, the leading zero gets dropped since the system seems to only accept integers. Has anyone discovered a workaround for this? Any tips or settings I could adjust would be really helpful!
4 Answers
You might want to check the configuration utility in Net2. There’s a setting that controls how data is read from the cards. You could try tweaking that to see if it helps with the leading zero issue.
We faced a similar issue! It turns out that Net2 only recognizes the last six digits of the UID that come off as hexadecimal from the card reader. If you convert those last six digits from hex to decimal, you get the number Net2 expects. For example, if your card reads as 0000C67A23, take the last six digits (C67A23), convert that to decimal, and it gives you 13007395. This worked for us!
From my experience, Net2 takes the last eight digits of the card's serial number as a decimal value. It might help to create an Excel sheet that converts from hex to decimal so you can manage the formatting effectively before entering them into Net2.
That's definitely how Net2 seems to process UID numbers—it treats them as integers and drops leading zeros. When we had a similar issue, we standardized how the UIDs were formatted before importing them, which saved us a lot of hassle down the road. We also had troubles with another system where we had to normalize everything, so it helped to have a consistent format from the start.
Totally agree! It’s worth ensuring you have a system in place to avoid these kinds of problems later on.
Yeah, exactly! When we integrated across different systems, that led to a lot of confusion with leading zeros. Normalizing the format before it hits your access control database is such a good practice.