Jump to content
Ultimaker Community of 3D Printing Experts

Tinker firmware - introduction


Recommended Posts

Posted · Tinker firmware - introduction
On 8/7/2020 at 8:20 AM, Rene88 said:

Is it still good to use Tinker Firmware with my Ultimaker 2+ extended? or beter use stock firmware?

Yes, I like it much. The firmware is basically an extended version of the stock firmware, it is based on it.

  • Link to post
    Share on other sites
    • Replies 161
    • Created
    • Last Reply

    Top Posters In This Topic

    Top Posters In This Topic

    Popular Posts

    I was asked to sum up some facts about the alternative "tinker" firmware. Here are the basics and the main links to start with it:   What is the "Tinker-Firmware"? It's an alternative firmware for

    I would like to say thank you for your reply and helping me in my problem

    I'd get a uninterruptable power supply.   So you will need 2 of the features that come with tinkerMarlin.  I mentioned above - you can set the Z position of the print head exactly.  In this

    Posted Images

    Posted · Tinker firmware - introduction
    9 hours ago, joatrash said:

    Is anyone having troubles with this firmware and Cura 4.7?

    No, but I rarely print longer print jobs on my UM2+Ext. 

    I will give it a try in the next days, with a longer print job.

  • Link to post
    Share on other sites
    Posted · Tinker firmware - introduction

    Ok... I've spent a couple days experimenting now and there's something going on with Tinker on a specific 3d model I am trying to print. If I go back to the original (latest) UM2+ firmware it prints fine. I now tried slicing with cura 2.5, 4.1 and 4.7 and the results are similar- the print just stops after a while as if it were finished. The same model, sliced waaaaaaay back with an early cura (2.1 I think) still prints.

    The weird thing is that I went back and redid the model with different topology, made it 100% error free, manifold and watertight but the result is the same. If IS a rather detailed model though, at around 50MB. Unfortunately, I can't share this particular model, since it's a confidential file, but I'll try a different model (that I CAN share) and see if I get errors on that too.

  • Link to post
    Share on other sites
    Posted · Tinker firmware - introduction

    OK... more testing. Look at this:

    image.thumb.png.db0cd35d2ca1a621bea2ee02bc462d57.png

    image.thumb.png.4fdf5b477e8285ca5be7cd0106f48dfa.png


     

     

    I imported the gcode files into Simplify3d just to look at them. It looks like Cura has inserted random super-fast print head movements because the red lines are exactly where the print failed. UMs original firmware seems to be able to handle the files anyway, but Tinker stops printing when it reaches those lines every time.

    Any thoughts as to what could be going on?

  • Link to post
    Share on other sites
    Posted · Tinker firmware - introduction
    3 hours ago, joatrash said:

    Any thoughts as to what could be going on?

     

    Dunno, can you translate "random super-fast print head movements" into a more precise measuring unit?🙂

    Or can you share the gcode file?

     

  • Link to post
    Share on other sites
    Posted · Tinker firmware - introduction
    1 hour ago, tinkergnome said:

     

    Dunno, can you translate "random super-fast print head movements" into a more precise measuring unit?🙂

    Or can you share the gcode file?

     

    Haha, well looking at the screenshot... the red line seems to indicate a moment of 9000mm per  minute!

    But I did more digging. It looks like the problem might be hardware-related on my end. I suspect a faulty SD-card reader. (Or if it's not, then Windows is indexing the SD card even though it's not supposed to be.) Looks like errors start showing up in files when the SD card is removed. Information in the files goes missing, like here:
    image.thumb.png.31e419ce9b8312126e4ced2a5cfb968a.png
    Broken copy on the left, error-free copy on the right.

    Apologies for thinking it was a Tinker issue.

    ONE puzzling thing though... the UM firmware seems to IGNORE the error and carry on, but Tinker stops. is there an extra-sensitive error-check in there?

  • Link to post
    Share on other sites
    Posted (edited) · Tinker firmware - introduction

    The headbed of my UM2+ does not cool down anymore (temp keeps rising).

    I think the mosfet for heater3 is broken and i'm not really in the mood of buying a new mainboard 😉

     

    The mainboard has 3 heater terminals:

    heater1 (occopied), heater2 (free) and heater3 (this is the heater for the headbed).

    I also see that there are 3 seperate mosfets for all these 'heaters'.

     

    So, i'm thinking, using the Tinker firmware, is it possible to use the 'heater2' terminal (not occopied) on the mainboard for the original headbed?

     

    @tinkergnome Is there maybe a setting/option in the Tinker firmware to set heater2 as primary heatbed?

     

    BR,

    Ray

    Edited by rayholland
  • Link to post
    Share on other sites
    Posted · Tinker firmware - introduction
    2 hours ago, rayholland said:

    So, i'm thinking, using the Tinker firmware, is it possible to use the 'heater2' terminal (not occopied) on the mainboard for the original headbed?

     

    The buildplate heater draws a lot more current than a hotend. Dunno, but you should be absolute sure that the capability of the outputs is really the same before you change anything.

     

    There are probably only minor things to change on the software side, but you have to compile a custom firmware in this case.

     

  • Link to post
    Share on other sites
    Posted · Tinker firmware - introduction

    Would changing the line '#define HEATER_BED_PIN      4'  to '#define HEATER_BED_PIN      3' in the pins.h be sufficient?

  • Link to post
    Share on other sites
    Posted · Tinker firmware - introduction
    10 hours ago, rayholland said:

    Would changing the line '#define HEATER_BED_PIN      4'  to '#define HEATER_BED_PIN      3' in the pins.h be sufficient?

     

    Probably yes. I would swap the pin numbers between HEATER_1_PIN and HEATER_BED_PIN

    Take sure that you are in the correct section (MOTHERBOARD == 72) and it should work.

     

  • Link to post
    Share on other sites
    Posted · Tinker firmware - introduction
    On 10/16/2020 at 3:25 PM, rayholland said:

    The headbed of my UM2+ does not cool down anymore (temp keeps rising).

    I think the mosfet for heater3 is broken and i'm not really in the mood of buying a new mainboard 😉

     

    The mainboard has 3 heater terminals:

    heater1 (occopied), heater2 (free) and heater3 (this is the heater for the headbed).

    I also see that there are 3 seperate mosfets for all these 'heaters'.

     

    So, i'm thinking, using the Tinker firmware, is it possible to use the 'heater2' terminal (not occopied) on the mainboard for the original headbed?

     

    @tinkergnome Is there maybe a setting/option in the Tinker firmware to set heater2 as primary heatbed?

     

    BR,

    Ray

    I have same Issu but the heater dont work, so never start printing

     

    Did you change the pin? because we can swtich to heater 2, but I dont know if the current would be supported because the mainboard has a finder relay 361190054011 that i dont know what is for...

     

    So if you could do it, please tell us, I will do it too and tells you

     

    Thanks!

  • Link to post
    Share on other sites
    Posted · Tinker firmware - introduction

    How do you change the abort retraction? I've changed my hot end and it retracts way too much for that hot end.

  • Link to post
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

    ×
    ×
    • Create New...