thopiekar

Like @ahoeben mentioned, we need the logs to see what is happening. By the way, I see you've created links to the AppData directory, are these links hardlinks? It will need a additional library to be implemented to Cura to support Windows links (regular symbolic links). I already added this idea to our bug tracker, but the idea has been killed during the last CBE. In my point of view, without the module "pylnk" it won't be possible to read these symbolic links, but if Windows supports hard links, it might work.

Alternatively you can use USB hubs with ON/OFF switches. Eg. https://www.amazon.com/Generic-7-Port-USB-Hub-Port/dp/B007S642BW

@ahoeben: at least a part of the price goes to Gina. I personally love when sellers are respecting the work of other individuals.

Thanks! Reported it at: https://github.com/Ultimaker/Cura/issues/1166

Thanks you for the report. I'll forward it to our developers. Is your model uploaded anywhere, so we could reproduce it? Thanks again!

Ok, thanks. The reason I'm asking is that I've go currently a idea how to make WiFi printing possible like @neotko expects it to work. Any other setup, like adding a camera, etc., would need a greater investment. Finally buying a RPi, installing OctoPi and adding a webcam, is no problem anymore. I already have a board here lying around, but powering it only for OctoPrint doesn't make any sense to me. I already tried to get OctoPrint running on my NAS and yes, it works great, but my NAS misses the USB-serial converter drivers, so nothing useful at the end. (Yes, it slices!) For those who are interested: https://github.com/thopiekar/octoprint-qnap-qpkg Maybe you're lucky with your UM printers and your QNAP provides the driver for you. Feel free to continue my work in this repository. As it seems that there is no huge interest in a simple printing via WiFi (with SD caching?) solution, I probably should suspend investigations in this direction. However, any new feedback on this is welcome!

Thanks! This info is very useful. How much would you invest for such an upgrade at maximum?

Thank you for your quick reply. How would you like to use your printer at this time? Would it be comfortable for you, you had your PC turned on during your print? Like known when printing via USB? Or would you expect to have your G-Code sent to your printer and have it saved there temporary?

I'm not often here on the forum, but I often saw people asking for additional WiFi printing support. So on the one hand the solution exists to use OctoPrint with @fieldOfView 's plugin. So my question is: Are there people out there, which are still interested in a WiFi printing solution without using OctoPrint? If so, what are your reasons? Which printer do you own? What would you expect from the WiFi printing addon? Where would you like to use your WiFi-powered printer? Would you mind, if the data transfer is not encrypted inside your network, when your printer is connected to your access point? Regards

@nallath: I guess what they want is to do the same as I did today with CATIA to import CATPart files in Cura (see JIRA). @daya: If I get you right and you want to call Cura via COM API, then I guess the answer is no. We would need to add support for this first.

Saw your PR on GitHub - well done. But there are some questions left... Why do you install all dependencies via yum? cura-build is able to compile all of them for you. Of course this is not needed, but this way you can be sure that you are running under the same tested conditions (while thinking of the dependencies). But so far, thank you for sharing your experiences with us.

The installers for Windows come with 64bit specific file which can't be executed. The message could be misleading as the file could be there but couldn't be executed. However, there is nothing wrong to run Cura on 32bit. On Ubuntu it is running on 32bit well.

As I my PPA is mentioned in different places, I just thought to open a topic here for all questions and discussions related to it. Here a short summary of it: It is a personal project and Ultimaker does not give any support on it. (Not mentioned in the FAQ) The benefit compared to the "fat bundle" provided by Ultimaker is that some software dependencies get installed multiple times on your installation when using the "bundle" by Ultimaker. Using my PPA you only install Cura. When looking at the upcoming 2.2 release (currently "master") you'll need to upgrade PyQt5 to 5.5, but it is available in the "master" PPA, too. There are two PPAs: One for stable (2.1) builds and one for weekly builds (what you know as "master" on GitHub. Updates and bugfixes for the current stable release (2.1) are sometimes earlier provided than by Ultimaker The weekly builds are not meant to be used for daily use, of course! I need to prepare the package updates manually, so sometimes builds might be delayed. Installation guide: https://thopiekar.eu/cura/ppa/installation/ Uninstallation guide: https://thopiekar.eu/cura/ppa/uninstallation/ Technical info and support https://thopiekar.eu/cura/ppa/technical-information/ Have fun!

