Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maker Select 3D/Cura 2.3/2.4 «The printer is not connected» #1434
Maker Select 3D/Cura 2.3/2.4 «The printer is not connected» #1434
Status: Won’t Fix/Do Not an issue, or an issue that we cannot fix or can live with. Type: Bug The code does not produce the intended behavior.
Comments
win10 64Bit, selected a Prusa i3 but also tried to create a custom printer to no avail, Works fine on Cura 15.0.4.6 and I confirmed I can communicate w/ COM3 at 115200. It seems others have this same issue and I’m not sure where to look. Looking at the log files in USBPrinting don’t even mention it looking to any port. It appears this is all auto configured now but I cannot find a log indicating what it is trying to do or where it is failing.
I’ve attached the two log files I’m aware of that may have something to do with this but any other help would be appreciated.
The text was updated successfully, but these errors were encountered:
It should be saying something like:
2017-02-17 12:29:51,659 - DEBUG - USBPrinting.USBPrinterOutputDevice._connect [308]: Attempting to connect to /dev/ttyACM0 2017-02-17 12:29:52,277 - DEBUG - USBPrinting.USBPrinterOutputDevice._connect [322]: Attempting to connect to printer with serial /dev/ttyACM0 on baud rate 115200 2017-02-17 12:29:58,798 - DEBUG - USBPrinting.USBPrinterOutputDevice._connect [322]: Attempting to connect to printer with serial /dev/ttyACM0 on baud rate 250000 2017-02-17 12:30:00,311 - DEBUG - USBPrinting.USBPrinterOutputDevice._connect [348]: Correct response for auto-baudrate detection received. 2017-02-17 12:30:00,321 - INFO - USBPrinting.USBPrinterOutputDevice._connect [355]: Established printer connection on port /dev/ttyACM0 What version of Cura are you using? We haven’t released any version 3.21.
My mistake guys. I had to zip them as they didn’t support uploading the logs directly. I attached them to the first post. I certainly didn’t see any USB printing lines in the logs when i looked but maybe I’m looking at the wrong logs.
You can find the logs by going to Help -> Show Configuration Folder. . An explorer window should open, and the folder will contain a file named «stderr.log». That’s the one we’re interested in.
Yeah Sorry I fixed it, hoped to fix it before anyone replied LOL.. stderr.log added to the zip. I only see reference to the usbprinting plugin loading but nothing else.
The log doesn’t mention any attempt to connect via USB at all, like you said. Ctrl+F on «USB» yields 9 results, all of which are about the plug-in being loaded at program launch.
One thing that you can try is to remove other Arduino-like devices from your computer (other than your 3D printer). Then restart Cura. It sometimes gets confused by other devices that speak the Arduino protocol.
Also, during the installation of Cura, did you select to install the Arduino drivers in the install wizard? It’s on by default (so the drivers get installed) but if you turned it off that would explain why it can’t make a connection. Perhaps it’s worth trying to re-install. You shouldn’t lose any settings unless you install an older version than what you had.
I have nothing else attached to any port aside from a USB keyboard/mouse. This pc has no other COM ports (Internal or external) either. Yes it did install the arduino driver. I assume that driver controls the internal serial port in my printer (Must be an arduino board?) I’ve saved my machine config which is the only thing I’d hate to lose so I’ll give it a go and report back. You’d think even w/o a driver installed it’d still try to talk to the COM port and maybe just have overrun or other communication issues. It’s not even attempting to connect.
Update
Completely removed Cura, removed all remnants in appdata, etc and installed 2.4 which is now out and the problem persists. It doesn’t even seem to attempt to communicate w/ any port or even search.
One oddity I noticed is that installing device driver pops up after I reinstalled 15.04.6 when 2.4 wouldnt see the printer. This does NOT pop up during the 2.3 or 2.4 install. I doubt it matters as the driver is already installed but something I figured I’d mention.
Also, the auto setting does not work in 15.04.6 for me either but the second I specify the COM port and the baud rate it sees it fine. I wish there was a way to just specify a COM port.
It’s correct that the device driver installation doesn’t pop up the second time (I think). The Arduino driver software hasn’t been updated for Windows for quite some time. Though I thought that the driver was updated like 1 year ago and we incorporated that change in Cura too.
There is very little we can do about this since we don’t have this Maker Select 3D, nor do we release a Cura v3.21. I hope that someone with this printer can verify this issue and propose a fix.
The thing is I’ve uninstalled 15.04.6 and reinstalled twice, each time it has reinstalled the driver. 2.x installs haven’t once attempted or requested to reinstall the driver. Not sure it matters but it’s like 2.x isn’t even looking for any device as the logs show so its not like it matters what device I’m using. It’s just trying to talk to a COM port as far as I understand so the actual device shouldn’t matter much should it? I made a mistake it was 2.3 and 2.4 I tried. No idea where I got 3.2.1 from. I’ve fixed the topic title. I’ve installed cura 2.4 on another pc i’ve got here and it’s the same situation, no reference to usbprintingoutputdevice.
Can someone who has a working printer perhaps paste in the contents of the files in the AppData\Local\cura\user and machine instances folders in windows? I’m unsure where it would be in other OSes
Probably you mistyped «2.3.1». In any case, the reason you’re not seeing a dialog for 2.x installs is that we use the silent install option of the installer. It should still install the driver though.
YEah I did mistype. I fixed the title but it ins’t reflecting this. Even if it is installing a driver there is no mention of it even trying to call the device in the logs.
Same issue here on windows 10 in 2.4, it doesn’t even seem to be trying to open a connection to anything. Repetier host works, simplify3d works, pronterface can connect, cura 15 can connect but only when the com port is specified.
2.4 on Windows 8.1 will connect whenever it feels like it which is generally never when I want it to (like right after I’ve closed the connection in repetier host) and never when I actually want it to. Almost like it’s the scared little kid at school always looking to the cool kids to know whose jokes to laugh at and where the good spots are to hang out, i’ll only connect to something after the cool kids have connected to it.
I think we’re just stuck on an old version. Regardless of the printer model I assume this would the same result given it doesn’t even try to look for anything on any port.
yeah I’m not using a maker select, I’m using a couple of mendel90’s. It was better when they gave you the option to which serial port to connect to back in cura 15, at least that worked.
Agreed. I’m going to see what this does in different OSes and see if I at least can see in the logs if the problem follows the OS or not.
There’s discussion here: https://www.reddit.com/r/3Dprinting/comments/5g76cs/confused_about_usb_printing_in_cura_231/ on making it list other devices rather than only usb ones but even that doesn’t work for me now so I don’t know what’s changed from 2.3.1 to 2.4 if anything (may be one of the many auto silent updates windows 10 does to itself)
I’ll read up on this. I’ve not gotten any 2.x versions to work.
Dave
I did make some progress. I changed the line def getSerialPortList(self, only_list_usb = False): to True and checked the registry key it is referencing. The COM port is there and it listed as \Device\VCP0. The fact that is says it is not arduino based tells me it is talking. Not sure why it says it is not arduino based however. Wonder if I need to use a different driver. Right now it’s using an FTDI supplied driver (v. 2.12.24.0) , I believe it is the driver installed via cura 15.x but I could be wrong.
It now is trying to communicate as it resets my printer when Cura loads.
Pertinent log info:
2017-03-02 01:48:43,527 — INFO — USBPrinting.USBPrinterOutputDevice._connect [305]: Could not establish connection on COM3: ‘Timeout’. Device is not arduino based. 2017-03-02 01:48:43,529 — DEBUG — USBPrinting.USBPrinterOutputDevice._connect [318]: Could not open port COM1 2017-03-02 01:48:43,533 — DEBUG — USBPrinting.USBPrinterOutputDevice._connect [312]: Attempting to connect to printer with serial COM3 on baud rate 115200
The time-out occurs when we get a package with length 0 or lower from the serial port. That message is then interpreted as a time-out on the serial port which is then interpreted as the device not being something we can talk with.
I did make some progress. I changed the line def getSerialPortList(self, only_list_usb = False): to True and checked the registry key it is referencing. The COM port is there and it listed as \Device\VCP0.
Mine was in there and it was called \Device\Serial2 and not even that only_list_usb change would make it see it, it still didn’t even try to open communications. My board was a CH340 based usb-serial chip.
Assuming we are talking about the same issue, turns out this is a really silly bug. Under USBPrinterOutputDevice in _connect, Cura first tries to detect an arduino device using this avr_isp library called stk500v2 . However, if this method fails, Cura never closes the port that this library uses. Every attempt to access the port at the different baud rates later in the function results in a «Access is denied» because Cura is stilling holding the port. I solved my problem by changing the following lines in USBPrinterOutputDevice.py:
programmer = stk500v2.Stk500v2() try: programmer.connect(self._serial_port) # Connect with the serial, if this succeeds, it's an arduino based usb device. self._serial = programmer.leaveISP() except ispBase.IspError as e: Logger.log("i", "Could not establish connection on %s: %s. Device is not arduino based." %(self._serial_port,str(e))) except Exception as e: Logger.log("i", "Could not establish connection on %s, unknown reasons. Device is not arduino based." % self._serial_port) programmer = stk500v2.Stk500v2() try: programmer.connect(self._serial_port) # Connect with the serial, if this succeeds, it's an arduino based usb device. self._serial = programmer.leaveISP() except ispBase.IspError as e: programmer.close() Logger.log("i", "Could not establish connection on %s: %s. Device is not arduino based." %(self._serial_port,str(e))) except Exception as e: programmer.close() Logger.log("i", "Could not establish connection on %s, unknown reasons. Device is not arduino based." % self._serial_port) It’ll be up to the Ultimaker team to finalize and bulletproof the fix, but this is what the problem is. In the meantime, my Printrbot Play is connecting just fine now. 😄