Revo 6 PID tuning just hangs
-
I will re verify, however, nothing has changed as this config g had been working just fine. it just sat for close to a year since i last printed and all i changed was updating the firmware and replace the v6 with a revo 6. it was almost just plug and play. i only had to install a xt 30 connector to the heater cable and it does show continuity through the coil at that connector. its when i went to try to pid tune that things just decided to causing grief...
-
Does the LED near the heater output light up when you turn on the heater to a set temp?
-
We could also switch to another heater output incase it's the heater mosfet that has failed. If it still doesn't work that would mean it's either the heater itself or the cable in between.
-
Does the temp displayed increase if you warm it up with your hands or a heat gun?
-
@Phaedrux said in Revo 6 PID tuning just hangs:
And you're sure the heater is connected to e1heat?
Yes, it is connected to E1 on the board
yes the led lights up.
let me find my heat gun
-
panel due displayed 19.5 c room temp. I put the heat gun to the nozzle area and then checked the panel due and it then showed 40.3c so the thermistor is working properly it seems.
-
@wingtip So what happens if you simply try heating the tool. i.e set the active temperature to something other than zero - say 50 deg C or so? Does it try to heat then?
-
@deckingman said in Revo 6 PID tuning just hangs:
@wingtip So what happens if you simply try heating the tool. i.e set the active temperature to something other than zero - say 50 deg C or so? Does it try to heat then?
does nothing
-
@wingtip Can you check the e1heat terminals with a multimeter? Is it putting out 12v when a temp is set and the LED is on?
-
lol, ive said a few times that ive verified its putting out 12 volts at the connector at the hotend when i do the pid command with a multimeter, at least till it cancels itself a minute later saying temp not rising... which makes no sense. so if its sending 12volts to the connector at the hotend, its definately got it at the mainboard, then when it cancels, it goes back to zero vdc. I will re verify though.
Im starting to guess that you guys are gettings about as stumped as i am
EDIT: ok i think this printer is possessed ... I went to re verify the voltages from the mainboard.- placed volltmeter leads on the board terminals, reached over to the panel due and set a temp of something around 60 or 70c and it kicked on, where it wasnt kicking on before. then i looked at the voltage, it was 10.5 volts this time.
2, i killed the temps. went to console on the panel due and entered m303 h1 s236 as before and ill be da**&&ed if it wasnt taking off and climbing, but again, showing only 10.5 volts on the meter. Will let it try to continue the tuning but im going to estimate that it will hang again on the cooldown/settling. Will let you know in a bit i guess
-
here is a screenshot from the dwc, it doesnt show the m303 command when i entered it on the panel due but the blue line indicates where the tuning command was entered... you can see that before it failed, and now it completed.... this is confusing as all hell.....
-
Is your heater cartridge 24v or something?
Do you see any change in temps reported?
What voltage are you reading from your power supply output? Does it have an adjustment pot?
-
again its the 12volt version of the revo.. but since it completed the tuning i entered the results to the config file, heated up the nozzle, inserted some filament and was throwing together a quick 20mm calibration cube file with the new nozzle settings etc and while doing that i got this:
-
@wingtip said in Revo 6 PID tuning just hangs:
@deckingman said in Revo 6 PID tuning just hangs:
@wingtip So what happens if you simply try heating the tool. i.e set the active temperature to something other than zero - say 50 deg C or so? Does it try to heat then?
does nothing
So it did not heat when commanded to do so. There are only two possible reasons that I can think of. Either there was no voltage on the heater due to a wiring fault, or the heater itself is faulty. The fact that it does now heat up, shows the fault to be intermittent and that is more likely to be a bad connection than a faulty heater ( but it's not impossible that it is a faulty heater).
If I were you, I would concentrate on getting the heater to work consistently - i.e. to always heat the hot end when an active temperature is set. There is no point in trying to PID tune it until that is fixed. You can forget about any configuration issues - it would never work if there was something amiss there. Also, you can forget about the temperature sensor as that seems to be working as it should. I would concentrate on tracking down a broken wire or faulty crimp connector on the heater itself.
-
@Phaedrux said in Revo 6 PID tuning just hangs:
What voltage are you reading from your power supply output? Does it have an adjustment pot?
Just measured the voltage at the board input and its right at 12 volts, which is coming from a 1000 watt ATX power supply.
im just spit balling here but i think the 10.5 volts has to do with the revo. I recall reading info and seeing is some videos like from thomas salander that the revo changes the voltage as it heats up to use less power as it gets near the set temp if i am remembering correctly... maybe thats why i saw the lower reading..
-
That could be, yes. That's why I asked to check the terminals.
So it has now tuned successfully and has heated up but threw a fault?
What command did you use to tune? What were the results? Did you save them with M500 and have M501 in your config.g at the end to load them?
-
@Phaedrux
the results are posted above in the screenshot. I manually saved to the config file and reuploaded to the machine. do i still need to do the M commands for that as well? -
Can you try tuning with M303 T0 S240
That should tune it as a tool head and include the part fan cooling effect.
-
I think this is finally resolved ... This was giving me fits cause it was so intermittent. But when I checked all the connections they would show ok. Finally during another continuity check, the intermittent connection finally revealed itself despite showing good several checks prior. It was a bad crimp. a simple bad crimp that just over time failed. Ichecked that particular connection several times.
Thank you everyone for all your patience and guidance which did help me make a few corrections to some gcode and updates.
-
Glad you got it sorted out. Those intermittent connection issues are hard to pin down.
-
-