Hi,
I have a very similar problem. however Im running on a ramps 1.4 nad if Im also using the G3D nozle.
Although this is an old topic, has a solution been found?
In my case the temp reading drops instantaneously and is held there (or jumps around at a faulty temp) for a random amount of time and then the actual temp value is read, in some instances (more often than I should like) the actual hotend reaches a temp value which is too high and then the firmware auto-shutsdown the print. This leads me to believe that the board still recieves the temp signal and corrects according only that the reading mechanism must be the faulty part.
I should add that I also changed the pin to which the hot end thermostat was connected to and I am still getting this weird drop.
I have a very similar problem. however Im running on a ramps 1.4 nad if Im also using the G3D nozle.
Although this is an old topic, has a solution been found?
In my case the temp reading drops instantaneously and is held there (or jumps around at a faulty temp) for a random amount of time and then the actual temp value is read, in some instances (more often than I should like) the actual hotend reaches a temp value which is too high and then the firmware auto-shutsdown the print. This leads me to believe that the board still recieves the temp signal and corrects according only that the reading mechanism must be the faulty part.
I should add that I also changed the pin to which the hot end thermostat was connected to and I am still getting this weird drop.