Posts made by xubu

@xubu

I figured out the calibration problem. The other half was tweaking stuff in config.g. looking good so far! Thx!

@dc42

I figured half the problem with the bltouch.
My wiring was incorrect. I was using the all 4 z probe pins (connector next to paneldue) + 1 e0 stop pin. Instead, i am now using 2 z probe pins (z probe in and ground) + 3 expansion pins (1, 2, & 8).

With that wiring, the bltouch pin drops and retracts at startup and during calibration of the first point but does not move to the second point. This could be a matter of playing with config.g.

No logging is displayed during calibration.
Really tempted for the Mini IR scanner as a replacement as im not fond of bltouch anyways.

Also, i have tried some simple commands through the paneldue. Pressing the return just clears the line. I cant tell if the duet registers anything. Also, i only have 4 wires connecting my duet (in connector next to z probe on the duet) and paneldue.

I have a tlm and have converted. But I'm have some trouble understanding whats happening and confirming things are right before printing.

I have a duet wifi at firmware 1.17 connected to a 7" paneldue.

I have read and followed information here and at thingiverse. Data in config.zip replaced all that was in /sys (iirc).

I can power on and when it turns on I see/hear the bltouch extend and retract.
I can home and move the head via paneldue. Duet seems to be okay with the default optical end stops provided by tevo. Temperature of bed and hot end is accurate reported through paneldue.

Here are my problems that Im having trouble with understanding.

1. After turning on, the heat bed immediately starts heating and does not stop heating (ive gone to 153 degrees Celsius) before saying that's too much. i wired this wrong. Mks pinout wasnt exactly forthcoming with info. Accidentally swapped main power and heat bed power wiring.

2. When performing bed leveling, the head stops at the first point. No commands are registered via paneldue and forcing a stop command leaves the paneldue in perpetual "connecting" state.

3. Unsure if I can send commands through paneldue. I go to console and there's a keyboard icon at the top right. I can tap anything (e.g. G30 for z probe testing) but I see no option to send. Is sending commands reserved for wifi/usb/ethernet connection?

I have not configured wifi settings, I can do this though if it would help.

If this should be in its own thread, i apologize.