That's not true. If you remove these packages APT could (!) probably decided to remove one of your preferred applications. Meta-packages are only depending on others and they are empty. Sometimes they come with some settings which are used to add some branding, but this is the maximum they do. In my case I don't use any kubuntu* meta-packages and everything works well However, to be sure we don't break anything I would prefer to disable the service. Ah, I thought it is only containing lowercase letters, but it should be: sudo systemctl disable ModemManager.service Systemd is managing all services on your computer (at least since the last 2 Ubuntu releases). Now it is default and should have been replaced Upstart.

There should be no problem using a USB v3 port. "dmesg" even says that your printer's board was found and ttyACM0 was created! Which desktop are you using? I had a similar problem in the past and I guess something might left during an upgrade that the service "modemmanager" is catching your printer and locks the connection. See: http://stackoverflow.com/a/33855995/6333993 But I would prefer to use "sudo systemctl disable modemmanager" to disable the service and reboot. Uninstalling modemmanager is also possible, but some "meta-packages" might depend on it. Finally: If "dmesg" says there is ttyACM0 there should be ttyACM0. Maybe in use or not accessible during any restrictions (which need to be disabled), but it really should be there.

Thanks! And what says: $ ls -la /dev/ttyACM* and $ groups

PS: There is also a PPA built from "master" with nightly builds. If you like you can check out whether your problems will be fixed in the future 2.2 release. https://launchpad.net/~thopiekar/+archive/ubuntu/cura-master But keep in mind: Don't report any issues using these packages to the Ultimaker support. This is still work-in-progress. If you want to use 2.1 again after using this PPA. Remove all cura packages, remove all local settings again, deactivate the "master" PPA and reinstall 2.1 from the "stable" PPA.

That's strange. Please copy from the log some more lines. It is possible that there are other messages related to this problem. Thanks!

Thanks! You'll need to run cura from the console. Just type in "cura" or check the logs at ~/.local/share/cura. Well, I wouldn't call the hardware "bad". It is absolutely able to do the job(!). Unfortunately Cura is just not able to flash the board. There could be different reasons: 1. There is a bug in Cura. 2. You don't have permissions to flash your Ultimaker! (and sadly Cura doesn't tell something about this). Make sure your user account is member of the "dialout" group. (It is also possible that I made other changes here in order to flash my Arduinos.) Please add a issue report on this at GitHub plus your model. I've got here one from an different site, which is >200MB, and I use that file often as the "worst case", when testing new Cura features. Again, report this on GitHub + append your model + add your error message. No problem. This is also something I worry about: If you are unlucky your are mixing new with old configurations by upgrading and downgrading again. You will need to make a full cleanup to make sure that there are no new settings that might confuse the "old" Cura. Remove ~/.config/cura and ~/.local/share/cura for this (there might be other locations for the old Cura).

@MEgg, if SuSE 13.1 uses Python 3.4 as default, you can better invest time into getting "cura-build" to create RPM packages or at least .tar.gz binary bundles.

Someone just made a PR with a OctoPrint Plugin. I'm sure you want to test it.

Great to see my PPA is useful for you The problem with the missing dependencies has been solved. You can mark these packages as "automatically installed" by "apt-mark auto ", so they will be removed in case they won't be needed in the far future. (Just in case..) @asb I can confirm it works great here, BUT it might be possible that your old settings are playing on your nerves. So I recommend to remove ~/.config/cura/* and ~/.local/cura/*. If there are important changes you've done to your profile(s) make sure you export them before removing these directories. Removing them will do a "factory reset".

Don't have OctoPrint installed, so I can't give you any details on that. But you can join the conversation at https://ultimaker.com/en/community/6083-connect-to-octoprint-from-cura and discuss. I would love to hear whether it is working or not