Results 131 to 140 of 172
-
02-23-2015, 11:26 AM #131
- Join Date
- Oct 2014
- Posts
- 114
If I disable the max endstops, x works fine, but Y doesn't home. If I disable both the max and the min, it doesn't compile with the G29 and z probe repeatability on.
If I comment both out, and the the pullups as you suggested, x and y home, but don't bounce and M119 returns all triggered but zmin.
-
02-23-2015, 02:11 PM #132
If a M502 makes things work again... It would almost seem something is getting stored wrong in the EEPROM. A M503 will print the values of the variables (out of the EEPROM) that are being used. Can you do a couple of things? First get the printer working normally and do a M503. Then get it sick and do another M503 and compare the numbers.
Also, it might be interesting to get the printer working correctly, do a M503 and then read values from the EEPROM using a M501 followed by a M503. Does a M501 get the printer to act sick?
-
02-23-2015, 02:43 PM #133
- Join Date
- Oct 2014
- Posts
- 114
It doesn't work with eeprom safe, I cannot get it to print since after a G29, the bed doesn't come up anymore. If I do a M502 it works again, but it also removes the matix data.
Right now with all the pullups, I cannot home all since the Zstop is a sensor and needs safe z homing. But the machine doesn't safe z with all pullups uncommented.
I will change the firmware back until I can do the G29 and send you that M503.
16:16:20.745 : echo:Steps per unit:
16:16:20.749 : echo: M92 X80.00 Y80.00 Z400.00 E100.00
16:16:20.749 : echo:
16:16:20.749 : Bed Level Correction Matrix:
16:16:20.753 : 1.000000 0.000000 0.000000
16:16:20.753 : 0.000000 1.000000 0.000000
16:16:20.753 : 0.000000 0.000000 1.000000
16:16:20.758 : echo:Maximum feedrates (mm/s):
16:16:20.758 : echo: M203 X500.00 Y500.00 Z50.00 E45.00
16:16:20.762 : echo:Maximum Acceleration (mm/s2):
16:16:20.762 : echo: M201 X9000 Y9000 Z100 E10000
16:16:20.766 : echo:Acceleration: S=acceleration, T=retract acceleration
16:16:20.766 : echo: M204 S3000.00 T3000.00
16:16:20.774 : 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)
16:16:20.778 : echo: M205 S0.00 T0.00 B20000 X15.00 Z0.40 E5.00
16:16:20.778 : echo:Home offset (mm):
16:16:20.778 : echo: M206 X0.00 Y0.00 Z0.00
16:16:20.782 : echo:Z_Probe_Offset (mm): 2.00
16:16:20.782 : echo:PID settings:
16:16:20.782 : echo: M301 P21.63 I1.54 D76.21
When ever I use the safe to eeprom the machine act erratic. Should have a M503 without ABL soon
Now I can't get it to safe home anymore.......hmm
Here is the M503 from a firmware with out safe G29 to eeprom. It doesn't safe z at the present...not sure why....
16:40:47.864 : echo:Steps per unit:
16:40:47.864 : echo: M92 X80.00 Y80.00 Z400.00 E100.00
16:40:47.867 : echo:Maximum feedrates (mm/s):
16:40:47.867 : echo: M203 X500.00 Y500.00 Z50.00 E45.00
16:40:47.871 : echo:Maximum Acceleration (mm/s2):
16:40:47.871 : echo: M201 X9000 Y9000 Z100 E10000
16:40:47.875 : echo:Acceleration: S=acceleration, T=retract acceleration
16:40:47.875 : echo: M204 S3000.00 T3000.00
16:40:47.884 : 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)
16:40:47.888 : echo: M205 S0.00 T0.00 B20000 X15.00 Z0.40 E5.00
16:40:47.888 : echo:Home offset (mm):
16:40:47.888 : echo: M206 X0.00 Y0.00 Z0.00
16:40:47.888 : echo:PID settings:
16:40:47.891 : echo: M301 P21.63 I1.54 D76.21
And here is an M503 from another machine using your G29 to eeprom successfully (besides the glitch witht he z stop triggering x min)
16:42:33.661 : echo:Steps per unit:
16:42:33.663 : echo: M92 X80.00 Y80.00 Z3200.00 E178.00
16:42:33.663 : echo:
16:42:33.663 : Bed Level Correction Matrix:
16:42:33.666 : 0.999995 0.000000 0.003262
16:42:33.666 : -0.000003 1.000000 0.000973
16:42:33.670 : -0.003262 -0.000973 0.999994
16:42:33.670 : echo:Maximum feedrates (mm/s):
16:42:33.673 : echo: M203 X500.00 Y500.00 Z4.00 E45.00
16:42:33.674 : echo:Maximum Acceleration (mm/s2):
16:42:33.678 : echo: M201 X9000 Y9000 Z100 E10000
16:42:33.678 : echo:Acceleration: S=acceleration, T=retract acceleration
16:42:33.682 : echo: M204 S3000.00 T3000.00
16:42:33.690 : 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)
16:42:33.690 : echo: M205 S0.00 T0.00 B20000 X20.00 Z0.40 E5.00
16:42:33.694 : echo:Home offset (mm):
16:42:33.694 : echo: M206 X0.00 Y0.00 Z-2.10
16:42:33.694 : echo:Z_Probe_Offset (mm): 1.20
16:42:33.694 : echo:PID settings:
16:42:33.698 : echo: M301 P19.34 I1.03 D90.64
Her is one without the G29 to eeprom but uploaded, and did an M119, then M502,M500,M501 and M119 and nothing is triggered without a motion on the machine.
17:01:53.400 : echo:Steps per unit:
17:01:53.405 : echo: M92 X80.00 Y80.00 Z400.00 E100.00
17:01:53.405 : echo:Maximum feedrates (mm/s):
17:01:53.409 : echo: M203 X500.00 Y500.00 Z50.00 E45.00
17:01:53.409 : echo:Maximum Acceleration (mm/s2):
17:01:53.413 : echo: M201 X9000 Y9000 Z100 E10000
17:01:53.413 : echo:Acceleration: S=acceleration, T=retract acceleration
17:01:53.417 : echo: M204 S3000.00 T3000.00
17:01:53.421 : 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)
17:01:53.425 : echo: M205 S0.00 T0.00 B20000 X15.00 Z0.40 E5.00
17:01:53.425 : echo:Home offset (mm):
17:01:53.429 : echo: M206 X0.00 Y0.00 Z0.00
17:01:53.429 : echo:PID settings:
17:01:53.429 : echo: M301 P21.63 I1.54 D76.21
17:01:54.792 : echo:Unknown command: ""
17:01:54.839 : FIRMWARE_NAME:Marlin V1; Sprinter/grbl mashup for gen6 FIRMWARE_URL:https://github.com/ErikZalm/Marlin/ PROTOCOL_VERSION:1.0 MACHINE_TYPE:Eight 3 EXTRUDER_COUNT:1 UUID:00000000-0000-0000-0000-000000000000
17:01:54.907 : echo:Active Extruder: 0
17:01:54.983 : echo:Active Extruder: 0
17:01:57.634 : Reporting endstop status
17:01:57.637 : x_min: TRIGGERED
17:01:57.637 : x_max: open
17:01:57.637 : y_min: open
17:01:57.637 : y_max: TRIGGERED
17:01:57.637 : z_min: open
17:01:57.637 : z_max: open
17:02:06.708 : echo:endstops hit: Y:-0.01
17:02:07.625 : echo:endstops hit: Y:-0.03
17:02:08.141 : echo:endstops hit: Y:-0.04
17:02:08.773 : echo:endstops hit: Y:-0.05
17:02:09.027 : echo:endstops hit: Y:-0.06
17:02:09.212 : echo:endstops hit: Y:-0.08
17:02:09.388 : echo:endstops hit: Y:-0.09
17:02:09.705 : echo:endstops hit: Y:-0.10
17:02:09.889 : echo:endstops hit: Y:-0.11
17:02:10.043 : echo:endstops hit: Y:-0.12
17:02:10.217 : echo:endstops hit: Y:-0.14
17:02:21.235 : Reporting endstop status
17:02:21.235 : x_min: open
17:02:21.235 : x_max: open
17:02:21.235 : y_min: TRIGGERED
17:02:21.237 : y_max: TRIGGERED
17:02:21.237 : z_min: open
17:02:21.237 : z_max: open
17:04:05.656 : Reporting endstop status
17:04:05.656 : x_min: open
17:04:05.656 : x_max: open
17:04:05.656 : y_min: TRIGGERED
17:04:05.656 : y_max: open
17:04:05.657 : z_min: open
17:04:05.657 : z_max: TRIGGERED
17:04:28.677 : echo:Hardcoded Default Settings Loaded
17:04:33.216 : echo:Settings Stored
17:04:36.219 : echo:Stored settings retrieved
17:04:36.219 : echo:Steps per unit:
17:04:36.223 : echo: M92 X80.00 Y80.00 Z400.00 E100.00
17:04:36.223 : echo:Maximum feedrates (mm/s):
17:04:36.227 : echo: M203 X500.00 Y500.00 Z50.00 E45.00
17:04:36.227 : echo:Maximum Acceleration (mm/s2):
17:04:36.231 : echo: M201 X9000 Y9000 Z100 E10000
17:04:36.231 : echo:Acceleration: S=acceleration, T=retract acceleration
17:04:36.235 : echo: M204 S3000.00 T3000.00
17:04:36.240 : 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)
17:04:36.243 : echo: M205 S0.00 T0.00 B20000 X15.00 Z0.40 E5.00
17:04:36.243 : echo:Home offset (mm):
17:04:36.247 : echo: M206 X0.00 Y0.00 Z0.00
17:04:36.247 : echo:PID settings:
17:04:36.247 : echo: M301 P21.63 I1.54 D76.21
17:04:49.241 : Reporting endstop status
17:04:49.241 : x_min: open
17:04:49.241 : x_max: open
17:04:49.241 : y_min: open
17:04:49.245 : y_max: open
17:04:49.245 : z_min: open
17:04:49.245 : z_max: openLast edited by Fri; 02-23-2015 at 04:44 PM.
-
02-24-2015, 08:22 AM #134
When you connect to the board, does it say "Using EEPROM values!" ? What does it say the Version is and the Stored Version are?
Here is the M503 from a firmware with out safe G29 to eeprom. It doesn't safe z at the present...not sure why....Last edited by Roxy; 02-24-2015 at 08:29 AM.
-
02-24-2015, 09:43 AM #135
- Join Date
- Oct 2014
- Posts
- 114
I discovered some errors and fix them, now I get a better initial reading, see below. I also noticed that the safe z coordinates were outside the max print size (did some mechanical changes to the x carriage) and therefore it wouldn't
safe z. All said, now it is still spotty about the safe z, if I connect, it doesn't do it, if I home x and y first (both do not bounce the first time) then it most of the time does the safe z. Not always though and sometimes it does it, but
moves to a position short of where it should go.
10:36:11.333 : start
10:36:11.338 : echo: External Reset
10:36:11.338 : Marlin1.0.0
10:36:11.339 : echo: Last Updated: Feb 24 2015 10:30:31 | Author: (Fri New E3 Eeprom no lcd)
10:36:11.342 : Compiled: Feb 24 2015
10:36:11.342 : echo: Free Memory: 4841 PlannerBufferBytes: 1232
10:36:11.346 : echo:Version: [V37] Stored version: [V37]
10:36:11.346 : Using EEPROM values!
10:36:11.346 : echo:Stored settings retrieved
10:36:11.346 : echo:Steps per unit:
10:36:11.350 : echo: M92 X80.00 Y80.00 Z400.00 E100.00
10:36:11.350 : echo:Maximum feedrates (mm/s):
10:36:11.354 : echo: M203 X500.00 Y500.00 Z50.00 E45.00
10:36:11.354 : echo:Maximum Acceleration (mm/s2):
10:36:11.358 : echo: M201 X9000 Y9000 Z100 E10000
10:36:11.363 : echo:Acceleration: S=acceleration, T=retract acceleration
10:36:11.363 : echo: M204 S3000.00 T1.00
10:36:11.371 : 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)
10:36:11.371 : echo: M205 S0.00 T0.00 B0 X1.00 Z0.00 E0.00
10:36:11.371 : echo:Home offset (mm):
10:36:11.375 : echo: M206 X0.00 Y1.00 Z3000.00
10:36:11.375 : echo:Z_Probe_Offset (mm): 15.00
10:36:11.375 : echo:PID settings:
10:36:11.378 : echo: M301 P0.40 I38.15 D0.00
10:36:12.727 : echo:Unknown command: ""
10:36:12.897 : FIRMWARE_NAME:Marlin V1; Sprinter/grbl mashup for gen6 FIRMWARE_URL:https://github.com/ErikZalm/Marlin/ PROTOCOL_VERSION:1.0 MACHINE_TYPE:FreeFab3d Eight3 EXTRUDER_COUNT:1 UUID:00000000-0000-0000-0000-000000000000
10:36:12.944 : echo:Active Extruder: 0
10:36:12.948 : echo:Active Extruder: 0
-
02-24-2015, 10:11 AM #136
- Join Date
- Oct 2014
- Posts
- 114
Roxy, I think my safe home speed is too fast. Where can that speed be changed. The axis homing speed is fine, but when it moves to the bed center (or whatever position to have the sensor on the bed) it moves very fast.
-
02-24-2015, 10:22 AM #137
During safe Z homing, the line
#define XY_TRAVEL_SPEED 8000
is used from Configuration.h If the speed of the motors was too high for them to move where they are being told to go to, it is possible for the firmware to think the extruder is in a different place than it is.
-
02-24-2015, 12:55 PM #138
- Join Date
- Oct 2014
- Posts
- 114
I will give this a shot. Btw, I made a bunch of silly small mistakes that made the machine act erratic. For example, I use Fan 2 on my prototype to feed my proximity sensor, but fan 2 pin was setup as contoller fan that
turns of after 60 sec and doesn't come un until something moves.....duhh.
-
02-24-2015, 01:30 PM #139
- Join Date
- Oct 2014
- Posts
- 114
It absolutely does that, just happened. I got it all pretty much working, it's just that initial safe home that is not 100%, every once in a while it doesn't go to where it should and the firmware thinks it is where it was suppose to go.
So it runs in the wall. Any ideas what could cause this now after everything else seams to work well.
-
02-24-2015, 02:54 PM #140
How about we start fresh? (It is hard to keep track of everything!) Can you describe the new issue from the beginning? When does it work correctly? When does it start doing bad things?
Ender 3 Neo - Jam Problem
Yesterday, 03:06 PM in Tips, Tricks and Tech Help