Jump to content

Cura rc2 / rc3 - OSX 10.6.4 - crash on GCode gen


jonjude

Recommended Posts

Posted · Cura rc2 / rc3 - OSX 10.6.4 - crash on GCode gen

Hi- I've followed the following path so far on a MacBook Pro running 10.6.4, and

I get same behavior for RC2 and RC3. Any suggestions ? Did miss something on the way ? Do I have to set Platform

Preferences somewhere ?

So far I've got to :

* Install the Python 2.7.3 dmg package so "python -V" returns with the 2.7.3 version number.

* Set the environment VERSIONER_PYTHON_PREFER_32_BIT=yes

* Install the wxPython 2.9.x for Python 2.7 dmg (targets the 2.7 install location)

* Try run Cura and get : need PyOpenGL

* By hand run the PyOpenGL-3.0.2a5 python install (targets the 2.7 install location)

* Set PYTHONPATH to include OpenGL location

* Try run Cura and get : need pyserial

* By hand run the pyserial-2.6 python install (targets the 2.7 install location)

* Set PYTHONPATH to include pyserial location

Printrun seems so far to work - RC2 and RC3 - for startup & function (connect, etc).

Cura starts & I go through initial setup and get Simple Window.

At stl model load I get :

Python[634] *** __NSAutoreleaseNoPool(): Object 0x11d40d4c0 of class NSConcreteMapTable autoreleased with no pool in place - just leaking

Can choose STL file from popup window (no preview) and then STL loads to give 3d view in Cura xyz view.

When I try to Slice to GCode I get :

Traceback (most recent call last):

File "/3Dprinter/osx64-Cura-RC2/Cura/gui/simpleMode.py", line 265, in

OnSlice

spp = sliceProgessPanel.sliceProgessPanel(self, self, self.filename)

File "/3Dprinter/osx64-Cura-RC2/Cura/gui/sliceProgessPanel.py", line 64,

in __init__

p = subprocess.Popen(sliceRun.getSliceCommand(self.filename),

stdout=subprocess.PIPE, stderr=subprocess.STDOUT)

File "/3Dprinter/osx64-Cura-RC2/Cura/util/sliceRun.py", line 116, in

getSliceCommand

pypyExe = getPyPyExe()

File "/3Dprinter/osx64-Cura-RC2/Cura/util/sliceRun.py", line 10, in

getPyPyExe

if platform.system() == "Windows":

AttributeError: 'module' object has no attribute 'system'

Hoping someone might have an idea ...

  • Link to post
    Share on other sites

    Posted · Cura rc2 / rc3 - OSX 10.6.4 - crash on GCode gen

    Hi,

    After searching some on Python discussion turns out I didn't need to

    set PYTHONPATH at all.

    Just need to specify 32bit.

    Confirm that RC2 and RC3 of Cura seem to work fine on MacOs OSX 10.6.4, using

    Python 2.7.3, python-2.7.3-macosx10.6.dmg

    wxpython2.9, wxPython2.9-osx-2.9.3.1-cocoa-py2.7.dmg

    PyOpenGL, PyOpenGL-3.0.2a5 (tar.gz)

    pyserial, pyserial-2.6 (tar.gz)

    Regards,

    JJude

  • 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
    • Our picks

      • UltiMaker Cura 5.7 stable released
        Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more. 
         
          • Like
        • 11 replies
      • S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
        (Sorry, was out of office when this released)

        This update is for...
        All UltiMaker S series  
        New features
         
        Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
          • Like
        • 0 replies
    ×
    ×
    • Create New...