Close



Page 16 of 40 FirstFirst ... 6141516171826 ... LastLast
Results 151 to 160 of 396
  1. #151
    This is great advice. I'm using Cura and Octoprint. Since I moved our tree forward against the upstream/master, I've noticed the Waiting for user message has changed to M105. M105 is the temperature poll for the extruder (IIRC). I think I am having a timeout issue with my Octoprint settings.

    what does your cura start gcode look like? mine is like this

    ;Sliced at: {day} {date} {time}
    ;Basic settings: Layer height: {layer_height} Walls: {wall_thickness} Fill: {fill_density}
    ;Print time: {print_time}
    ;Filament used: {filament_amount}m {filament_weight}g
    ;Filament cost: {filament_cost}
    M190 S50 ;Uncomment to add your own bed temperature line
    G21 ;metric values
    G28
    G29
    M109 S225 ;Uncomment to add your own temperature line
    G90 ;absolute positioning
    M82 ;set extruder to absolute mode
    G1 Z15.0 F{travel_speed} ;move the platform down 15mm
    G92 E0 ;zero the extruded length
    G1 F200 E3 ;extrude 3mm of feed stock
    G92 E0 ;zero the extruded length again
    G1 F{travel_speed}
    ;Put printing message on LCD screen
    M117 Printing...

  2. #152
    Student
    Join Date
    Dec 2014
    Location
    Clifton, NJ
    Posts
    4
    hey i am having an issue trying to get abl to work properly using either beckdac or ErikZalm's firmware. no matter what i do to #define Z_PROBE_OFFSET_FROM_EXTRUDER, it keeps trying to start printing with the extruder height set to the z height of the probe when its in the down position. Am i doing something wrong or are other people experiencing the same problem with the firmware using ABL.

    Thanks

  3. #153
    Super Moderator Roxy's Avatar
    Join Date
    Apr 2014
    Location
    Lone Star State
    Posts
    2,182
    Quote Originally Posted by bgct9a View Post
    hey i am having an issue trying to get abl to work properly using either beckdac or ErikZalm's firmware. no matter what i do to #define Z_PROBE_OFFSET_FROM_EXTRUDER, it keeps trying to start printing with the extruder height set to the z height of the probe when its in the down position. Am i doing something wrong or are other people experiencing the same problem with the firmware using ABL.

    Thanks
    For starters.... Turn off these configuration options if they are enabled in Configuration.h:
    Code:
    //#define EEPROM_SETTINGS
    //#define EEPROM_CHITCHAT
    Please report back what happens after you do that....

  4. #154
    Staff Engineer printbus's Avatar
    Join Date
    May 2014
    Location
    Highlands Ranch, Colorado USA
    Posts
    1,437
    Add printbus on Thingiverse
    I've ran into an issue in how Marlin accepts a user entry for a MakerFarm parameter, but can't offer an easy solution. Someone else would have to figure that out.

    As part of lcd_control_motion_menu() within ultralcd.cpp, the statement...

    MENU_ITEM_EDIT_CALLBACK(long5, MSG_AMAX MSG_Z, &max_acceleration_units_per_sq_second[Z_AXIS], 100, 99000, reset_acceleration_rates);

    is what would be used to change the setting for Amax Z, or the Z axis maximum acceleration under the Control | Motion menu. Apparently, a long5 can only be changed to something greater than 100 and in increments of 100. The MakerFarm default for Amax Z is just 5. Once you go the Amax Z menu, the value is automatically changed to 100 and you can't set it back to 5. The 100 in the above statement is the allowed minimum, but changing that alone doesn't fix much. I got lost in trying to trace through the MENU_ITEM macro hierarchy, and modifying how a type long5 is edited would affect editing the other type long5 acceleration parameters. Amax Z may need to ideally be changed to a different type if this issue were to be resolved. It'll likely be far easier to just never try to edit the Z acceleration parameter from the LCD.

    EDIT: Code is as of the end of Sept dacb fork.
    Last edited by printbus; 12-14-2014 at 07:32 AM.

  5. #155
    Student
    Join Date
    Dec 2014
    Location
    Clifton, NJ
    Posts
    4
    Quote Originally Posted by Roxy View Post
    For starters.... Turn off these configuration options if they are enabled in Configuration.h:
    Code:
    //#define EEPROM_SETTINGS
    //#define EEPROM_CHITCHAT
    Please report back what happens after you do that....
    hey much better, it is now lowering the extruder ty!!!

  6. #156
    Super Moderator Roxy's Avatar
    Join Date
    Apr 2014
    Location
    Lone Star State
    Posts
    2,182
    Quote Originally Posted by bgct9a View Post
    hey much better, it is now lowering the extruder ty!!!
    Do you understand what was happening? If you really need the EEPROM settings enabled, you can turn them on. But you have to save correct values to the EEPROM using M502 and M500. The reason is the settings in your Configuration.h file will not be used. Instead, the Marlin firmware will see values stored in the EEPROM, and use those instead.

  7. #157
    Student
    Join Date
    Dec 2014
    Location
    Clifton, NJ
    Posts
    4
    Quote Originally Posted by Roxy View Post
    Do you understand what was happening? If you really need the EEPROM settings enabled, you can turn them on. But you have to save correct values to the EEPROM using M502 and M500. The reason is the settings in your Configuration.h file will not be used. Instead, the Marlin firmware will see values stored in the EEPROM, and use those instead.
    this is where i am a little lost. I figured that what u upload to the mega is the new base settings and the whole eeprom usage is for when you use the lcd screen to make changes and then want to save them permanently.

  8. #158
    Staff Engineer printbus's Avatar
    Join Date
    May 2014
    Location
    Highlands Ranch, Colorado USA
    Posts
    1,437
    Add printbus on Thingiverse
    Quote Originally Posted by bgct9a View Post
    this is where i am a little lost. I figured that what u upload to the mega is the new base settings and the whole eeprom usage is for when you use the lcd screen to make changes and then want to save them permanently.
    Nope. This confuses people all the time. If EEPROM is enabled, the settings last stored there are always loaded at Marlin startup. Like Roxy said, you can over-ride those by sending the printer an M502 (load from factory default, where "factory" is the baseline in flash memory along with the executable code). An M500 can be used any time you want to save all the current settings being used into EEPROM. Uploading new firmware from the Arduino IDE does not modify the contents of EEPROM.

  9. #159
    basically, if you want to use the eeprom to adjust settings on the fly. as a rule of thumb you need to make notes of what you change, so that when you flash new firmware you update those changes in the actual firmware before flashing and after flashing the firmware automatically run an M502 to update the eeprom settings that were just flashed.

  10. #160
    Engineer
    Join Date
    Jul 2014
    Location
    Eastern Colorado
    Posts
    536
    I think the whole EEPROM thing is too much of a trouble-maker to be useful, IMO.

    I've encountered a pitfall regarding running ABL before every print, however. I just replaced both my Z nuts, because the one on the RAMPS side either wore out, or the threaded rod did. It's only in one small area, however, which I believe is due to the constant up-down of the probing wearing that one section more than any other. The Z nut on the RAMPS side kept slipping down the threaded rod during ABL, throwing the whole alignment out of whack by nearly 2mm. No matter how much I hand-turned the Z rods to level them, the topographic map was always the same, or very close. The new Z nut is just a stopgap measure for now, until I can get new threaded rods.

    If your rods, like mine, get black from oil and whatever other junk, look for one area that's shinier than the rest, around the point where your ABL probing happens. This is a sign that that spot is getting worn out quicker.

    It seems that though I despise using the EEPROM, I may have to in order to avoid this excessive wear issue.

    edit: Replacing the Z nuts did the trick:

    Before (with hand-turning the Z rods in between each time):

    Recv: Bed Height Topography:
    Recv: Origin: Front Left
    Recv: --0.99552 --0.58427 --0.10027 +0.40423 +0.91598
    Recv: --0.96627 --0.53202 --0.05352 +0.45073 +0.95223
    Recv: --0.94152 --0.50377 --0.01652 +0.51248 +1.00023
    Recv: --0.92702 --0.47602 --0.01177 +0.54798 +1.04023
    Recv: --0.91602 --0.45577 +0.01198 +0.56598 +1.07823

    Recv: Bed Height Topography:
    Recv: Origin: Front Left
    Recv: --0.98843 --0.57268 --0.10043 +0.40732 +0.96382
    Recv: --0.96243 --0.53468 --0.05293 +0.43907 +0.95182
    Recv: --0.92243 --0.50643 --0.02218 +0.48957 +0.98982
    Recv: --0.91618 --0.47068 --0.00618 +0.55457 +1.03332
    Recv: --0.93643 --0.47818 +0.00357 +0.55457 +1.08282

    Recv: Bed Height Topography:
    Recv: Origin: Front Left
    Recv: --0.98989 --0.57314 --0.11264 +0.40236 +0.94361
    Recv: --0.96639 --0.53439 --0.06864 +0.43836 +1.01611
    Recv: --0.94014 --0.50789 --0.02189 +0.47636 +1.04811
    Recv: --0.92014 --0.48814 --0.00989 +0.50836 +1.09411
    Recv: --0.94389 --0.48214 +0.00211 +0.52486 +1.10486

    Recv: Bed Height Topography:
    Recv: Origin: Front Left
    Recv: --0.98813 --0.57938 --0.10138 +0.41412 +0.93487
    Recv: --0.95538 --0.53113 --0.05763 +0.46062 +0.99837
    Recv: --0.92613 --0.51163 --0.01738 +0.49237 +1.06087
    Recv: --0.91513 --0.48213 --0.01138 +0.52462 +1.06912
    Recv: --0.95738 --0.50538 --0.01913 +0.51512 +1.08862

    After:

    Recv: Bed Height Topography:
    Recv: Origin: Front Left
    Recv: --0.22164 --0.12064 --0.03789 +0.01611 +0.06361
    Recv: --0.19539 --0.08789 +0.00186 +0.05711 +0.11011
    Recv: --0.17564 --0.06214 +0.04186 +0.09611 +0.12236
    Recv: --0.14789 --0.03514 +0.07536 +0.13861 +0.18036
    Recv: --0.17814 --0.03839 +0.07011 +0.14111 +0.18611
    Last edited by AbuMaia; 12-14-2014 at 06:18 PM.

Page 16 of 40 FirstFirst ... 6141516171826 ... LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •