Jump to content

navigator

Member
  • Posts

    76
  • Joined

  • Last visited

Posts posted by navigator

  1. I use a UM2+ modified to a Mark2 which I have been using quite successfully with Cura 3.2.1 with custom modified  filament profiles including PVA.

     

    When using Cura 3.3.1, everything works well apart from my PVA custom filament does not show up in the filament choices - I have tried to import the PVA profile which Cura 3.3.1 states it has loaded successfully, but it is still not available to choose.

     

    I assume that a PVA profile is being blocked for use with my UM2+/Mark2, and wonder if anyone knows a work around to get this to work.

     

    VMT for any assistance.

  2. Dear Community, currently I'am working on the Mark2 upgrade for my UM2+ (great project :-). I was wondering if the current Cura resources files on GitHub will work with the latest versions of cura 3.0.X or do I have to downgrade towards Cura 2.x?

    Does someone have any experiences on this.

     

    Running latest Cura with v.17.09 firmware here with no problems at all.

    Get it built, and enjoy the dual extrusion :)

    • Like 1
  3. Ok, i solved the problem by replacing the transistors, now everything is working as expected :)

    One thing I noticed, if I cancel a job, the main extruder drives nuts in every action following like it totally lost orientation, trying to bypass boundaries.

    Anyone else noticed this? Maybe related to firmware?

    I had something similar once where it would retract the filament as if it was doing a material change - did a full system reset, re-entered all the data gained from initial set up and never had any more problems.

  4. Try turning your screw anti clockwise - I seem to remember it was the reverse to what you would expect - the head of the socket screw rests on the top of the lid and turning anti clockwise will cause the spring to compress.

    Both of my screws are in the area you indicated :)

  5. Have got it running now - Just loaded into the root of 'C' drive instead of the default location and now seems OK!

    Further to my remarks above, I have looked further and now got it up and running in the normal programs area.

    On closer inspection I noticed the downloaded update file obtained from Cura was named ' Ultimaker Cura-3.0.4-win64' whereas previous versions were named 'Cura-3.xx.xx' and the file name was the path to the installation.

    Removed the extra 'Ultimaker' from the installation directory and all running fine, and Mark2 etc also there. :)

  6. Anyone else having problems running Cura 3.04?

    Firstly I upgraded from 3.03 but did not delete version 3.03, and after starting 3.04 once (checked version number on splash screen) my system always started with version 3.03 after the initial and only start up of 3.04.

    I then deleted version 3.04 from the 'Programs and Features' in control panel as it was showing as installed and on running the 3.04 install program again I deleted the previous version 3.03. Once again version 3.04 ran OK, but on trying to start the program again it could not be found on my system.

    I also noted that 3.04 did not import the machine definitions for my Mark2 set up and only remembered my UM2+ settings.

    I once again deleted 3.04 and reloaded 3.03 which runs fine and also has remembered the Mark2 settings.

    Running Win10 1709 build 16299.19.

    Any suggestions most welcome :)

  7. I've had these fitted for a while now, but also fitted an extra heat sink on the boards themselves in addition to the smaller ones for the UM motherboard and have had no problems at all - Also got extension cables so all boards are underneath the UM and outside the motherboard area - Heat sinks are those found for RPI boards.

    Picture below:

    nj7XZQc.jpg

    Even when they have the supplied plastic sleeve around them, they still remain cool.

    • Like 1
  8. I used the original parts to do the upgrade with great results, but my old head did have the Olsson upgrade fitted and IRobertl feeder.

    I also replaced the heater and sensor to newer versions later on, but it all worked fine - just had to change esteps for extruder which was easy using Tinker firmware (This also would have allowed me to change extruder direction easily instead of hard wiring!!).

    Link to my post: https://ultimaker.com/en/community/48788-ultimaker-mark2-the-smart-dual-extrusion-upgrade?page=7&sort=#reply-180700

  9. I thought I was the only one. I have the same issue on my work laptop. I resorted to using the older 2.5 and that works fine for some reason. I never dug into the problem because I hadn't heard of many people having the issue and figured it was just something weird on my end.

    I guess it's time to dig into the logs and see if there are any clues in there.

     

    Thank you for your information - It helped me stop pulling my hair out, and upgrade to the latest firmware. :)

  10. Experiencing a slight problem when using RepRap gcode vice Ultimaker2 on Cura 2.5 - When using RepRap, when the first head goes to the second head for the first time for prime etc. I always get a heavy vibration/noise which appears to be the Z axis being forced to move, but no problems at all with the Ultimaker code.

    Any ideas???

    Also, how do you get the Auto PID to work - I would like to optimise my heaters, but when I press the 'Auto' selection nothing happens :(

    Is it functional in the firmware at the moment, or an addition for later releases?

    VMT for help.

    Andy

  11. I think we need to start a data collection regarding power settings. Maybe when we have enough people with working settings, we can figure out something that is shutdown-safe for everyone.

     

    Good idea SyntaxTerror and I'll add my settings which I've never had problems with on having a shutdown.

    Using your board (VMT) with extrusion upgrade kit on main head (UM2 Ex) and original UM2 head /extruder as second head - I have changed the temperature probe and heater (40W) to UM2+ specs.

    My power settings: 160/150/45/45 - hope this helps.

    PSU is a GS220A24-R7B.

  12. I would like to report a problem that I have found and solved.

    For those who had wrong z positioning after a tool change [T0 to T1] with a gcode created in S3D, I found the cause, pay attention, you have to set to ZERO the "tool change retraction distance" in "advanced" tab.

    Nice find - been trying to sort out why that's been happening for ages now.

    Update: Just checked and mine was at zero, still got Z height problem with S3D - Cura works fine :(

  13. Weird thing though is that no matter what value I set to Y, it will not move the X rod farther from the parked head. I tried both small and extreme values such as Y=20, Y=0, Y=30 and Y=50 but it will not stop the X rod from hitting/squeezing the parked hotend.

    Thats what I thought you meant in your original post - I also had that, and reducing the pressure on the head in the Y direction whilst in the docking position cured it for me.

  14. One last thing: I've noticed that my 1st hotend would crash to the parked 2nd hotend when it's wiping and I can't solve it even if I set the wiping coordinates farther from the front and more to the left. The 1st hotend will always move to front center slightly crashing to the parked hotend. Is this something that's firmware-specific behavior?

    I think I know what you mean, and if I'm correct you may have your head docking position pushing on the 2nd head too much.

    Just try backing off a bit on the Y docking position (save and test swapping heads etc) and see if that helps out.

×
×
  • Create New...