[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4693: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4695: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4696: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4697: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
Printrbot Talk Forum • View topic - If you get "commands waiting" and can't connect...

If you get "commands waiting" and can't connect...

Need help troubleshooting hardware issues... talk here

If you get "commands waiting" and can't connect...

Postby mreiben » 2012-Jun-Thu-20-Jun

I have been searching for two days to try to fix this and I hope that a few people here might have an answer. I am using a printrboard on a prusa mendel build, and all of the hardware is connected and ready to go, but I can't seem to make the next easy step of connecting the printer to my computer.

I have installed pronterface on windows, osx and ubuntu, and in each environment I have been unable to connect to my printer. On windows only "com3" shows up as a port, but it wont connect at any baud rate. On the mac tty.usbmodem12341 is an option, but it also will not connect at any baud rate.

The "getting started" documentation seems to suggest that downloading pronterface and slic3r should boot right up, but I have been struggling. Any advice?

Thanks!
  • 0

mreiben
Waiting to connect to printer...
 
Posts: 2
Joined: 2012-Jun-Thu-20-Jun
Reputation: 0

If you get "commands waiting" and can't connect...

Sponsor

Sponsor
 

Re: Pronterface says "connecting..." forever

Postby pocketscience » 2012-Jun-Thu-22-Jun

Assuming you've checked all the obvious stuff like 12V power to the board (green LED is on) it sounds like it might be a HW fault.


G.
  • 0

printrbot backer #147
pocketscience
Solid infill...
 
Posts: 229
Joined: 2011-Dec-Wed-04-Dec
Location: Sydney, Australia
Reputation: 0

Re: Pronterface says "connecting..." forever

Postby ecnelutalf » 2012-Jun-Thu-22-Jun

At least for windows have you installed the necessary file: http://pjrc.com/teensy/serial_install.exe
Be sure to install as administrator.

Also, I have found that I need to boot up in the following order.
1.) Turn on power supply first
2.) Plug into computer
3.) Open Pronterface

Any deviation will leave me with the connecting message....

Hope this helps
  • 0

ecnelutalf
I'm an end stop.
 
Posts: 51
Joined: 2012-Mar-Tue-20-Mar
Reputation: 1

Re: Pronterface says "connecting..." forever

Postby pocketscience » 2012-Jun-Thu-23-Jun

There's nothing extra to install for Mac (that's what I'm using), so the fact he sees the same issue on all platforms suggests something more than installing the FTDI drivers for Windows - although it's a good point to confirm. On my Mac I don't have to follow any set procedure to connect to my board and overall the Printrboard/pronterface connectivity seems pretty stable.


G.
  • 0

printrbot backer #147
pocketscience
Solid infill...
 
Posts: 229
Joined: 2011-Dec-Wed-04-Dec
Location: Sydney, Australia
Reputation: 0

Re: Pronterface says "connecting..." forever

Postby ecnelutalf » 2012-Jun-Thu-23-Jun

Try this. Disconnect and turn off power. Then unplug your Y-end stop. Then try connecting.
  • 0

ecnelutalf
I'm an end stop.
 
Posts: 51
Joined: 2012-Mar-Tue-20-Mar
Reputation: 1

Re: Pronterface says "connecting..." forever

Postby scantrontb » 2012-Jun-Fri-03-Jun

  • 0

Don't planto mihi adveho illac
PB+ #786
User avatar
scantrontb
Can update firmware
 
Posts: 825
Joined: 2011-Dec-Sun-14-Dec
Location: federal way, wa
Reputation: 5

Re: Pronterface says "connecting..." forever

Postby monstermark » 2012-Jun-Fri-06-Jun

I have the same issue. If my y-axis is not at 'home' then I cannot connect. It made me crazy until I finally figured out it was the end-stop causing the issue.
  • 0

monstermark
Loading filament...
 
Posts: 22
Joined: 2012-Apr-Sat-22-Apr
Reputation: 0

Re: Pronterface says "connecting..." forever

Postby jr57k » 2012-Jun-Fri-07-Jun

2 points

1) the printrboard doesn't use the FTDI USB to serial chip like most other older arduino based solutions. It uses a different ATMEL chip for the main processor that doesn't rerquire this intermediate chipset but instead has a VCP built in. Based on your comment about COM3 I'm guessing you hadn't loaded the proper driver per the instructions page on printrbot.com. Once you do that another serial port should present itself, usually something higher than COM4 (mine is 14 for example). It's a much better solution with fewer errors and better stability. BTW 115200 is what you should be aiming for on the connection speed.

