purps

Any and all help appreciated, as I really need to get this working! The Pause At Height plugin seems to do this weird thing where it skips layers after the resume, has anybody else seen this? This little test model is just a simple cylinder. Does the code look right? Or is it 1mm out? Or should this not matter seeing as LAYER21 has the correct Z value? Also check out what it looks like when the gcode is loaded back into Cura - it has this strange really thick layer which extends down into the already printed part. This may just be graphical, however I thought I'd mention it in case it's relevant. ..................................................... ;LAYER:20 G0 X84.048 Y108.184 Z2.27 ;TYPE:WALL-INNER G11 G1 F1800 X84.246 Y108.045 E688.43371 G1 X84.522 Y107.882 ............................................. G0 X83.417 Y106.711 G0 X84.036 Y108.193 ;TIME_ELAPSED:659.170046 ;TYPE:CUSTOM ;added code by post processing ;script: PauseAtHeight.py ;current z: 2.370000 ;current height: 2.100000 M83 G1 E-6.500000 F1500.000000 G1 Z3.370000 F300 G1 X25.000000 Y25.000000 F9000 G1 Z15 F300 M84 E0 M0 ;Do the actual pause G1 E6.500000 F1500.000000 G1 E50.000000 F199.998000 G1 E-6.500000 F1500.000000 G1 Z3.370000 F300 G1 X84.036000 Y108.193000 F9000 G1 E6.500000 F1500.000000 G1 F9000 M82 G92 E704.151040 ;LAYER:21 G0 X84.036 Y108.193 Z2.37 ;TYPE:WALL-INNER G11 G1 F1800 X84.263 Y108.034 E704.16074 G1 X84.499 Y107.895 E704.17033 G1 X84.748 Y107.766 E704.18015 G1 X85.017 Y107.653 E704.19036 ................................. Cheers, Matt.

Thank you for the reply. I will have a play with the settings that you mention, I am always keen to experiment. The prints came out fine, so I think maybe it's graphical?

The plot thickens... This is the Cura 2.4 gcode for the exact same part, viewed in the gcode viewer (in Cura 2.5). As you can see, the artefacts are there, but not as severe. I also have the printed parts from this Cura 2.4 gcode, and they are flawless. Guess I'll try printing with the Cura 2.5 gcode and see what happens. Maybe just a graphical thing?

Removing knurling pattern seems to "solve" the issue. Obviously not really a solution.

Hi all, I printed this same part out in Cura 2.4, and I'm fairly sure it didn't do this. The layers in question should just be plain simple circles, but the walls are doing this strange thing circled in blue. Any ideas? Cheers, Matt.

Obviously we need to report issues, ask questions etc, that's how it works... ...but I would just like to say that I'm really enjoying Cura 2.5 and really appreciate the hard work that goes into it. Loving the new more detailed layer view, and how you can see which direction the solid layer stripes will be going. Very useful if you like to create your own support structure! Thanks again, Matt.

...and I now have UM2+ having just upgraded, and can report the same.

Sorry to resurrect an old thread, but I just wanted to say thank you so much for this information. I can't believe I made this numpty mistake as well - I'll put it down to tiredness. It would have taken a very long time to diagnose without this thread, especially as I had absolutely no desire to remove that flipping mainboard again. Cheers, Matt.

Has anybody else found that Cura 2.5 only upgrades the firmware to 2.4? This is on a UM2. Or have I got some issue due to my old installation of Cura? Cheers, Matt.

Beg your pardon, temperature sensor. Thank you both for the advice - as you'll see in the aforementioned thread, the firmware issue is sorted. Cheers, Matt.

