I have been using a laptop to print on my Lulzbot mini (1) but I’d prefer to not have that particular laptop tied up the entire time I’m printing.
I’m trying to get things set up on one of my other laptops, however, when I install everything I get to the point where I plug the machine in and I get the “Wrong Machine” error.
"Firmware reports printer type doesn’t match the printer you’re trying to connect to… "
Note, my laptop running Cura LE version 4.13.5 works with the printer just fine.
When trying to run Cura LE 4.13.10 (newest I got) from two other laptops I’m getting the wrong machine error.
Hey man just wondering. I used to have all the drivers set up and everything for my lulzbot mini, but i tried getting it going again on a brand new laptop, and I’m trying to find all the files I need to start using cura. I have cura for lulzbot on the newest version, but I cant seem to connect the printer to my computer. I remember something about having to install drivers to get my old computer to recognize the printer, but the only information I can find now when I try and look it up is for the taz 100 and 101. It also could just be the cord I’m using because it was from a cheap geetech printer, but aside from that I just wanted to make sure my computer has all the right software. Any help would be greatly appreciated.
The 100 and 101 are ancient machines. Like 2012-era printer ancient.
The Mini uses a simple Serial/COM port communication, which should not require any drivers.
If you have issues connecting, it might be some drivers you’ve installed that are interfering, a bad serial cable, a bad USB port, or that you need to manually assign the COM port in CuraLE instead of letting it auto-detect.
I believe the Lulzbot version of Cura installed all the needed drivers for me.
I think my issues were fixed by connecting the printer and having the software update the printer firmware to the newest setting(s). I think my computer might not have been registering the connection (cura couldn’t “see” it) but it still managed to update the firmware. Then everything worked.
(*Note, you’re supposed to record some defaults for the printer before updating firmware but I’ve been OK so far since those defaults haven’t been changing when I update…)