That's an extremely nice opamp!
Also rather expensive.
But nice !! :-)
- Something is fundamentally wrong with the real-world circuit that is not shown on the diagram.
The described behaviour makes no sense at all in one area so the rest is suspect.
That is, once one thing is completely un-understandable it can mean there is some major factor that has been missed.
LM6152 data sheet here.
The non inverting input is high impedance and NOTHING that the opamp does in normal use will affect it's voltage - so if something does then something is very wrong outside normal opamp behaviour.
The LT1638 data sheet here that you say worked is also a nice op amp, but in almost exactly the opposite way.
It couldn't pull the skin off a rice pudding downhill on a good day with the wind behind it.
Its forte is super low power and it has super low bandwidth and slew rate to go with it.
Whereas, the LM6152 is a 75 MHz bandwidth !!!! 45 V/uS slew rate !!!!!!!!!! stunner more at home in ski-jumping or single digit standing 1/4 miles.
SO I'd guess that the LM6152 is having major instability and oscillation problems which the LT1638 avoids by virtue of just being so darned slow that it is not pushed into oscillation by whatever is troubling the LOM6152. It may be that better power supply decoupling really close to the IC, or a whiff of low pass filtering in the feedback path (maybe a resistor << R3 in M1 source and a NF or less on inverting input to ground?, ...?) may help.
If you have no decoupling at all on the IC power supply near the IC, write it in the lessons learned book - even if it doesn't fix the problem.
OpAmp overloaded:
It does not seem to be what is causing the problem, but you opamp is sinking more current than allowed for a formally correct design when the LED is on.
With opamp output high Vout is 15V (rail-rail amp)
If VLED = 2.5V then Iout = (Vout-VLed)/ R4 = (15-2.5)/1k = 12.5 mA
Isource _max_typical = 6.2 mA, minimum = 3 mA and max = 17 mA.
So your attempted output is double typical available and 4 x minimum and less than best case.
This could do no worse tha pull Vout well below rail - and worst case could cause device malfunction.
However, it does not seem to be relevant to the problem that you describe.
Note: Formal professional design requires you to design for worst case parameters in the worst case situation that you require the design to work in.
This often leads to performance far below what it appears a device may usually achieve and often worst-case design is extremely conservative and functionally unnecessary.
However, if you want the circuit to always work, this is the correct way to design it.
In order to bring order out of chaos, I enjoy looking at older questions and helping them to completion. This question, along with the good contributions from the above commentors can be moved forward to help others :
Using the IR sensor as described, I have merely modified the OP's circuit so that the stated function can be implemented.
As stated by comments above, low power op-amp needs a transistor to be able to drive the "vibration motor". Transistor Q1 has been added. Use any transistor that has V-gate threshold less than 4 volts, along with minimum Id of 100mA.
LM393 output is open collector, thus the addition of R1.
R2 was added to put some hysteresis into the circuit, so that the op-amp output doesn't oscillate (bang bang, go hi then low) when sensor signal is close to the setpoint.
Setpoint is achieved by the potentiometer.
The circuit proposed is not supposed to be an exact solution, but one that will give a starter point for others.
Best Answer
There's an error in observing the valid electrical parameter for Vin CM range (common-mode) on the datasheet.
The input transitors need this to bias the NPN differential input amplifier.
You need a ground sensing comparator like the quad-LM339 (PNP inputs) or a negative Vee supply of at least 2V on the 741.