Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. Ein Sunon Lüfter war wohl auch zuvor verbaut oder? Ist das nicht vielleicht ein üblicher 80x80 lüfter? Von denen findet man einige bei ebay, aber bei 75x75 sieht es sogar über ebay hinaus sehr mager aus. Denke nicht, dass es sich Ultimaker in den frühen Jahren leisten konnte einen Lüfter nach eigenem Maß anfertigen zu lassen 😉
  3. Some days things just work out. So if anyone is actually interested, I moved the Z control over to the E2 port. Managed to work out what I did so many years back and did the same for this port. Brief summary Used a Marlin version of the firmware Swapped pins in pins.h //Original /* #define Z_STEP_PIN35 #define Z_DIR_PIN 36 #define Z_STOP_PIN 29 #define Z_ENABLE_PIN 34 */ //New #define Z_STEP_PIN 49 #define Z_DIR_PIN 47 #define Z_STOP_PIN 29 #define Z_ENABLE_PIN 48 //Original /* #define E1_STEP_PIN 49 #define E1_DIR_PIN 47 #define E1_ENABLE_PIN 48 */ //New #define E1_STEP_PIN 35 #define E1_DIR_PIN 36 #define E1_ENABLE_PIN 34 Compiled and it failed because of an old bug / typo where "fpos_t" should have been "filepos_t" Just did a search and replace for all, compile, find more in other dependent files, repeat until it compiled OK. Uploaded, worked!
  4. Gave up a while back but I really want to get this up and running again. My PC running Windows 10 can see the board, it shows up as Arduino Mega 2560 under com ports Cura just doesn't see it at all. Now rocking version 4.0.0 Can I upgrade the firmware via the Arduino IDE? Every search I have tried brings me back to the "use Cura" instructions.
  5. taking a break from movies and trying some cuteness. but it seems as either my z screw is dirty or my printer is unable to close a semi sphere smoothly, hence the random line. its 1.2 wall so it should be plenty, its on both models, ill try a few tests in the meantime! miaow, pusheen kitty inspired.
  6. It seems really difficult to peform a XY calibration. Actually I tried to, but I had a big bug on the BB print. The extruder always trying to push in and push out the filament (is it a normal behavior?). Then I have a really bad result on the glass, which is not enough relevant to perform the calibration. I guess... Can you help me to understand?
  7. Hallo, Hast noch das UM2 Board? Das ist das einzige woran ich mich erinnern kann ist dies: Weis nicht was da der aktuelle stand ist Gruß
  8. Thank you very much, I've ordered springs thanks to you! I also changed the Printcore, buy a new one and installed it. It was strange because I found something in the new printecore, like a really really thin plastic wire, and I did not success to remove it. So I let it in and charge the Printcore with. It seems to work well. So now, The error from the auto leveling has disappeared. I will wait for the spring and then I will manually set the bed. Unfortunately, it seems that the XY calibration is really hard to perform. Actually, the BB Printcore print like nothing really well (see in the attached picture). The extruder for this nozzle is always trying to push in push out. Is it a normal behavior? Can you help me to understand? Thanks very much for your support
  9. Found the bug. Made the changes on the script with FreeCAD 0.18, but some functions are not backwards compatible to 0.17. Made it working for both now.
  10. That did the trick. Thank you.
  11. Merci beaucoup pour les conseils. En changeant de Printcore l'erreur est partie !
  12. There is no option to store this data in another location.
  13. Deutsch? In deutscher Abteil ist deutsch schreiben erlaubt bzw. erwünscht😉 Hier aktuell ein gleiches Thread: Gruß
  14. Kurze Aufklärung: Es wird nicht in der Bewegung gedruckt sonder es wird kein retract ausgeführt und dadurch läuft etwas Material raus. Eine einfache Möglichkeit dies zu verhindern wäre das Combing umzuschalten (z.B. auf "Innerhalb der Füllung"). Ein Problem könnte sein, da es auf den ganzen Teil angewendet wird, entstehen mehr/viele Retracts die andere Probleme mit sich bringen können. Gruß Gerd
  15. I would go with this. I would let the print and plate thoroughly cool before submerging in water.
  16. Hallo, mein Radiallüfter an meinem UMO hat einen Lagerschaden und scheppert ganz ordentlich. Ich finde aber ums verrecken keinen Ersatz. Die Dimensionen des Lüfters sind pi mal Daumen ca. 75 x 75 mm und ca 24mm Höhe. Am besten wäre vielleicht ein Sunon? Weiß jemand, wo ich Ersatz für meinen bekomme? Ich hatte einen gefunden, aber der ist 30mm hoch und passt somit nicht unten rein. Das ist der Lüfter, der die Bauteile am Board des UMO kühlt. Danke für eure Tips. LG Sebastian
  17. Hallo gibt es beim UM2 eine Option für Filamentsensor nachzurüsten? Danke für eure Hilfe und Info Gruß
  18. Have you tried the same test cube with the printers original software? If this print works, I would suggest comparing the G-code of both slicers. Maybe you can trace back from where wrong parameters come from. 😉
  19. Hello, did you get any news regarding that matter? i'm also interested
  20. I have to work across several PCs and would like to keep my Cura 4.0 installation on a USB key or network drive. Is there a way to do a portable installation that puts all of the bits in the target location? I tried installing it to the removable drive path, but it looks like it still puts a bunch of stuff in C:\Users\<username>\AppData\Roaming\cura. Thanks!
  21. Ta commande et juste. je reçois la même sortie. j'ai résolue mon problème. Ce qui ce passer s'est que Cura utilise la sorti 2 donc en utilisant la sortie standard il ni avait rien. Avec ce code ça fonction presque comme je veux, du moin sa retourne les résultat dans un fichier. from os import popen, system CheminSortie = r'"C:\Users\Ivain\Desktop\testeretour console\Sortie.gcode"' CheminFichier = r'"C:\Users\Ivain\Desktop\testeretour console\Box.stl"' Profile = r'"D:\Program Files\Ultimaker Cura 4.0\resources\definitions\tam.def.json"' system(f"CuraEngine slice -v -j {Profile} -o {CheminSortie} -l {CheminFichier} 2> SortieTeste.txt") le fait de remplacer > par 2> lui indique qu'il doit utiliser cette sortie je te joint le fichier retourner. donc si tu passe cette commande a NodeJs tu auras un fichier contenant la sortie. Reste plus qua trouver un moyen de faire la même chose mais dans une variable pour la récupérer dans no langage respectifs. CuraEngine slice -v -j <tonprofile> -o <Fichierdesortie> -l <lestl> 2> SortieTeste.txt PS: le fichier box et un cube de 20 mm Teste3.3mf
  22. I did at that time of test, also got a x/y shift months after. In the end like I say on the other post I just moved out to duet3d and been enjoying the quality of life of a proper 32bit cpu with trinamic steppers. Happy printer, happy life
  23. Here is a sample piece for this problem, a plate with a cylinder hole which diameter is small (2 -3 mm) if you look at the preview slicing for the first layer below is the picture there is a problem if the speed of the red circle outer wall is too high. The picture below give an idea of what would happen, the blue line . The plastic , which in this place, is alone and not glued to the brim as the red square, will be dragged by the movement of the nozzle. So the hole is very badly initiated, One solution is to drastically lower down ( to 10mm/s for instance) the printing speed for the outer wall and inner wall during this kind of movement. You have to do that only on the first layer, on the other layers, the printed filament sticks a lot better the plastic on the level below, than on the hot bed This is what this plugIn does; reducing the printing speed on outer and inner walls on the first layer if the nozzle changes direction over very short distances (such as those made to make a circle) The plugIn is realised with 2 files, to achieve 2 main goals 1) allow a debbugging process using stand alone Python with IDLE interpreter (I shall show it in a seperate post later) 2) create a script superclass to get all the mechanic to have the scripts follow the same process in the GCode file For this you have 2 files, myScripts for the super script class and the script file here BottomTinyHolesSpeed1.py Below a picture of the begining of the GCode file after post process You can see that 2 scripts were executed (BLHWS1 which is this one and RPT1 which is a new version of the plug in I gave in another post) I tried to launch twice the 2 plug ins and as they are designed to be launched only once the super script class manage it and write it in the GCode Also, in the LAYER 0, which is the one on the hot bed, the script modify the printing speed in the walls of the tiny hole inside the red line the lower speed and in the blue line the older one scripts.zip
  24. En utilisant ça : CuraEngine.exe slice -v -j "D:\Program Files\Ultimaker Cura 4.0\resources\definitions\ultimaker2_plus.def.json" -l "D:\Program Files\Ultimaker Cura 4.0\TEST\anthony.STL" -o "D:\Program Files\Ultimaker Cura 4.0\TEST\test.gcode" Et en ayant créé un dossier "TEST" contenant un STL bidon. J'ai le GCODE en PJ Est-ce que tu peux essayer de reproduire exactement ces étapes ? test.gcode
  25. Merci pour l'info. Regarde par hasard s'il est possible d'activer un logger qui soit verbeux et de récupérer ce qu'il dit. Il y a probablement une erreur (fichier de conf, variables d'environnement, etc) qui est échappée et que tu ne vois pas. Sinon je n'ai pas de finalité avec Python, mais bien avec l'invite de commande (je travaille en NodeJs). Et il se trouve que cette commande sera la même dans les deux cas 🙂. C'est pour gérer ma ferme
  26. Eine statische IP-Adresse alleine verhindert nicht die Firmware-Updates (zur Cloud kann ich nichts sagen). Ich vermute, das je nach Netzwerk-Route noch irgendwo eine Firewall oder ein Proxy-Server im Weg steht und der Drucker dadurch nicht "nach Hause telefonieren" kann. Die IT-Abteilung sollte aber in der Lage sein, herauszubekommen, wo es hängen bleibt.
  1. Load more activity
  • 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!