The Engineering Projects

Infrared Tracker Sensor Library for Proteus

Hello friends, I hope you all are doing great. Today, I am going to share a new Infrared Tracker Sensor Library for Proteus. By using this library, you will be able to simulate IR based tracker sensor. This library contains 4 tracker sensors in it. This Infrared Tracker Sensor is not present in Proteus software and we are sharing it for the first time. We have already shared 2 Proteus Libraries of Infrared sensors, you should check them as well. Note:

• You should also have a look at:
  • IR Proximity Sensor Library for Proteus.
  • Infrared Sensor Library for Proteus.

First, let's have a look at what is tracker sensor and why is it used?

Where To Buy?
No.	Components	Distributor	Link To Buy
1	IR Tracker Sensor	Amazon	Buy Now
2	Arduino Uno	Amazon	Buy Now

What is IR Tracker Sensor???

• IR Tracker Sensor uses Infrared technology and contains two IR LEDs on it.
• A signal is transmitted from one LED, which is reflected back after hitting some target and is received by the second LED.
• This sensor is normally used in Line Tracking Robotic Projects, where the black line is sensed by this IR Tracker sensor.

Infrared Tracker Sensor Library for Proteus

• First of all, download the zip file of Proteus Library by clicking the below button:

Download Proteus Library Files

• Once you downloaded the zip file, extract it and open the folder named "Proteus Library Files".
• You will find three files in it, named:
  • InfraredTrackerSensorTEP.IDX
  • InfraredTrackerSensorTEP.LIB
  • InfraredTrackerSensorTEP.HEX
• Place these three files in the Library folder of your Proteus software.

Note:

• If you are facing problems with adding a library in Proteus 7 or 8 Professional, then have a look at How to add a new Library in Proteus 8 Professional.

• Now open your Proteus software or restart it, if it's already running.
• In the components section, we need to make a search for Infrared Tracker Sensor, and you will get results as shown in the below figure:

• As you can see in the above figure, now we have 4 infrared tracker sensors in our Proteus database.
• Let's place these sensors in the Proteus workspace, that's how they will look like:

Adding Hex File to the sensor

• Now we need to add the hex file to the sensor, so double click on the sensor to open its Properties Panel.
• In the properties panel, we have a textbox named "Program File".
• In this textbox, browse to the hex file of the sensor, which we have placed in the Library folder of Proteus software, as shown in the below figure:

• After adding the hex file, click the OK button to close the properties panel.

Our sensor is now ready to operate.

Infrared Tracker Sensor Pinout

• As you can see these sensors have five pins in total, which are:
  1. V: Power.
  2. G: Ground.
  3. D0: Digital Output.
  4. A0: Analog Output.
  5. Test: For Testing Purposes.

Why Test Pin is used?

• As it's a simulation, so we can't actually generate IR pulses, that's why I have placed this Test Pin.
• As the voltage at Test Pin will increase, the sensor will consider it as the obstacle is coming close.
• We will place a potentiometer at this Test Pin.
• This Test Pin is not present in a real IR Tracker sensor.

So, let's design a simple simulation of this Infrared Tracker sensor to have a look at its working:

Infrared Tracker Sensor Proteus Simulation

• Design a simulation in Proteus, as shown in the below figure:

• I have placed an LC circuit in front of the analog output because we have to convert the peak to peak voltage to Vrms.
• This LC filter is also not required in real hardware, but in simulation, we need to place it to get an analog value.
• Now, let's run our Proteus simulation of the IR sensor and if everything goes fine, you will get results as shown in the below figure:

• I have simulated two of these sensors, the rest will work the same and as you can see depending on the potentiometer, we got different values at the output.

So, that was all for today. I hope this library will help you guys in your engineering projects. If you have any questions/suggestions, please use the below comment form. Thanks for reading. Take care !!! :)

Why Connected Gadgets Are a Bad Fit for Municipal Applications

These days, it seems everything is a part of the internet of things (IoT). There is hardly a category of consumer gadget that doesn’t have an IP address or that connects to the internet in some way. One of the most venerable and respected authorities in tech news had good reason to wonder if many internet of things devices should even exist. We all need to be more careful about our salt intake. But does that somehow justify the existence of a salt dispenser with an internet connection? The internet is not going to be much help when cooking toast. Yet you can get a toaster with that feature. It is important we don’t overreact to the obvious abuses of technology. There will always be opportunists to take advantage of a new technology trend and leave a bad taste in the mouths of potential consumers. On the whole, connected devices are a good thing and can provide an extra measure of utility and security. As with everything, one just has to be discerning enough to know the difference between items that are genuinely helpful and ridiculously wasteful.

Safety

A city or township could deploy powered exoskeletons for the part of the workforce that literally does the heavy lifting, The wearer of the suit is the sole operator of the suit. No part of the operation is subject to an iffy connection with a network. The wearer controls the suit at all times. The reason exoskeleton suits are so safe is that they are always under the complete control of the wearer. Each element of the suit is activated by the operator’s initiative. If the operator wishes to lift something heavy and awkward, she uses familiar grappling and lifting motions and the exoskeleton responds. This arrangement enhances the ability of a single lifter to move objects that might otherwise require multiple people. It is always safer when a person can lift with less strain and reduce the tendency to drop items that could cause injury if mishandled. When it comes to heavy lifting, the only thing you want your equipment connected to is a skilled human who knows how to use it.

Security

Police departments, emergency responders, and hospitals cannot afford to be hacked. One thing we have learned about the internet of things is that security is seldom the highest priority. When it comes to purveyors of these goods. They often come with basic passwords that don’t have to be changed before being deployed. Your security cameras should never activate until you have a secure password. These companies are also not especially vigilant when it comes to providing the best hardware and software encryption. Their priority is selling and not security. We have already seen the consequences of hospitals being held hostage by ransomware attacks. We have seen hackers get into public utilities such as the water supply. Every connection to the internet is a vector of attack. The last thing you want is for every light bulb in the sheriff’s office to be an easy target for hackers. If security is your priority, stay away from connected devices to the extent possible.

Savings

Municipalities don’t have money to burn. They have to operate on a strict budget. They can ill-afford $60 light bulbs. Connected devices tend to cost more because they have added components and unnecessary complexity. That also means they are less likely to last as long as a simpler device. One of the reasons is that connected devices have a software component. What happens when that software needs an update or becomes obsolete? In far too many cases, the device becomes useless. Sooner than you want, your internet of things will be transformed into a basement of bricks. That said, IoT has a lot of promise when deployed well. But the technology is not a good fit for municipal deployment due to legitimate concerns about safety, security, and spending.