tinkergnome

I also have no clue about blender and 3ds, but i want to second this approach: I'm pretty sure that you have a hidden (inner) wall in your model (marked on your screenshot) and you have to redesign it in some way without such a wall... (you have to remove all internal faces)

Yep. Downloading the whole github repository is not neccessary. Browse to the release section and take the compiled *.hex file from there. ...small addition: i think you need one of the preceding Cura versions (15.04 should work fine). To be honest: i have not tried it, but i'm afraid that "Install custom firmware" is not implemented (yet?) for the 15.06.xx versions.

Phew... this duplicity is a bit frightening... The doubled "end-of-print-retraction" (after pause and subsequent aborting) was a bug. It will be fixed with the next release of the stock firmware (AFAIK) - and is already fixed for the recent tinker version. And it seems that i share some parts of the workflow with spiruline... Actually - a preheat menu is already on my todo list for the next release. It will be accessable directly from the main menu - most probably along with "change-" and "move material". I think - first i should take a look at the UMO firmware how the preheating of the nozzle is handled... The main limitation is the lack of spare time... I'm moving to a new appartment at the moment - the printer is already sleeping in his cardboard box - so it will take a few days... (or weeks...) But at least there's hope...

I only know the modifications for Version 14.09 and 14.12 - but probably you're able to modify the "sceneView.py" by yourself. Just search for "_autoUpdate" in the provided files or call the dude for assistance...

Regarding the mobile use... I'm afraid that the answer is predictable, but i have to ask anyway..: When will it be available for TapaTalk?

Hi jeex, Assuming that you don't want to copy the json files manually back and forth all the time... there's no way. I hope that's only a temporary state and it comes back soon. It's a really huge drawback of the recent version that the print settings are not saved along with the gcode. That's the main reason why this version is pretty useless (yet?) - at least for my workflow... Hopefully there will be a "project managing" plugin some day - but i have no clue if someone is working on it.... @nallath?

Yep. That's what the M82 and M83 commands are good for... I think this plugin uses G90 and G91 too (not sure) And while you're at it, keep in mind: While using UltiGCode the E-coordinates are interpreted as mm^3 (volumetric). A relative value of +400 should give you an extrusion of approx. 62mm - if not there was something wrong with the relative/absolute mode... And yes - the extrusion of very large distances is prevented by the firmware - the limit is 1000mm per command (approx. 6379mm^3 for 2.85mm filament). If you try a larger (relative) move of the E-axis - it's just ignored. A connected printrun/pronterface is not a bad idea for debugging btw. You get a warning on the serial console in those cases.

or add an M302 gcode command somewhere to allow cold extrusions

Für alle älteren Cura-Versionen bis (einschließlich) 15.04 kannst Du in den Maschinen-Settings einfach den GCode-Flavor auf "RepRap (Marlin/Sprinter)" umstellen. Die neue Cura-Version 15.06.xx ist in dieser Hinsicht (noch?) etwas verkrüppelt - genaugenommen nicht nur in dieser Hinsicht... :angry: Damit hast Du nur die Möglichkeit, als Druckerprofil den "Ultimaker Original+" auszuwählen, oder im Installations-Verzeichnis die Datei ".../resources/settings/ultimaker2.json" von Hand zu ändern. Relevant sind (mindestens) die Einstellungen "machine_gcode_flavor", "machine_start_gcode" und "machine_end_gcode" - aber das wäre dann schon sehr "experimentell"... Am Ultimaker2 bekommst Du in beiden Fällen nach Auswahl der Druckdatei die "Classic Warning" - und das bedeutet, das die Material-Einstellungen vom Drucker nicht benutzt werden. Also genau das, was Du erreichen willst.

It seems to me that supporting STEP files is on the wishlist for a long time. Perhaps it's worth to reopen this old discussion about Stepfiles and G02/G03 arc gcodes?

As you mentioned - it isn't... TEMP_SENSOR_2 is not relevant (not used at all for the UM2 AFAIK). The counting begins at 0 (TEMP_SENSOR_0 for the first etc.) Only two different defines are needed to compile the stock firmware either for one or for two extruders. And this should work similarly for the tinker version: Single Extruder: TEMP_SENSOR_1=0EXTRUDERS=1 Dual Extruder: TEMP_SENSOR_1=20EXTRUDERS=2 I've just added the (compiled) dual version to the recent tinker release. I'm afraid that you will have to make some other changes - but this depends on the type of your hardware modifications. Just be aware that you probably have to struggle with the compilation anyway (sooner or later)...