2) while not directly related to your problem of connecting, I have had to unplug the board and plug it back in (do this at the computer end please to avoid breaking the micro USB connector on the board itself) when I abort a print by turning the power supply off and back on again. The board when it reboots doesn't like to talk through the stale connection that was present before the power cycle. I thought I'd mention it because it's a little nagging thing that may be tripping some people up.
  • 0

jr57k
Layer 300 of 1234
 
Posts: 320
Joined: 2012-Apr-Sat-18-Apr
Location: Augusta, GA
Reputation: 0

Re: Pronterface says "connecting..." forever

Postby pocketscience » 2012-Jun-Fri-08-Jun

  • 0

printrbot backer #147
pocketscience
Solid infill...
 
Posts: 229
Joined: 2011-Dec-Wed-04-Dec
Location: Sydney, Australia
Reputation: 0

Re: Pronterface says "connecting..." forever

Postby monstermark » 2012-Jun-Fri-10-Jun

  • 0

Last edited by monstermark on 2012-Jun-Thu-17-Jun, edited 3 times in total.
monstermark
Loading filament...
 
Posts: 22
Joined: 2012-Apr-Sat-22-Apr
Reputation: 0

Re: Pronterface says "connecting..." forever

Postby mreiben » 2012-Jun-Fri-13-Jun

I have rev. c, and according to the seller it is tested with merlin firmware pre-installed. Could a firmware problem be causing this?

Thanks for the replies so far, as soon as I get home I will check the drivers that I installed, do a calculated power-reboot cycle, and try disconnecting the y-axis endstop.
  • 0

mreiben
Waiting to connect to printer...
 
Posts: 2
Joined: 2012-Jun-Thu-20-Jun
Reputation: 0

Re: Pronterface says "connecting..." forever

Postby monstermark » 2012-Jun-Fri-13-Jun

I have a rev b and rev c board.

Funny thing is this same thing happens on the rev c board.

Try this;

before you power on the power supply or connect the USB to your computer make sure the y-axis is at home.

Next turn on the power supply.

Then connect the usb.

Now click the connect in pronterface.

You should connect just fine.

The limit switch is n/c (normally closed) when it is not depressed, I have a belief that this is causing an issue with the board. There are others with rev c and the same issue.

I have just learned to live with it since it only bugs me when I forget to home the axis before I connect.

Good luck.
  • 0

monstermark
Loading filament...
 
Posts: 22
Joined: 2012-Apr-Sat-22-Apr
Reputation: 0

Re: Pronterface says "connecting..." forever

Postby ecnelutalf » 2012-Jun-Fri-13-Jun

I have a rev C board too. I also have the problem that I cannot disconnect the USB port during an SD print or I lose power to the board.

I PM'ed Laine about it and he said it may be the version of the firmware put on it. His works fine, but the vendor may have inadvertently used a slightly larger firmware install that exceeds the space capacity of the board. Some of the code would be left out, not enough to make it not work, but will create problems.
  • 0

ecnelutalf
I'm an end stop.
 
Posts: 51
Joined: 2012-Mar-Tue-20-Mar
Reputation: 1

Re: Pronterface says "connecting..." forever

Postby scantrontb » 2012-Jun-Fri-14-Jun

  • 0

Don't planto mihi adveho illac
PB+ #786
User avatar
scantrontb
Can update firmware
 
Posts: 825
Joined: 2011-Dec-Sun-14-Dec
Location: federal way, wa
Reputation: 5

Re: Pronterface says "connecting..." forever

Postby lwalkera » 2012-Jun-Fri-15-Jun

All of the rev C boards were made without a review from me. As far as I know, all the rev C boards (which were all made for people other than Printrbot) were all loaded with the LUFA CDC bootloader instead of the Atmel factory-programed FLIP bootloader. The LUFA bootloader is limited to only 64k of code space because of the protocol they chose.

With SD support enabled, Marlin can get close to or exceed 64k depending on the other features that are enabled and the version of gcc it was compiled with. If you have an AVR ICSP cable, I'd try reloading the stock bootloader from here http://www.atmel.com/dyn/resources/prod ... -1-0-1.zip and reflashing Marlin with the FLIP software from Atmel.
  • 0

