Jump to content
Ultimaker Community of 3D Printing Experts
Sign in to follow this  
czucker

ReplicatorG can't connect to my Ultimaker

Recommended Posts

Update: The same exact errors occur in both Ubuntu and OS X (10.7.4). I can see the com port and update firmware, just not connect.

Hi,

I just finished building my Ultimaker and installed ReplicatorG.

I've set the driver and port, but can't get the software to connect.

When it tries to connect I can here the Z motor whirring, but that's it.

ReplicatorG gives the following error:

[22] Ultimaker not responding to RTS reset. Failed to connect after 4 attempts.
[22] Supports RC

Any thoughts?

Thanks,

Chris

Share this post


Link to post
Share on other sites

I managed to get Crua 12.07, and RepG, working under OS X.

The NetFabb demo connected on the first try.

I still can't get Cura 12.08 to work though. When I try to connect to the Ultimaker in the first run dialog the motors tense up every few seconds and then I get the error above.

I'll poke around when I have a moment and supply more info, but I believe that I'm running the latest version of Ubuntu (in a VM). I'll try re-installing Python as well.

Now that this seems to be isolated to a problem with Cura, can this thread be moved to the appropriate area?

Share this post


Link to post
Share on other sites

I checked my OS X install and it looks like the only version of Python installed is 2.7.

Slicing to gcode, hitting print and then connect produces the following in 12.08. 12.07 still works fine for me.

 

Last login: Thu Oct 25 22:18:51 on ttys003 Kitchens-MacBook:~ tv$ /Users/tv/Downloads/Cura/cura.command ; exit; objc[40627]: Object 0x10a129f30 of class NSConcreteMapTable autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug Exception in thread Thread-1: Traceback (most recent call last): File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 530, in __bootstrap_inner self.run() File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 483, in run self.__target(*self.__args, **self.__kwargs) File "/Users/tv/Downloads/Cura/Cura/gui/printWindow.py", line 460, in PrinterMonitorself.machineCom.sendCommand("M105") File "/Users/tv/Downloads/Cura/Cura/util/machineCom.py", line 178, in sendCommand self.serial.write(cmd + '\n') File "build/bdist.macosx-10.7-intel/egg/serial/serialposix.py", line 489, in write raise SerialException('write failed: %s' % (v,)) SerialException: write failed: [Errno 9] Bad file descriptor  

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Our picks

    • Taking Advantage of DfAM
      This is a statement that’s often made about AM/3DP. I'll focus on the way DfAM can take advantage of some of the unique capabilities that AM and 3DP have to offer. I personally think that the use of AM/3DP for light-weighting is one of it’s most exciting possibilities and one that could play a key part in the sustainability of design and manufacturing in the future.
        • Like
      • 3 replies
×

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!