Cura does not connect to network printer if the printer wasn't started before Cura

[klaus_kraemer 0]

Sometimes it's quite annoying - why does Cura only recognize an UM3 when the UM3 is already switched on before Cura got started?

If you have Cura already running and switch on your UM3 afterward, Cura won't connect to the UM3.

If Cura has been started before the printer has been switched on there is only one solution: close Cura, switch on your UM3 and then restart Cura. Not very convenient...

Edited July 1 by klaus_kraemer

[ultiarjan 1,097]

I agree it's a pain, did you try "manage printers" and just refresh? easier than restarting cura.... but again I agree this should not be necessary....

 

[ahoeben 473]

What OS are you using? Does it matter how long Cura has been running before it stops recognising new printers? Is it a consistent thing or just sometimes?

[klaus_kraemer 0]

8 hours ago, ahoeben said:

What OS are you using? Does it matter how long Cura has been running before it stops recognising new printers? Is it a consistent thing or just sometimes?

 

It's Windows 10, the "thing" is very much consistent and can be reproduced by 100%. No , it does not matter how long Cura has been running - it's simply about the order what's been started / switched on first.

 

You start Cura before switching on the printer, Cura's only offered choice is "Save to File"...

 

9 hours ago, ultiarjan said:

I agree it's a pain, did you try "manage printers" and just refresh? easier than restarting cura.... but again I agree this should not be necessary....

 

 

Never tried this, because I didn't connect "managing" Printers to the problem. Sure will try these days as a workaround.

[nallath 574]

Yay for windows issues. This is actually an issue with Windows which caches certain things. It should re-do it after 30 minutes, but I can understand people not wanting to wait for that.

[klaus_kraemer 0]

Quite hard to believe there shouldn't be a way to get around this behaviour. Ok there's no printer driver for UM3 as far as I know, But continually testing an IP connection should be feasible anyway...