All Activity

j'ai essayé en mode admin également, et toujours le même problème, rien ne se passe.

Dear all, Any suggestions why my bed dose not want to touch the nozzle?

the noise isn't from the servos working, they run nice and quiet, it is when the system gives up and the full load on the servo is released. here is a video of the fault.

Instead of running Cura over remote desktop, consider installing OctoPrint on your Z83 to connect to the printer over USB and using Cura on your main PC for slicing. It's far lighter on system resources and has a web interface which lets you upload and control prints so remote desktop isn't an issue. You can also connect a webcam so you can watch the stream from anywhere to see if your print has failed in some way (it's saved me a fair amount of filament a couple of times). I run mine from a Raspberry Pi 3B so your mini PC is more than powerful enough.

This buzzing sound doesn't sound 100% right? I guess it's quite quiet on the S5 but on the UM3 it's noisier - I forget but that seems quite possible. I'm used to the S5 noise as I turned off active leveling on my UM3 but it's still on for my S5 so I guess I've forgotten what it sounds like. Still it would be nice if you posted a 10 second video showing leveling to youtube or something. I seem to remember the S5 has MUCH quieter servos.

The way it works: The build plate (the aluminum one under the glass) forms a capacitor with the plate in the print head. The capacitance increases as the plates get closer together. I'm pretty sure there is an oscillator where the frequency changes as the plates get closer together. Anyway when the nozzle touches the glass bed the plates should stop moving closer together. Should. When that happens the nozzle is assumed to have touched the glass. If instead the nozzle moves up as you described, it will NOT stop as the plates are still moving together! This should not happen. The bed is cantilevered and pushing down on it should move it down. It's critical that the amount of force needed to push down on the bed and move it downwards 0.1mm is less than the force needed to push the nozzle up into the print head. There is a spring inside the printcore that pushes hard on the nozzle. Harder than the cantilever force for the first 0.1mm or so. So it's possible the spring in the right printcore is too weak. You can measure it. It should take about 1kg of force to move the nozzle the first mm. More likely something is wrong with the sensor. More likely the bed *does* move down slightly before the printcore starts moving up.

I don't know how well it might fulfil your needs, but for regular Cura there is a plugin for Dremel printers available in the Marketplace (button at top right of Cura).

Je n'ai pas encore essayé la 5.7. En mode administrateur peut-être ?

Hi checking my S5 tonight but i think its LM8UU and LM10UU wich are easily available trough amazon . I will post my measure here .

Thank you for your answers. The mold setting did the trick. I need to tweak a tiny bit to get the print exactly as I like but on the whole that was the answer. PizzaTijd: The scull is not from that collection. I included it to see how it worked with the eyes and nose. It will not be usable in a print with the others (as I like those to have a hole straight through) but that is OK. It was only added to learn from.

From what i can tell these logs are all for Dremel slicer not UltiMaker Cura. You will need to contact Dremel for help with that. As for running UltiMaker Cura it might be possible Dremel is using the same system directories as UltiMaker Cura (this has been noted to happen with other brands) which corrupts the UltiMaker Cura files. UltiMaker and most of the community here isn't able to offer much advice for unofficial releases of UltiMaker Cura.

Sounds good. And please post the project file as I think most of your issue is with the settings.

I apologize for my stridency, it was not intended to "go after" anyone. But correcting me without understanding the platform in question was 'going after' me. Especially since the my original comment on Iron Python wasn't germane to the problem, it was intended to forestall any questions about my ineptitude in Python coding. Also, telling me that logging was on by default, when my original post said that no log files were created, meant that the original post wasn't read, completely, before commenting. And lastly, I have reported all these issues, and more, on Github. I document them, and a few days later they are closed, because "further or requested information wasn't received". This has happened several times, so I despair of that path for a remedy. I have never had to do anything special, other than install the app for "all users", to make it it work with remote desktop. So as far as I know neither explicit support nor recommendation is required from Cura to make it compatible with remote desktop. And in fact, it works fine with remote desktop, as long as the remote desktop link isn't disturbed *at all*. I do note that the installer doesn't ask if it should be installed for the current or all users, and it should, or default to all users. This is a default option presented by the Windows installer, YMMV for other installers. By the bye, I also reported that to Github, and it was "closed because further information wasn't provided". I also reported that USB connection to the printer isn't consistent. I was told USB connection wasn't supported, and the issue closed. In Windows, Device cataloging, departure and arrival via the GUID is robust, so the above response is opaque. For me remote desktop access is driven by a physical disability and access to the 3D printer. It really isn't an option for me not to use remote desktop, hence the reason I'm so eager to get it working on the Z83. Again.

The system is an Acer all in one desktop running intel i5 7th gen processor. I currently have the Dremel slicer is on the machine and runs without any issues. As I have acquired an Anycubic printer I needed to install Cura to slice files for it to use. I went with Cura for the obvious reason that the Dremel slicer uses the same engine and similar GUI to make life much easier. After installing 5.7 it does not start, not even a splash screen. I am hoping that it does not mean issues with the graphics driver of the system. Any help to get this sorted out would be greatly appreciated. stdout.logstderr.log

Je précise que tout mes pilotes sont à jours

Bonjour à toutes et tous, je rencontre un problème lors du lancement de cura version 5.7.0 sur Windows 10. L'installation se passe sans problème, mai au moment de lancer l'appli rien ne se passe. Même en essayant de lancer l'appli dans le répertoire installé dans programme sur mon disque C rien ne se passe. j'ai essayé de désinstallé et réinstaller cura.exe plusieurs fois mais le problème persiste. Quelqu'un aurait il une solution à ça? Merci bien.

Thanks for the help I did only install an OE fan, the sticker/part number was backup in case the delay continued. I have contacted Support. I will check the wire routing again, are there any images of official routing? bd

Bonjour, je rencontre un problème avec l'ultimaker S5. Fichier en JP. Le volume de mon objet est bien en dessous du volume mais je reçois comme problème "e fichier ne correspond pas au volume de la fabrication ". J'ai essayé: - une rotation avant de slicer, - j'enlevé le support, - Adhésion du plateau None, -Modifier le remplissage et la densité du remplissage, -L'objet est centré au point (0,0,0), -J'ai aussi essayé les paramètre recommandés il avait fonctionner avec la roue en JP, mais actuellement j'ai essayé de refaire la roue, ça ne marche pas. J'ai diminué les dimension (50x50x1,2) sur la roue Toujours le même problème. Besoin d'aide SVP J'ai le Cura 5.7 Firmaware 8.3.1 SupportPhone.stl

it sounds like you have interference despite having decent scores. Considering you have replaced the fan, i would make sure you have not accidentally smashed wires in the printhead. Smashed wires cause noise that messes with the sensor.. sometimes these need to be replaced sometimes simply correcting the routing of the wire will fix it. I understand UltiMaker was out of stock on fans for a few weeks. But if you self sourced the fan, please ensure its the same model. A similar fan for example from amazon will usually not work and generates interference with the sensor readings. Beyond that I would recommend following the final steps at the bottom and contacting support with your log files etc as they can often help find issues or errors. UltiMaker does not provide formal support via the community, but I wanted to make sure information here was accurate and not misleading. Improperly troubleshooting the issue can endup more costly than it needs to be.

How does the system know it has touched the nozzle? Is the capacitive sensor that sensitive? it appears it doesn't detect the touching and carries on up until the Z axis stalls. bd

It is an Ultimaker 3 I have 3 of those, all more or less the same problem, after trying around I will try to get a different brand of filament …. I spend a lot of time cleaning, and calibrating, and because all 3 printers give(almost) the same result with the same settings, I’m excluding a setting (for now) they all run on the same most recent stable firmware, and have the exact same file, leading to the exact same result, with the exact same material, ordered on the same time, so I’m now going to try to exclude the materials from the problem, to see if it stays consistent ….. thanks for the tips! I let you know when i switched it…

reading through the link you referenced (again 🙂 ), the only true thing I haven't fully tested is brand new cores although two of mine are very low hours. I have ordered a new AA and BB to test tomorrow I will update you on the results. bd

Looking at how dirty beadsters printhead is inside.. and the fact that the fan sticker is some reason on the outside of the printhead makes me think the fan is too dirty or even damaged.. If that fan is not running at spec it can cause issues with active leveling. A new fan is fitted ( the sticker is to remind me of the part number because I couldn't get an OE one, which eventually arrived), and I have tried that plugged in and un-plugged, the picture is of cores that have been flooded and cleared and worked perfectly after for a long time before this fault I have new cores and still have the same problem.