Skip to content
New issue

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

Chosing AUTO serial port ignores specified baud rate #892

Closed
C-o-r-E opened this issue May 14, 2015 · 7 comments

Comments

Projects
None yet
4 participants
@C-o-r-E
Copy link
Contributor

commented May 14, 2015

I've observed that when connecting to a printer and selecting AUTO for the port, even if the baud rate is specified, it uses 115200.

In my case I have the baud set to 250000.

Version: 1.2.0-dev-832-gfa98210 (devel branch)

Here is a snippet of the Octoprint terminal (not that its really needed).

edit because the bot closed the issue

  1. What were you doing?
    Connecting to a printer. Port is set to AUTO. Baud rate is set to 250000
  2. What did you expect to happen?
    Expected a connection to be made with the specified baud rate
  3. What happened instead?
    It connects with 115200 baud instead resulting in corruption
  4. Branch & Commit or Version of OctoPrint:
    Version: 1.2.0-dev-832-gfa98210 (devel branch)
  5. Printer model & used firmware incl. version
    (if applicable - always include if unsure):
    Not applicable
  6. Browser and Version of Browser, Operating
    System running Browser (if applicable - always
    include if unsure):
    Firefox 37.0.2
    Linux 3.13 x64
  7. Link to octoprint.log on gist.github.com or pastebin.com
    (ALWAYS INCLUDE AND DO NOT TRUNCATE):
    You asked for it...
  8. Link to contents of terminal tab or serial.log on
    gist.github.com or pastebin.com (if applicable - always
    include if unsure or reporting communication issues AND
    DO NOT TRUNCATE):
    Here
  9. Link to contents of Javascript console in the browser
    on gist.github.com or pastebin.com or alternatively a
    screenshot (if applicable - always include if unsure
    or reporting UI issues):
    Here
  10. Screenshot(s) showing the problem (if applicable - always
    include if unsure or reporting UI issues):
    Not needed

I have read the FAQ.

@GitIssueBot

This comment has been minimized.

Copy link
Collaborator

commented May 14, 2015

Hi @C-o-r-E,

It looks like there is some information missing from your ticket that will be needed in order to process it properly. Please take a look at the Contribution Guidelines and the page How to file a bug report on the project wiki, which will tell you exactly what your ticket has to contain in order to be processable.

If you did not intend to report a bug, please take special note of the title format to use as described in the Contribution Guidelines.

I'm closing this one now as it is currently incomplete. Please feel free to comment here to request a reopen of this issue once you can provide all required information.

Best regards,
~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being.

@C-o-r-E

This comment has been minimized.

Copy link
Contributor Author

commented May 14, 2015

Hey @GitIssueBot

I edited the issue. I would like to request a reopen.

@foosel foosel reopened this May 14, 2015

@ffr2822

This comment has been minimized.

Copy link

commented May 28, 2015

Some further information: I just set up OctoPrint using an octopi image - and found I could not connect to my TAZ 5 with "AUTO" - it never seemed to step down from 250Kbps. I had to specify 115Kbps. This matches what I would expect on a PI as the serial performance (even on a 2) is not exactly stellar.
Again, this was a TAZ 5, RAMBo 1.3L, Marlin 2015-Q1, Octoprint version 1.1.1-30

@foosel

This comment has been minimized.

Copy link
Owner

commented May 28, 2015

@ffr2822 that's a different issue and from the sounds of it already fixed in devel

@ffr2822

This comment has been minimized.

Copy link

commented May 28, 2015

No worries - just trying to add a data point.

On May 27, 2015, at 11:11 PM, Gina Häußge notifications@github.com wrote:

@ffr2822 that's a different issue and from the sounds of it already fixed in devel


Reply to this email directly or view it on GitHub.

Michael Baumann
baumann@uber-geek.org

"The most exciting phrase to hear in science, the one that
heralds new discoveries, is not 'Eureka!' (I found it!) but
'That's funny ...'" -- Isaac Asimov

foosel added a commit that referenced this issue May 29, 2015

Fix: Re-open detected serial port with specified baudrate
The serial port was previously kept open from the Stk500 initialization, which defaults to 115200 baud.

Closes #892
@foosel

This comment has been minimized.

Copy link
Owner

commented May 29, 2015

Should be fixed in devel

@foosel foosel closed this May 29, 2015

@foosel

This comment has been minimized.

Copy link
Owner

commented May 29, 2015

@ffr2822 I think I came off a bit aggressive there, sorry for that. I just re-read your issue, and I'm not so sure anymore that it's what was fixed in devel or if it's something else entirely (or maybe even a problem with pyserial itself). Could you try how your TAZ behaves under devel and if the issue persists there open a ticket?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.