Topics created by Whitewolf

@Whitewolf:

…..........................
I am not a chemical expert but I can only guess that this same thing is happening with other filaments when they are spending too much time in the nozzle for a given temp.........................................

That's a definite, and can be one of the problems with a mixing hot end. What can happen is that the loaded but unused filaments "cook" inside the melt chamber even at normal printing temperatures if left for any length of time. Then when you come to start printing with that filament, what comes out to start with, for the first few mm, is a lot of vapour and a very runny, almost liquid messy stuff. You have to be aware of that and try to keep all the filaments moving, even slightly and/or arrange/slice the multi part object in such a way that no single filament is left unused in the melt chamber for too long.

My S3D hasn't worked since the upgrade, keeps crashing every time i open a dialog window.

Support havent been that helpful. Looking on their forum, I'm not the only one with these issues so until they fix it I can't recommend it

I've gone back to Slicer (Prusa edition) and its working well (Better than S3D v3[but cant comment on V4 yet])

I added a couple more renderings, I just noticed that if you look closely at the second rendering, you can actually see the path on each side where the bowden tube ends inside the body and where the filament path begins (the filament path is still encased in the body up until it makes contact with the gears

Try shutting off the heat sink fan or put it on a PWM connector and slow it down.

Connect a separate temp probe to it so you can fine tune at what temp things go wrong. Stay below that.

No offence taken. The point I was making is that an object in motion will maintain it's speed without any additional force being applied. In the case of an orbiting satellite, gravity and centrifugal forces balance each other out so it maintains it's orbit. Or in the case of an elliptical orbit, there can be two or more gravitational forces being applied, so the forces acting on it vary. The same principal applies though - that is to say, it will maintain it's motion, whether that be in straight line, circular or elliptical, without any additional force being applied and it takes very little force to move it slightly, but a great deal more force to accelerate the object out orbit.

Not sure if I missed it, but has anyone printed PC on a PC sheet? Did it weld itself? How was warping?

I have a way but it might be hard with your setup. Move your z to the pre leveled. Enable the motor motors your stepper should be locked pull to a full step loosen your coupler on your z height assuming you only have one Z acme shaft and then tighten your set screw. I have tried this before while calibration diagnosing but after that I didn't really have a use for it.

Agreed, as usual most celebration dates in america have nothing to do with the actual event. Thanksgiving is a prime example, its date was changed a dozen times throughout history in order to improve chirstmas sales to boost the economy. The actual date has nothing to do with what is being celebrated.

Reading your link i want to do some experimentation. I know what they are addressing has to do with deltas but i, at some point in the past read about a bug in Simplify3D that was overcome by changing layer height to 2.0001

Even though i have a cartesan i want to see if theres any difference between changing the points where steps vs microsteps land on the layers

totalitarian, if you like getting sick or dying of poisonous gases, it is fine. But please don't spew life threatening misinformation on public forums. There are lots of guys tinkering with these toys, including kids.

I'm glad you figured it out. My guess is that your bed.g file had a row of zeros at the start because y=0 was not accessible to the probe, and that row of zeros was confusing DWC.

Christian hasn't built a .bin version of DWC 1.16 because that release is targeted ad the forthcoming 1.19 firmware release.

Yeah i read that on the wikipedia, it just had me scratching my head because as you can see in the photo the psu states it has 5vsb

I cracked the PSU open last night and 5vsb doesnt exist on the PCB everything is clearly labeled even the non used like -12v

@dc42:

Ian is right, you must always specify the T parameter in any M581 or M582 command.

Thank you, I will update the wiki as it just says M581 S-1 with no other arguments

@dc42:

Auto tune in 1.18 will always overshoot the target temperature. You need a larger difference between the target temperature you use in M303 and the temperature limit set in M143. You should use the default P1.0 in M303.

Thank you!

I set the temp limit to 400C (the limit of the PT100)

; Heaters M143 S400 ; Set maximum heater temperature to 400C

Then set the target to the highest temp of filament I plan to use

M303 H1 P1.0 S380

This was the console message:

Warning: Heater 1 appears to be over-powered and a fire risk! If left on at full power, its temperature is predicted to reach 609C. Auto tune heater 1 completed in 545 sec

M307 H1 result:

Heater 1 model: gain 589.9, time constant 284.6, dead time 5.0, max PWM 1.00, mode: PID Computed PID parameters for setpoint change: P17.2, I0.061, D60.3 Computed PID parameters for load change: P17.2, I1.100, D60.3

Any Suggestions or is it safe to leave like this? Not sure if the parameters adjust for the over powered message automatically.

I must have gotten overwhelmed learning all this gcode 🙂 It works Thank you

Is there a way for it to work on files with spaces in them? I know the easy answer is to save without spaces, but sometimes I forget 😃

Good call on the delete statement first!

I've no idea if that would work. We did make a few Duet WiFi prototypes using ESP-07 WiFi modules which have an antenna socket.

In order to help you we need information about the endstops you have, for example photos of them and links to any documentation you have for them.