Topics created by davidewen

@dc42 said in Unable to tune chamber heater:

@davidewen what temperature do you heat the chamber to, how long does it take to get there, and what is the ambient temperature? These figures will give me an idea of the heating rate, so that can see whether the current limits are appropriate.

Thanks for getting back to me.

I generally heat the chamber to 60C.
I haven’t timed it, but I think it takes about 30 minutes.
Ambient temperature is 70F

@dc42 said in Hot End fan not being controlled by temp:

@davidewen that would almost certainly be from line 74, the M307 command with the very small R parameter.

Thank you for the feedback.
I'm working to get my chamber heater functional again.
I have another forum post going for that here.

https://forum.duet3d.com/topic/30954/unable-to-tune-chamber-heater

I have modified line 74 (now line 72) and I'm still getting the "bad model parameters" response.

Here's the new code for line 72. Let me know if you want the entire config.g file uploaded again.

Since the chamber heats up and cools down so slowly, should I just ignore this error?

M307 H2 R0.01 K0.200:0.000 D60 E1.35 S1.00 B1

@davidewen no worries...just rememberd I saw it!

@Phaedrux

Ah. Ok. I'll make that change.

@davidewen said in Z seam blobs, pause at layer change:

Please advise and I'll send it.

Perhaps slice a smaller object.

@fcwilt

Discovered today that my filament sensor is missing.
I'll go back through my original config.g to see if I can find the settings.

Got the 1st test print completed.
I had to baby step +0.4 to get filament to come out.
This is with mesh comp. on.

Figured out why homing wasn't working.

For some reason, X needs to be homed 1st followed by Y.
So, I had to split those up in the homez.g file

I still get the "jump" when homing.

@dc42

Thank you for the response.

I have changed minZ to -2
What is "segmentation"?

David

@davidewen Do you mesh-probe the bed, when it is at room temp or working temp? That can have a great influence on the flatness of the bed. Depending on the probe-type you'd have to switch off the bed heater while probing, because the electric field can change the trigger height.

@davidewen said in Error Short to Ground reported by driver(s):

@phaedrux said in Error Short to Ground reported by driver(s):

Bossa doesn't work with the mini5+. The 2x quick presses of the reset button are required to make the board show up as a USB storage device in finder. Then you copy the firmware file onto that drive to write it.
Can you confirm that's where you're looking?

Yes, 2x press of the RESET button causes the STATUS LED to quickly flash, but Bossa does not recognize the board.
It does not show up in Device Manager or as a USB device.

I will however double check when I get home this afternoon.

What should happen when you press he Reset button twice in quick succession on the Duet 3 Mini is that the red STATUS LED cycles between bright and dim. When that happens, the USB drive should appear on your PC. Make sure that the USB cable you use is not a power-only cable for charging smartphones etc.

If the STATUS LED blinks slowly (once per second) then it is running firmware.

If it blinks quickly then it should blink a number of times, stop, and repeat. In that case the number of blinks is an error code.

@davidewen
First you should define a "filament-error#.g" macro, which is called at filament runout (# is the number of your extruder).
In this "filament error macro" you can create and set a global variable.
After setting the variable, add a blocking message (M291...)
You have to reset the variable after confirming the filament change.

Create a "daemon.g" file in the sys folder. Here you can check the variable and make your beeps.
eventually something like this...

while global.beep = true M300 S500 P1000 ; beep with 500Hz for 1sec G4 P1000 ; delay of 1sec

@droftarts
I'm around 60% complete of a 11 hour print. I'll update when it's finished.

@alankilian

Thanks for your help Alan.
The wiring was incorrect. Now that I have it correct, it's working.

@phaedrux
Thanks.
That did the trick.

That would all be controlled by your slicer end gcode.

@elmoret
Ok, thank you.