Klipper3d / klipper

Klipper is a 3d-printer firmware
GNU General Public License v3.0
9.45k stars 5.3k forks source link

Duet Maestro Z_PROBE_IN / Z_PROBE_MCU #2996

Closed asolino closed 4 years ago

asolino commented 4 years ago

I'm trying to configure an NPN Inductive Sensor and, according to the documentation I should be connecting the probe's signal to Z_PROBE_IN, and then configure klipper's [probe] section. However, I cannot access the Z_PROBE_MCU PIN (in theory AD11), klipper would not recognize such PIN. According to the schematic Z_PROBE_MCU and Z_PROBE_IN are connected together.

Any help would be appreciated. Kudos for this project, love klipper.

klipper-gitissuebot commented 4 years ago

Hi @asolino,

It did not look like there was a Klipper log file attached to this ticket. The log file has been engineered to answer common questions the Klipper developers have about the software and its environment (software version, hardware type, configuration, event timing, and hundreds of other questions).

Unfortunately, too many people have opened tickets without providing the log. That consumes developer time; time that would be better spent enhancing the software. If this ticket references an event that has occurred while running the software then the Klipper log must be attached to this ticket. Otherwise, this ticket will be automatically closed in a few days.

For information on obtaining the Klipper log file see: https://github.com/KevinOConnor/klipper/blob/master/docs/Contact.md

The log can still be attached to this ticket - just add a comment and attach the log to that comment.

Best regards, ~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being.

asolino commented 4 years ago

Attaching log... klippy.log

KevinOConnor commented 4 years ago

Unfortunately, the upstream Duet documentation is terrible with pin naming. I updated the Klipper generic-duet2-maestro.cfg with some hints for the probe pins (commit 75506417).

In short, the real name of the Z_PROBE_IN pin is PC15.

-Kevin

asolino commented 4 years ago

Thanks for your quick answer @KevinOConnor, works like a charm.

May I ask where did you get that PIN info from? I was looking at the schematic here. I'm trying to make the CR-20 LCD to work with the Maestro (and Klipper of course) and can't get it to work. The right pin mapping could be of help.

KevinOConnor commented 4 years ago

The duet schematics show the micro-controller pin numbers. The Atmel sam4s datasheet has a translation from those pin numbers to the gpio names.

If the "CR-20 LCD" is the same as the "128x64 Full Graphic Creality CR10 / ENDER 3 stockdisplay" listed in config/sample-lcd.cfg then it isn't directly compatible with the Maestro. However, you may be able to build a custom wiring harness to connect the pins you need.

-Kevin

asolino commented 4 years ago

The duet schematics show the micro-controller pin numbers. The Atmel sam4s datasheet has a translation from those pin numbers to the gpio names.

Thanks a lot for the info @KevinOConnor.

If the "CR-20 LCD" is the same as the "128x64 Full Graphic Creality CR10 / ENDER 3 stockdisplay" listed in config/sample-lcd.cfg then it isn't directly compatible with the Maestro. However, you may be able to build a custom wiring harness to connect the pins you need.

Based on some research I did, I don't think it is exactly the same but yeah, I think I'll need to do some wiring myself.

Thanks again. Closing this issue since original problem is now working.