Jump to content
Ultimaker Community of 3D Printing Experts
  • Sign Up


  • Content Count

  • Joined

  • Last visited

Everything posted by SpecialKrio

  1. good news! (at least for me lol) I've launched the M42 command with Repetier host and I have found all the pin enabled. Now I must understand how to write the Gcode properly In the Cura Propeties: Machine settings - Extruder Start G-code. What I wish is to do is: 1- Retract the filament while it hops on the Z axes; 2- Activate the corresponding pin so the changing nozzle sistem is trigged via the electromagnet; 4- come back to the print position while the filament goes foward; 5- continue with the normal G-code Since cura lets me to write G-code at the beginning and the end of each nozzle movement I have now to Understand what is better to write at the start and what at the end. And How to write it in G-code properly. I'll be out for a while... hope to find some time soon to test it.
  2. Hi and thank you for your message! Well actually, since this idea is at its very first stage, I would consider the hardware design after I will solve the software issue. But thank you for your tip, I will take in mind! At this stage my goal is to turn some leds on, through theese pins, using a specific G-code command. I want to double check the pin first, if they are really not active by the firmware or they are, and I've simply put a wrong G-code command. Thanks for your help
  3. Hello and thank you for your message. Yes I generally make my firmware from that link. What I'm now working on, is basically a rotary sistem to switch from a nozzle to the other, the concept is not so new, I'm just try to make my own design. All the hardware parts are already made, in attached a link of a 3D simulation video https://www.dropbox.com/s/5ldv04cqo05ydcc/rotary double nozzle6.mp4?dl=0 As you can see from the video at the early beginning, I wanted to swich the nozzle meccanically with a specific movement of the head (as the UM3 does). My early idea was to type the gcode for that movement using the option in Cura that allows you to modify the g-code at the start and end of every nozzle. What I would like to do now is to trig the movement via two electromagnets. Imagine on top of the head two little magnets that atract the nozzle's holder. On my board, close to the USB port, there are 8 pins: ground, 5volt, and 6 free pins (from 8 to 13). They are connected with Arduino board but they are not used by the ulti board. My idea is to use them to give curent to the electromagnets. Hope the idea is clear. Thank you for your tip I will try even if I'm more skilled in harware mod than software XD! I used arduido IDE just to make some leds blinking, nothing more.... Can I count on your help if I'll find any difficulties to make it? Thks
  4. Hello everybody, My Ultimaker Original Has some modifications like DIY Hot Bed (with 100K thermistor), axes motors outside the machine and so on. I generally modify my firmware from the "firmware builder" provided by this website. I'm now working on a new concept for a better usage of my second nozzle and I need to activate the pins from 8 to 13 that are not used by my board so far (version 1.5.7.). I've wired them to make some experiments: I've connected a LEd to see if they can be activated, they blink twice when I turn my printer on. But I don't know how to use them, I guess I need to make some adjustement on the firmware. CAN SOMEONE HELP ME ON IT? (My final intention is to activate them when my printer passes from a nozzle to the other, I will add some line of Gcode in the cura's options in machine settings) Thank you.
  5. link to the video: https://www.dropbox.com/s/5ldv04cqo05ydcc/rotary double nozzle6.mp4?dl=0
  6. Hi there! just landed on this forum... congratulations! The last post is on january 2018 hope someone is still interested on it! I'm writing you becouse I've decided to work on a similar project for my UMO (two nozzle swop their height via a rotation). In order to trig the rotation the print head needs to do a specific movement every time it passes from a nozzle to the other and viceversa... nothing new.. exactly the same concept with a different shape. here the simulation: https://www.dropbox.com/s/kys2yq4jwg9nflb/rotary-double-nozzle2.gif?dl=0 As I've understood you just insert a GCode strip for it... no mod on firmware nor low level programming... that souns awesome to me! Could you please explain me a little more? how the GCode works? where should I write them? (I use cura) and how to customize for my specific movement? For what I know I can make some modification to the start-Gcode and End-Gcode in the machine setting in Cura (screenshoot attached)... but I really don't know if it is helpful and if so what shoul Iwrite. thank you!Hi there
  7. I'm not at home now and probably I will be not untill the end of the year. So I can't touch my printer until that moment. No... is really not familiar to me lol! XD I just remember tha I run an customized firmware built on a specific platform (I made this ages ago). After Make all the modification needed I downloaded the file, i should have a copy and it migh be that one: (I don't know if is what u are talking about) #ifndef CONFIGURATION_ADV_H #define CONFIGURATION_ADV_H //=========================================================================== //=============================Thermal Settings ============================ //=========================================================================== #ifdef BED_LIMIT_SWITCHING #define BED_HYSTERESIS 2 //only disable heating if T>target+BED_HYSTERESIS and enable heating if T>target-BED_HYSTERESIS #endif #define BED_CHECK_INTERVAL 5000 //ms between checks in bang-bang control //// Heating sanity check: // This waits for the watchperiod in milliseconds whenever an M104 or M109 increases the target temperature // If the temperature has not increased at the end of that period, the target temperature is set to zero. // It can be reset with another M104/M109. This check is also only triggered if the target temperature and the current temperature // differ by at least 2x WATCH_TEMP_INCREASE //#define WATCH_TEMP_PERIOD 40000 //40 seconds //#define WATCH_TEMP_INCREASE 10 //Heat up at least 10 degree in 20 seconds #ifdef PIDTEMP // this adds an experimental additional term to the heatingpower, proportional to the extrusion speed. // if Kc is choosen well, the additional required power due to increased melting should be compensated. #define PID_ADD_EXTRUSION_RATE #ifdef PID_ADD_EXTRUSION_RATE #define DEFAULT_Kc (1) //heatingpower=Kc*(e_speed) #endif #endif //automatic temperature: The hot end target temperature is calculated by all the buffered lines of gcode. //The maximum buffered steps/sec of the extruder motor are called "se". //You enter the autotemp mode by a M109 S<mintemp> T<maxtemp> F<factor> // the target temperature is set to mintemp+factor*se[steps/sec] and limited by mintemp and maxtemp // you exit the value by any M109 without F* // Also, if the temperature is set to a value <mintemp, it is not changed by autotemp. // on an ultimaker, some initial testing worked with M109 S215 B260 F1 in the start.gcode #define AUTOTEMP #ifdef AUTOTEMP #define AUTOTEMP_OLDWEIGHT 0.98 #endif //Show Temperature ADC value //The M105 command return, besides traditional information, the ADC value read from temperature sensors. //#define SHOW_TEMP_ADC_VALUES // extruder run-out prevention. //if the machine is idle, and the temperature over MINTEMP, every couple of SECONDS some filament is extruded //#define EXTRUDER_RUNOUT_PREVENT #define EXTRUDER_RUNOUT_MINTEMP 190 #define EXTRUDER_RUNOUT_SECONDS 30. #define EXTRUDER_RUNOUT_ESTEPS 14. //mm filament #define EXTRUDER_RUNOUT_SPEED 1500. //extrusion speed #define EXTRUDER_RUNOUT_EXTRUDE 100 //These defines help to calibrate the AD595 sensor in case you get wrong temperature measurements. //The measured temperature is defined as "actualTemp = (measuredTemp * TEMP_SENSOR_AD595_GAIN) + TEMP_SENSOR_AD595_OFFSET" #define TEMP_SENSOR_AD595_OFFSET 0.0 #define TEMP_SENSOR_AD595_GAIN 1.0 //This is for controlling a fan to cool down the stepper drivers //it will turn on when any driver is enabled //and turn off after the set amount of seconds from last driver being disabled again #define CONTROLLERFAN_PIN -1 //Pin used for the fan to cool controller (-1 to disable) #define CONTROLLERFAN_SECS 60 //How many seconds, after all motors were disabled, the fan should run #define CONTROLLERFAN_SPEED 255 // == full speed // When first starting the main fan, run it at full speed for the // given number of milliseconds. This gets the fan spinning reliably // before setting a PWM value. (Does not work with software PWM for fan on Sanguinololu) //#define FAN_KICKSTART_TIME 100 // Extruder cooling fans // Configure fan pin outputs to automatically turn on/off when the associated // extruder temperature is above/below EXTRUDER_AUTO_FAN_TEMPERATURE. // Multiple extruders can be assigned to the same pin in which case // the fan will turn on when any selected extruder is above the threshold. #define EXTRUDER_0_AUTO_FAN_PIN -1 #define EXTRUDER_1_AUTO_FAN_PIN -1 #define EXTRUDER_2_AUTO_FAN_PIN -1 #define EXTRUDER_AUTO_FAN_TEMPERATURE 50 #define EXTRUDER_AUTO_FAN_SPEED 255 // == full speed //=========================================================================== //=============================Mechanical Settings=========================== //=========================================================================== #define ENDSTOPS_ONLY_FOR_HOMING // If defined the endstops will only be used for homing //// AUTOSET LOCATIONS OF LIMIT SWITCHES //// Added by ZetaPhoenix 09-15-2012 #ifdef MANUAL_HOME_POSITIONS // Use manual limit switch locations #define X_HOME_POS MANUAL_X_HOME_POS #define Y_HOME_POS MANUAL_Y_HOME_POS #define Z_HOME_POS MANUAL_Z_HOME_POS #else //Set min/max homing switch positions based upon homing direction and min/max travel limits //X axis #if X_HOME_DIR == -1 #ifdef BED_CENTER_AT_0_0 #define X_HOME_POS X_MAX_LENGTH * -0.5 #else #define X_HOME_POS X_MIN_POS #endif //BED_CENTER_AT_0_0 #else #ifdef BED_CENTER_AT_0_0 #define X_HOME_POS X_MAX_LENGTH * 0.5 #else #define X_HOME_POS X_MAX_POS #endif //BED_CENTER_AT_0_0 #endif //X_HOME_DIR == -1 //Y axis #if Y_HOME_DIR == -1 #ifdef BED_CENTER_AT_0_0 #define Y_HOME_POS Y_MAX_LENGTH * -0.5 #else #define Y_HOME_POS Y_MIN_POS #endif //BED_CENTER_AT_0_0 #else #ifdef BED_CENTER_AT_0_0 #define Y_HOME_POS Y_MAX_LENGTH * 0.5 #else #define Y_HOME_POS Y_MAX_POS #endif //BED_CENTER_AT_0_0 #endif //Y_HOME_DIR == -1 // Z axis #if Z_HOME_DIR == -1 //BED_CENTER_AT_0_0 not used #define Z_HOME_POS Z_MIN_POS #else #define Z_HOME_POS Z_MAX_POS #endif //Z_HOME_DIR == -1 #endif //End auto min/max positions //END AUTOSET LOCATIONS OF LIMIT SWITCHES -ZP //#define Z_LATE_ENABLE // Enable Z the last moment. Needed if your Z driver overheats. // A single Z stepper driver is usually used to drive 2 stepper motors. // Uncomment this define to utilize a separate stepper driver for each Z axis motor. // Only a few motherboards support this, like RAMPS, which have dual extruder support (the 2nd, often unused, extruder driver is used // to control the 2nd Z axis stepper motor). The pins are currently only defined for a RAMPS motherboards. // On a RAMPS (or other 5 driver) motherboard, using this feature will limit you to using 1 extruder. //#define Z_DUAL_STEPPER_DRIVERS #ifdef Z_DUAL_STEPPER_DRIVERS #undef EXTRUDERS #define EXTRUDERS 1 #endif // Same again but for Y Axis. //#define Y_DUAL_STEPPER_DRIVERS // Define if the two Y drives need to rotate in opposite directions #define INVERT_Y2_VS_Y_DIR true #ifdef Y_DUAL_STEPPER_DRIVERS #undef EXTRUDERS #define EXTRUDERS 1 #endif #if defined (Z_DUAL_STEPPER_DRIVERS) && defined (Y_DUAL_STEPPER_DRIVERS) #error "You cannot have dual drivers for both Y and Z" #endif // Enable this for dual x-carriage printers. // A dual x-carriage design has the advantage that the inactive extruder can be parked which // prevents hot-end ooze contaminating the print. It also reduces the weight of each x-carriage // allowing faster printing speeds. //#define DUAL_X_CARRIAGE #ifdef DUAL_X_CARRIAGE // Configuration for second X-carriage // Note: the first x-carriage is defined as the x-carriage which homes to the minimum endstop; // the second x-carriage always homes to the maximum endstop. #define X2_MIN_POS 80 // set minimum to ensure second x-carriage doesn't hit the parked first X-carriage #define X2_MAX_POS 353 // set maximum to the distance between toolheads when both heads are homed #define X2_HOME_DIR 1 // the second X-carriage always homes to the maximum endstop position #define X2_HOME_POS X2_MAX_POS // default home position is the maximum carriage position // However: In this mode the EXTRUDER_OFFSET_X value for the second extruder provides a software // override for X2_HOME_POS. This also allow recalibration of the distance between the two endstops // without modifying the firmware (through the "M218 T1 X???" command). // Remember: you should set the second extruder x-offset to 0 in your slicer. // Pins for second x-carriage stepper driver (defined here to avoid further complicating pins.h) #define X2_ENABLE_PIN 29 #define X2_STEP_PIN 25 #define X2_DIR_PIN 23 // There are a few selectable movement modes for dual x-carriages using M605 S<mode> // Mode 0: Full control. The slicer has full control over both x-carriages and can achieve optimal travel results // as long as it supports dual x-carriages. (M605 S0) // Mode 1: Auto-park mode. The firmware will automatically park and unpark the x-carriages on tool changes so // that additional slicer support is not required. (M605 S1) // Mode 2: Duplication mode. The firmware will transparently make the second x-carriage and extruder copy all // actions of the first x-carriage. This allows the printer to print 2 arbitrary items at // once. (2nd extruder x offset and temp offset are set using: M605 S2 [Xnnn] [Rmmm]) // This is the default power-up mode which can be later using M605. #define DEFAULT_DUAL_X_CARRIAGE_MODE 0 // As the x-carriages are independent we can now account for any relative Z offset #define EXTRUDER1_Z_OFFSET 0.0 // z offset relative to extruder 0 // Default settings in "Auto-park Mode" #define TOOLCHANGE_PARK_ZLIFT 0.2 // the distance to raise Z axis when parking an extruder #define TOOLCHANGE_UNPARK_ZLIFT 1 // the distance to raise Z axis when unparking an extruder // Default x offset in duplication mode (typically set to half print bed width) #define DEFAULT_DUPLICATION_X_OFFSET 100 #endif //DUAL_X_CARRIAGE //homing hits the endstop, then retracts by this distance, before it tries to slowly bump again: #define X_HOME_RETRACT_MM 5 #define Y_HOME_RETRACT_MM 5 #define Z_HOME_RETRACT_MM 1 //#define QUICK_HOME //if this is defined, if both x and y are to be homed, a diagonal move will be performed initially. #define AXIS_RELATIVE_MODES {false, false, false, false} #define MAX_STEP_FREQUENCY 40000 // Max step frequency for Ultimaker (5000 pps / half step) //By default pololu step drivers require an active high signal. However, some high power drivers require an active low signal as step. #define INVERT_X_STEP_PIN false #define INVERT_Y_STEP_PIN false #define INVERT_Z_STEP_PIN false #define INVERT_E_STEP_PIN false //default stepper release if idle #define DEFAULT_STEPPER_DEACTIVE_TIME 60 #define DEFAULT_MINIMUMFEEDRATE 0.0 // minimum feedrate #define DEFAULT_MINTRAVELFEEDRATE 0.0 // Feedrates for manual moves along X, Y, Z, E from panel #ifdef ULTIPANEL #define MANUAL_FEEDRATE {50*60, 50*60, 4*60, 60} // set the speeds for manual moves (mm/min) #endif // minimum time in microseconds that a movement needs to take if the buffer is emptied. #define DEFAULT_MINSEGMENTTIME 20000 // If defined the movements slow down when the look ahead buffer is only half full #define SLOWDOWN // Frequency limit // See nophead's blog for more info // Not working O //#define XY_FREQUENCY_LIMIT 15 // Minimum planner junction speed. Sets the default minimum speed the planner plans for at the end // of the buffer and all stops. This should not be much greater than zero and should only be changed // if unwanted behavior is observed on a user's machine when running at very slow speeds. #define MINIMUM_PLANNER_SPEED 0.05// (mm/sec) // MS1 MS2 Stepper Driver Microstepping mode table #define MICROSTEP1 LOW,LOW #define MICROSTEP2 HIGH,LOW #define MICROSTEP4 LOW,HIGH #define MICROSTEP8 HIGH,HIGH #define MICROSTEP16 HIGH,HIGH // Microstep setting (Only functional when stepper driver microstep pins are connected to MCU. #define MICROSTEP_MODES {16,16,16,16,16} // [1,2,4,8,16] // Motor Current setting (Only functional when motor driver current ref pins are connected to a digital trimpot on supported boards) #define DIGIPOT_MOTOR_CURRENT {135,135,135,135,135} // Values 0-255 (RAMBO 135 = ~0.75A, 185 = ~1A) //=========================================================================== //=============================Additional Features=========================== //=========================================================================== #define SD_FINISHED_STEPPERRELEASE true //if sd support and the file is finished: disable steppers? #define SD_FINISHED_RELEASECOMMAND "M84 X Y Z E" // You might want to keep the z enabled so your bed stays in place. #define SDCARD_RATHERRECENTFIRST //reverse file order of sd card menu display. Its sorted practically after the filesystem block order. // if a file is deleted, it frees a block. hence, the order is not purely cronological. To still have auto0.g accessible, there is again the option to do that. // using: //#define MENU_ADDAUTOSTART // The hardware watchdog should reset the Microcontroller disabling all outputs, in case the firmware gets stuck and doesn't do temperature regulation. //#define USE_WATCHDOG #ifdef USE_WATCHDOG // If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on. // The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset. // However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled. //#define WATCHDOG_RESET_MANUAL #endif // Enable the option to stop SD printing when hitting and endstops, needs to be enabled from the LCD menu when this option is enabled. //#define ABORT_ON_ENDSTOP_HIT_FEATURE_ENABLED // Babystepping enables the user to control the axis in tiny amounts, independently from the normal printing process // it can e.g. be used to change z-positions in the print startup phase in realtime // does not respect endstops! //#define BABYSTEPPING #ifdef BABYSTEPPING #define BABYSTEP_XY //not only z, but also XY in the menu. more clutter, more functions #define BABYSTEP_INVERT_Z false //true for inverse movements in Z #define BABYSTEP_Z_MULTIPLICATOR 2 //faster z movements #ifdef COREXY #error BABYSTEPPING not implemented for COREXY yet. #endif #ifdef DELTA #ifdef BABYSTEP_XY #error BABYSTEPPING only implemented for Z axis on deltabots. #endif #endif #endif // extruder advance constant (s2/mm3) // // advance (steps) = STEPS_PER_CUBIC_MM_E * EXTUDER_ADVANCE_K * cubic mm per second ^ 2 // // hooke's law says: force = k * distance // bernoulli's priniciple says: v ^ 2 / 2 + g . h + pressure / density = constant // so: v ^ 2 is proportional to number of steps we advance the extruder //#define ADVANCE #ifdef ADVANCE #define EXTRUDER_ADVANCE_K .0 #define D_FILAMENT 2.85 #define STEPS_MM_E 836 #define EXTRUTION_AREA (0.25 * D_FILAMENT * D_FILAMENT * 3.14159) #define STEPS_PER_CUBIC_MM_E (axis_steps_per_unit[E_AXIS]/ EXTRUTION_AREA) #endif // ADVANCE // Arc interpretation settings: #define MM_PER_ARC_SEGMENT 1 #define N_ARC_CORRECTION 25 const unsigned int dropsegments=5; //everything with less than this number of steps will be ignored as move and joined with the next movement // If you are using a RAMPS board or cheap E-bay purchased boards that do not detect when an SD card is inserted // You can get round this by connecting a push button or single throw switch to the pin defined as SDCARDCARDDETECT // in the pins.h file. When using a push button pulling the pin to ground this will need inverted. This setting should // be commented out otherwise #define SDCARDDETECTINVERTED #ifdef ULTIPANEL #undef SDCARDDETECTINVERTED #endif // Power Signal Control Definitions // By default use ATX definition #ifndef POWER_SUPPLY #define POWER_SUPPLY 1 #endif // 1 = ATX #if (POWER_SUPPLY == 1) #define PS_ON_AWAKE LOW #define PS_ON_ASLEEP HIGH #endif // 2 = X-Box 360 203W #if (POWER_SUPPLY == 2) #define PS_ON_AWAKE HIGH #define PS_ON_ASLEEP LOW #endif // Control heater 0 and heater 1 in parallel. //#define HEATERS_PARALLEL //=========================================================================== //=============================Buffers ============================ //=========================================================================== // The number of linear motions that can be in the plan at any give time. // THE BLOCK_BUFFER_SIZE NEEDS TO BE A POWER OF 2, i.g. 8,16,32 because shifts and ors are used to do the ringbuffering. #if defined SDSUPPORT #define BLOCK_BUFFER_SIZE 16 // SD,LCD,Buttons take more memory, block buffer needs to be smaller #else #define BLOCK_BUFFER_SIZE 16 // maximize block buffer #endif //The ASCII buffer for recieving from the serial: #define MAX_CMD_SIZE 96 #define BUFSIZE 4 // Firmware based and LCD controled retract // M207 and M208 can be used to define parameters for the retraction. // The retraction can be called by the slicer using G10 and G11 // until then, intended retractions can be detected by moves that only extrude and the direction. // the moves are than replaced by the firmware controlled ones. // #define FWRETRACT //ONLY PARTIALLY TESTED #define MIN_RETRACT 0.1 //minimum extruded mm to accept a automatic gcode retraction attempt //adds support for experimental filament exchange support M600; requires display #ifdef ULTIPANEL #define FILAMENTCHANGEENABLE #ifdef FILAMENTCHANGEENABLE #define FILAMENTCHANGE_XPOS 3 #define FILAMENTCHANGE_YPOS 3 #define FILAMENTCHANGE_ZADD 10 #define FILAMENTCHANGE_FIRSTRETRACT -2 #define FILAMENTCHANGE_FINALRETRACT -100 #endif #endif #ifdef FILAMENTCHANGEENABLE #ifdef EXTRUDER_RUNOUT_PREVENT #error EXTRUDER_RUNOUT_PREVENT currently incompatible with FILAMENTCHANGE #endif #endif //=========================================================================== //============================= Define Defines ============================ //=========================================================================== #if EXTRUDERS > 1 && defined TEMP_SENSOR_1_AS_REDUNDANT #error "You cannot use TEMP_SENSOR_1_AS_REDUNDANT if EXTRUDERS > 1" #endif #if EXTRUDERS > 1 && defined HEATERS_PARALLEL #error "You cannot use HEATERS_PARALLEL if EXTRUDERS > 1" #endif #if TEMP_SENSOR_0 > 0 #define THERMISTORHEATER_0 TEMP_SENSOR_0 #define HEATER_0_USES_THERMISTOR #endif #if TEMP_SENSOR_1 > 0 #define THERMISTORHEATER_1 TEMP_SENSOR_1 #define HEATER_1_USES_THERMISTOR #endif #if TEMP_SENSOR_2 > 0 #define THERMISTORHEATER_2 TEMP_SENSOR_2 #define HEATER_2_USES_THERMISTOR #endif #if TEMP_SENSOR_BED > 0 #define THERMISTORBED TEMP_SENSOR_BED #define BED_USES_THERMISTOR #endif #if TEMP_SENSOR_0 == -1 #define HEATER_0_USES_AD595 #endif #if TEMP_SENSOR_1 == -1 #define HEATER_1_USES_AD595 #endif #if TEMP_SENSOR_2 == -1 #define HEATER_2_USES_AD595 #endif #if TEMP_SENSOR_BED == -1 #define BED_USES_AD595 #endif #if TEMP_SENSOR_0 == -2 #define HEATER_0_USES_MAX6675 #endif #if TEMP_SENSOR_0 == 0 #undef HEATER_0_MINTEMP #undef HEATER_0_MAXTEMP #endif #if TEMP_SENSOR_1 == 0 #undef HEATER_1_MINTEMP #undef HEATER_1_MAXTEMP #endif #if TEMP_SENSOR_2 == 0 #undef HEATER_2_MINTEMP #undef HEATER_2_MAXTEMP #endif #if TEMP_SENSOR_BED == 0 #undef BED_MINTEMP #undef BED_MAXTEMP #endif #endif //__CONFIGURATION_ADV_H
  8. My goal is to make a big modification so I have a "second pop-up nozzle" like the ultimaker 3. Thats why I need this setting. Also moving the print head in a specific position before change the nozzle to trig the mechanism and make the second nozzle to pop-up out. (I hope is clear what I mean) thks again
  9. Mhhhh ok consider the fact that I'm no too confidential with modifying g-code... Saying that, I have an Ultimaker Original with Its original board (Just few modification like heated bed etc.). A Marlin firmware runs the machine. I really wonder to know how to manage the g-codes. Thank you for your super fast reply!
  10. Hi! I Need to do what you have done by mistake but in purpose! How you made it?
  11. Hi everybody! I'm currently modding my UMO with 2 nozzles using a similar concept used by the Ultimaker3 (retracting second extruder). But I have some issue to set it properly on Cura. I cannot set the gap between the nozzles (i just can set the Z offset between nozzle and the bed and it can be not different fron a nozzle to the other). As you can image i need to tell to cura "change the hight of the bed when use the second extruder" and also "Go to a specific X/Y position before change extruder" to trig the second extruder to pop up. How to do that? P.S. If it gonna work I will post the project. Thak you all!
  12. SpecialKrio

    New print

    Version 1.0

    1 download

    New print
  13. Hello guys. I want to modify my UMO's head and I need two longer head's shafts but I don't want to lose quality. I wanted to use UM2's shaft because I think they are longer enough (they should be 320mm isn't it?) But it looks pretty difficult to me to find them and so I want to have a look somewhere else. But I need to know the spec that I need to look for: type of the metal; bend tolerance; surface treatment etc. Some one of you know that? Also... Do you know if chromed bars are better? They look shiny with no rough surface and they don't get rust (which can happen with standard ultimaker''s barrs). Thanks to all.
  14. Yes! I have exactly the same problem! I wished to buy just the inner shield... and saying "is not in production anymore" it has no sense. Wooden ultimaker is still here on this website. I contacted the same seller "crea 3d"... Now I've found the last piece in stock on "3ditaly" store (also an authorised seller here in Italy) but... jesus I had to buy a whole kit... and it was f****ing expensive! At this point I hope they really have in stock the original piece at least!
  15. Hello guys. I got some trouble with my ulticontroller and now the inner shield is broken. I asked for a new one but the seller said that is out of production. What does it mean? UMO is not in production anymore? I really wish to have the original piece, even if I have to buy the whole controller again.
  16. I made this topic just because I have some ideas in my mind for my Ulti Original that's why is in this chat. And sorry if is a repetitive topic. My question was more like a confirm question. I've also asked about the "pois-like bushing" aka "graphite copper bushing". Are them used in the Ulti 2 or, they come from the unofficial market? If they are used in the Ulti 2, do they give an considerable benefit? (for our printer in terms of time and costs spent). Sorry if the question about maintenance wasn't clear... I was talking about the "graphite copper" bushing and not about "whole copper" one. I guess it doesn't need oil... but yet... is still not clear to me if they are used on new ultimaker's machines or not. Thanks to everybody and peace!
  17. Hey dude! how's going! Nice to hear you again. Yes. the shooting is complete and I'm now working on the post-production and editing. This year I had other tasks to do, i stopped to work on it for several months and so the timing has become drammatically extended :(!.. but yes... I'm very happy about the result! As soon as I can, I'll upload some photoes on my Ultimaker's Profile! Anyway... about my question on "bearing or sintered bushing": I'm trying to understand why all the ultimakers use the bushing on the external x,y axes, and also the differences between them and their application field. I guess because the linear bearing (as the name suggests) can only slide and not rotate? So generally a bearing gives less friction(but only in one direction), what about accuracy? Have them the same "play"? If yes how to mesure? I saw the ULTI2 has a different bushing. Ithink an "graphite copper bushing". Which are the benefits? Less friction? Do they need oil or they are "self- dry-lubricating"? do they fit on an ULTI original? I have alot of other questions, but I risk to go out of theme...maybe later! Thanks!
  18. Hi! I'm trying to understand the difference between a bearing and a bushing. Why all the ultimakers use bronze bushing on the external x-y axes? The difference of the other axes is that the pieces have two movements, linear and rotational. But why is better using the bushings there? I wonder if changing with bearings could be a good modification. thks.
  19. Maybe the right thing it would be to have in machine "settings", not only X and Y offset but also an Z offset... yeah it sounds more clear to me...
  20. Hi guys! Nice to be part of this community! Even if I have an UNO since"14 I've never been part of the community! I use my printer for several experiments and mainly for a personal project (animation in stop motion) I made on it several modifications (maybe I'll ubdate some photoes soon). I also thought to create a sort of "swappable" double nozzle as the UM3. I also want my second extruder to go upper and a bit more down respect to the first nozzle so it doesn't interferes with the other. I just want to move one of them to make it easer to create. I already know hot to make it (phisically), but I have some lake in programming... so my question is: How I can tell to Cura to use basically two different "Z axes" coordinates? Immagine the case if the second nozzle goes down 3mm more than the first. Is enought to say in Cura>Expert Config.>"Distance Z (mm)"= "-3"? Or it doesn't work like that? Maybe that configuration modify only the "support solid". Hope my question is clear! Cheers!
  • Create New...