Cura exporting empty gcode

[Local 0]

I'm having a lot of trouble getting Cura to do... anything.

Every time I save a gcode, print, sent to sd path etc: I get a gcode file that reads only "Connect to 127.0.0.1:49674 failed"

I've tried so many configurations, so many installations and versions of cura and loads of different files.

I've spent 13 hours non stop on this now and I think its time for somebody to tell me I'm doing something dumb =(

Anybody?

[DidierKlein 729]

What version of Cura?

What printer? Over Usb i guess?

[nallath 1,120]

Disable your firewall.

[Local 0]

Completely forgot I'd written this =/

Thanks for the replies.

The answer in case anybody needs it was simple. I just needed a completely new operating system. I only wish I was told before I spent my life savings on the printer doh!

RE: disabling the firewall... What??? If that were the case Cura would be immediately removed from my machine and the printer sold.

[nallath 1,120]

RE: disabling the firewall... What??? If that were the case Cura would be immediately removed from my machine and the printer sold.

 

Huh? Why? Some firewalls simply have a far to aggressive policy, so they block local sockets. It's a fairly standard means to connect one bit of software with another.

Edited February 17, 2016 by Guest

[Local 0]

Huh? Why? Some firewalls simply have a far to aggressive policy, so they block local sockets. It's a fairly standard means to connect one bit of software with another.

 

That'd be very different, opening internal sockets and disabling my firewall are two different things. I am very conscious of the software running in my machines. Anything that wants out without me asking it to gets the boot.

I apologise for misunderstanding your meaning.

Edited February 17, 2016 by Guest

[nallath 1,120]

That'd be very different, opening internal sockets and disabling my firewall are two different things. I am very conscious of the software running in my machines. Anything that wants out without me asking it to gets the boot.

I apologise for misunderstanding your meaning.

 

Yeah, but explaining people how to open internal sockets is hard (and depends on the firewall in question). Telling them to (temporarily) disable the firewall is easy

Cura doesn't need external access / data to do its thing and I want to keep it that way.

[Local 0]

Yeah, but explaining people how to open internal sockets is hard (and depends on the firewall in question). Telling them to (temporarily) disable the firewall is easy

Cura doesn't need external access / data to do its thing and I want to keep it that way.

 

Hear hear. I agree. Unfortunately it's way too easy to disable a firewall. That's why I first misunderstood you. In almost every tech forum I've been on "Disable your firewall/antivirus" is up there with "Reinstall Windows" as an answer to anything.

"My fuse blew in my monitor"

"Have you tried disabling your antivirus"

"My friend had this, he had to reinstall his Windows"

etc: =D

It's good to hear you're keeping Cura grounded. The one thing I've been really happy with it with so far is it doesn't need installing either. I hope it stays that way too.

Edited February 17, 2016 by Guest