Weistek Ideawerk WT200

[Micke Lejåker]

Hello eller Hej.

I have som problems with my Ideawerk.

It is very loud and prints waves all over the prints.

The bearings is stiff (oiled 3 days ago).

Can´t use SD-Card.

I have used it for 2 mounths. Or like 1000g of PLA filament.

It vibrates lik crazy.

Is there anyone else with problems?

[Owen M. Collins]

If you can post a picture of a print, that would be helpful. There are some really experienced people in this group that can diagnose issues when they see an object made by the printer. 

Sent from my mobile

--
You received this message because you are subscribed to the Google Groups "3D Printer Tips, Tricks and Reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 3dprintertipstricks...@googlegroups.com.
To post to this group, send email to 3dprintertips...@googlegroups.com.

[Micke Lejåker]

Here is a Photo of a Palett, The surface is printed in Y-axel.

[Jetguy]

I think this is actually a simple answer.

The Weistek 150 and 200 both use a pretty standard mightyboard Rev E controller and a derived firmware from the original Makerbot code.

One thing that does annoy me about the Weistek brand is they used high resistance/inductance motors rated at 0.4 Amp and self limit current based on the 12 volt power brick source. Since this is ALSO a mightyboard based system, it's entirely possible to change the Vref values for each axis and thus resulting current the steppers are trying to regulate to.

So what I think is happening is the user is using the wrong slicing software not configured for this printer. Whatever code or slicer they used, it uses the "default" makerbot start and end codes and thus is writing the digipot values to higher Vrefs than stock. Since the motors self limit current- this results in massive stepper clipping.

So the real answer is- use the factory software and this problem likely goes away- or learn to modify your start.gcode and use the correct values for your printer.

On Monday, January 26, 2015 at 8:48:32 AM UTC-5, Micke Lejåker wrote:

[Jetguy]

Also, other huge clues in the original question.

The SD card not working means you are likely not following the instructions and using the correct software for the files.

The stock firmware only reads cards 2GB or smaller larger card are not supported.

It can only read a properly encoded X3G.

So every single bit of this sounds like the user decided to use a different slicer than stock and it's not working.

Here is the proper software and manual page.

http://www.ideawerk3dprinter.com/12.html

Also note, YOU MUST NOT FLASH THESE WITH ALTERNATE FIRMWARE!!!

It will not work with the LCD and will drive the motors to higher default currents.

[Brad Hopper]

Whaa? Why would start gcode set vrefs? And why would firmware only support 2g SD cards? Sure, best to RTFM but those seem like silly default behaviors.

[Dan Newman]

On 26/01/2015 7:07 AM, Brad Hopper wrote:

> And why would firmware only support 2g SD cards?

I think the answer to that is they forked the Jetty Firmware (older versions of Sailfish) before
we had turned on FAT-32 + SDHC support (and fixed some bugs associated with doing so). We didn't
do that work until Sailfish 4.4 and the Weistek folks worked from, I'm told second hand, 3.5.

Dan

[Ryan Carlyle]

Brad, Mightyboards have digipot-controlled stepper driver Vrefs. You don't trim a potentiometer, you just set the stepper current via gcode commands. There are three ways this is used in practice:
1) Genuine Replicator 1/2/2x bots have undersized power supplies, so stepper current is dialed back while preheating extruder(s)/HBP to maintain position while heating without exceeding the PSU capacity. (Yes, this is a bad reason.)
2) It makes BotStep style stepper drivers 100% interchangeable and non-user-tuned. So you can swap them around between XYZAB slots without needing different Vref trim.
3) Bots sensitive to extruder stepper heat when printing PLA can turn down the extruder stepper current to limit heat creep. (Yes, this is a bad reason.)

[Micke Lejåker]

I use the same SD-card as i did in the begining... it just stoped reading from it

[Jetguy]

SD cards die all the time. I assume you can read the SD card in the computer?

Have you reformatted the card?

What software are you using?

Again, the problem is the combination of symptoms.

SD card not working is not unheard of- most likely, bad card, bad format, bad file.

That coupled with the note of extreme noise and vibration so bad it shows up in the print - yet it still prints something an maintains positional registration.

That can only be stepper current is waaaaaay off and given how easy that is to do by using incorrectly formatted start.gcode in your slicer- not a total surpise.

What I'm getting at is- if you clearly made the mistake of using the wrong code - then other mistakes (wrong SD card format, wrong file format, etc) are also a very real possibility from a troubleshooting standpoint.

[Micke Lejåker]

I am using Doraware W1.1 and the SD-card works in the computer.

In the begining the printing was very good.... I have taking the printer apart and lubricate the bearings. The belt on the X-axel was very hard. So i adjusted it just a little bit.

The machine is very loud and VIBRATES alot.

[Micke Lejåker]

One of the first prints:

[Micke Lejåker]

After like 4 weeks;

[Micke Lejåker]

Yesterday:

[Ryan Carlyle]

Damaged ball bearing maybe?