Solved Matter Control stuck on "Attempting to connect"

Ive been trying to get a old robo 3d r1 printer to work, so I got my old linux computer and installed mattercontrol, when I follow the instructions to the tee and the programs starts to connect, it just gets stuck on "attempting to connect". Any help?

EDIT: Manual connection also does not work

EDIT 2: All objects in queue say connection failed: unknown reason

 

Alright, will try later. I did do manual setup and the port i connected to is around the lines of "dev/tty/A__0" (dashes means i dont know.) If the port is broken, then well rip, if its the software, then ill go try cuda on a different pc.

 

I had the same problem with my new Robo R1+ under Ubuntu (16.04 and 17.04). I haven't resolved the issue, since I switched over to macOS to do the initial setup, then (per my original plan) hooked the printer up to a Raspberry Pi running OctoPi. This configuration works fine. (Note that OctoPi is Linux-based, so it's not a question of Linux being incompatible with the printer.) My suspicion is that the Arduino board in the printer requires the computer to send it firmware that's not installed by default in Ubuntu (and presumably by whatever distribution you're using, if it's not Ubuntu). In fact, Googling it, I found this page with instructions on setting up several Linux distributions to work with Arduino boards, so maybe you could follow those instructions and get it to work.

 

In the audrino IDE, it says board at com 1 is not avalible, and it just loads in mattercontrol

 

I tried them seperately.

 

the error always appears no matter if its plugged in to the printer or not

 

on my windows, the IDE does the exact same thing with nothing attatched

 

Are you using the Arduino IDE from the same Linux box connected to the printer? If so, then that test won't get around a lack of firmware files in Linux, if that's what's causing the problem. Try plugging the printer into a computer running macOS or Windows. (Windows requires loading some drivers, IIRC.) Even if you don't want to use macOS or Windows for printing, this test will help isolate the problem -- if the other OS can talk to the printer, then you know the printer's hardware is OK; but if not, chances are you're looking at a fault in the printer hardware (or maybe a cable, if you use the same cable).

 

I found the culprit for my own instance of this problem, and it's one of those things that makes me cringe that I didn't think of it immediately: Device file permissions. When you plug in the printer, Linux creates a device file for it -- /dev/ttyACM0, with ownership by root:dialout on my system (running Ubuntu). As my normal user account was not a member of the dialout group, I did not have access to this file, so although MatterControl found the device file, it was unable to communicate through it. The best solution in this situation is to add yourself to the dialout group. When I did that, MatterControl was able to connect. (I had to log out and back in again, although I think there's a command that'll do the trick more elegantly than that.)

Note, however, that ownership and permissions rules vary from one distribution to another. Thus, if you're using something other than Ubuntu, you may need to add yourself to some group other than dialout or even create a custom udev rule to get it to work. If you need help with this, I can provide it, but I'll need information from you such as the distribution you're running, the permissions and ownership on /dev/ttyACM0 (or whatever device file Linux creates for the printer), and your ordinary user's group memberships. Running MatterControl as root would be another way around the problem, but that's hideously unsafe from a security point of view, and it'll create ownership headaches on any files that MatterControl creates, so I strongly recommend against doing it that way, except perhaps for a brief test if you can't get it to work by adjusting your group membership.

Also, note that I tried adding the Arduino packages suggested by the site to which I linked earlier before noting the permissions issue, so there's a possibility that these packages are required, too.