Jump to content

tinkergnome

Ambassador
  • Posts

    2,774
  • Joined

  • Last visited

  • Days Won

    61

Posts posted by tinkergnome

  1. I don't know why it is in the "lite" branch.  I don't know what the various branches mean.  What is the difference between "lite" and "master"?

     

    Interesting stuff, but this branch is obviously not intended for the current printers...

    i read terms like:

    - two extruders...

    - experimental ultimainboard...

    - automatic bed leveling with capacitive sensor..

    ..and some more stuff to screw up competitors... :)

    • Like 1
  2. The value is a bit weird... M92 sets the steps per mm AFAIK.

    I'm afraid that Marlin ist not prepared to control more than one extruder at the same time. It supports only one active extruder at a time. How did you achieved this?

    If i get you wrong, and the extruders are used successively - the right place for this command would be the toolchange sequence (right after "T0" resp. "T1").

    But to be honest: i never used Repetier Host...?

  3. The firmware is always posted before it's even released.

     

    AFAIK - there are no commits relating to the fan control - at least not during the last year...

    That's why i ask...

    I just try to enlighten the rumours that this feature is somehow dependent on the firmware version...

    If you're right - it isn't.

    Let's see, if @SandervG confirms this.

  4. That is a good idea, thanks! Could we agree this would serve the same purpose and functionality?

     

    Acknowledged.

    ...and as a footnote:

     

    Isn't it more interesting to know what a certain users says in regard to a certain topic then just the fact a comment was made?

     

    From my perspective...not in any case. Anders (for example) always makes "posts of interest" - regardless of the topic...(honestly) - and there are a few other users too.

    That's what the "friends" function is good for.

  5. A large share of the advanced users who used to like Ultimaker for its openness and willingness to listen and be flexible though, will now no longer have any particular reason to stick here or stick to Ultimaker.

    [...]

    New products that I am working on will appear for sure, but I am focusing on platform independent solutions now days and the development process will not be available here since there is no particular reason for me to spend time here if the group of people I want to reach has diminished.

     

    While reading this, a feature request crosses my mind...

    Can we have a "Follow this user" function?

    That means: get a notification for every new post of hand selected users (or "friends" - if you like)

    I apologize in advance if this is announced already and i missed it...

    • Like 1
  6. Hi @Patrick181,

    if I am not mistaken it is a combination between a firmware upgrade but also a change in the electronics.

     

    Hi Sander,

    a supplementary question:

    If i am not mistaken these changes are not published as open source yet, but it will be made available later (in a couple of months - as always).

    Can you attest this?

  7. And as a result of that, the number of posts on the new forum seems to be stuck at about 30/day, compared to the 170/day the old forum had.

     

    Just some personal thoughts...

    To make a new forum - and to make it this way - was a lonesome decision of the Ultimaker heads. Ultimaker did not asked the community and there was obviously no interest to consult the community prior to that.

    But hey... Ultimaker is a business concern and not our playground...

    The company in question made all decisions for the new forum, they pay for it and it runs on their servers. They made a change because they wanted to - nothing else. It's their forum and not (longer) ours... :(

    We - the community members - just have to learn to accept these facts.

    (finally - the Ultimaker company is the appropriate authority for support, but not the community...)

    On the other hand:

    As far as i can see - the community members are making their own decisions. I see much less activity, much less contribution and a lot of knowledge has even leaved the forum completely.

    I think, these are facts that Ultimaker just has to learn to accept (and to live with...).

    I assume, the intention was a bit different.. It's just a "lose-lose situation" for everyone at the moment.

    Stuff it, my life doesn't depend on this, i don't make a living from this forum.

    It's a pity, but it is like it is..

    Like i said: just some personal thoughts - and now: hurt me... :)

    • Like 4
  8. @tinkergnome: maybe we could use the reprap opto endstop electronic (http://www.reprap.org/wiki/Gen7_Endstop_1.3.1+) as sensor. What would be the best / easiest way to help you with the recovery firmware and to include this or a similar sensor ? I have downloaded the firmware (github via git) and compiled the source incl. the simulator. It is working so far. By the way what ide are you using fot developing. For minor projects arduino ide is sufficent, but for the firmware I think it is a bit too unstructured. Is Code::Block with arduino extension a good choice or Eclipse C++ with Arduino ?

     

    First: i'm afraid that we relegate the UI-changes to the fringe a bit...

    Although i "hijacked" this thread myself (in the past), may i suggest to open a new topic for the sensor project?

    I must admit that i don't want to tinker with the electronics part in the near future, because i'm a little bit pinched for spare time atm... I'm afraid this whole topic will be (mostly) your turn.

    I will try to assist with the firmware changes if needed. If i understand aright you want to extend the "Tinker firmware" to interprete the sensor readings.

    It should be easy to contribute and merge these things via GitHub.

    The first question that crosses my mind: is it possible to detect a connected sensor automatically or will this modification require a separate branch/fork?

    I think, the (sensor triggered) response could be quite easy: pause the print, switch off the nozzle heater and allow changing of filament - basically: trigger the existing pause function.

    To answer your second question:

    Primarily i use Code:Blocks because i'm lazy and the project file is included in the master branch... :)

    The script package.h is used to compile the *.hex files for releases. It can be started out of GitBash and (basically) uses the existing Makefile.

    I'm always open minded for simpler solutions - so please keep me updated if you find one... :)

  9. Any ideas how to go ahead?

     

    A few suggestions:

     

    • Feeder: use as less contact pressure as possible, too much pressure will deform flexible filaments to an oval and it will get stuck in the bowden fairly often...(the |Robert|-Feeder can really be a great help with this)

    • Slicer: switch retractions off (and accept the stringing... :)) - your chances are much better this way - my experience: retractions are nearly impossible to use with flexible filaments on a bowden feeder

    • Speed: start with slow speeds (20mm/s or even slower) - you can raise it later if it works

    • Flow: just increase the flow rate until the lines touch each other, 130% is fairly common for flexible materials (alternatively: reduce the configured filament diameter to 2.70 or even lower)

    • Temperature: AFAIK recommended for InnoFlex is 210-250 °C - i would start with a medium value (i don't know the specs - it was just a quick google search, so maybe i'm wrong...)

    • a drop of oil is the "golden doorknob" - i usually use this dust filter and humidify the sponge with a few drops of sewing machine oil

     

    P.S.: diesen Thread hier hast Du gefunden?

  10. Und die andern Leute wie sieht das bei euch aus???

     

    Besser... :)

    Mein Stundenzähler ist zwar "kaputt" (Fachbegriff :)), aber bei mir hält die Platte seit mindestens 300 Druckstunden durch (eher mehr...).

    Sie hat zwar inzwischen ein paar "Kampfspuren", das liegt aber eher daran, das (z.B.) XT und FlexiFil manchmal zu gut darauf halten... (auch nach dem Abkühlen).

    Wichtig scheint zu sein, dass die Druckplatte wirklich fettfrei ist - das gilt aber genauso für die Glasplatte (oder alles andere, was es so gibt).

    Ich wische die Platte vor jedem Druck mit Bioethanol ab. Das hatte ich "grad zur Hand", als ich mit der Druckerei anfing und bis jetzt scheint es zumindest nicht zu schaden. Also bin ich dabei geblieben.

    Bevor ich jemals wieder zur Glasplatte zurückkehre, werde ich wahrscheinlich erstmal die Rückseite der Aluplatte benutzen...

    ...oder aus Bequemlichkeit diesen hier eine Chance geben: http://www.buildtak.eu

    ...bisher ist aber dafür noch kein Bedarf.

  11. @tinkergnome: Would it be possible to write the settings to disk (sd card) and only use it if needed ?

     

    Sure..., but although it is not recommended... one can use the printer without sd card...

    So - you would need a "fallback scenario" anyway...

    I assume it is not ever a good idea to use dynamic memory allocation in a firmware, but probably it has some benefits for this purpose... (just a rough idea atm...)

  12. Is there a guide how to setup the firmware development environment ? I did notice that you need Arduino IDE 1.0X and not the newer versions, but how can you setup the simulation environment ? Is there a step by step guide ?

     

    Regarding to the Marlin simulator you can follow the links in this post.

    You need SDL 1.2 and the easiest way would be to use the project file for Code::Blocks (it's included in the folder "MarlinSimulator").

    Good luck!

  13. The M605 and M606 are for saving current settings of the UM2 such as print temperature for later recall. It's the only way TweakAtZ can recall values on an UM2 set on the machine itself. If you don't need it, remove it. Others may want to use it. The number of setting sets that can be stored could be reduced from 10 to a smaller number if RAM is really an issue.

     

    Many thanks for the explanation, so i must admit that removing this part was not my best idea...

    The buffer for 10 settings allocates permanently 700 Bytes of RAM. This are nearly 10 percent of the available 8kB only for this single thing - and irrespective of the use of these commands.

    This topic needs definitly a close look again - i put it on my todo list...

    Greetings to Zurich!

  14. Can you read the values in the firmware from the Analog connector ?

     

    Basically Marlin should be able to use any pin the Arduino offers (read and write). You have to define the correct pin number in "pin.h" and make use of the corresponding functions from the Arduino libs ("analogread" resp. "digitalread").

    If i remember correctly there exists at least one unused "safety connector" with an open (unconnected) cable near the printhead....?

    A very nice solution would be a combination of a cheap sensor like this and these (introduced) resurrection system.

    Looking at your skills - i am confident... :)

  15. Will it be possible to use this feature to continue prints, which ran out of filament.

     

    The problem in this scenario is usually the heated printbed. As long as it stays hot and the printed object doesn't come loose it is often possible to recover the print.One can simply measure the current height and restart from there... The latter is the solution that i'm trying to achieve with this new firmware function.

    But once the object no longer sticks to the build platform the print is ruined anyway...

     

    Would it be possible to attach a switch to the mainboard to "remember" where the filament ran out ?

     

    I'm just a software guy and have nearly no clue about electronics, but it seems that some enthusiasts are working on filament sensors. I cannot find the example that i have in mind, but there are others here and here (for example).

    These solutions are perhaps a bit exaggerated for this purpose, but it looks promising.

  16. I beleive that version 15.04 also has the feature to turn on the rear fan on the latest UM2 when the temp reaches 40°c (on my extended it does that with standard firmware 15.04) that's basically why i'm asking :)

    [...]

     

    I see... :)

    I heard that rumor too, but there are no commits on GitHub related to this (as far as i can see...). Perhaps it's completely handled by the hardware, or it's a secret firmware change that is not published (yet).

    I have no clue...

  17. [...]

    Great to see you back!

    I have had something weird with your firmware not sure why, the version is 15.02 i think. When i do a print everything is fine, when i do another print without switching off, it seems that the icons are lost somehow

    I'll have to try that with the latest version, did you do the 15.04 version yet?

     

    First: i never went away - it was just not so easy to (re)activate my forum account and i considered the matter not soooo urgent... :)

    Regarding the firmware:

    I noticed some weird things with this version too (at least sometimes...). I guess it was some kind of stack overflow (or something similar).

    I removed the support for the (custom) gcode commands M605 and M606 since version 15.03. These stuff allocated a huge amount of the rare RAM and i never saw that anyone used it.

    It seems that those issues went away with the recent version, you should give it a try.

    i know ...someday i should ask @dim3nsioneer about the intention of these commands... ;)

    Obviously there will be no "tinker" version 15.04 - the last changes of the default firmware were only "cosmetic" AFAIK (basically the displayed support address for fatal errors has changed and the material preset "UPET" was renamed to "CPE"). I believe - we don't need to rush it...,

    but the story continues

    I'm trying to implement a "recover an aborted print from a selectable height" - function (*) at the moment. This will be release 15.06 (or probably 15.07...;))

    (*) = working title ;)

  18. Phew! I am back!  :)

    Thanks to Arjan who has redirected me to Sander...

    Thanks to Sander who has passed my issues with the forum account to the developers...

    ...and thanks to the nameless developer who was able to reset my password manually...  :)

     

    Can someone explain me what is the difference between the normal and the big bang version of this firmware ?

     

    I somehow like the term "big bang"...

    Seriously:

    The custom firmware is compiled with PID control for the printbed temperature.

    Because of this reported issue i released the "b" version with the standard "bang-bang" control method (in addition).

    The difference is described in the links.

    If i find some spare time it will become a selectable option someday... (it's on the todo list)

    Greetings from the tinkercave!

    • Like 2
  19. ...

    I've not looked into it but i think that other info is available in UltiGcode (it's possible to copy a profile from gcode).

    Do you think it's possible to display more info?

    ...

     

    Let's see...

    The informations for (estimated) printing time and material length are read from the comments at the top of the gcode file (only for UltiGCode-flavor AFAIK).

    Displaying the time in another format (incl. minutes) should be easy.

    The Cura profile is a different challenge...

    It is embedded at the end of the gcode in an encoded format. Due to the very limited RAM available at the Arduino board - decoding and parsing of the Cura profile would be... ... ... not so easy...

    Perhaps a better approach:

    Someone... could write a Cura plugin that includes the major profile informations as comments at the top of the file.

    The same might work for progress informations. Basically the end-position of the E-axis is needed. I guess, the firmware could calculate the progress and the estimated printing time more accurate just by comparing the current E-axis position to the last position...

    Mmmhhh - or a more general approach...

    how long would it take to parse the whole file at the beginning (without printing) and track the max. positions...? I think this is worth a test...

     

  20. ...

    Is this an incompatibility with the new Arduino IDE and I need to downgrade to 1.0.6 or did I miss a setting somewhere?

    ...

     

    Hi Reiner,

    you got it...

    I think there goes something wrong during a macro expansion with the new compiler version,

    i did not make to investigate this further until now.

    Arduino 1.0.6 works fine, and AFAIK daid still uses 1.0.3

     

  21. ...

    Although printing was fine, I could not go to page 2 in the menu (just no response when clicking) and I had no remaining print time info... Any idea what could have gone wrong?

    ...

     

    To be honest... no quick idea at the moment... :?:

    Do you get the same behavior with the simulator? (easier for debugging).

    If you want: you can send me the modified sources (for comparison purposes) and i can take a look at it this evening.

    I send you a PM.

     

×
×
  • Create New...