Skip to content

Documentation about endstops outdated

The documentation on your blog is a bit outdated. The behavior is configured with a define statements now.

Blog

// Use HIGH for normally open endstops and LOW for normally closed endstops
const uint8_t endstopStateTriggered = HIGH; 

Code

// State of endstops - Use LOW for normally open endstops and HIGH for normally closed endstops
// Possible values: LOW // HIGH
// Default: LOW
#define AS_ENDSTOP_STATE_TRIGGERED LOW

But I wonder, is the change of the value intentionally? Before the endstop state for NO endstops was HIGH and now it's LOW? Is this correct?