Martin, I do not have 2 printers to test this but under the machine settings there is a serial port setting.

It is set to AUTO by default.

I think if you change it to point to a specific serial port you should solve your issue.

HTH, Simo.

On Wed, 2018-01-24 at 15:32 +0100, Martin Kolman wrote:

On Tue, 2018-01-09 at 16:39 -0500, Tom Callaway wrote:

...

I'm ready to update the cura-lulzbot stack (and firmware), but in order to do that, I need to get python-uranium-lulzbot into Fedora. The package review is here:

https://bugzilla.redhat.com/show_bug.cgi?id=1532837

Thanks,

~tom _______________________________________________ 3dprinting mailing list -- 3dprinting@lists.fedoraproject.org To unsubscribe send an email to 3dprinting-leave@lists.fedoraproject.org

Couple of random notes/observations/questions about the new lulzbot-cura.

Overall looks nice, the UI has some good improvements (the new printer control UI doesn't look that good for example), more options are available and a lot more stuff is tweekable (printer/filament definitions).

But we have also hit an annyoing issue:

When hitting "connect" Cura now actively probes all usb-serial devices (!) - we have currently 2 printers connected and this can cause the other printer (Rebelix X2 controlled by pronterface) to stop printing and disconnect (!).

The old lulzbot-cura did not do this and we have not yet found any option in the GUI to override this behavior (eq. only ever touch a specific usb-serial device). Do you know about some other way to prevent the autoprobing/autodicsconnect (CLI options/config files) ?

Best Wishes Martin Kolman _______________________________________________ 3dprinting mailing list -- 3dprinting@lists.fedoraproject.org To unsubscribe send an email to 3dprinting-leave@lists.fedoraproject.org

Nevermind, after updating the firmware it started working again, weird that though, the older cura had no problem, but even downgrading to the cura-lulzbot released at F27 GA I was not able to talk to the printer anymore ...

Simo.

On Thu, 2018-04-19 at 12:12 -0400, Simo Sorce wrote:

I just updated to 2.6.69 from testing after tryin the latest stable and I have to report that it does not seem to recognize my Lulzbot Mini. It tries to connect and then brings up a warning that the wrong printer has been detected.

I have to say the new UI is really visually bad compared to the previous one, but it has more knobs so I am trying to convince myself it is OK, but I would like also to be able to actually print.

Ideas ?

Simo.

On Tue, 2018-01-09 at 16:39 -0500, Tom Callaway wrote:

...

I'm ready to update the cura-lulzbot stack (and firmware), but in order to do that, I need to get python-uranium-lulzbot into Fedora. The package review is here:

https://bugzilla.redhat.com/show_bug.cgi?id=1532837

Thanks,

~tom _______________________________________________ 3dprinting mailing list -- 3dprinting@lists.fedoraproject.org To unsubscribe send an email to 3dprinting-leave@lists.fedoraproject.org

-- Simo Sorce Sr. Principal Software Engineer Red Hat, Inc _______________________________________________ 3dprinting mailing list -- 3dprinting@lists.fedoraproject.org To unsubscribe send an email to 3dprinting-leave@lists.fedoraproject.org

On Thu, 2018-04-19 at 16:32 -0400, Tom Callaway wrote:

On 04/19/2018 12:45 PM, Simo Sorce wrote:

...

Nevermind, after updating the firmware it started working again, weird that though, the older cura had no problem, but even downgrading to the cura-lulzbot released at F27 GA I was not able to talk to the printer anymore ...

Yeah, there is a firmware incompatibility with the latest stuff. Should hopefully be a one-time thing.

It would be nice if the pop-up error could hint at upgrading the firmware as something the user may want to look at if they think the error message is "wrong".

Simo.