Laine Walker-Avina
Printrbot Beta-tester and Printrboard Designer
lwalkera
Honeycomb infill 25%...
 
Posts: 291
Joined: 2012-Feb-Sat-04-Feb
Location: Folsom, CA
Reputation: 33

Re: Pronterface says "connecting..." forever

Postby pocketscience » 2012-Jun-Fri-19-Jun

  • 0

printrbot backer #147
pocketscience
Solid infill...
 
Posts: 229
Joined: 2011-Dec-Wed-04-Dec
Location: Sydney, Australia
Reputation: 0

Re: Pronterface says "connecting..." forever

Postby jr57k » 2012-Jun-Fri-22-Jun

As for the PC thing, it's odd because I've got like 9 computers at home, 5 macs, 4 Win7 machines. For some reason although I'm a mac guy and I program on one at work all day I've only printed from the PCs.

As for the crappy responses..... Welcome to printrbottalk.com! :roll:
  • 0

jr57k
Layer 300 of 1234
 
Posts: 320
Joined: 2012-Apr-Sat-18-Apr
Location: Augusta, GA
Reputation: 0

Re: Pronterface says "connecting..." forever

Postby scantrontb » 2012-Jun-Sun-04-Jun

  • 0

Don't planto mihi adveho illac
PB+ #786
User avatar
scantrontb
Can update firmware
 
Posts: 825
Joined: 2011-Dec-Sun-14-Dec
Location: federal way, wa
Reputation: 5

Re: Pronterface says "connecting..." forever

Postby jr57k » 2012-Jun-Sun-08-Jun

You can get a programmer at sparkfun.com. I think it's just a USB serial (FTDI) to TTL with the correct cable. Ive got two ina box somewhere. Just make sure you get the correct voltage (3.3V or 5V I can't remember.....)


Did you buy your board from printrbot.com?
  • 0

jr57k
Layer 300 of 1234
 
Posts: 320
Joined: 2012-Apr-Sat-18-Apr
Location: Augusta, GA
Reputation: 0

Re: Pronterface says "connecting..." forever

Postby lwalkera » 2012-Jun-Mon-15-Jun

  • 0

Laine Walker-Avina
Printrbot Beta-tester and Printrboard Designer
lwalkera
Honeycomb infill 25%...
 
Posts: 291
Joined: 2012-Feb-Sat-04-Feb
Location: Folsom, CA
Reputation: 33

Re: Pronterface says "connecting..." forever

Postby bitswype » 2012-Jun-Wed-20-Jun

Has anyone contacted brook to let him know of this problem so that others don't get stuck with the crippled boot loader?
  • 0

Backer #1634 (PB+)
User avatar
bitswype
I'm an end stop.
 
Posts: 50
Joined: 2011-Dec-Tue-01-Dec
Reputation: 1

Re: Pronterface says "connecting..." forever

Postby jr57k » 2012-Jun-Wed-21-Jun

  • 0

jr57k
Layer 300 of 1234
 
Posts: 320
Joined: 2012-Apr-Sat-18-Apr
Location: Augusta, GA
Reputation: 0

Re: Pronterface says "connecting..." forever

Postby lwalkera » 2012-Jun-Thu-04-Jun

  • 0

Laine Walker-Avina
Printrbot Beta-tester and Printrboard Designer
lwalkera
Honeycomb infill 25%...
 
Posts: 291
Joined: 2012-Feb-Sat-04-Feb
Location: Folsom, CA
Reputation: 33

Re: Pronterface says "connecting..." forever

Postby doctek » 2012-Jun-Thu-14-Jun

Here is a bit from my notes on bringing up Printrboard (running for over 7 weeks now, we have 5 running).

Marlin firmware is installed as described by lincomatic here: lincomatic blog

I used FLIP from Atmel as described on the Printrboard Reprap Site to load Marlin.

Other than fixing motor directions, calibration, end stop sense, etc., the only real problem I had was that Printrboard would hang on booting if the Y-axis was homed. I believe this is due to the fact that Printrboard uses the /SS pin to read the Y end stop. If SDCard use is enabled and this pin is asserted, then the SPI port will not be readable and the initial SD read will hang - at least I think that's what's happening. So I moved the Y end stop to the pin for the E stop (which is not enabled by default). Doing this solved the problem with hanging on reset and the board works fine.

