LowiekVDS

We found what the problem was and I am currently working on a solution. I don't know how long it will take, but I hope it is done soon! The problem was that the printer gets a lot of commands it needs to execute to define a curve. And before it can execute the next command, it needs to update the display. Because of the dirty, inefficient way I implemented the display, it takes a lot of time until it fully updates. As a result, the commands that define the curve are executed too slow after each other so the printer moves too slow in curves. So a temporary solution is disabling the display. If you would like to try that on your printer, here is the download link to the working version with the display disabled : https://www.dropbox.com/s/3wwxy97vp9noubt/geen_lcd_2.hex?dl=0

When I try to import Solidwork files using the plugin on Windows 10, the program just hangs... Otherwise, I like the black theme!

I assume that the difference lies in your firmware... :PMore details please... The UMO uses a different mainboard AFAIK, or is it the same? It's hard to guess, what you have changed. Can you explain it a bit? Are the source files available somewhere? How is it compiled (compiler switches, active debugging options or something along these lines)? Is there any suspicious output on the serial console? Any noticeable differences if you start the same print from sd card or from USB? Hello, Because the motherboard of the UM2 and the motherboard of the UMO are both based on an Arduino Mega, running the firmware on the UMO original is not hard. You can just compile the code without problems using the Arduino IDE. But making it run like it is supposed to on UMO, is another story. Because if you just change the motherboard, it wil give errors. So I tricked the firmware into thinking that it is running on the UM2 motherboard, plus some changes so that everything runs like it should on the UMO (changes in pins.h for example). As an example, we use the RepRap Discount Full Graphic Smart Controller on the UMO. Once again, I let the firmware think that it is using the original UM2 display, and changed/added a lot of code so that it actually renders correctly on the RepRap display. The method I am currently using for achieving this is a quick and dirty way, but it is not that good. I have plans to implement a way better method to make the display work smoother. You can download the source code and the .hex file of the latest version if you want to try this on your own UMO here : https://www.dropbox.com/s/las74lz5aadok78/UMO_Mark2.rar?dl=0