Jump to content

CarloK

Expert
  • Posts

    558
  • Joined

  • Last visited

  • Days Won

    22

Posts posted by CarloK

  1. I'm not sure what you mean with the 'Print-Jobs-Page', I guess you mean the page on de Cura Connect web page?

    Is it an UM3 or S5 printer? And what firmware revision?

     

    What you can try on a UM3 printer, go to menu System/Maintenance/Cura Connect reset.
    A similar menu item is there on the S5, but I'm not near such a machine now so you will have to find the menu yourself.

  2. I'm not aware of a bug in this regard, but the soon to be released v5.1 firmware has the whole underlying software for the manual and Active Levelling rewritten. I'd wait for this new software and see if levelling got more accurate.

     

    Our design goal is that Active Levelling becomes more accurate than what you can achieve by manual levelling. On the larger S5, but also UM3, we have noted that (ambient) temperature changes have an impact and automated levelling before every print is then the way to go.

  3. Did you look at the referred links? This isn't my expert field, but to my best understanding this file on the printer is what you are looking for.

    Too bad we are not (yet) allowed to open our github repositories, so that's why you won't find the info there. But, the printer itself is a good source of info (enable developer mode and using SSH the whole printer is open to you).

  4. See the reply above for the nice formatted Swagger page with API documentation.

    Or download the raw json file from: http://ipforyourprinter/docs/api/api_documentation.json

     

    We attempt to keep this document up to date, but it isn't tested a lot. When you find problems, then please report them so we can fix it.

  5. Yes, in the UM2 there is only 1 software package. So when you upload a new version from Cura it will overwrite your version.

     

    That said, the UM2(+) has been around for a while and new updates become rare since most known bugs have been fixed. The last update was about a year ago, I think, and only in the upcoming Cura 3.5 release the next update is planned. If you want to be at that latest revision you would have to create your own new modified version again.

  6. Yep, could very well be a material.txt related problem. Most likely the name of the new added material was 8 characters or longer and then weird things will happen. Solution is to reset to factory settings.

  7. This is positive as the motion controller is the last component being updated and it means all other parts have succeeded. Rebooting the machine shouldn't be a problem as it will check the motion controller to have the most recent version at every boot and update then when necessary.

  8. The original firmware has the maximum temperature limited at 260C and no easy way to work around that.

    The 260C limit is there because at high temperatures the PTFE coupler degrades, the higher the temperature, the faster the degrading. A decoupler damaged like this can still look ok, but will possibly have a smaller opening causing extra friction and under extrusion.

    Short story: no Ultimaker support for higher temperatures than 260C.

    Workarounds: Use one of the available alternative firmwares, or compile your own firmware version based on the open source Ultimaker code. The firmware and a description can be found here: https://github.com/Ultimaker/UM2.1-Firmware

    The change to be made to the source files is in the file configuration.h, line 166. There you change the maximum defined temperature value from 275C to whatever you want (note that the value defined here is 15C higher because of a safety margin).

    • Thanks 1
  9. 15 hours ago, Torgeir said:

    I'd wish there was a hidden stepper menu, that could be altered for the UM2 users, this hardware is -not very far apart..

    Could you elaborate a bit more, since now I think I understand you but am not sure. Do you mean the UM2 and UM2+ are very similar? And then, what settings would you like to see in that new stepper menu?

  10. @MGSR printing files of 500Mb in size shouldn't be a problem, we tested the printer with files op to 1.3Gb without problems. You are the first person to report this problem so it is not a common problem. Something in your environment or way or configuration causes this problem.

     

    Finding the cause is difficult when you can't share the gcode.

     

    My first suspect is a problem with your SD card. It is very easy for the file system to get corrupted, for example one time ejecting the card without first selecting the 'eject' function on your computer is enough to cause these problems. It might also be an SD card brand that's more susceptible to noise or other data corruptions.

     

    Could you re-try with a well known SD card brand? And first fresh format the card with then only this single file on the card?

  11. 4 minutes ago, Link said:

    Will the firmware update be made with the next release of Cura or can you/do you release firmware on its own ?

    My intention is to have the current state included with the upcoming Cura 3.5 beta release. Otherwise we'll post a download link here on the forum.

    • Thanks 1
  12. 5 hours ago, Link said:

    Also, could we get some more information on the screen whilst a print is running, like the tinker firmware. I am always nervous about installing 3rd party FW so an official UM version with nozzle temp, build plate temp etc would be great !  

     

    That's a new feature request and was rejected many times before since it conflicts with the Ultimaker strategy where the printer should be as easy as possible to use.

    My personal opinion is that Ultimaker should also cater to the tinkerers. One way to do that would be by adding a menu setting where you can enable an 'advanced menu' feature. This will be considerable effort and since the UM2 is an older product we won't get time to create that. Tinkergnome's software has proven itself to be a good alternative for the tweakers. It is almost impossible to brick your UM2. Try the alternative and you can always revert to the original firmware.

  13. 5 hours ago, Link said:

    At GitHub there is for the UM2+ only 1 reported issue:

    - A problem with filament grinding after material change.

     

    has this one been fixed as it’s not listed in the list of fixes in the next release ?

    The specific situation as reported in that issue has been solved by the 3 already mentioned fixes to filament position at the end of a print. However, I haven't closed the ticket yet since I found another problem: when you pause a print and then abort, the filament is retracted too far. 

     

    This problem is giving me headaches... I've looked at it for a whole day and then had to work on other projects again. It still has my attention but I don't get a lot of time to support the UM2. Right now I'm thinking about creating a release with all above fixes so you people at least get several improvements. And, ... it is open source. Everybody can look into the program and contribute improvements...

  14. 26 minutes ago, Nicolinux said:

    I can't remember correctly how this bug "worked" but there was something about the print head freezing in place at the end of a print. It was about parsing .gcode files and the fix was to add enough random characters to not trigger the bug. Does it ring a bell?

    I guess you mean the bug reported here. That bug created a blob at the end of a print and only happened with Cura v3.2.

    This wasn't mentioned in my list of fixes but is there as well and was fixed in Cura 3.3 too.

     

    There is also another fix for the quickstop function where the position of the e-axis was set wrong. This is a 3rd fix to the filament position at the end of a print. Submitted by Tinkergnome.

  15. @KiwiMrDee Thanks for your report. This is a known problem and has partially been fixed by the two above mentioned retraction fixes. The only known problem situation is where you first pause and then abort a print.

     

    We will investigate this further, but I have limited time to look into the UM2 problems. The Cura 3.4 beta release is nearing, so perhaps we release the current list of improvements and move further improvements to a future release.

  16. Our graphic designers are not convinced this feature is important. It's the usual fight between tweakers who want to see lots of details and the majority of users who want to have a simple to use machine.

     

    To convince our User Experience responsible guys we need more info. The layer number by itself is just dumb technological data. Can you elaborate more onto why you want to see the layer number? You are now asking for a technical solution, but we need to understand the underlying problem so we can implement the best solution.

     

    For example, you say you want to view a certain feature to be printed. But why is that important? what would you do when that fails? How bad is it when you arrive 5 minutes later and see how it was printed? Perhaps we can pause the printer before this critical part is printed and ask you to press continue when you are present so you can watch this being printed (this feature is already available in Cura as the 'pause at height' plugin). Or, just thinking along, would it be better to have your UM3 phone app to signal you that a certain layer is reached and you can watch progress on you phone screen? Or what about a time-lapsed video? There are all kind of options, but without understanding why you need the layer info we can't help you think about a solution. 

     

    Showing the layer number feels like a half-baked solution that perhaps was the best reachable solution in older printer models but right now we have lots more options. I do understand you have a problem, its just that we don't fully understand what it is.

  17. 4 weeks have passed and no replies.... Everybody is happy with the UM2(+) as it is?

     

    Here are a few things that will be in the oncoming release:

    Copied stepper module fixes from UM3 / Open source Marlin project:

    These fixes solve the problem where during fast movements you sometimes heard a loud tick sound like some mechanical hiccup was occurring.

    - Fix: the multiply routine could have an overflow, solved by adding a 24x32-bit routine
    - Fix: ensure the stepper interrupt triggers immediately again when it takes too long.

     

    Improve material import:

    - Fix: a material name length of 8 would crash the printer. Now consistently allow a length of 8 characters everywhere.

    - Fix: illegal values for the material retraction-length and retraction-speed are now set to default values.

    - Change: Improve error handling for very large positive or negative numbers.

     

    Other changes:

    - New: added Tough PLA (TPLA) material profile.

    - Fix: retract at end of print. Contributed by TinkerGnome.

    - Fix: another bug with retraction at end of print. If we were already retracted (G10), then we were retracting too much.

    - Fix: M117 was missing a character when printing via USB. Cherry-picked from UMO repository. Contributed by AmedeeBulle

    - Change: Changing material during a print is made 15 to 30 seconds faster by removing an unneeded filament heat-up (the filament is already hot).

    - Change: several menu's where the only option was to 'Click for return' now have the focus set to this button. This removes the need to first rotate the button and results in faster user experience.
     

    PLEASE REPORT PROBLEMS!!!!

    In the forums I see people complaining about no new firmware releases coming out, but when no problems are reported then we can't fix them.

    Report your problem at github or post it here, then I'll add it to github.

  18. In about a month we expect to release firmware v5.2, a major release for the UM3 which integrates the S5. In this release over 150 issues in Cura Connect only were addressed, many feature improvements, but also bug fixes. When I checked the list there are several fixes related to (old) print jobs. Since we didn't experience the above mentioned problem in the system tests it seems likely the problem as described here is fixed.

×
×
  • Create New...