Closed ruggb closed 9 years ago
Do you get the same crashing results with G28 X Y
as with G28
(except Z not moving, obviously)?
Can you post your Configuration.h
here, in a Gist, or on Pastebin?
I didn't try sending a G28, I assumed Repetier did that when I clicked the home all button. I tried tripping the endstops when it was moving but it does not respond to any of them. They all work if I home the axis individually.
//\ changes make //== changes considering
and yes G28 x y gives the same result
Wow, that sure is an old Configuration.h
file. Let me see about updating that for you to the latest. You should post your Configuration_adv.h
too so I can update that for you as well.
One thing that jumps out is this line:
#define EXTRUDER_OFFSET_X {30.0, 0.0}
It should probably be:
#define EXTRUDER_OFFSET_X {0, 30.0}
The offset is relative to E0.
I want to define the1 farthest from 0 as the default extruder. I thought that would work? I tried to find something later but couldn't figure out the version numbering. It was originally from the guy who created this corexy printer. It would be neat if the ver # was in the file. What else might be out of date. The routine for quick_home is in marlin.main.h isn't it? thx
[config removed]
I meant marlin.main.cpp
BTW is BABYSTEPPING implemented for corexy yet?
No, babystepping is not implemented for COREXY yet.
Your updated Configuration.h
is below. The only added bit that you probably don't need is the part that says:
// Disable max endstops for compatibility with endstop checking routine
#if defined(COREXY) && !defined(DISABLE_MAX_ENDSTOPS)
#define DISABLE_MAX_ENDSTOPS
#endif
You can just uncomment #define DISABLE_MAX_ENDSTOPS
instead, if you need it.
If you aren't sure whether to leave #define ENDSTOPPULLUPS
enabled, then you probably should. You can use the M119
command to see the current state of your endstops.
The endstops I have are the MakerBot version and they have a 10k resistor in parallel with a 4.7k and a diode. I figured that was enough, and they work individually.
Please post your Configuration_adv.h
so that I can update that for you too.
i thought i posted this but I guess I missed something in the process this forum is a little strange to me. how do i get the latest files for Marlin? do I have to update each or can I dnld the whole thing?
To get the 'latest' code of Marlin: Go to 'https://github.com/MarlinFirmware/Marlin'. Change from 'Release' to 'Development' branch. (Near the green symbol) At the bottom of the right column click 'Download ZIP'
to get 'Marlin-Development.zip'.
Or: git clone https://github.com/MarlinFirmware/Marlin.git git checkout Development
Got it - got it - got it -- now I am confused I found this == https://github.com/MarlinFirmware/Marlin/releases and got this == Marlin-1.0.2.zip == problem with QUICK-HOME is still there.
then u sent me here == https://github.com/MarlinFirmware/Marlin and got this == Marlin-Development.zip and here == https://github.com/MarlinFirmware/Marlin.git and got this == Marlin-Release.zip
at least "Marlin 1.0.2" gives me a version # I assume Marlin-Release.zip is the same version as above since that came from a "releases" page and it was on the top of the list, but I don't know how to verify that, and why is it posted under a different name??? I assume Marlin-Development.zip would be >> 1.0.2 but it would be nice to see a version number like 1.0.2.198 or whatever.
@ruggb Everything behind the "Or:" was mend literally to be used on the command line using the 'git' program.
Anyway - with 'Marlin-Development.zip' you got the 'latest' code. When looking into 'Configuration.h' yol find in line 43 the actual version number. When all went well you will read
thx unfortunately that convention does not carry over to the releases - which is why I never saw it. The worst thing in documentation is to have the same thing defined more than once. Compilers don't let u get away with that. BUT even worse is to list the same thing in 2 different places with 2 different names and worse yet without identification. Maybe there is a better way??
not to beat a dead horse but I just found this in the Marlin-1.0.2 and the Marlin-Release versions but nothing similar in the development version. u8g.drawStr(62,19,"V1.0.0 RC2-mm");
maybe u could use a defined value there that is stated in the config file. It would eliminate the multiple doc problem.
Good observation. So you can see - we did something to organize the chaos, Removed the double and centralized in Configuration.h. Taking the buss and riding a bike is almost the same difference as, loading a .zip and checkout with git. So - if you want to investigate the way between the bus-stops (versions) - learn git.
ah yes - I have been consumed constantly for months on this 3D printer, Prior to that I thought I was going to get into Linux and git came up, but.............. u know how that goes. toooooo much information.
Back to the toppic. How is ' QUICK_HOME' on a 'Core-XY' with Marlin '1.0.3 dev' working for You now?
have not tried it yet - soon
1.0.3 needs work when I tell it to home it does the same thing for single or multi - it takes one step in the wrong direction on both axis and stops.
I found it part of it - your logic for the endstops is reversed - "false" should be "true" for negative logic == grd = active the wrong direction step was the bounce.
QUICK_HOME . IS working I discovered that I did have a dev copy -- that must have been the one it worked on previously but I became so confused with versions I lost it.
it still isn't stepping - it is like an issue with an open thermistor....................OK I made it work by chg to 1 extruder but I do have 2 so I am not sure why it appears like it isn't seeing E1 thermistor.
BABYSTEPPING does not have the gotcha for corexy now -- does that mean it is functional for corexy??
I just had a thought - maybe it is a definition thing u left out. I notice there are 4 heaters now instead of 3 + the bed -
#define TEMP_SENSOR_0 5
#define TEMP_SENSOR_1 5
#define TEMP_SENSOR_2 0
#define TEMP_SENSOR_3 0
#define TEMP_SENSOR_BED 0
Since redundancy it there also, does that infer that 0 & 1 r for E0 and 2 & 3 r for E1? I'm checking.............NOPE it does not work with 2 extruders defined and the above set = 5 for 0 and 2 It does work for 1 extruder with 0 set to 5.
Also, my extruders r E3Ds and the heater resistance is 3.5 ohms - that may be a better number than 6.7 in the watts calc line.
Lets stay with the endstops for a while. Could you please send a M119 from the host - to report the end-stop-status of your switches? Maybe it will help you to play a bit with ENDSTOP_INVERTING. https://github.com/MarlinFirmware/Marlin/blob/Development/Marlin/Configuration.h#L334
Please note the difference between:
//#define TEMP_SENSOR_1_AS_REDUNDANT
and
#define TEMP_SENSOR_1_AS_REDUNDANT
The first is deactivated - the second is active.
Redundancy is only possible for the first extruder. The correct entry for two extruders with redundand thermistors for extruder1 are supposed to look like:
#define TEMP_SENSOR_0 5
#define TEMP_SENSOR_1 5
#define TEMP_SENSOR_2 5
#define TEMP_SENSOR_3 0
#define TEMP_SENSOR_BED 0
Normally a E3D has no redundant thermistors.
If TEMP_SENSOR_1_AS_REDUNDANT is active please deactivate.
@thinkyhead tried his best to port your old configuration to the new one. So don't complain about an entry you have not had in you old configuration. If you think 3.5 Ohm is the better value - just take it - it's your printer.
BABYSTEPPING is currently NOT supposed to work with Core-XY!
1st - the endstop issue is fixed -- I set the inversion to true - as it was in ver 1.0.2 - ver 1.0.3 changed them incorrectly from what I see. M119 shows max endstops always triggered. min endstops work fine with them set as true - I am using a version of the Mendlemax endstop boards. If u change all this back to the way it was in ver 1.0.2 it will be correct - "false" must be "true".
// Mechanical endstop with COM to ground and NC to Signal uses "false" here (most common setup).
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.
const bool Z_PROBE_ENDSTOP_INVERTING = false; // set to true to invert the logic of the endstop.
I don't have redundant thermistors but I have no idea why there r 4 sensors listed - no explaination. I set 0 & 1 to 5 then 0 & 2 to 5 neither works with 2 extruders. 1 extruder with 0 = 5 works.
There was a compile trap to inform that babystepping did not work for corexy in 1.0.2. If it does not work in 1.0.3 u need to put it back in.
The trap IS in '1.0.3 dev' - and works! Usually on RAMPS the thermistor for the bed is connected to the board between the connectors for E0 and E1. Could this be the problem?
There are now 4 thermistors + 1 for the bed because we now want to support up to 4 extruders.
I am going to have to dump a bunch of these builds b/c I am totally confused now. it appears that the // Mechanical endstop with COM to ground and NC to Signal uses "true" here (most common setup). is correct since that is what I am running with. Somehow I must have chgd them in the wrong config file then loaded the right one. my apologies!!!!!
I still can't get it to step with extruders = 2 and setting ALL or any combination of the heaters sensors to 5
so the trap apparently has been moved or chgd such that I don't recognize it - but I am not a programmer so forgive me.
Thanks for posting your Configuration_adv.h
, @ruggb – You had only re-posted your Configuration.h
.
Here's an updated Configuration_adv.h
for you.
I want to define the1 farthest from 0 as the default extruder.
In that case you want
#define EXTRUDER_OFFSET_X {0, -30.0}
how do i get the latest files for Marlin?
Find the ".zip" link on the bottom-right of this page https://github.com/MarlinFirmware/Marlin/tree/Development
Yes, you will need the latest code (1.0.3 dev) to use the configurations I posted. We're not fixing 1.0.1 or 1.0.2.
That configuration_adv.h appears to be the same as the one in 1.0.3 dev. Is that correct? If so, the only issue appears to be when I define EXTRUDERS 2 it won't step. It will home. I have all sensors defined as 5. Did I miss something or is it a bug?
It is Configuration_adv.h
modified with your settings.
That is curious that when EXTRUDERS is 2 your printer won't move.
Got it, thx. well, I just tried 1.0.2 again and I have the same issue - Repetier does not show a sensor indication for E1 and I have chkd all the h/w up to the bd. I may have a bd problem. If Marlin does not see all the sensors it will not step. Looks like I need some serious digging. I think I will first try a config I thought worked previously. I guess I can get easily confused, ya think?.
??? I have a ramps 1.4 bd. It has 3 T inputs, 2 designate for Te0, Te1 and 1 for Tbed. electrically they r identical. If I connect Te1 to Tbed and set T0=5, T1=0, T2=5, T3=0, T4=0 will that match T2 with E1. If not, can I do that by designating redundancy. I am trying to figure out how to test that input.
The pins for the analog inputs of the temp-sensors for RAMPS are defined in 'pins_RAMPS_13.h'. Their names are:
#define TEMP_0_PIN 13 // ANALOG NUMBERING
#define TEMP_1_PIN 15 // ANALOG NUMBERING
#define TEMP_2_PIN -1 // ANALOG NUMBERING
and
#define TEMP_BED_PIN 14 // ANALOG NUMBERING
swap them to your taste.
OK the answer is MOTHERBOARD 34 no longer works -- it has to be = "RAMPS_13_EEB" Maybe I had the wrong one in the first place. thx for ur help.
if Z = 300 but it is really at 100 and I give it the command G1 z200 why doesn't it stop when it hits the endstop?
let me try that again - if Z = 300 but it is really at 100 and I give the cmd G1 Z100 why doesn't it stop when the endstop is triggered? IE when it is executing a G1 command it appears the endstops have no function. The work fine doing a home.
By default they are only enabled during homing. After that soft endstops are sufficient to prevent it hitting the end.
On 13 May 2015 at 00:39, ruggb notifications@github.com wrote:
let me try that again - if Z = 300 but it is really at 100 and I give the cmd G1 Z100 why doesn't it stop when the endstop is triggered? IE when it is executing a G1 command it appears the endstops have no function. The work fine doing a home.
Reply to this email directly or view it on GitHub https://github.com/MarlinFirmware/Marlin/issues/2046#issuecomment-101460546 .
// What is this for?
define ENDSTOPS_ONLY_FOR_HOMING
When this is enabled, end-stops will only be turned on during homing, and will be ignored during printing, if they happen to get triggered.
OK the answer is MOTHERBOARD 34 no longer works -- it has to be = "RAMPS_13_EEB"
Yes, I already put that into the Configuration.h
above for you.
Yeah, I think I found the MB version about the time u sent that. Was that config for the dev version or the release version? If i comment out the endstops for homing only will that stop it if it gets lost and hits the stop before it thinks it should? My Z isn't functioning super reliably yet.
Was that config for the dev version or the release version?
We only support and test the Development version around here, because the idea is to catch current bugs, not bugs that may not exist anymore.
got it, thx
when endstops for homing only is commented out it does not step except to home but the stepper is activated - Is that the way it is suppose to operate?
A point of confusion. The Ramps bd documentation shows T0 T1 T2 on the board in that order. As listed in PINS for the Ramps 1.3 bd -- TEMP_0_PIN = 13, TEMP_1_PIN = 15, TEMP_2_PIN = -1 and TEMP_BED_PIN =14 The config shows 4 Tx settings plus a bed. I suppose u should have a TEMP_3_PIN = -1 also. OK, I define T0 and T1 b/c I have 2 extruders and when I install the bed, T-BED. T0 ends up on T0 of the board, T1 ends up on T2 of the board and T-BED ends up on T1 of the board because T0 is attached to 13, T1 to 14 and T2 to 15. U might want to consider changing that or adding some verbage. It took me an hour digging up docs to figure out why it wasn't working.
when endstops for homing only is commented out it does not step except to home but the stepper is activated - Is that the way it is suppose to operate?
That is how it will operate if your endstops are showing up as triggered for some reason, such as having the wrong inverting setting or the wrong pullup setting. What does M119
say?
When I set
QUICK_HOME
it will run BUT it crashes into the stops. If I home each axis individually the endstops work fine. I think I had one config that worked but I can't find it. This is a CoreXY system. It does it from the display or from Repetier. I have not been able to find anyone who has a clue. Any ideas?