It's sorted. Phew. Although the firmware is only 2.4, not 2.5 - is there no new firmware with 2.5? The problem was drivers... on both the Windows machine and the Linux machine. Two independent problems that gave the same symptoms. So I started with the Windows machine, reinstalled the Arduino driver (by installing Cura 2.5), and it worked straight away. I don't know what was wrong with the Arduino driver before. I'll have a look at the Linux machine in slower time, but at least I know what the problem was. Can I just say a massive thank you to @SyntaxTerror and @amedee for looking into this with me - it felt a lot less daunting knowing there are people willing to help me out! And sorry to @spiracy for implying you had conned me haha, but what do you expect, I find threads listing all these problems you've had and your eBay account disappeared haha. Cheers, Matt.

Thanks guys, believe it or not I was actually aware of the stepper motor direction issue - however that's what I thought the G-Code mod was for! Clearly not. OK, so can I safely install the new hot end, but wait until later for the feeder? Everything else, the heaters, the new thermocouple, everything at the hot end of the UM2+ upgrade kit will be OK with firmware Vers:_15.04.5? Thanks again, Matt.

Ok thanks.

If I tell Cura 2.5 that I'm using an UM2+, the gcode will be correct, no?

As the title says really! I would appreciate any and all help. Discussion of my firmware upgrade problems is here https://ultimaker.com/en/community/44827-cant-update-firmware-on-um2-i-think-ive-checked-all-the-obvious-stuff Obviously that problem needs solving, but in the short term I need to crack on as I have orders to fulfill. Cheers, Matt.

Guys thank you so much for your inputs. Reflashing through the ICSP header and/or via avrdude sounds quite drastic. Of course I will give it a go if necessary. Is the ICSP essentially a serial connection? How does it differ from USB? I'll check for /dev/ttyACM0 later when I get home. So do my code dumps confirm that usbcore is not registering the device? Thanks for the video. Can I safely do this on an UM2? I found this thread where @gr5 gives his usual helpful advice (Posted Apr 10, 2014 - 8:48 PM), so I shall give that a go on the Windows machine. https://ultimaker.com/en/community/6100-how-to-update-um2-firmware Other things I will mention, just in case..... One of the LEDs has broken (or gone to very high resistance...), causing the other 5 in the segment to go dim. Surely that wouldn't be causing this problem? I realise I am scraping the barrel here. Thank you both again for your support. I hope we can get to the bottom of this!

No it's never worked. Had the printer about a month. I have been using the printer solidly for a month and I was very happy with it. It seems to print just fine. Those threads from @spiracy were in March 2015 and the current version is March 2016... So he either managed to update it, or it's a brand new mainboard I'm guessing. But I don't know. Never tried printing from USB. Why do you ask?

amy@amy-laptop /sys/bus/usb/drivers/cdc_acm/7-1:1.0 $ ls -la total 0 drwxr-xr-x 5 root root 0 Apr 20 20:26 . drwxr-xr-x 6 root root 0 Apr 20 20:26 .. -r--r--r-- 1 root root 4096 Apr 20 20:35 bAlternateSetting -r--r--r-- 1 root root 4096 Apr 20 20:26 bInterfaceClass -r--r--r-- 1 root root 4096 Apr 20 20:26 bInterfaceNumber -r--r--r-- 1 root root 4096 Apr 20 20:35 bInterfaceProtocol -r--r--r-- 1 root root 4096 Apr 20 20:35 bInterfaceSubClass -r--r--r-- 1 root root 4096 Apr 20 20:35 bmCapabilities -r--r--r-- 1 root root 4096 Apr 20 20:26 bNumEndpoints lrwxrwxrwx 1 root root 0 Apr 20 20:26 driver -> ../../../../../../bus/usb/drivers/cdc_acm drwxr-xr-x 3 root root 0 Apr 20 20:35 ep_82 -r--r--r-- 1 root root 4096 Apr 20 20:35 modalias drwxr-xr-x 2 root root 0 Apr 20 20:35 power lrwxrwxrwx 1 root root 0 Apr 20 20:26 subsystem -> ../../../../../../bus/usb -r--r--r-- 1 root root 4096 Apr 20 20:35 supports_autosuspend drwxr-xr-x 3 root root 0 Apr 20 20:26 tty -rw-r--r-- 1 root root 4096 Apr 20 20:26 uevent

