V4 extruder nightmare !

[Tim]

Yeah, it's a bit confusing the way they put it, as they seem to suggest that you have to go stick the values back into the firmware source code and recompile it. It's not that drastic. The values are in EEPROM and can be written with a command to the printer.

I'm not sure if the end of the auto-tune actually saves the PID settings or not. From what I can tell, it just returns those numbers. So given the feedback

Code: Select all

RECEIVED: Kp: 15.94
RECEIVED: Ki: 0.86
RECEIVED: Kd: 74.16

you want to now send the command:

Code: Select all

M301 P15.94 I0.86 D74.16

then save to EEPROM with the command:

Code: Select all

M500

And that should do it! "M301" by itself with no arguments will return the PID values currently in effect, so you can check if the new values are being used after a power cycle.

[TheRyanRanch]

Well, I successfully printed an ABS project, however I had to have the heat cranked up to 265C for it to continue to flow, I also am trying to print ESun PETG right now, and the temp I am trying is 275 to get that to flow. something clearly is FUBAR here?

I could of sworn that the V4 could go above 275C because every time I try, the S3D system shuts off the extruder, like it is capped out at 270c ????

any thoughts?

-sr

[innkeeper]

is the temperature staying stable or is it bouncing around a lot?

also can you get your hands on a temperature probe to do a comparison check?

[Jules]

You shouldn't have to take the temps up that high for PETG. Had you considered just ordering a spare hotend from Makergear? (Change out the whole thing?)

http://www.makergear.com/products/m2-upgrades

[TheRyanRanch]

Innkeeper, After doing a PID, the temps are very stable +- 1 or 2 degrees, so now what?

does the Extruder Multiplier come into play or perhaps something in the software that may be doing this?

ughhhh.......

[TheRyanRanch]

Jules, I do have a call into Tech support and they are sending out some parts ! Tech Support has been extremely good on this, I don't think I would of had such luck with another company, but in the meantime i'm not making products and customers or PO'd !!!

[Tim]

in the meantime i'm not making products and customers or PO'd !!!

Yeah, well, the M2 is a solid machine but it isn't invincible. If you involve paying customers, it's probably a good idea to have a spare of everything important. Hardware debugging is always fastest when you can swap in a known good part and see if the problem goes away. I'm at the mercy of various parts of my machine, but then I'm just a hobbyist, so a few weeks of downtime isn't a problem.

[Jules]

in the meantime i'm not making products and customers or PO'd !!!

Yeah, well, the M2 is a solid machine but it isn't invincible. If you involve paying customers, it's probably a good idea to have a spare of everything important. Hardware debugging is always fastest when you can swap in a known good part and see if the problem goes away. I'm at the mercy of various parts of my machine, but then I'm just a hobbyist, so a few weeks of downtime isn't a problem.

Me too, (just a hobbyist), but i try to keep at least one spare of everything on hand, (nozzles, hotend, fans, printed drives & mounts, plates) - cause i've jammed/clogged/ripped/stripped/chipped/dropped/bumped and generally run this thing ragged in the six months since i got it.

And besides, you know any machine is always going to develop the problem right in the middle of something important - it's an immutable law of nature, that cannot be denied.

[TheRyanRanch]

in the meantime i'm not making products and customers or PO'd !!!

Yeah, well, the M2 is a solid machine but it isn't invincible. If you involve paying customers, it's probably a good idea to have a spare of everything important. Hardware debugging is always fastest when you can swap in a known good part and see if the problem goes away. I'm at the mercy of various parts of my machine, but then I'm just a hobbyist, so a few weeks of downtime isn't a problem.

Me too, (just a hobbyist), but i try to keep at least one spare of everything on hand, (nozzles, hotend, fans, printed drives & mounts, plates) - cause i've jammed/clogged/ripped/stripped/chipped/dropped/bumped and generally run this thing ragged in the six months since i got it.

And besides, you know any machine is always going to develop the problem right in the middle of something important - it's an immutable law of nature, that cannot be denied.

Definitely words to live by, I know I should have had my spare parts inventory stocked, but I have only had this machine for a month and was hoping to get out of the gate "making parts" a little further along

[Jules]

... I have only had this machine for a month and was hoping to get out of the gate "making parts" a little further along

Chuckle! Clogged my first nozzle and jammed the hotend on day 4......on the bright side, at least it gets you over your absolute terror of clogging the nozzle.

If anything on these machines can be considered "disposable" it's probably the hotends. Keep a spare on hand, because even though it's not easy to do, they can be jammed/busted if you get something wrong with the settings, (or with the V4, even by extruding too much sticky filament like PETG too fast). It just takes us time to learn what and what not to do. They are surprisingly resilient little things.

If something screwed up the thermistor in that one, MakerGear will surely make it right if you've only had it for a month. But its a good idea to buy another one to keep on hand, just to have one to use while you are waiting on the parts. (I asked when i bought mine and that is what was recommended, spare hotend and spare borosilicate plate, in case i dropped it or pulled a chunk out of the glass. Good advice because i did in fact chip it a couple of months in. And i was able to use the spare hotend while i had the original pulled out to unclog it.)

The rest of the stuff, yeah, you can wait on it. It's not necessary to have a spare filament drive or motor mount on hand in the beginning, we just tend to do them with a higher infill when we get around to it.