HTH
  • 0

doctek
Waiting to connect to printer...
 
Posts: 5
Joined: 2012-Jun-Thu-14-Jun
Reputation: 0

Re: Pronterface says "connecting..." forever

Postby scantrontb » 2012-Jun-Fri-21-Jun

  • 0

Don't planto mihi adveho illac
PB+ #786
User avatar
scantrontb
Can update firmware
 
Posts: 825
Joined: 2011-Dec-Sun-14-Dec
Location: federal way, wa
Reputation: 5

Re: Pronterface says "connecting..." forever

Postby doctek » 2012-Jun-Fri-22-Jun

Great questions! Obviously, I should have been clearer.

When I say I moved the Y end stop to the E stop pin, I mean that I not only moved the connector (which would be the same as disabling it), but I modified the code in Pins.h to recognize the Y end stop on the pin formerly associated with the E stop. The result is that the Y end stop signal is now recognized on the pin formerly reserved for the E stop input.

For more info on the /SS pin and why it shouldn't be used as an input if you plan to use the SPI port, have a look at the Atmel data sheet for the 90USB1286. In fact, I think that any Atmel AVR that has an SPI requires that the /SS pin not be used as an input except as an SPI /SS control signal.

Hopefully this explanation makes things clearer.
  • 0

doctek
Waiting to connect to printer...
 
Posts: 5
Joined: 2012-Jun-Thu-14-Jun
Reputation: 0

Re: If you get "commands waiting" and can't connect...

Postby plexus » 2013-Apr-Sun-15-Apr

  • 0

User avatar
plexus
Site Admin
 
Posts: 2117
Joined: 2011-Dec-Mon-16-Dec
Location: Toronto, Canada
Reputation: 95

Re: If you get "commands waiting" and can't connect...

Postby EpicFail » 2013-Apr-Tue-21-Apr

I was just looking for something like this. it happened after I tried updating marlin, then coming back to the standard builld * though i did turn on Advance K*
  • 0

EpicFail
Waiting to connect to printer...
 
Posts: 5
Joined: 2012-Dec-Sat-04-Dec
Reputation: 0

Re: If you get "commands waiting" and can't connect...

Postby bpgoss1 » 2013-May-Mon-05-May

finished assembling and no activity from the printer. I've installed pronterface and attempted to connect Pronterface simply says connecting forever. I have tried ensuring that all axis's are set to home. Perhaps the following proterface error log file information will prove useful:

Exception in thread Thread-1:
Traceback (most recent call last):
File "threading.pyc", line 532, in __bootstrap_inner
File "threading.pyc", line 484, in run
File "printcore.pyc", line 97, in _listen
File "io.pyc", line 520, in readline
File "serial\serialwin32.pyc", line 212, in read
ValueError: Attempting to use a port that is not open

Traceback (most recent call last):
File "pronterface.py", line 1566, in connect
File "printcore.pyc", line 76, in connect
File "serial\serialwin32.pyc", line 30, in __init__
File "serial\serialutil.pyc", line 260, in __init__
File "serial\serialwin32.pyc", line 56, in open
serial.serialutil.SerialException: could not open port COM3: [Error 121] The semaphore timeout period has expired.
Exception in thread Thread-3:
Traceback (most recent call last):
File "threading.pyc", line 532, in __bootstrap_inner
File "threading.pyc", line 484, in run
File "printcore.pyc", line 97, in _listen
AttributeError: 'NoneType' object has no attribute 'readline'

Traceback (most recent call last):
File "pronterface.py", line 1566, in connect
File "printcore.pyc", line 76, in connect
File "serial\serialwin32.pyc", line 30, in __init__
File "serial\serialutil.pyc", line 260, in __init__
File "serial\serialwin32.pyc", line 56, in open
serial.serialutil.SerialException: could not open port COM3: [Error 121] The semaphore timeout period has expired.
Traceback (most recent call last):
File "pronterface.py", line 1566, in connect
File "printcore.pyc", line 76, in connect
File "serial\serialwin32.pyc", line 30, in __init__
File "serial\serialutil.pyc", line 260, in __init__
File "serial\serialwin32.pyc", line 56, in open
serial.serialutil.SerialException: could not open port COM3: [Error 121] The semaphore timeout period has expired.
Exception in thread Thread-1:
Traceback (most recent call last):
File "threading.pyc", line 532, in __bootstrap_inner
File "threading.pyc", line 484, in run
File "printcore.pyc", line 97, in _listen
File "io.pyc", line 520, in readline
File "serial\serialwin32.pyc", line 212, in read
ValueError: Attempting to use a port that is not open