amy@amy-laptop /sys/bus/usb/drivers/cdc_acm $ ls 7-1:1.0 7-1:1.1 bind module new_id remove_id uevent unbind So it looks like it's there.

OK I did this and no complaints.

I'm looking at the mainboard now - it's genuine at least. I'll put it back together and check what you suggested shortly. Thank you.

As in modprobe?

I feel physically sick. Just tried to contact the guy I bought the printer from, and his eBay account has been closed. He had told me his thingiverse username, and by pure chance I happened to see the same name on these forums when googling the price of new mainboards - his name is @spiracy Check out these threads... https://ultimaker.com/en/community/11294-ultimaker-2-sos https://ultimaker.com/en/community/11492-ultimaker-2-main-board Really worried I've been sold a duff printer here. Paid £920 for it. I'm going to open it up and see what the mainboard looks like, maybe it's been replaced with a cheap copy or something?

And... [ 1.420232] sd 0:0:0:0: [sda] Write Protect is off [ 1.420236] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 1.420262] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 1.420449] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 1.453082] sda: sda1 sda2 sda3 [ 1.453631] sd 0:0:0:0: [sda] Attached SCSI disk [ 1.516118] usb 7-1: New USB device found, idVendor=2341, idProduct=0010 [ 1.516121] usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.516124] usb 7-1: Product: Ultimaker 2.0 [ 1.516126] usb 7-1: Manufacturer: Ultimaker BV (www.ultimaker.com) [ 1.740080] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 1.741903] ata2.00: ATAPI: TSSTcorp CDDVDW TS-L633J, SC00, max UDMA/100 [ 1.744866] ata2.00: configured for UDMA/100 [ 1.748771] scsi 1:0:0:0: CD-ROM TSSTcorp CDDVDW TS-L633J SC00 PQ: 0 ANSI: 5 [ 1.768802] psmouse serio1: elantech: assuming hardware version 2 (with firmware version 0x040215) [ 1.771720] sr 1:0:0:0: [sr0] scsi3-mmc drive: 16x/24x writer dvd-ram cd/rw xa/form2 cdda tray

Sorry [59.629969] pci 0000:00:1e.0: bridge window [mem 0x80100000-0x802fffff] [ 59.629974] pci 0000:00:1e.0: bridge window [mem 0x80300000-0x804fffff 64bit pref] [ 59.629998] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [ 59.630002] pci 0000:00:1e.0: PCI bridge to [bus 08] [ 59.630006] pci 0000:00:1e.0: bridge window [io 0x6000-0x6fff] [ 59.630012] pci 0000:00:1e.0: bridge window [mem 0x80100000-0x802fffff] [ 59.630017] pci 0000:00:1e.0: bridge window [mem 0x80300000-0x804fffff 64bit pref] [ 59.630170] pci_bus 0000:02: Allocating resources [ 59.630189] pci_bus 0000:04: Allocating resources [ 59.630227] pci_bus 0000:06: Allocating resources [ 59.630242] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [ 59.630246] pci 0000:00:1e.0: PCI bridge to [bus 08] [ 59.630249] pci 0000:00:1e.0: bridge window [io 0x6000-0x6fff] [ 59.630256] pci 0000:00:1e.0: bridge window [mem 0x80100000-0x802fffff] [ 59.630261] pci 0000:00:1e.0: bridge window [mem 0x80300000-0x804fffff 64bit pref] [ 74.796103] usb 7-1: USB disconnect, device number 2 [ 115.192051] usb 7-1: new full-speed USB device number 3 using uhci_hcd [ 115.380895] usb 7-1: New USB device found, idVendor=2341, idProduct=0010 [ 115.380900] usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 115.380902] usb 7-1: Product: Ultimaker 2.0 [ 115.380905] usb 7-1: Manufacturer: Ultimaker BV (www.ultimaker.com) [ 115.383050] cdc_acm 7-1:1.0: ttyACM0: USB ACM device