robinmdh
-
Posts
326 -
Joined
-
Last visited
-
Days Won
11
Content Type
Forums
Events
3D Prints
Posts posted by robinmdh
-
-
On 7/3/2020 at 12:09 PM, Erkan3D said:
Can I use this with S3?
The camera location and the API hasn't changed so I would imagine yes...
-
A shame that https://support.ultimaker.com/hc/en-us/articles/360012087619-Using-the-Ultimaker-APIs misses some of the API's on the printer.
Each of the API's has a swagger based description and generated documentation on the printer, we currently have 4 API's on the printer that I'm aware off:-
printer API - base URL http://<printer-ip>/api/v1/ - documentation in: http://<printer-ip>/docs/api/
More info on the authentication on this: Auth is only needed to set data and start print-jobs, etc.
Though if you only use the cluster API to queue/start print jobs then you will not need to do authentication.
The next ones have the base URL and documentation in the same place. - cluster API: http://<printer-ip>/cluster-api/v1/
-
material station API: http://<printer-ip>/material-station-api/v1/
This one is only available when you have a material station attached. -
fault API: http://<printer-ip>/fault-api/v1/
This shows any error/warning messages that may be blocking the screen of the printer.
the Cura questions I would trust @nallath on that.
-
1
-
1
-
printer API - base URL http://<printer-ip>/api/v1/ - documentation in: http://<printer-ip>/docs/api/
-
yes 😞
I'm still a little sad colors got left out when we build the S5, I would have much preferred colors to indicate printer-state or allowing the user to set a color for the printer.
-
1
-
-
I don't speak Spanish, but if you have flow sensor errors you can turn those off i the settings menu. (the cause can be your filament type or the slicer/profile you used or tweaked. (E.G: flexible materials can't be printed very fast with a bowden tube, so our profiles for example with TPU are printing a bit slower))
If you have errors during the height probe of the buildplate then I suggest you contact your reseller.
If it's something else, I can't help you with such a vague request.
-
1
-
-
there is also a mod for the S5 here:
-
hi @WeberUlti,
Sorry to hear that, the ER998 is a problem with the display code (it should be gone after a reboot), and are with the introduction of 5.6.8 using a tool called sentry to find issues like this that may happen more rarely on our printers.
I think the not being able to start a new print is a Ultimaker connect issue. please try a Ultimaker connect reset from the settings menu. -
@Roli4711 Thanks for the feedback!
On 6/7/2020 at 12:16 PM, Roli4711 said:I was one of the biggest critics of Ultimaker. However, the latest firmware seems to do a lot well.
1. The video feed has never crashed since Tuesday.
2. The change from the same material with strings that fall off has improved massively. Until now, no part fell off during a new print or during a change of material and then remained on the print. Before that, 4 out of 5 prints / changes were the case.3. No Errors by changing materials (start or change).
This means that the S5 Pro Bundle can now be used really well. Nevertheless, there are still a few points that need to be looked at again:
1. The connection via LAN sometimes crashes. After 10-20 seconds, however, it exists again.
2. CURA often has connection problems and the completion notification is no longer correct.3. Since I often print with the same filament one after the other, I should be able to tell the printer that it is not spending so much material at the beginning. There is no point in simply stripping off so much material when using the same color and material. It also makes the whole process much faster.
4. When changing the material during printing (filament runs out) the change takes a relatively long time and there may be small layer errors. It's the same as in point 3, whereby (almost) always the same material is used as before.Overall, the new version is a quantum leap.
- The LAN connectivity problem is not something I've seen, is this in cura or the ultimaker connect website or the cloud?
- completion notification?
- We have the plan of not unloading the material until it is necessary (for a new print, etc) or a certain time has passed so that you can quickly print again with the same materials (if it was up to me that'd be released already.... sigh... but it's also more complicated than you'd expect....).
- If we change between the same (color, type, brand) material we do purge less material, but it's more about re-establishing the meld, so that retractions actually work. usually that happens during the print and it simply assumes there are very few retractions in the first layer. It's also flushing out "degraded" material which you really notice when printing with PVA or Nylon. It's less than you might think when you see the string of plastic, about 2x the contents of the hotend. As a software engineer it's also not my call anymore (like it was in the early days of the UM3 ... fun/chaotic times those were .... ).
Again thanks for the feedback!
-
We are planning a bunch of changes to improve accuracy for everyone regardless of calibration but nothing like what you suggest, I'll pass it along to those working on this .
that said here are some tips:- The Z reliability would be hugely improved by running manual leveling to make sure your buildplate is in the same plane as the printhead. We do squash layers in the Z direction to slowly remove skew and buildplate non flatness compensation. Similar to what is shown here (though we now probe multiple points, etc):
- Further you could make sure your X and Y belts are tight!
- Did you print with the engineering profile in Cura? Because the feeds and speeds (changes in flow rate) and layer order also influence the dimensions of the print.
- There is also a slice error in the Z axis dependent on the layer height of the machine, is your object an exact multiple of this? Even in that case you will likely miss up to a whole layer height, sue to the slicing in layers process the print is prone to shrink a bit.
We do have calibration of the X and Y offset between the 2 nozzles but indeed nothing to calibrate the precision.
I would instinctively question if you print a cube that small would the error in that part be representative for the whole travel range of the machine? if you were to print a cube the size of the printer's volume it might be better but it would still miss things like backlash (and take ages).
-
3 hours ago, Sandi said:
a warning about corrupt profiles. ER999 disappeared.
And now I have some new info to look at, thanks!
That said we've made s serious error to squash ER999/ER998 and other reasons to get certain ER screens in the new version 5.6.x -
You might have more luck if you ask this in the Cura forum, or presumably you could check for firmware support from creality.
-
that's a shame the 5.2.11 can be found here: http://software.ultimaker.com/releases/firmware/stable/5.2.11.20190503/um-update-5.2.11.20190503.swu
Or for unbricking purposes from sd card http://software.ultimaker.com/releases/firmware/stable/5.2.11.20190503/recovery-5.2.11.20190503.img
We are working on the ER998 occurrences and will introduce software to better track these kinds of problems!
-
@Remote-Pizza I would simply advise you to turn off the prime blob, this is currently the default in Cura AFAIK.
Or in the case of a 3d party slicer modify the G280 line to read G280 S1 making sure that no G92 is following this.
G280 S1 sets the retracted length away from the nozzle as the negative e position so that G1 E0 meant the filament is at the tip of the nozzle (assuming no oozing or expansion). -
8 hours ago, Oornhed said:
Hi
I had an ER61 yesterday after 3 days print about that the material couldn’t be unloaded and the whole print was aborted. This was due to that the printer should change material but could not unload the material and then aborted the print and confirmed it as finished.
Could you please check I think the printer could wait for correcting actions and then continue to print otherwise it’s very dangerous to print big prints with automatic filament change?
We've been working on that all of last week, it's almost finished. We will now catch this earlier and allow the user to fix it, it will still PAUSE the print as in that case the break failed, so the printer can't detach the filament from the printhead and it will need the user to help before it can continue. It is likely this will be in the next firmware update, 5.6.x. The exact contents of that update is still TBD (To Be Determined) so I'm not 100% sure.
-
13 hours ago, redhatmatt said:
You say it's there again? Where? What's the menu path? I'm updated to the latest firmware I've been offered... 5.5.12-20200226-Ultibot
@RudydG's saying the problem of not being able to turn off the light is there again.
I'm not sure about the UM2 and I don't think it was a problem for the S5 but for the UM3 it certainly was added a bit later on.
The only thing I can suggest is tell your resellers as well, the more people request something the sooner it is made.
-
1
-
-
The coming update finishes the air-manager integration,, it's out NOW!
Here's a copy of the release notes:
# Release 5.5.12
Firmware 5.5.12 brings functional improvements and bug fixes:
- Users can manually reset the lifetime counter of the Air Manager filter after replacing it
- To prevent any damage, Ultimaker S5 stops when having communication issues with the Air Manager
- Improved reliability when unloading material to the Material Station (ER61)
- Ultimaker S5 guide the user through the process of Air Manager Filter Replacement
- Air Manager set up steps are now present in the Welcome wizardFor full release notes, visit **Ultimaker.com/firmware**
## How to update
Users running firmware 5.1.94 or newer can update directly to 5.5.12. When running an older version than 5.1.94, make sure to update to the stepping stone firmware 5.1.94 first.
For more information, go to **Ultimaker.com/firmware**
-
That issue is in the top 30~ish
So right now you have version 5.4.x and it looks like 5.5 will be released soon, we're talking about releasing 5.6 soon afterward. This has not been fixed yet so I'd expect it in 5.7 or later. If you have need of this I would suggest contacting your reseller support.
With regard to the material station we have been working on reducing unrecoverable errors, making the whole process faster, fixing bugs, etc.
-
1
-
1
-
-
@SandervG couldn't direct message the attachments to me could you? or maybe @Robot_Rob, could you send them to me?
I'm missing the zipped general purpose logs. and the spliced file :D
-
the TL;DR is sent me logs and a sample and I might be able to find out more.
long version:
Thinking out loud(in text) here...
The first thing that comes to mind is a corrupted/broken usb stick, that can cause similar problems, but you're printing via Ethernet...
Try to use the UFP format, if you're not already that will likely detect corruption since it's a zip container.On 2/6/2020 at 1:07 PM, Robot_Rob said:one in cura and one in blender -> both were printable without error.
I assume you don't mean you use Cura to design, so are you slicing in some other program or designing your input in some other program? I assume blender and some other CAD tool? you tried OBJ output as well... (from the other cad tool as well?)
On 2/6/2020 at 1:07 PM, Robot_Rob said:I am at the end of my wisdom now, are there any other factors that could influence the print in such a way?
Not really most of everything is passed trough and if Cura generated the output so it should be good for our printer. The only bit of code that can go wrong is this.
while True: line_count += 1 line = f.readline() if len(line) < 1: break # Skip empty lines. line = line.strip() # We can get bytes back, but from now on we work with strings, so convert them. if type(line) is bytes: line = line.decode("utf-8") if len(line) == 0: continue if line.startswith(";"): self._time_estimator.parseLine(line) self._parseMetaData(line) continue self._controller.queueGCode(line) if self._abort: self._controller.abortQueue() log.info("File handler aborted") break
This is the only part that exception you got can come from.
- The readline reads either plain text (in the case of a .gcode file) or reads from a zip stream (in case it reads from a .ufp file). the reading from the zip stream could fail, IO could fail for instance if a USB stick is removed during printing.
- The line has to be valid utf-8, this is where file corruption usually goes wrong.
- The timeEstimation and _parseMetaData could cause errors, they do assume the lines that start with:
- ;LAYER:
- ;LAYER_COUNT:
- ;TIME_ELAPSED:
That there is a integer following the first 2 and a float following the last, if that is not the case it will break there...
obviously the abort is not set so.
You could send me the logs of the print, you can dump the logs to usb via maintenance -> diagnostics -> dump logs to usb. Maybe include a sample failing ufp or gcode file, if printing from USB please also include the file read back from the usb stick.
-
On 1/29/2020 at 8:53 PM, DrCeeVee said:
Maybe that UART stream isn't as stable as it should be. Maybe something gets corrupted in there, and forces Marlin to misbehave.
There is error detection on this link, so marlin messing up because of bad communication is unlikely, anything that gets garbled is resent. Reading files from a corrupted USB stick is more in line with things I've seen but the UFP file format should prevent printing from a corrupt file.
Bad communication can happen, often because of environmental conditions or a bad cable, the worst this should cause is stops and slowdowns degrading print performance. If you believe this to be the problem and want to check this you could enable developer mode and log in as the ultimaker user and when you get the prompt run `exec self._controller.getDriver().getErrorCounts()` if you get huge numbers of read errors try turning off other machines in the printers surroundings.
-
On 2/1/2020 at 8:43 AM, Link said:
Also, when you are setting up a new material, you need to be able to change retraction settings on the printer, as it stands you have to reslice a whole new print to just see the affect of less retraction !, it takes so much longer to debug or set anything up with this UI, its painful !
That sounds like a fairly PRO feature IMHO, and it if is the distance of speed those moves are not distinguishable by the printer from other moves, so speed and amount of retract would be quite difficult to tweak.
A possible workaround is not that difficult though, if it is not the retraction amount or speed but the jerk and such then those settings are changed for travel moves and extrusion moves so if you remove those from your sliced file you could enable developer mode and log in as the ultimaker user, then use the sendgcode to try different values during the print.
On 2/1/2020 at 8:43 AM, Link said:with these printers being so expensive doing something like this (which may brick it) is not really a comfortable situation.
Yeah, that I get, we may be able to get stuff like this included, hidden under a switch in the settings menu in the future.
As to the disclaimer: I did test this twice and did not brick any printers but I don't want anyone to get mad if this goes wrong in any way. -
On 1/30/2020 at 3:12 PM, uncle_bob said:
Does the same port / same idea / same developer mode apply to the S5 and UM3? Simply put, can I shoot key / value combos at all of them and control the lights on the whole batch? That and and random RPi would get me to the desired goal of turning everything down (or up) at the same time.
yes, to idea, nope to the interface.
The telnet interface is an air-manager/material-station debugging tool only.
There are a few http API's though which do allow for led control of the printer AFAIK.
http://<your-printer-ip>/docs/api/#!/Printer/put_printer_led_brightness
You do need to use the authentication for that one. the attached file might help with authentication if you want to build that.
-
On 2/1/2020 at 8:36 AM, Link said:
when you say new purge behaviour what are you referring to ?
I mean the new purge material next to the buildplate behavior we build for the material station. This is currently not being used on a standalone S5/UM/S3 etc.
This is done to create a more consistent tip on the filament when it is being unloaded and makes sure you start with the material you intended to when loading. But it also helps because when you purge between the same material we at least get rid of the degraded material in the tip of the nozzle. This reduces clogs because without the added pressure of extruding close to the buildplate it is easier to get rid of hardened/carbonized plastic.
-
On 1/24/2020 at 8:27 AM, Link said:
Also, is there a way to stop a a disabled print core heating up during the bed level process, i have my second core disabled (but still in the print head) for single extrusion prints, but during the bed level process this core still has to heat up to over 200deg just to do a single probe at the start of the sequence, why does this need to happen and also if that core is disabled in cura when does it prob at all ?, i would rather that core wasn't heat cycles for no reason, that will def add to its potential lifespan.
I don't think heating up the nozzle has any significant impact to it's lifespan, our stress tests show very little wear/tear from continuously extruding (non abrasive materials, so no copper fill or carbon fill) material and being hot, though I don't think we've specifically done heat up/cool-down cycle testing. The material inside the nozzle will degrade by being heated up though and repeated heat ups without use can cause clogs, this seems very rare. The new purge behavior helps a lot in this regard.
-
2 hours ago, Smithy said:
I guess you have a typo, because 420000 > 65535 🙂
yeah, one 0 too many.
fixed it above.
Disable print removed confirmation message
in Firmware
Posted · Edited by robinmdh
nano is not installed on the printer, try:
Then hit insert to enter edit mode, make your changes, hit the ESCape key to enter command mode and type ":wq" to write the file and quit the editor.
you can also install nano via apt.