Topics created by secure

@secure If the first print completes without issue but a subsequent print fails, then logic would dictate that something in the first print end code or a post print macro, is changing a configured setting. It would be useful to know if you always home the printer before every print or only before the first one. If it's the latter, then possible causes are that the end code turns the motors off which will then lose the homing position. Another possibility is that positioning is changed from relative to absolute and that it is not being set to relative at the start of the sliced gcode file.

To get to the bottom of this, we'd need to see everything in the sliced gcode file up to the first move, and everything after the last move. If there are calls to other macros within those sections, we'd need to see those too.

@phaedrux said in weird homing behavior:

What kind of endstops are they?

Increase the distance of your homing moves to be larger than the full size of your bed. Are you have it now, it would only be able to home successfully if you start from the center of your bed.

Are you sure your axis limits are correctly sized?

Is this a corexy?

@phaedrux said in weird homing behavior:

What kind of endstops are they?

Increase the distance of your homing moves to be larger than the full size of your bed. Are you have it now, it would only be able to home successfully if you start from the center of your bed.

Are you sure your axis limits are correctly sized?

Is this a corexy?

Basic micro switches

Exactly. It is successfully homing if the head starts from the center of the bed. If not, XY sw may trigger randomly. I tried to increase distance but not remember if it was larger than the bed size. I will try it again. Thanks

Yes with some margin.

Dual Y/Z/E, -H Bot cartesian. Fresh built.
WhatsApp Image 2022-01-14 at 00.52.26.jpeg

@danzaywer I did it. Powered the board with adjustable power supply to see the current it draws. 0.18A at idle and 1.80A when hotend is on.
Ac outlet 230volt stable. PSU output 24.2volt stable. Board power input connector 24.0 v stable.

@percar It is in a PiD mode. I'm using two PSU. The 24V psu is for the board, 12V psu is for leds and 12v fans around enclosure. Filament spool made by a turntable. It is a free spinning bearing.

@rjenkinsgb I understood what you mean. I tried it. Nothing seem works really right now.

I don't know if this macro shows a layer height change or over extruded layer? I think layer height is different than others.
Anyway I'm tired. Don't shut off the heater bed and problem is solved.

WhatsApp Image 2021-12-18 at 17.31.48.jpeg

@secure your fan mapping looks wrong

; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P1 S0 H-1 T45 ; set fan 0 value. Thermostatic control is turned on M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P0 S1 H-1 ; set fan 1 value. Thermostatic control is turned off M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency M106 P2 S1 H-1 ; set fan 2 value. Thermostatic control is turned off

you have the M106 for P1 before the M950 for F1.
you should probably have this

; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 1 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H-1 T45 ; set fan 0 value. Thermostatic control is turned on M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency M106 P2 S0 H-1 ; set fan 2 value. Thermostatic control is turned off

Note the layout change.
I've also inverted your S values on each M106 as they were incorrect
You should then map F0 and F2 to your tools in M563
This is of course assuming that fan 0 and fan 2 outputs are your cooling fans and fan1 are your heat sink fans

@secure said in Duet wifi connected to router but computer can't connect to duet:

Today it is connected without any problem.(chrome)

If you did change the url to http then chrome will likely remember from time to time, on the same device/account (if that is what was the issue)

@secure if droidcam is serving a rtmp or IP cam stream then you should be able to run DuetLapse on just about any other device on your network that can run python3.

It's built for a Pi but I'm using it on a Ubuntu laptop and it is working fine.

Try 2.0.7.

Wow!
I found it!
I was running two PSUs.
One 24v psu for printer duet board.
One 12v small psu to power up just leds around the printer and duet board cooling fans.

They were using same parallel AC ground.
My gut feelings told me to cut the small psu ground wire.
That fix it!

Odd but fixed.
Anyway I will get rid of bltouch with smt more relaible

@secure To edit config.json you'd have to load it up in the configurator, make changes, and save it out again.

Or just stick to editing config.g since it's human readable.