Close



Results 1 to 10 of 172

Hybrid View

  1. #1
    Super Moderator Roxy's Avatar
    Join Date
    Apr 2014
    Location
    Lone Star State
    Posts
    2,182
    Quote Originally Posted by Fri View Post
    Roxy, sorry for the delay. I am using a FreeFab3d ML2 printer, it's a hybrid between a Mendelmax and Bukobot.

    Can you start an new thread? Let me take a look at your fw tomorrow and see how easy I can implement it.
    How about we proceed with me actually putting the Auto Bed Leveling Matrix saving to EEPROM into my firmware, and you crossing your Configuration.h settings over to it. Upon further thought, I don't think you will need to worry about the Pins.h file. I think we just replace the Pins.h file in my code base with what ever you have since you have a totally different printer and won't be using anything I've messed with.

    And then... Everything we are doing in this thread is related to Auto Bed Leveling Matrix saving to EEPROM. It will belong in this thread!

    Quote Originally Posted by Fri View Post
    Here are some answers, I was under the impression that I am using the latest version of Zahn's Marlin.

    1. The offset of the sensor from the extruder is minus -43 for x, but the position where it probes is reflecting the position of the sensor...not the extruder. So x 10mm is the sensors position.
    Yes, but here is my concern: If the probe is -43mm on the X Axis... When you home the extruder, the nozzle is going to go to 0. But the probe is going to go to -43mm on the X Axis. Do you have the clearance so it doesn't hit something? I'm guessing it is just fine or you would have already run into problems. Right?

    Quote Originally Posted by Fri View Post


    1. Clearance is fine with 4 2 2 , it is plenty of movement and clearance for the sensor to go out and back on. I am using abl, but with a proximity sensor, no moving parts.
    2. Marlin Main. Void setup, these are controlling fans, at certain temps.

    The G28 issues are new to me and they may well be the problem....I will check this out asap.

    Thanks so much!
    OK... Hang tight! As soon as I can, I'll get the Auto Bed Level Matrix code to save it to EEPROM in my code base and post it. And then, you just cross your Configuration.h settings over to it and with luck it just runs. With that said, DACB and PrintBus are seeing some flakyness in the code base they are running and right now there is a question of what is causing it. It is entirely possible what ever is causing their firmware to misbehave is the same thing that is giving you problems.

    But here is the deal... If I get the Auto Bed Level Matrix code saving to EEPROM in my code base, we will have almost identical code and it will be much easier for me to figure out what is wrong if you continue to have problems. Hopefully, what ever you see, I'll be able to duplicate.

  2. #2
    Technologist
    Join Date
    Oct 2014
    Posts
    114
    Quote Originally Posted by Roxy View Post
    How about we proceed with me actually putting the Auto Bed Leveling Matrix saving to EEPROM into my firmware, and you crossing your Configuration.h settings over to it. Upon further thought, I don't think you will need to worry about the Pins.h file. I think we just replace the Pins.h file in my code base with what ever you have since you have a totally different printer and won't be using anything I've messed with.

    And then... Everything we are doing in this thread is related to Auto Bed Leveling Matrix saving to EEPROM. It will belong in this thread!

    Sounds good.


    Yes, but here is my concern: If the probe is -43mm on the X Axis... When you home the extruder, the nozzle is going to go to 0. But the probe is going to go to -43mm on the X Axis. Do you have the clearance so it doesn't hit something? I'm guessing it is just fine or you would have already run into problems. Right?

    Yeah, there is plenty of room for the sensor, I will send a pic or video one of these days....

    OK... Hang tight! As soon as I can, I'll get the Auto Bed Level Matrix code to save it to EEPROM in my code base and post it. And then, you just cross your Configuration.h settings over to it and with luck it just runs. With that said, DACB and PrintBus are seeing some flakyness in the code base they are running and right now there is a question of what is causing it. It is entirely possible what ever is causing their firmware to misbehave is the same thing that is giving you problems.

    But here is the deal... If I get the Auto Bed Level Matrix code saving to EEPROM in my code base, we will have almost identical code and it will be much easier for me to figure out what is wrong if you continue to have problems. Hopefully, what ever you see, I'll be able to duplicate.
    Perfect! I will look out for it.

Posting Permissions

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