It has been nearly a year since I left california and started hunting for jobs in Minnesota, and I must say I couldn’t be happier. Entrust Datacard has given me many chances to prove my worth as an engineer. This document will highlight some of the tasks I have completed while working at Entrust Datacard(EDC).

RFID Tags

Initially I was hired as a firmware engineer to work on EDC’s most widley used printing platform. However not long after my employment a need arised for a “RFID Tag Czar”, someone who could quickly and easily take on the full range of responsibilites with the RFID tags used by our printing supplies. I was of course estatic to be given the opportunity to showcase my skills as an engineer who could be the lead developer for a large portion of our supplies business.

After accepting the job responsibilites I was quickly thrown into the deepend. There was a backlog of work that needed to go get finished and there was minimal documentation on how to accomplish it. I worked cross departmentally to quickly get up to speed on our products and the way they were used. By the end of my second week much of the major maintance work was finished. This meant I was now free to tackle other issues that were being seen with our RFID tags, including a failure rate of 5%-10%.

Reduction in RFID tag failures

I of course cannot go into specifics, but can say that in order to fix the problem I had to take ownership of 2 different code bases and fix both firmware and software. The systems were not properly reporting errors and therefore when communication was lost the tag would be “broken”, and we had no way to fix it because there was 0 error handeling.

I immediatly began identify the errors, and determining where in the programming process they were being broken. After Identifying the several differnt points of failure I than began fixing the software to handle fixing these errrors when they were detected. However the firmware with which this software communicated was not setup to handle these new error commands and therefore it too had to be modified. This was an on going problem for 3 months, however at the end of 3 months the number of fixable errors was down to below 0.5%.