Mac Repetier and slic3r update

[DaGroundZero]

I am running Repetier 0.56 for Mac. I was running slic3r 0.9.7 with no problems. I decided to try the new slic3r and things went south. I installed the new slic3r in a new folder. I was able to slice my .STL, and all looks okay. I run into problems when I actually try to run the gcode in the Host software. My ext and bed temps lock up, and it is like the Host is waiting for updates and never receives them. My LCD continues to increase, and level out when set temps are reached. The printer does not print.

I was able to slice something using Kiss and run it thru no problems.

I've tried to remove all of the versions of Slicer and Repeiter host and re-install. I have switched back to slic3r 0.9.7 with no help.

Any ideas?

Thanks

[dpmacri]

I am running Repetier 0.56 for Mac. I was running slic3r 0.9.7 with no problems. I decided to try the new slic3r and things went south. I installed the new slic3r in a new folder. I was able to slice my .STL, and all looks okay. I run into problems when I actually try to run the gcode in the Host software. My ext and bed temps lock up, and it is like the Host is waiting for updates and never receives them. My LCD continues to increase, and level out when set temps are reached. The printer does not print.

I was able to slice something using Kiss and run it thru no problems.

I've tried to remove all of the versions of Slicer and Repeiter host and re-install. I have switched back to slic3r 0.9.7 with no help.

Any ideas?

Thanks

Before I switched to an E3D hot-end, I started having a similar problem (also using Mac) where my bed would heat up, but the hot-end never reached the desired temperature (just 1 degree below). What I ended up doing was using the LCD to bump the temp 5 degrees, which would cause it to exceed the original temp to be reached and the print would begin. Then I'd bump it back down using the LCD. Not sure if that's the same problem you're having or not.

[geneb]

dpmacri, that sounds a lot like a PID tuning issue to me.

g.

[dpmacri]

Yeah, that was my assumption, too. And I spent some time tweaking the PID values to try to get it to work, but I never figured it out before my E3D hot-end showed up and enough changed that the problem went away