Closed brylandry closed 6 years ago
Just to clarify: X is failing to home with RCBugFix
?
Please post your modified configuration files. The items you posted above don't seem complete.
z was 15.81
That is easy to fix. Take what ever number is in your Z number (the third one) and
#define DEFAULT_AXIS_STEPS_PER_UNIT {80,80,4000,52.2}
multiply it by 10/15.81. Rebuild the firmware. Do a M502 and M500. And print a new calibration cube.
Somehow I missed that this was about calibrating Z steps. This may also help:
It's not the z steps I changed it from 640 to 750 just to see what would happen it still printed 15.81 no difference that's my old firmware. Now the bug fix firmware I just changed this firmware to match my machine and I can't get x to home it just sits there and buzzes for a few seconds then homes y and z without homing x
I changed it from 640 to 750 just to see what would happen it still printed 15.81 no difference
Did you reset the EEPROM too? M502
followed by M500
to make sure it's not using the old stored value.
I can't get x to home it just sits there and buzzes for a few seconds
Does M119
show that all the endstops are behaving correctly?
If it's "buzzing" that sometimes indicates too high a feedrate. I doubt that's the case here, however.
It's most likely a configuration issue. We've got basic axis homing pretty well down at this point.
Please post your modified configuration files. The items you posted above don't seem complete.
So i did what Roxy-3D said which should have changed z height but it's exactly the same 640 is the number i calculated from the prusa calculator it worked before i installed the bltouch now granted Iv'e changed to different firmware but it did work when i printed out my bltouch mount couldn't get the bltouch to work with the one i used to make the mount been messing with different firmware ever since hictop bltouch.zip oh and this file is the one all works but z prints 15.8 and should print 10. mm
That's one old-ass version of Marlin. What does the output of M503
look like?
Hello,
Same issue i think.
manually moving to a position sets that position as 0. When i was moving manually using Pronterface the axis (all 3, XYZ) were moving in + direction but not reacting on - direction.
So if i have moved the X +20 it has moved and when i wanted to go back to -20 it was staying in +20, just i've heard small "thick" like a micro step in stepper, but not seen any actual move.
And the printer is just standard Prusa i3, 3 min endstop modules makerbot clones. 4 nema 17 steppers, and DRV8825 , everything on RAMPS 1.4
Strange thing was that when i was checking endstops
SENDING:M119
Reporting endstop status
x_min: TRIGGERED
y_min: TRIGGERED
z_min: TRIGGERED
echo:endstops hit: X:-0.00
echo:endstops hit: X:-0.01
echo:endstops hit: X:-0.01
echo:endstops hit: X:-0.02
echo:endstops hit: X:-0.02
echo:endstops hit: X:-0.03
echo:endstops hit: X:-0.03
echo:endstops hit: X:-0.04
echo:endstops hit: X:-0.04
echo:endstops hit: X:-0.05
echo:endstops hit: X:-0.05
echo:endstops hit: X:2.94
echo:endstops hit: X:2.94
echo:endstops hit: X:2.93
So after every move i've had endstop hit, even if min software endstops in config was not uncommented, and commented.
No change.
than i have reset the settings with M502 and M500.
SENDING:M503
echo:Steps per unit:
echo: M92 X200.00 Y200.00 Z8000.00 E500.00
echo:Maximum feedrates (mm/s):
echo: M203 X300.00 Y300.00 Z5.00 E25.00
echo:Maximum Acceleration (mm/s2):
echo: M201 X3000 Y3000 Z100 E10000
echo:Accelerations: P=printing, R=retract and T=travel
echo: M204 P3000.00 R3000.00 T3000.00
echo:Advanced variables: S=Min feedrate (mm/s), T=Min travel feedrate (mm/s), B=minimum segment time (ms), X=maximum XY jerk (mm/s), Z=maximum Z jerk (mm/s), E=maximum E jerk (mm/s)
echo: M205 S0.00 T0.00 B20000 X20.00 Z0.40 E5.00
echo:Home offset (mm)
echo: M206 X0.00 Y0.00 Z0.00
echo:Material heatup parameters:
echo: M145 S0 H180 B70 F0
echo: M145 S1 H240 B110 F0
echo:PID settings:
echo: M301 P22.20 I1.08 D114.00
echo:Filament settings: Disabled
echo: M200 D3.00
echo: M200 D0
Now i can move the all axis back and forward + - , but they are ignoring the minimal end stops on my ramps,
ENdstops are fine, connections are fine too.
This is one freaky kind of marlin i have.
Update:
Right now just after reflashing the same firmware with the same config i cannot take - (minus) direction using menu entry move X when choosing any amount, 1mm or 10mm.
but + (plus) direction works fine.
On LCD I see HOME X, (HOME is my label in translation for X min endstop triggered, but print head is in max position where i do not have any endstop, i just can't understand that situation.
when using menu entry Home Z the steers do not work correctly, just like wrong frequency is pended to them. Y when using Home Y is going in wrong direction (+ not - as it should) but it moves only a few millimeters and stops.
when triggering Home all in LCD menu Z is going up not down, so it is going in a different way than just triggering only Z home.
x is homing to max
and y (build plate) as before in MAX (+) direction only a few millimeters and stops,
and Z is going also to max and stops after a 2 sec or so.
Toptal mess....
when using Pronterface to manually move x to MIN, that is what i get
echo:endstops hit: X:-0.00
echo:endstops hit: X:-0.01
echo:endstops hit: X:-0.01
echo:endstops hit: X:-0.02
echo:endstops hit: X:-0.02
echo:endstops hit: X:-0.03
echo:endstops hit: X:-0.03
echo:endstops hit: X:-0.04
echo:endstops hit: X:-0.04
echo:endstops hit: X:-0.05
echo:endstops hit: X:-0.05
echo:endstops hit: X:-0.06
echo:endstops hit: X:-0.07
echo:endstops hit: X:0.93
echo:endstops hit: X:0.92
echo:endstops hit: X:0.92
echo:endstops hit: X:0.91
echo:endstops hit: X:0.91
echo:endstops hit: X:0.90
after every try the home is set to the amount i have tried to move but the stepper holds in place and is not moving.
I've tested the bug fix branch.
no changes in config, just enabling the controller and sd card, and changing max positions from 200,200,200, to 190,190,170 (xyz) when i use in menu of my full graphic controller option HOME X it is trying to home Z and X , when i try home x it is homing only x, trees, but same problem like in RC.
also there is problem with Z steppers they sound strange like wrong frequency and not moving well and stopping with no homing.
When i do try to move the steppers using Pronterface, they work fine but only in + direction.
in negative direction (MIN) they do not move at all.
Solved.
#define min_software_endstops false // If true, axis won't move to coordinates less than HOME_POS.
#define max_software_endstops false // If true, axis won't move to coordinates greater than the defined lengths below.
I suggest setting those to false by default.
I do not know a person who needs it enabled when building a printer.
That 2 lines have ruined my 3 days...
Edit...
As the direction of Y stepper was reversed - to max, + to MIN i've noticed that stepper plug for Y in ramps is in oposite direction than the stepper for X, so i wanted to have same cabling for easy reference in future an i have switched off power supply and USB from my laptop, swapped the direction of the plug to reverse the direction of stepper, and....
The problem with not moving to MIN in - direction has come back...
ROTFL.
WIthout any chnges or reprograming firmware.
WTF changing manualy cabling direction on working setup has to do with blocking reverse actions on axes, and informing on lcd that for example X endstop is activated (it is not really because i'm looking on it) and sending
SENDING:M119
Reporting endstop status
x_min: TRIGGERED
y_min: TRIGGERED
z_min: TRIGGERED
ROTFL
My old ass firmware. i'd love to thar deugg or rc working
SENT: M503
READ: echo:Steps per unit:
Steps per unit:
READ: echo: M92 X80.00 Y80.00 Z405.06 E94.50
M92 X80.00 Y80.00 Z405.06 E94.50
READ: echo:Maximum feedrates (mm/s):
Maximum feedrates (mm/s):
READ: echo: M203 X500.00 Y500.00 Z5.00 E25.00
M203 X500.00 Y500.00 Z5.00 E25.00
READ: echo:Maximum Acceleration (mm/s2):
Maximum Acceleration (mm/s2):
READ: echo: M201 X3000 Y3000 Z100 E10000
M201 X3000 Y3000 Z100 E10000
READ: echo:Acceleration: S=acceleration, T=retract acceleration
Acceleration: S=acceleration, T=retract acceleration
READ: echo: M204 S3000.00 T3000.00
M204 S3000.00 T3000.00
READ: echo:Advanced variables: S=Min feedrate (mm/s), T=Min travel feedrate (mm/s), B=minimum segment time (ms), X=maximum XY jerk (mm/s), Z=maximum Z jerk (mm/s), E=maximum E jerk (mm/s)
Advanced variables: S=Min feedrate (mm/s), T=Min travel feedrate (mm/s), B=minimum segment time (ms), X=maximum XY jerk (mm/s), Z=maximum Z jerk (mm/s), E=maximum E jerk (mm/s)
READ: echo: M205 S0.00 T0.00 B20000 X20.00 Z0.40 E5.00
M205 S0.00 T0.00 B20000 X20.00 Z0.40 E5.00
READ: echo:Home offset (mm):
Home offset (mm):
READ: echo: M206 X0.00 Y0.00 Z0.00
M206 X0.00 Y0.00 Z0.00
READ: echo:PID settings:
PID settings:
READ: echo: M301 P49.10 I6.32 D95.33
M301 P49.10 I6.32 D95.33
READ: ok
ok 10X10X10 cube printed great it seem that M502
and M500
is what i wasn't doing when i flashed firmware it's still that old ass firmware though but it's working
Thanks Guy's
Bryan
I suggest setting those to false by default. That 2 lines have ruined my 3 days...
@Netoperz Actually, we got rid of them.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
So i was told to get to bug fix.
My problem is I installed a BLTouch, and everything was working fine except when I printed a 10mm x 10mm x 10mm cube X and Y were ok, but Z was 15.81. So @thinkyhead told me to download the RCBugFix branch. My Marlin is 1.0.2. I have a HICTOP 3DP08 using Simplify3D for slicer.
Not sure why x is not homing.
Oh and using arduino 1.6.12 Marlin-RCBugFix.zip marlin bltouch.zip