Close



Page 37 of 38 FirstFirst ... 2735363738 LastLast
Results 361 to 370 of 396

Hybrid View

  1. #1
    Engineer-in-Training
    Join Date
    Jul 2016
    Location
    Pennsylvania, USA
    Posts
    255
    Hi

    It's the mesh pattern validation stuff that I'm waiting for .... trust but verify ... I've dropped the median filter back to 3 samples on the BLTouch and need to check things from time to time.

    Bob

  2. #2
    Staff Engineer printbus's Avatar
    Join Date
    May 2014
    Location
    Highlands Ranch, Colorado USA
    Posts
    1,437
    Add printbus on Thingiverse
    What is your compile error?

    I did a debug build for someone a long time ago, and what it boiled down to was this (from configuration.h at the time)

    // ==> REMEMBER TO INSTALL U8glib to your ARDUINO library folder: https://github.com/olikraus/U8glib_Arduino

    Without that library, the graphic stuff won't build.

    EDIT: Ah. Just saw your comment that came in while I was typing.

  3. #3
    Engineer-in-Training
    Join Date
    Jul 2016
    Location
    Pennsylvania, USA
    Posts
    255
    Hi

    Start from a scratch compile, undefine their default display and define the graphics controller. Unless there is a very new bug, it should compile.

    Bob

  4. #4
    Engineer-in-Training
    Join Date
    Jul 2014
    Posts
    305
    Quote Originally Posted by printbus View Post
    What is your compile error?

    I did a debug build for someone a long time ago, and what it boiled down to was this (from configuration.h at the time)

    // ==> REMEMBER TO INSTALL U8glib to your ARDUINO library folder: https://github.com/olikraus/U8glib_Arduino

    Without that library, the graphic stuff won't build.

    EDIT: Ah. Just saw your comment that came in while I was typing.
    Quote Originally Posted by uncle_bob View Post
    Hi

    Start from a scratch compile, undefine their default display and define the graphics controller. Unless there is a very new bug, it should compile.

    Bob
    I got it working! I found a typo in the following section:

    "#define PREHEAT_1_TEMP_HOTEND 180
    #define PREHEAT_1_TEMP_BED 70
    #define PREHEAT_1_FAN_SPEED 0"

    So when it was trying to compile it couldn't match those values with another .h file. All is fixed for now. Thank you!

  5. #5
    Engineer-in-Training
    Join Date
    Jul 2014
    Posts
    305
    Quote Originally Posted by Roxy View Post
    It works. But the RC-8 / RCBugFix version does not allow you to save the mesh. The UBL Branch lets you save the mesh and it also provides very nice Mesh Validation Pattern and Editing commands for the Mesh.
    I apologize for all the questions, but I do appreciate your knowledge and time.

    This morning I started modifying the RC Bug Fix and then I read this comment. In the future I am planning on using the BL touch to implement ABL/Mesh Leveling. if I understand your comment correctly, with RC Bug Fix it won't save the Mesh but will run at the start of every print to create that mesh. Is this correct?

    I just want to ensure whatever firmware I use I will be setup for success with my planned upgrades.

  6. #6
    Super Moderator Roxy's Avatar
    Join Date
    Apr 2014
    Location
    Lone Star State
    Posts
    2,182
    Quote Originally Posted by BLKKROW View Post
    I apologize for all the questions, but I do appreciate your knowledge and time.

    This morning I started modifying the RC Bug Fix and then I read this comment. In the future I am planning on using the BL touch to implement ABL/Mesh Leveling. if I understand your comment correctly, with RC Bug Fix it won't save the Mesh but will run at the start of every print to create that mesh. Is this correct?

    I just want to ensure whatever firmware I use I will be setup for success with my planned upgrades.
    Yes... Your understanding is correct. And incidentally, the BL-Touch stuff was added after UBL forked from RC-7. So you can use a BL-Touch with UBL, but you have to set it up as manually instead of just saying you have a BL-Touch probe. I'm off skiing in Taos. As soon as I get back I'm going to be doing a 3-way merge to get UBL running on top of RC-8. At that point, the simple BL-Touch support will be in UBL also. Realistically, it will be a week or two into January before that happens.

    But if you are going to do Mesh Bed Leveling... You really should consider bringing up the UBL system. You will get 100% adhesion across the entire bed every time.

  7. #7
    Engineer-in-Training
    Join Date
    Jul 2016
    Location
    Pennsylvania, USA
    Posts
    255
    Hi

    You have two simple choices:

    1) Auto bed leveling, (bilinear or whatever) that just does it's thing with a G29 gcode. It resets when any G28 (X,Y,Z) comes in.
    2) Mesh bed leveling, this runs with a sequence of G28 commands (or at least it used to). There is a bit more to the startup script as a result.

    The BLTouch has it's own issues, but seems to be "good enough".

    Bob

  8. #8
    Engineer-in-Training
    Join Date
    Jul 2014
    Posts
    305
    So I am working through the firmware and am getting compile errors.

    https://www.dropbox.com/s/sjafx44u4d...arlin.rar?dl=0

    That is a RAR of my firmware, can someone look at it and let me know what I did wrong? Thank you!

  9. #9
    Engineer-in-Training
    Join Date
    Jul 2016
    Location
    Pennsylvania, USA
    Posts
    255
    Hi

    Start from scratch and do a compile. It should compile without errors. If it does not, re-install your toolchain and re-download the code. Next, add your changes one at a time and do a compile. The one that makes it puke is suspect Multiple definitions for a feature are the most common issue (You can only have one display etc). If you are a "bulk change" sort of person, make notes on each line you change. Do the process in reverse, comment out each change and compile after each reversal.

    That may sound like a lot of time and a lot of work. It is enormously faster than waiting for somebody else to download your config and then find the time to check it out. There is inevitably a bit of back and forth with that process:

    The first layer issue with your config is that it is defining ULTIPANEL as the display and then looking for the data structures that are associated with it. Do you have a normal MakerFarm or have you modified the display?

    Bob

  10. #10
    Engineer-in-Training
    Join Date
    Jul 2014
    Posts
    305
    Quote Originally Posted by uncle_bob View Post
    Hi

    Start from scratch and do a compile. It should compile without errors. If it does not, re-install your toolchain and re-download the code. Next, add your changes one at a time and do a compile. The one that makes it puke is suspect Multiple definitions for a feature are the most common issue (You can only have one display etc). If you are a "bulk change" sort of person, make notes on each line you change. Do the process in reverse, comment out each change and compile after each reversal.

    That may sound like a lot of time and a lot of work. It is enormously faster than waiting for somebody else to download your config and then find the time to check it out. There is inevitably a bit of back and forth with that process:

    The first layer issue with your config is that it is defining ULTIPANEL as the display and then looking for the data structures that are associated with it. Do you have a normal MakerFarm or have you modified the display?

    Bob
    Thank you for your input!

    I have been copying a lot of settings from the original Marlin 1.02 that is provided by Colin. So I will keep digging through it and see what happens.

    Yes I do have the original Graphical LCD.

Page 37 of 38 FirstFirst ... 2735363738 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
  •