CarloK

The latest UM2(+) firmware is included with Cura and had its last update with the Cura 3.3 release in April 2018. There is also a beta version which fixes some bugs but never made it to an official release: 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'). These are the changes compared to the v3.3 Cura 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 (or more) 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). - Returning from the preset menu did not set focus on the preset menu (1 off) - Several trivial beautifications.

I moved your question to the Cura section of this forum where it will get more attention. I know of some problems in older Cura versions, but the problem you mention here is new to me.

What kind of print core are you using? Is it an original Ultimaker print core? This type of problem in the XY calibration print most likely comes from using a print core with a bad configuration (there is a small programmable memory on the print core). See this thread for how to re-program the printcore. Note that there are different files for Ultimaker print cores and 3dsolex cores. Looking at it again, the 3dsolex 'solution' will not fix this specific error. Leave a note here when you have 3dsolex so I can look into it.

It's been more than 2 years since I worked on that bug fix. We intended to have this new firmware integrated with the Cura 3.3 release, but it might have been delayed till the 3.4 release. This shouldn't matter since everyone is now on Cura 4.8, right? The extra text at the end of the gcode is there for any printers running older firmware from before Cura v3.3, so even the older firmware versions will work correct. I don't see anything weird in the posted gcode. Also the fact that the print did succeed once is an indication the problem is not in the gcode file. Which Cura version are you using? You said you updated the firmware using Cura. Which Cura version was that? Are you printing from SD card? Could this be a newer type that the printer can't handle? Can you describe your system setup? Like, is there a usb cable between the printer and a computer? Or are you using an external host like octoprint?

The request to always show the MAC address has been noted. I can't promise if and when we are going to implement it, but it sounds like a reasonable request so I hope we can do it soon. The frame lights can be controlled from gcode with the command: M142 w[0-255] Note the lower case 'w' A value of 0 is off and 255 is completely on.

What is your Cura version?

You are not the first to be confused by the text on the screen. The exact text is: Here we want the user to use the multi-function button in front of the printer. This text is only shown for the rear position. We should've used a more clear wording here to differentiate between the multi-function wheel and the build plate screws. For the other two positions the text is: Here you are supposed to use the build plate screws. A few remarks on the procedure: - There is a flaw, when executing this procedure multiple times, the buildplate will be set higher and higher. Eventually the buildplate will reach its maximum on the thumb screws. Problem is that at this setting the Active Leveling will fail because of wrong spring tension in the bed. Before starting the leveling procedure you should ensure the build plate screws are not at either maximum (14mm would be the perfect distance, see the earlier mentioned link for a tool). - The 1mm in the first calibration round is just a guide line and not exact. I myself always start with the calibration card, and then the second round is just for verification.

This is weird, the printer can only start a pause action from two actions: 1) The user selecting the pause option in the menu 2) A pause command in gcode You are sure not to have pressed the menu pause function. Which leaves option 2. Which slicer program are you using? Did you perhaps activate a plugin like 'pause at height" in Cura When still withou clue, can you post the last 50 lines of your gcode file here?

This is on a UM3, isn't it? The second print core is printing too close to the build plate. There are a few things that can cause this and for now I see only two possible options: 1) Do a factory reset from the menu to clear all existing leveling data. It should work correct after this. Perhaps first note the XY offsets for your current print cores to avoid having to do the calibrations again. I always leave them at the default value as the results are good enough for me. or 2) Do not use the automatic leveling. On the smaller bed size from the UM3 this is a nice gimmic, but manual leveling will give you just as good printing results and is slightly faster. On a larger printer like the S5 the automatic leveling is required to get good adhesion.

No, you don't want to tighten your bed that far. The active leveling procedure is a tight balance between the tension of the bed springs and the sping inside the print core. The bed should be manually set at a height of 14mm, see the link in the post from @fbrc8-erin for a detailed description and procedure. The correct height setting in manual leveling is 0.15mm. With a difference of 1mm there will be massive under extrusion for the first layer and poor bed adhesion.