Traceback (most recent call last):
File "pronterface.py", line 1566, in connect
File "printcore.pyc", line 76, in connect
File "serial\serialwin32.pyc", line 30, in __init__
File "serial\serialutil.pyc", line 260, in __init__
File "serial\serialwin32.pyc", line 56, in open
serial.serialutil.SerialException: could not open port COM3: [Error 121] The semaphore timeout period has expired.
Traceback (most recent call last):
File "pronterface.py", line 1566, in connect
File "printcore.pyc", line 76, in connect
File "serial\serialwin32.pyc", line 30, in __init__
File "serial\serialutil.pyc", line 260, in __init__
File "serial\serialwin32.pyc", line 56, in open
serial.serialutil.SerialException: could not open port COM3: [Error 121] The semaphore timeout period has expired.
Traceback (most recent call last):
File "pronterface.py", line 1566, in connect
File "printcore.pyc", line 76, in connect
File "serial\serialwin32.pyc", line 30, in __init__
File "serial\serialutil.pyc", line 260, in __init__
File "serial\serialwin32.pyc", line 56, in open
serial.serialutil.SerialException: could not open port COM3: [Error 121] The semaphore timeout period has expired.

Any help?
  • 0

bpgoss1
Loading filament...
 
Posts: 14
Joined: 2013-May-Mon-04-May
Reputation: 0

Re: If you get "commands waiting" and can't connect...

Postby RetireeJay » 2013-May-Mon-10-May

I think that the discussion in this thread is oriented to people who want to modify their firmware on the Printrboard.

If you have a stock Printrboard from Printrbot, and you are not trying to re-flash the firmware, then your problem is probably much simpler.

Look at my post in this thread about installing the USB Serial Driver and see if it helps. viewtopic.php?f=18&t=3356&p=22269&hilit=did+you+install+the+usb+driver#p22268
  • 0

