Jump to content


Team Ultimaker
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by CarloK

  1. 1) In the current firmware (v5.5) we don't check the checksum on reading. GR5's method now works and later the correct CRC is written. Checking the CRC on reading is a long standing wish to implement since on some printers the long cable to the printhead creates bad readings. Starting a print with corrupted configuration data can lead to all kind of print failures. So yes, for now GR5's method works but might fail with a future firmware. 2) The nozzle diameter as numeric value isn't ignored. It's currently used in generating the XY-printing pattern and more uses might follow. 3) The counters are not touched by my code, they are at another memory address range. And I'm not going to explain in this forum how to reset those counters. 😎 4) You describe the XY-calibration settings correctly. This wasn't something I was referring to. 5) The fancy header in the gcode is required for the newer printer firmware versions to accept the file. As noted, the attached files were created for the UM3 series of printers since the original topic starter was using an UM3 Extended. For the S5 printers change the line: ;TARGET_MACHINE.NAME:Ultimaker 3 to ;TARGET_MACHINE.NAME:Ultimaker S5 @gr5 you correctly indicate the attached files will not work for 3dsolex print cores. I don't know the physical properties of those cores. So people using a 3dsolex core should use your procedures.
  2. @jphahn63 This forum section is about discussing the software (firmware) inside the Ultimaker printers. I don't completely understand your request, but to me it looks like a Cura request which then should be posted in the Cura section of this forum.
  3. Thanks for reporting the 5.3.4 update being marked as 'new' even after installation. This was a problem on our web server and has been fixed now. About the log message for a testing version not being found: Ultimaker uses test releases for people to test new versions that fix problems or add new features. These test releases have not gone through an extensive test procedure and hence are not considered good enough to be released as 'stable'. Since the S3 is a new printer model we never before released a test version and so this message pops up in the log file. To avoid confusion about these log messages I just uploaded the identical v5.4.3 to testing as well. The testing and stable versions are identical so it makes no difference which one you install.
  4. The only suggestion I wanted to make is that you go for the cheapest as both types will work. As GR5 says, the old one delivers a bit more power but we as Ultimaker are not allowed to sell it anymore with new printers. The newer type is a bit more environmental friendly and will save a few cents in electricity.
  5. T1 and T2 are BC817 NPN transistors. T3 is a BC807 PNP transistor So glad Ultimaker provided the schematics so people will study them .... 🙄 https://github.com/Ultimaker/Ultimaker2/blob/master/1091_Main_board_v2.1.1_(x1)/Main Board V2.1.1.pdf T3 indirectly switches on the 24V for the motors and the bed. So with a wrong type of transistor here it explains the wrong behavior in your printer.
  6. During the printing of the XY-calibration pattern you can adjust the flow and temperature like with any other print, but our goal is that for all Ultimaker approved materials this should be working out of the box. The 0.25 nozzle is not as well tested as the 0.4 nozzle and I will test again to see if I can find some grinding related problems.
  7. Did you perhaps install firmware for another printer? You say you have the UM2 and installing firmware for a UM2+ could show this behavior. Which Cura version are you using? We are now at Cura 4.3, but I remember about a year ago there was a bug in Cura where firmware versions for the UM2 and UM2+ were mixed up. Instructions for re-installing the firmware on a failing UM2 printer The newer versions of Cura are being 'nice' to your printer and that's why they fail in programming. In order to start the programming process, Cura has to reboot the printer. That's what older versions of Cura did when you connected the USB cable. Disadvantage was that when you were printing and you started Cura, then your multi-day print would reboot as well.... Oops. So, now Cura is nice to the ongoing print process but as a consequence fails to program a printer that's stuck. Your workaround is to use another program for programming the printer. One option is this old version of Cura: https://software.ultimaker.com/cura/Ultimaker_Cura-15.04.06.exe There are other programs as well, but I haven't done this since long so are not aware of the current situation. Look for programs that can program an Arduino AtMega 2560 board The UM2 firmware is a *.hex file and is included in the Cura program directory. For the UM2+ a release candidate for the next official version can be downloaded here: https://github.com/Ultimaker/UM2.1-Firmware/blob/UM2.1_JarJar/releases/beta/MarlinUltimaker2plus_20181007.hex (right click on link, and then 'save link as').
  8. I just stumbled upon this thread and thanks for reporting. I can confirm this fixed in firmware 5.2.13 (not released yet) and 5.3 (S3 only).
  9. I had a long look into this problem, but it is a difficult one to tackle since I can't reproduce it myself. My feeling is that the problem is caused by a sequence of actions involving the combination of manual leveling and Active Leveling. In the V5.0 release for the S5 we completely overhauled the Active Leveling software. Since the S5 build plate is larger than for the UM3 the undulations became too big to be solved with a simple 3-point leveling, that's why we introduced the grid based probing. The probing algorithm itself was also rewritten to be more accurate and faster. The v5.2 release integrated the UM3 and S5 to be one software package again which for the UM3 has a lot of changes under the hood that you won't see but will be beneficial like: - A year of software development, including lots of bug fixes. - A new Linux version - A new file system on the internal Flash memory for improved long term stability - The overhauled Active Leveling - A much improved version of Cura Connect, including Cloud connection - etc But.... for the users in this thread the v5.2 firmware breaks Active Leveling on the right print core. And I can't reproduce it which annoys me a lot after all the time I spent looking for the cause. The problem seems to be caused by switching between manual and Active Leveling. Could one (or more) of you please sent me the log files from your printer when it fails? Sent the files to me by private email (hover your mouse on my name avatar picture, a pop-up will show with email option). Add a short description of what you did and what you saw happen.
  10. When my trick didn't fix the problem then I assume the power supply is damaged and you best replace it. There are several compatible power supplies: Mean Well GS220A24-R7B is the older model Mean Well GST220A24-R7B is the current model which complies to the latest regulations regarding efficiency and EMC radiation but has a slightly stricter output capacity (the load variation range is more limited). Both models will do the job, except that companies are not allowed to sell the older model anymore for new products. You as a consumer can buy the cheapest one you can find. As reference, here in Europe the new model is sold for €63 excl. VAT.
  11. The XY calibration adapts for the different core diameters by adjusting the amount of material extruded and adjusts the brim pattern too. @rebekah_harper When you say there are problems, can you elaborate? Looking at the code it seems to always print at 0.3mm which for a 0.25 nozzle better would be lowered to 0.2mm.
  12. I had a look at these instructions and they are incomplete / wrong ! There are the following problems: - Only the print core names are changed. Other parameters that should be there are ignored which create problems in, for example, XY calibration where a misformed pattern will be printed. - The checksums are not updated. When a new firmware will check this for errors, then the printcores will be rejected. For an UM3 you can re-program the print cores by following the procedure below: - Disable Active Leveling (not required, but saves 5 minutes). - place the core to be programmed in the slot on the left. - print one of the files below. - Remove the print core. When you insert it again the new configuration will be read. aa04_program.gcode bb04_program.gcode
  13. I just found your other thread where you report print core problems. My conclusion is that there is a problem in reading the configuration data from your AA 0.4 print core. You can re-program your print core by: - Disable Active Leveling (not required, but saves 5 minutes). - place the core to be programmed in the slot on the left. - print one of the files below. - Remove the print core. When you insert it again the new configuration will be read. Note that on this forum there are alternative methods for programming the print cores, but these have the following problems: - Only the print core names are changed. Other parameters that should be there are ignored which create problems in XY calibration like you posted above. - The checksums are not updated. When a new firmware will check this for errors, then the printcores will be rejected. - bb04_program.gcodeaa04_program.gcode aa025_program.gcode
  14. Changing the steps / mm can be done without firmware modifications, but then you have to correct it with every print job. You can do this in the start code section in your Cura's printer definition: G92 E<steps/mm> Disadvantage is that this gcode now only works on your modified printer. The UM2+ / UM3 feeder wheels do wear down. When tested with composite material, just printing 1 roll of filament was enough to cause extensive wear on the feeder wheel. That's why the abrasive resistant CC-printcore is not supported on the UM3. The S5 feeder wheel was hardened extra. Perhaps you can get a replacement feeder wheel?
  15. A printer rebooting during the build plate heating up is almost certain a power supply problem. During the first phase of heating up, till about 50C, the power supply is stretched to its limits. Since everything was working smoothly before and now not anymore, what did you change with respect to the power supply block? Did you perhaps switch the power supply block with that from another printer? Did the ambient temperature in the room change? Perhaps the power supply block gets warm because it is now in the sun or next to an active heater? When nothing was changed and none of the above questions applies, then perhaps you have a power supply block that's at the lower end of the specifications. Contact your reseller if warranty applies. There is also a software workaround when you are brave enough to change a configuration file on the printer... - Enable developer mode from the menu - Open an SSH connection to the printer - log in as root / ultimaker - type: vi /usr/share/griffin/griffin/machines/um3.json - Scroll down to line 102 - Change the maximum power supply wattage from 221 to 200 (first press the 'insert' key to be able to insert new text). - exit the editor by typing after each other the 4 keys: 'ESC : w q' - exit the SSH connection by typing: exit - reboot the printer
  16. I have an idea about where the problem comes from. Do you people have set the Active Leveling frequency to 'never'? Setting it to 'never' means that firmware 5.x will use the manual leveling settings. But when you insert an unknown print core I noticed some people use the Active Leveling to measure this print core. My hunch is that there is a problem in this combination of Active Leveling and Manual Leveling where both methods use slightly different data. Until we fix this the workaround would be to either: - re-level with Manual Leveling or - Always use Active Leveling (don't set the frequency to 'never').
  17. No, there is no release date planned yet. The camera API problem is fixed but not considered large enough to validate a new release. The workaround is to use the hard coded camera paths like: http://x.x.x.x:8080/?action=stream and for a picture http://x.x.x.x:8080/?action=snapshot If you ever add more camera's to the the printer, then the second camera will be at port 8081, the 3rd at port 8082, etc. There are no plans to change these paths, so hard coding them in your application shouldn't be a reason to wait for a new firmware release.
  18. @David Stewart Thanks for the feedback and I'm glad to have been able to help someone.
  19. @Bob38, the WiFi module is not reporting in. When broken, in about 50% of the cases, it then reports with a specific warning in the dmesg.log file. That message is missing here but te WiFi module isn't reported on USB so I suspect the module is broken. I suggest to contact your reseller / distributor. Even when warranty is out, they might come with a good proposal. Otherwise, a replacement WiFi module is sold by Ultimaker for $100 and can be exchanged relatively easily. In my opinion $100 for the \WiFi is way too much, but it is an older model that is no longer for sale. Alternative suppliers can be found when you search the internet for 'WUBA-171GN', I found it for $42 in the US and €38 in the UK. Another option is to connect a wireless router to the LAN connection, or try using a power-line modem on the LAN connection.
  20. Let's keep this thread related to 1 topic: Active bed leveling on the UM3. Wifi related problems should go in another thread. @Patronus reported a bed leveling problem where the procedure seems to run fine, but then when printing both nozzles are pressed too hard into the build plate. I'm looking into this using the provided log files. @erind and @David Stewart, you both are reporting a problem where the bed leveling procedure fails with an error message. The print cores are pushed into the bed during active leveling. This shouldn't happen, the print cores should be just touching the build plate. For printers where this happens, first perform the following checks: 1) The screws for manual leveling the build plate should have some moving distance. When tightened all the way, the bed leveling will fail. Some procedures describe a bed height of 14mm but as a guide line the aluminum build plate should be level with the aluminum front plate (not sure how to describe this better). 2) If bed leveling still fails after correcting step 1), then run the 'bed level sensor test' that was added to the diagnostic menu.
  21. The file sorting wasn't implemented because of the limited RAM size that Tinkergnome refers to. Now with hindsight there is a trick we can apply to re-use some memory space that's not used at the time of file selection, or at least have the most recent file appear on top as in the UM3. But ... development of the UM2 software by Ultimaker has stopped, perhaps a bug fix release will follow but no new features. Since a week I have my private UM2. With the UM2 software being open source I'll have a look into this some time later.
  22. Are you printing from USB? The line nr. errors often are caused by a usb stick with memory errors.
  23. I'm now waiting almost a month for the requested log files.... 😪 Without the log files I can't convince our management to put the probem high on the actions list. Please people. help me helping you! This works two ways. You correctly complain about problems, but when I want to help you, you should give me some pointers. Please mail me the log files using the message function of this forum (hover over my name next to this post and from the menu that pops up select the 'message' option). Create the log files by performing an Active Leveling function and then from the Maintenance menu choose the option 'Dump logs to USB'. Ensure to include all generated files, including the probe report files.
  24. @Patronus I'm sorry to hear about your problems. Similar problems have been reported by a few people but we need more info to investigate this. A month ago I asked two people to email me the log files from an Active Leveling procedure but I'm still waiting their reply. Could you please perform an Active Leveling procedure and mail me the log files? You can create the log files by performing an Active Leveling procedure and then use the maintenance menu option for 'Dump log files to USB'. Send these files to me using the mailing function of this forum (hover over my name next to this post and in the pop-up is a 'message' symbol). Please include all dumped files, that's including the probe reports. Without the log files I can't convince our management to put the probem high on the actions list.
  25. Sorry to hear the modification didn't work. Instead of posting another change that might not work either, you'll have to wait for me to return home later this week. Perhaps I can figure out another change but want to test it out on my machine first.
  • Create New...

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!