All Activity

does anyone of you know what pitch the z screw on an s5 has?

Habe schon kleinere Positionen angefahren aber das geht auch nicht. Ja X0 entspricht G28 Er fährt ja beim beenden auf die Anschlagposition und dann auf X0 Hier mal ein G Code vom Filamentwechsel wo er auch auf -20 fährt. Filamentwechsel Zeile 3304 AK_Schutz AHK v2.gcode

It's an old thread so sorry to reply now, but since I was directed here from google when searching about the slow boot of UM2+C, it's worth correcting the statement above. The UM2+C does NOT run linux, but just a version of Marlin. If you check the schematics of the mainboard used, the microcontroller used is an ATMEGA2560, which is WAY WAY too slow to run any operating system. It runs just Marlin, and it's also not particularly good at it, if you consider that Marlin above a certain speed starts sending steps to the motors not uniformly, but in groups of two or four. Check "marlin double quad stepping", which starts happening at 10 kHz, which means for the UM2 series 125 mm/s. So we don't know why the UM2+C is so slow, but it's not linux.

Look at the prepare tab: your model is way broken: The blue and pink dot pattern generally means faces are either missing or have their normals flipped. If you're running Windows, Microsoft's "3D Builder" app (I think it comes with Windows 10 but you need to install it manually in Windows 11) is actually great at fixing models (as well as doing things like simple cuts and a bunch of other things). And because I just made some brownies and I'm in a good mood... here you go: texas1_fixed.3mf

I think I will try printing on the 200 mm square PET tape but maybe I should start at a cooler than the previously used temperatures and heat my way up only if there are adhesion issues. I do not expect any adhesion issues: According to videos I've seen, there are no insurmountable issues with ABS adhesion on PET tape under certain conditions, eg., fan blowing air over the print, etc. I plan to try the PETG on the PET tape, as well. The strings could be an advantage. It's been argued that adhesion is too great, consequently because maybe the compression or the temperature is too high on the first layer. But the print needs to come off very easily after cooling (or whenever) without damaging it. And it needs to remain as flat as possible, like a film. It could be described as a net. [There are a lot of variables there!] I am really excited about this project! I am hoping I can get close to these parameters, and I also expect to have more of my mind blown by the technology! 😄

Thanks! I just filled out the contact form.

CF Nylons can only be printed with CC cores on the S series. You need to make sure you have one installed or it wont let you print them

We'll be able to help you can provide a lot more information than that. What would be best is if you can share your Cura project file (.3mf, in Cura, go to File > Save Project) but as well help to know things like: is there a specific error you're receiving, can you slice the same model in a different kind of filament, can you slice other models in carbon nylon? I'm not an expert with UltiMaker printers so I'm afraid I can't offer too much specific advice myself, other than making sure you have the correct print core selected. You might also find help in the extensive knowledge base or by contacting UltiMaker support on their support site.

Hi @Andrew_F, To answer this simple, -there is an open (rupture) in your temperature wiring! When this happen, the the temperature go sky high.. "How high, depend of the internal circuit after the "PT100" input!" So, there is a broken wire, some place between your nozzle and the feeder! This is where the wiring bundle always move/bending, -just look here. If this was a permanent failure, it would fail all the time, but this is intermittent -so a now and then connection.. The wires always on a move, -suffer the most, -go figure. Thanks Torgeir

Unfortunately, UltiMaker does not provide direct support via the Community. Please contact UltiMaker Support directly for help with this issue. here: https://support.ultimaker.com/s/contactsupport

I'm leaning towards the printer. I keep the tail ends of filament rolls around for things like this. On the left is your original project, printer, and profile. I adjusted my home offsets to account for the Origin at Center of your delta printer. On the right is my setting profile. Both were printed on my Ender 3 Pro (cuz that's what I've got.) I know my camera isn't great, but I don't see the step on either of them even under a magnifying glass. I'm starting to think that maybe the long travel moves between the legs are having an effect. Maybe there is some shaking or something going on. It might be worth your while to do a preventative maintenance check on the mechanicals. Things can come loose, get out of adjustment, whatever. It may help, and it can't hurt. I have a regimen I go through once a month and I always find something that needs re-adjusting. In regards to settings, you might try changing the infill from gyroid to grid (not as much motion) and consider dropping the Acceleration from 5000 to 1000. I know your machine can handle the 5000 - but maybe not today.

Why Ultimaker Cura is not slicing my model when I use Carbon Nylon filament on my S5 3D printer.

There is a maker, "scottdee" who has decided to put my name and my business name as a "villian" on most of his thing descriptions. How can I get that off of there? I have no idea why he does it. I have never printed anything of his and never will. I'm not even interested in the items where he puts my name in the description. (Luke B. and BestBattlePlan) Is there some policy to prevent him from sharing my personal information on a public website? It's really creepy. Thanks.

Yes, more or less. There can be a slight difference between the legs. One can be "more shifted" than the other two vice versa. Not with consistency though.

I look at too many of these things and I got two projects mixed up. OK. It's a good name brand printer. I'm not familiar with the mechanicals on a delta though. Do all the legs show that layer shift? Are they all moving away from the seat centerline like the one in the image?

Please don't go after community members. They are only offering help. It sounds like you feel you have found bugs in UltiMaker Cura, this needs to be reported via github not via ranting at community members on the community forum. Report bugs here: https://github.com/Ultimaker/Cura/issues Additionally it appears your issue relates to remote desktop? that isn't even officially supported or recommended by UltiMaker. Details here: https://support.ultimaker.com/s/article/1667337917781

Ya know, I was trying to sneak that by. There may be some issues with the "Tiled Infill" plugin (at least on certain systems). Since they are both in the back end I thought I'd mention it.

It is a FL SUN Superracer