I still think you have Wi-Fi network connection problems. A thought came up: When you setup the S5 for WiFi connection, did you select the correct country settings? And the same for your WiFi router? These settings should be equal in both devices as the allowed frequencies differ for many countries. Selecting different settings in the two devices will result in instable network connections (and is illegal). To exclude wireless network problems, temporarily use an ethernet cable.

I'm not familiar with solutions like Octoprint, but those create a form of network conectivity. What are you missing from those solutions that you would expect from an Ultimaker solution to include?

There is a problem with the right print core, notice how this pattern isn't printed. I suspect the calibration data for the nozzle switching bay got lost or corrupted. Could you try the tests under menu: Maintenance / Diagnostics / Switching test When this shows problems, then calibrate the Switching Bay position under the menu: Maintenance / Calibration / Calibrate lift switch

I don't think the Two Trees Sapphire pro printer is in the list of printers support by Cura. Which printer model did you select when slicing in Cura? What diameter is your nozzle? Did you create this startup code? I can't find this in one of the existing printer models. It looks weird with 2 times the M82 code, you only need one. The M83 looks like an error and will mess up your extrusion (extruding way too much).

Contact your reseller. There is a procedure for restoring the firmware, but since it requires to remove the bottom cover there is a danger for touching high voltage components. Your reseller can help you and use the correct procedure to meet your countries regulations.

Like mentioned above, the Ultimaker printers only work on the 2.4GHz band. Trying to connect the printer to a 5GHz network will never succeed. Most likely your guest network is at 2.4GHz. Most routers that support 5GHz, also can be configured to grant access at 2.4GHz.

The returned length is in mm, so just over 52m in your example. Take the number with a grain of salt. The feature is in a prototype state and wasn't developed further since the flow sensor proved to work so well. The value is an indication but I would count with a 30% margin if you want to be sure. Here a link with info on material lengths for new spools: https://support.colorfabb.com/hc/en-150/articles/360002291617-What-is-the-length-of-filament-on-your-spools-

It is available in the web api of the printer but I don't think we show it in any remote tool like Cura or Digital Factory. Surf to the web page of your printer and you will find an online document about the printer's remote access functions. When you are on the same network as your printer you can enter the next line in your browser and it will show you a value which is the remaining length or -1 when unknown. Example: http://192.168.1.168/api/v1/printer/heads/0/extruders/0/active_material/length_remaining Replace the 192.168.1.168 by the ip address of your printer Change the '0' after extruders to a '1' for the second extruder.