This is only almost correct... Temp3 should be connected to the temperature sensor of the heated bed. Temp2 is intended for the PT100 sensor of a second nozzle. The nozzle heater is connected to the screw connector marked with "heater1" - "heater2" is apparently intended for the second heater (consider the provided voltage (24V AFAIK). If you're in doubt - take a look at the board description or at the assembly manual

@SandervG: don't you know the latest photos showing the 3dsolex workshop? Can you imagine a machine that outperforms the precision of this one:

Looks like it's printed without support... which slicer (and which printer) do you use? BTW: could you add your printer (and location) in your user profile please? An advice is: print it with support... If you model this piece by yourself, you can even make your own support structure. A narrow frame below the edges of the cuts (to support the perimeters) is sufficient. Leave a gap of about 0.15mm at the top of the support structure. The rest of the surface can be bridged then very nicely. Do you know the designing guide of the famous |Robert|?

i mixed in the quote from the other thread: Sorry, but it highly depends on what you put together... (i think you don't explained this yet?) There is a dual extruder version of the UM2 firmware from stock - included in all recent versions of Cura. You know your hardware setup - you have to decide if it is sufficient for you. Edit: Perhaps you could also explain how this topic is related to Simplify3D? Any firmware runs on its own, there should be no dependency on a specific slicer....?

Well, "unchecked" is the default for all recent Cura versions since 2015 (15.01 and newer), "checked" was the default for all older versions. But it exists as an (switchable) option only in 15.04 (AFAIK). As a reference: The differences were first discussed in this thread.

Hi @Kermit65, if i were you..., i would... (in ascending order) add a small chamfer to the edges where the small parts are attached to the base printing with zero infill but a larger shell width instead (try 1.2mm - 3 shells) increase the layer height to (at least) 0.1 and increase the bottom/top thickness to (at least) 1.0mm - i even think there will be no drawbacks if you use a combination of 0.12 / 1.2 consider to split the parts in a different way (to make it printable without support) Edit: ...and don't use the default speed settings - the default infill speed (80 mm/s) is way too fast IMHO. Set all speeds to the same value (or the advanced speed settings all to zero) - and choose 40mm/s as the basic print speed.

@peetersm: while you're at it... The suspicious behavior is switchable in Cura 15.04 - so you can make a direct comparison if you like...

You can take a look at the assembly manual (page 65) - but as gr5 said: be aware that the recent changes (from 2015) are probably not included yet. @gr5: you really should accept that there is a menu option for this since firmware V14.10 "Maintenance -> Advanced -> Set fan speed"

To prevent cold extrusions the minimum extrusion temperature is 170°C by default. That's a common Marlin feature and not special to Ultimaker. The default of 170°C is set after power on and after leaving the "Move material" menu, but can be changed by executing a M302 gcode command. In case of an Ultimaker2 one could even prepare an autostart gcode-file on the sdcard with this command. As a conclusion: no need to fiddle with the firmware, just do it - we're curious!

Wait a minute... if i get you right, this is just a test for your tool changer. You want to achieve a tool change on every layer (independent of any toolchange command). And you're looking for an easy way to integrate a retraction (without the need to struggle with the current E-position), right? My suggestions are: you definitly don't want to zero the e-position between layers... - remove the "G92 E0" lines - that's the main source of your problem if possible - remove the "G1 E..." commands too and use firmware retractions instead "G10" resp. "G11" or switch on (temporary) relative positioning ("G91 G1 E-2.5 G90" resp. "G91 G1 E2.5 G90") This should do the trick. ;LAYER G10 G0 F9000 X100.000 Y180.000 G0 F9000 Y192.7 G0 F9000 X64.000 G0 F3000 X16.000 G0 F5000 Y100.000 G0 F5000 X100.000 Y100.000 G0 F5000 X16.000 G0 F9000 Y180.000 G0 F3000 Y192.700 G0 F3000 X64.000 G0 F9000 X100 G11 ;FINISH ;LAYER G91 G1 E-2.5 G90 G0 F9000 X100.000 Y180.000 G0 F9000 Y192.7 G0 F9000 X64.000 G0 F3000 X16.000 G0 F5000 Y100.000 G0 F5000 X100.000 Y100.000 G0 F5000 X16.000 G0 F9000 Y180.000 G0 F3000 Y192.700 G0 F3000 X64.000 G0 F9000 X100 G91 G1 F200 E2.5 G90 ;FINISH

I'm not sure, but AFAIK it should be able to run with Mac OS X Here are some links: Marlin Simulation... on your desktop?!? (For developers) Missing note about how to compile and run the simulator SDL 1.2

Hi Erik, there is hope... You could make a test with the latest version of the tinker firmware and/or discuss and endorse this pull request. Greetings to Stockholm from the tinker cave...

i think so... usually the order of the array elements is X, Y, Z, E

Yep. Welcome to the club... The issue is reported on Github, you can join the discussion, if you like.