Printrbot Plus operational January 2013
Brass threaded rods (5/16" X 18) & nuts for Z axis
GT2 belts & pulleys
Cable chain to reduce probability of fatigue failure in wires
E3D V5 Hot End, 0.4mm nozzle, also 0.8 and 0.25 in use occasionally
PB fan mount + 40mm fan -- using printed mount adapter, not the E3D supplied fan
Injection molded extruder gears
Optical Z "endstop" (custom designed and built)
Have used many pounds of T-Glase filament. Now also doing some work with Ninjaflex SemiFlex
Print on glass with Scotch Craft Stick or other glue stick
"My next printer is..." Prusa i3 MK3, upgraded to MK3S
User avatar
RetireeJay
My next printer is...
 
Posts: 5014
Joined: 2013-Jan-Wed-13-Jan
Location: Greenville, SC
Reputation: 498

Re: Pronterface says "connecting..." forever

Postby Richy_T » 2013-Jul-Tue-22-Jul

  • 0

Richy_T
Levelling print bed...
 
Posts: 44
Joined: 2013-Jun-Thu-14-Jun
Reputation: 0

Re: If you get "commands waiting" and can't connect...

Postby ggutshal » 2013-Oct-Fri-07-Oct

I'm sorry I'm a bit confused here. I just purchased a Simple kit. I've assembled it and got the Windows driver installed. When I plug the printer in, a new COM port appears. When I click connect, it turns green. When I go to the manual control tab in Repetier, it says "6 Command Waiting". When I click any of the arrow buttons it just increases the number in the "Command Waiting" message. Both the X & Y axises are against the switch. Reading through this thread it sounds like I have to re-flash the board. Is that correct? Sorry if I'm being dense.
  • 0

ggutshal
Loading filament...
 
Posts: 15
Joined: 2013-Oct-Fri-07-Oct
Reputation: 0

Re: If you get "commands waiting" and can't connect...

Postby RetireeJay » 2013-Oct-Fri-08-Oct

No, you shouldn't have to re-flash the board.

On the right-hand side of the Repetier screen, there is an "OK" button (you may have to scroll down to see it). Some people find that they need to click on that button to get their connection going (although for some reason I never have to).

The other potential hang-up involves the serial communication. See this post: viewtopic.php?f=20&t=4280#p28089
  • 1

Printrbot Plus operational January 2013
Brass threaded rods (5/16" X 18) & nuts for Z axis
GT2 belts & pulleys
Cable chain to reduce probability of fatigue failure in wires
E3D V5 Hot End, 0.4mm nozzle, also 0.8 and 0.25 in use occasionally
PB fan mount + 40mm fan -- using printed mount adapter, not the E3D supplied fan
Injection molded extruder gears
Optical Z "endstop" (custom designed and built)
Have used many pounds of T-Glase filament. Now also doing some work with Ninjaflex SemiFlex
Print on glass with Scotch Craft Stick or other glue stick
"My next printer is..." Prusa i3 MK3, upgraded to MK3S
User avatar
RetireeJay
My next printer is...
 
Posts: 5014
Joined: 2013-Jan-Wed-13-Jan
Location: Greenville, SC
Reputation: 498

Re: If you get "commands waiting" and can't connect...

Postby ggutshal » 2013-Oct-Fri-10-Oct

I got that squared away now. I am using the latest version of repetier and there was a setting that needed changed (for the life of me I can't find the thread that clued me in).
  • 0

ggutshal
Loading filament...
 
Posts: 15
Joined: 2013-Oct-Fri-07-Oct
Reputation: 0

Re: If you get "commands waiting" and can't connect...

Postby jwatte » 2013-Nov-Sat-13-Nov

  • 0

jwatte
I'm an end stop.
 
Posts: 55
Joined: 2013-Jul-Sun-17-Jul
Reputation: 3

Re: If you get "commands waiting" and can't connect...

Postby k4rqz » 2013-Dec-Wed-00-Dec

my assembled Printrbot Plus arrived today 12/10/2013 and I had the same problem with a Win7 machine. I had to go to "Manual Control" tab and "Debug Options" box there's an OK button. After hitting that, commands are sent, and everything is fine. I'm using Repetier-Host V0.90C
  • 0

k4rqz
Waiting to connect to printer...
 
Posts: 1
Joined: 2013-Nov-Tue-10-Nov
Reputation: 0

Re: If you get "commands waiting" and can't connect...

Postby holmes4 » 2014-Jan-Wed-21-Jan

  • 0

Steve
PB+ Backer 1402
User avatar
holmes4
Bowden extruder
 
Posts: 871
Joined: 2011-Dec-Sun-12-Dec
Location: New Hampshire, USA
Reputation: 14

Re: If you get "commands waiting" and can't connect...

Postby RetireeJay » 2014-Jan-Wed-21-Jan

  • 0

Printrbot Plus operational January 2013
Brass threaded rods (5/16" X 18) & nuts for Z axis
GT2 belts & pulleys
Cable chain to reduce probability of fatigue failure in wires
E3D V5 Hot End, 0.4mm nozzle, also 0.8 and 0.25 in use occasionally
PB fan mount + 40mm fan -- using printed mount adapter, not the E3D supplied fan
Injection molded extruder gears
Optical Z "endstop" (custom designed and built)
Have used many pounds of T-Glase filament. Now also doing some work with Ninjaflex SemiFlex
Print on glass with Scotch Craft Stick or other glue stick
"My next printer is..." Prusa i3 MK3, upgraded to MK3S
User avatar
RetireeJay
My next printer is...
 
Posts: 5014
Joined: 2013-Jan-Wed-13-Jan
Location: Greenville, SC
Reputation: 498

Re: If you get "commands waiting" and can't connect...

Postby BoingBoing11 » 2014-Jan-Fri-13-Jan

I had that problem too. i went to Printer Settings in Repetier Host, and set the opening handshake from low>high>low to disabled. Fixed the problem for me, hope that's helpful!
  • 0

BoingBoing11
Waiting to connect to printer...
 
Posts: 1
Joined: 2014-Jan-Fri-13-Jan
Reputation: 0


Return to Troubleshooting talk

Who is online

Users browsing this forum: No registered users and 2 guests

cron