Re: ORD Bot Hadron Inquiries - Help Appreciated
Posted: Mon Oct 14, 2013 5:21 pm
Okay, another weird problem. I've made a bit of headway, my Configuration.h now looks like this:
//===========================================================================
//=============================Mechanical Settings===========================
//===========================================================================
// Uncomment the following line to enable CoreXY kinematics
// #define COREXY
// coarse Endstop Settings
//#define ENDSTOPPULLUPS // Comment this out (using // at the start of the line) to disable the endstop pullup resistors
#ifndef ENDSTOPPULLUPS
// fine Enstop settings: Individual Pullups. will be ignored if ENDSTOPPULLUPS is defined
// #define ENDSTOPPULLUP_XMAX
// #define ENDSTOPPULLUP_YMAX
// #define ENDSTOPPULLUP_ZMAX
// #define ENDSTOPPULLUP_XMIN
// #define ENDSTOPPULLUP_YMIN
// #define ENDSTOPPULLUP_ZMIN
#endif
#ifdef ENDSTOPPULLUPS
#define ENDSTOPPULLUP_XMAX
#define ENDSTOPPULLUP_YMAX
#define ENDSTOPPULLUP_ZMAX
#define ENDSTOPPULLUP_XMIN
#define ENDSTOPPULLUP_YMIN
#define ENDSTOPPULLUP_ZMIN
#endif
// The pullups are needed if you directly connect a mechanical endswitch between the signal and ground pins.
const bool X_MIN_ENDSTOP_INVERTING = false; // set to true to invert the logic of the endstop.
const bool Y_MIN_ENDSTOP_INVERTING = false; // set to true to invert the logic of the endstop.
const bool Z_MIN_ENDSTOP_INVERTING = false; // set to true to invert the logic of the endstop.
const bool X_MAX_ENDSTOP_INVERTING = false; // set to true to invert the logic of the endstop.
const bool Y_MAX_ENDSTOP_INVERTING = false; // set to true to invert the logic of the endstop.
const bool Z_MAX_ENDSTOP_INVERTING = false; // set to true to invert the logic of the endstop.
#define DISABLE_MAX_ENDSTOPS
//#define DISABLE_MIN_ENDSTOPS
// Disable max endstops for compatibility with endstop checking routine
#if defined(COREXY) && !defined(DISABLE_MAX_ENDSTOPS)
#define DISABLE_MAX_ENDSTOPS
#endif
I can now see when endstops are triggered, however if I type M119 into Repetier Host repeatedly, the end stops report triggered and open randomly. Example: without touching any of the endstops or moving any of the axis, if i type in M119 3 times in a row, it might report this:
13:23:27.218 : N395 M119 *5
13:23:27.240 : Reporting endstop status
13:23:27.240 : x_min: open
13:23:27.240 : y_min: open
13:23:27.240 : z_min: open
13:23:31.434 : N397 M119 *7
13:23:31.452 : Reporting endstop status
13:23:31.452 : x_min: open
13:23:31.452 : y_min: open
13:23:31.452 : z_min: open
13:23:33.435 : N399 M119 *9
13:23:33.454 : Reporting endstop status
13:23:33.454 : x_min: open
13:23:33.454 : y_min: open
13:23:33.454 : z_min: TRIGGERED
sometimes y_min is triggered and its not even connected right now. it sound light something is setup incorrectly in the firmware, or the board itself is defective. because I don't see any way the board could report something as triggered when there is not possible way it could be (not hooked up)
//===========================================================================
//=============================Mechanical Settings===========================
//===========================================================================
// Uncomment the following line to enable CoreXY kinematics
// #define COREXY
// coarse Endstop Settings
//#define ENDSTOPPULLUPS // Comment this out (using // at the start of the line) to disable the endstop pullup resistors
#ifndef ENDSTOPPULLUPS
// fine Enstop settings: Individual Pullups. will be ignored if ENDSTOPPULLUPS is defined
// #define ENDSTOPPULLUP_XMAX
// #define ENDSTOPPULLUP_YMAX
// #define ENDSTOPPULLUP_ZMAX
// #define ENDSTOPPULLUP_XMIN
// #define ENDSTOPPULLUP_YMIN
// #define ENDSTOPPULLUP_ZMIN
#endif
#ifdef ENDSTOPPULLUPS
#define ENDSTOPPULLUP_XMAX
#define ENDSTOPPULLUP_YMAX
#define ENDSTOPPULLUP_ZMAX
#define ENDSTOPPULLUP_XMIN
#define ENDSTOPPULLUP_YMIN
#define ENDSTOPPULLUP_ZMIN
#endif
// The pullups are needed if you directly connect a mechanical endswitch between the signal and ground pins.
const bool X_MIN_ENDSTOP_INVERTING = false; // set to true to invert the logic of the endstop.
const bool Y_MIN_ENDSTOP_INVERTING = false; // set to true to invert the logic of the endstop.
const bool Z_MIN_ENDSTOP_INVERTING = false; // set to true to invert the logic of the endstop.
const bool X_MAX_ENDSTOP_INVERTING = false; // set to true to invert the logic of the endstop.
const bool Y_MAX_ENDSTOP_INVERTING = false; // set to true to invert the logic of the endstop.
const bool Z_MAX_ENDSTOP_INVERTING = false; // set to true to invert the logic of the endstop.
#define DISABLE_MAX_ENDSTOPS
//#define DISABLE_MIN_ENDSTOPS
// Disable max endstops for compatibility with endstop checking routine
#if defined(COREXY) && !defined(DISABLE_MAX_ENDSTOPS)
#define DISABLE_MAX_ENDSTOPS
#endif
I can now see when endstops are triggered, however if I type M119 into Repetier Host repeatedly, the end stops report triggered and open randomly. Example: without touching any of the endstops or moving any of the axis, if i type in M119 3 times in a row, it might report this:
13:23:27.218 : N395 M119 *5
13:23:27.240 : Reporting endstop status
13:23:27.240 : x_min: open
13:23:27.240 : y_min: open
13:23:27.240 : z_min: open
13:23:31.434 : N397 M119 *7
13:23:31.452 : Reporting endstop status
13:23:31.452 : x_min: open
13:23:31.452 : y_min: open
13:23:31.452 : z_min: open
13:23:33.435 : N399 M119 *9
13:23:33.454 : Reporting endstop status
13:23:33.454 : x_min: open
13:23:33.454 : y_min: open
13:23:33.454 : z_min: TRIGGERED
sometimes y_min is triggered and its not even connected right now. it sound light something is setup incorrectly in the firmware, or the board itself is defective. because I don't see any way the board could report something as triggered when there is not possible way it could be (not hooked up)