jumpmobile

I wouldn't mind the bending: iron (especially steel) is harder than aluminium and therefore should withstand the forces when ripping of a printed object more easily. Maybe this rigidity will cause trouble when the nozzle crashes into the surface of an iron/steel-sheet since it is much harder than brass also. But a crash is exactly what one wants to avoid with the sensor-system. Iron also has a heat conductance that is two thirds lower than that of aluminium. Maybe this will inflict perfomance of a heatbed, but then again: people are using heatbeds in combination with glass wich has two hundreth heat-conduction and that also works. Here is a video of Z-leveling with hall-probe: So the idea is not that far from makeable...

But isn't this resolution eliminated by the manual-leveling procedure? A M3-thread has a pitch of 0.5, so one tenth of a turn will give you 50 microns height difference. Edit: On magnets-positioning: You just place a magnet behind the Hall-sensor (so, both on the print head) and the just measure the flux as a ferromagnetic heatbed is approaching. Described here: http://www.hall-sensor.biz/ quote: "Mounting a Hall sensor and a magnet in one device gives new possibilities. Non-magnetic ferromagnetic objects can be detected, and distances measured. Several metals have ferromagnetic properties and can be used, including some Stainless Steel versions. To be able to use strong magnets for a large range, and to be able to see very small changes, the Hall sensors must also show a good sensitivity for small changes in a strong magnetic field."

Oops. Why does the accuracy have to be so high?

What about using this sensor for automated bed leveling? http://www.thingiverse.com/thing:89146'>http://www.thingiverse.com/thing:89146'>http://www.thingiverse.com/thing:89146'>http://www.thingiverse.com/thing:89146 approach (http://www.thingiverse.com/thing:89146) is using the Ultimaker endstop switch mounted to the printhead. It seems to work but the hall sensor would do an even better job since there is no need for it to touch the build platform for measuring its distance to the nozzle. Therefore it doesn't need to be retracted during the print process. This chip allows for distance measuring up to 4 mm which i think would be enough distance to be out of the way during printing or if the nozzle even crashes into something. For the magnetic field one could use neodymium-magnets and an iron-plate instead of an acrylic or heated aluminium bed.

Hello Ulti-Makers! After more than one year 'read only' it was time for me to join the UM-Forum. My name is Fabian and I am a student at the university of Karlsruhe. Technically i don't have my own printer. The one I use is property of the "Arbeitskreis Kultur & Kommunikation" which is a small Institute on our Campus led by students. My job is to maintain the printer, give basic workshops for CAD-Designing (openSCAD) and generally make the printer accessible to everyone who is interested in 3D-printing. I must say that after one and a half year with that machine I have neither ran out of things to print nor to improve on the UM. I installed something like a "closed build-environment" -which is pretty close to the one on the UM2-, a hotend from E3D, various belt-tensioners, heatbed, new fanducts, fine-tuned stepperdrivers etc. etc. I really enjoy working on the machine and improving it and this forum helped me with getting new ideas and support on problems. Thanks to everyone. You guys are special! Jumpmobile

Jep Just look at the term-tab in the printing-window.

I have the same problem. Haven't found anything on the interwebs so i am pretty much stuck. Sicyons workaround sounds okay, but this isn't how i wanted to use the Printer. If it stops prints like out ouf the blue then it is not a good host for printing. On the other hand: I am sharing my printer regularly with newbies who will get confused pretty quickly if I start using one Software for printing and the other one for slicing and an SD-card for printing via Ulticontroller and so on. Also I like Cura very much and would be really glad if this could get fixed soon.

Soooo? When do we get to know? Really, my prints are not even close to that...

Hi What's up with the PID debug output? The box is there, but i cant choose it.

Hey This is the the friend of Jumpmobile writing. His version of Cura is now comunication with the printer. Firmwareupdates and First run wizard are working fine. Here is what I did: About firmware upgrades: On Linux (not tested on other platforms...) only the Thread that created the UI can interact with it. It's therfore not possible to update it in a seperate thread. My solution (i'm not experienced in python - unfortunatly it breaks the firmware upgrade dialog) was: in firmwareInstall.py - replace threading.Thread(target=self.OnRun).start() with everything in the OnRun definition --> Upgrade dialog is broken but update works About connecting with autodetecting baudrates: It seems like the printer is crashing if you try to communicate with the wrong baudrade (Seems to be a firmware bug). Simple solution: add time.sleep(5) in line 377 of machineCom.py --> Cura waits for 5 seconds after each baudrate, the printer restarts in that time and the connection works.

I have shown my problem to a friend of mine who is into computer science. He managed to stop it from crashing, when trying to update the firmware, but the connection problems still exist. I don't have time yet, but I will write what he did in the next post.

When I try to install the custon firmware I made Cura immediately vanishes. I ran it again in a console and got this error: python: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0. [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. python: ../../src/xcb_io.c:274: poll_for_event: Zusicherung »!xcb_xlib_threads_sequence_lost« nicht erfüllt. Aborted (core dumped) I have no idea what that means (but it is kind of neat that the program actually apologizes for aborting :-)

Hi I have been reading the UM-Forum for a while and you guys give great support! Until today there was no reason for me to post anything because most of my problems were solved by either you or the google.groups-ppl. (and most of you are active in both) so first of all thank you! So here is the first problem i haven't found a solution for. I have a Linux system (ubuntu 13.10) and recently updated to Cura 13.10. I am running my UM over an Ulticontroller. On the machine itself there is a Marlin-Firmware running that has been updated a few months ago (but not by me. I share my printer with some other people). Today i wanted to connect Cura to the printer and it now doesn't connect. That is propably because the firmware update was the original Marlin directly from the github which is set to 250000 baudrate, which is a known problem on Linux. My Question: How do I install a new firmware without using Cura? Is there a way to do this with an SD-card and ulticontroller or must i use Pronterface? Greetings Jumpmobile