@CWD_london Please provide more info. What is your system setup? - What printer model do you have? - What firmware version is on your printer? - What material are you printing with? - What nozzle size is mounted? - Is this a recent problem? Did it work correct before? What changed? - Did you change anything to the printer setup (moved or replaced the Ultimaker spool holder?) Many things can go wrong with the flow sensor and I both hate and love this feature. I still feel bad for the print I restarted multiple times because of a flow sensor error, only to discover later that the filament was entangled and the sensor was correct. What did you already check? Here a list of potential problems and solutions collected from this thread (semi random order): - Perhaps the sensor is correct... Verify your filament at the feeder position. If there is a large dent, then the feeder wheel did slide over the filament because of too large resistance. Perhaps your filament was entangled or the nozzle is clogged. - Printing too fast is another legit error cause. The extruder can't keep up with the requested extrusion rate (for this nozzle size). - The nozzle is clogged. Did you try cleaning with the cold-pull method? - Some 3rd party material spools are wound poorly with binding at the sides of the spool. - Material quality degradation. PVA is a known difficult material regarding moist sensitivity (it should break easily when bending, i.e. be rigid and break without bending. If it bends before breaking it's not sufficiently dry). - A too flexible material. Materials like TPU have limited support on the Ultimaker printers. Only up to TPU-90 is supported I think. - The feeder might be clogged with material shreddings. Open the feeder and clean it out. - The feeder wheel is slipping because of wrong tension. The indicator should be in the middle of the gauge. See also Robobartz post about the screw popping out: - The feeder wheel is worn out. The feeder wheels in the S3/S5 (not UM3) are treated to have improved wear resistance for abbrasive materials (like carbon fills but this has its limits. - Firmware 5.2.11 has problems on some networks (very busy analysing traffic). Disconnect the ethernet cable or wifi. - The Bowden tube might create extra friction, perhaps by loose filament particles. Test by decoupling the bowden tube from the print head and releasing the lever on the feeder. When the filament is difficult to pull you've found a problem. Try cleaning it out / replace a worn out tube. - Some people move the filament from the back of the printer to other locations. This affects the curvature/angle at which the filament enters the feeder causing the flow sensor to have less contact with the filament. Move external spools to the opposite side of the bowden tube which they feed into. - Some people use non-Ultimaker spool holders, for example for holding extra large 5kg spools. This is outside specifications. At least ensure these spool holders spin with low friction. When all fails, disable the sensor (on the main screen hit the gear icon, then go to the settings button. Flow sensor is second from top.)

You missed the first post in this thread. It has a link to a recovery image which I believe is still the 4.3.3 version. Here is the UM3 v4.3.3 recovery direct link: https://software.ultimaker.com/jedi/releases/UM3_recovery-4.3.3.20180529.img And the recovery for UM3 v5.2.16: https://software.ultimaker.com/releases/firmware/9511/stable/5.2.16.20200331/recovery-5.2.16.20200331.img These files work for both the standard UM3 and the UM3 Extended.

Opgelost in firmware v5.6

I'm currently working on another project, not on the S3/S5 so anything I mention here is from own experience. The bad part is, we are using old software. The good part is, we are using old software. Many bugs have been solved since the original release and I'd like to see many of our libraries updated to newer versions. The good part is that the software is working on thousands of printers with relative few problems and most of the problems are perhaps annoying, but at least known. @Whitespace what changed in your setup for these errors to start occuring? Is it a new printer or did you perform a software update? What firmware version are you running?

IT-departments never cease to surprise me... With a correct DHCP configuration you don't need static ip-addresses. Your DHCP server can be configured to always assign the same ip-address based on a once configured MAC address. Then, for the host name, DHCP has an option to change the hostname as well. So, with a well equipped IT-department they could handle it all themselves instead of you having to do crazy things (and we as well). Note that RFC-1035 says the length is limited to 63 characters. So why your IT-department comes with an 18-character limit is surprising. As a side effect of renaming: Cura won't be able to detect the printer anymore automatically, you will have to enter the ip-address instead. Changing the host name: - Ensure printer is in developer mode - Log in to the printer with SSH - type: vi /etc/rc.local - in line 4 you see a line starting with 'hostnamectl .... ' Mark this line as a comment by inserting a '#' as the first character - insert a new line 5: hostname my-fabulous-new-name - Save the file - reboot the printer with 'reboot' command - Log in again and - Check by giving the 'hostname' command without parameters. This change will have to be applied after every firmware update.

You have two problems that I think are unrelated: 1) After rebuilding your printer the printer shows an ER05 for the Z-axis being broken 2) Cura 4.5 can't upload firmware from a Windows 10 computer I want to focus on problem 1 first, since when we get that working you don't mind about problem 2 anymore. There is an article on this forum where people reported the same problem when the 5V fan connector was connected to the wrong pin header. In the middle of the board is a connector marked JP3 - 8/16 step, when you connect the fan here it causes the stepper motor to make smaller steps and missing the Z-switch. The right connector is 4cm to the right and marked J34 - 5V Fan. See this thread for more details and photo's:

Thanks for reporting, it is assigned internal ticket number EM-3499 All our translations are centralized in a widely used tool. Something went wrong and for many languages the hour symbol changed to an 'M'.