Well, first of all to *completely* clear things up Iron Python is *NOT* an interpreter, it uses the JIT compiler system common to all Visual Studio languages. Consequently, it is 10 to 100 times faster, and can access the entire dotNET ecosystem. In fact, Iron Python, C++, etc. (and yes even Visual BASIC) files can be mixed and matched in a Visual Studio project, because in the end it compiles them all to a common intermediate language that gets fed to the JIT compiler at run time. Second, how does the VMM react to insufficient physical or virtual (page file) memory? By throwing a system error, not "can't access a handle in a DLL". OK, so windows VMM isn't as effective as the YUKS (Linux and the rest of the band) platforms. So, it will either throw a system error, e.g. "out of memory", or crash. The "can't access a handle in a dll is clearly an applications level error", not a system error. I'm not a codee, I'm an electrical engineer and my experience with the windows VMM is from pivoting multi-gigabyte matrices in SPICE. I have generated many "out of memory" errors, particularly in WinXP as it can only have (nearly) 4GB of physical memory. This is doubly true when you allow Windows to manage virtual memory, as I do, because it will increase virtual memory as needed. Limited by available disk space, of course. And when it works correctly. The "can't access a handle in a DLL", message is not coming from the memory manager. The structure of the DLL is to have a table of calls mapping the called routine name to an offset in memory of the called routine. It is, essentially indirect. If the contents of the table contains an incorrect offset, you will get a page fault. The "can't access a handle in a DLL", is coming from the indirect lookup code, saying it can't find the requested routine in the lookup table, not that it couldn't find it in memory. Also, again, the Windows memory manager isn't as shiny as the YUKS one, so accessing forbidden memory, will generate a page fault, or send Windows into the weeds, not a courteous "I can't find that, please try again". Nevertheless, the missing handle exception returned by the Qt6Widget lookup should propagate back to the calling routine, allowing it to be captured and documented... Third, as I've already documented when Cura > 5.4.0 starts and crashes, it does not create either a version folder or either log file in %appdata%\Cura. If it did, I would have already appended it like a I did for 5.3.1. Any log file at all would help, as I have no idea where the problem is occurring, although it appears to be in the painfully slow interpreted loading of all the different printer profiles. As an aside, why aren't these loaded as needed, life is short enough, it takes forever, even on my I7 laptop? It is worth noting that after invocation the spinner comes up for a few seconds, then goes away, and it is 10 or 15 seconds before the error appears. So, this fault isn't occurring at init, yet *there are no log files generated* (or application version folder in %appdata%\Cura), this is what is baffling me. The missing handle error is coming from Qt6Widgets.dll, which for some reason is in two places in the application directory, instead of the GAC, where it belongs. Cura 5.3.1 uses version 6.2.4.0, Cura 5.7.0 uses version 6.6.0.0. I would of thought that this DLL contains the "controls" used in the UI, which doesn't come up until after the printer profiles are loaded? I'm wrong about Python, as you say, but without a log file of any kind, what choice do I have to troubleshoot but change things until I get a response? So, I repeat is there a command line switch to enable logging, 'cuz *nothing* is created for versions > 5.4.0, full stop. I could attach a debugger, but generally the messages to the debugger are generated in the same exception handler that logs them, so... Finally, I installed Cura 5.7.0 on the Z83, and before starting it copied the entire application (application and %appdata%\Cura folders) from my laptop, also running Win 10 Home 64b, and where it runs successfully, to the Z83. The results where exactly the same. So, there is either a difference between the WinPE version of Win10 Home 64b running on the Z83 and the mundane Win10 Home 64b running on my laptop, or something, external to the Cura installation is missing from the Z83. Perhaps I should dismount from Rocinante, but I very much doubt this is a memory problem, which wouldn't prevent logging until lights out. Also, Cura is installed for the *current* user, not all users. Consequently, if started by a remote desktop session, it will stop if the remote desktop session is lost even for a second. "All users" is a built in choice in the windows installer, and presented by default, and it should be up to the user to decide which to use. And if not, it should be "all users", allowing disconnect from the remote desktop without affecting Cura.

There really shouldn't be anything different just because there are islands. I'll think about it but off the top of my head, whether it could be something in the settings or a hardware trick that is in the the printer, I don't know what could cause that. If you printed cooler than the 230 you had, then the plastic will have reacted differently. PLA is by nature very brittle. If you make the seam location the mid point of your build plate then the seams on the legs should face inward. That's about the best you can do. Your build plate is 202 x 202 so make the X and Y of the seam location 101 and 101. Lets go back to the beginning here. What kind of printer is this? You've called it a Betaminion, but I don't see it come up in my search.

Hi glx, Thanks for the reply. did a hot and cold pull prior to posting. All clear. Also ‐ wierdly my printcore shows a max temp in the 200s Appreciate your input. posting on aphone thatis destroying formatting . will tidy up later

Agree to go to support, but the first step for me would be to wait for material to creep up feeder tube, if it's just creeping along and looks stalled. Or disengage the feed sprocket and manually feed it the last inch.

Oh, sure, go ahead, blame the innocent plugin 😉 I don't see how that plugin could cause CuraEngine to fail... It mostly just toggles the Cura preference to auto-slice. Pausing and unpausing effectively results in restarting the slice, which CuraEngine should be able to do just fine.

Unfortunately, UltiMaker does not provide direct support via the Community. Please contact UltiMaker Support directly for help with this issue. here: https://support.ultimaker.com/s/contactsupport

Here are some pictures of the result with your profile @GregValiantIMG_8970.pdfIMG_8972.pdfIMG_8971.pdf The islands are way more brittle now than they were withe the previous settings. Can I also adjust the seam in a nicer way? Can't seem to get it as straight as i did before.