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

[Request] Show the current baudrate #2859

Closed
DominikPalo opened this issue Oct 21, 2018 · 11 comments
Closed

[Request] Show the current baudrate #2859

DominikPalo opened this issue Oct 21, 2018 · 11 comments
Labels
bug Issue describes a bug done Done but not yet released request Feature request
Milestone

Comments

@DominikPalo
Copy link
Contributor

DominikPalo commented Oct 21, 2018

It would be nice if OctoPrint shows somewhere the baudrate of the connection when it is used in the auto mode, because now it is not possible (at least I didn't find a way how to) get the current baudrate. For example as a tooltip on the "Disconnect" button the connection panel, or somewhere in the terminal tab.
image

@GitIssueBot GitIssueBot added request Feature request and removed request Feature request labels Oct 21, 2018
foosel added a commit that referenced this issue Oct 30, 2018
@foosel
Copy link
Member

foosel commented Oct 30, 2018

Partially implemented as a side effect of the fix/implementation of #2740. The commit above fully implements it that the current settings are now reflected in the selection boxes after a connection has been established:

image

Pushed to maintenance, soon devel, to be released with 1.3.10

@foosel foosel added the done Done but not yet released label Oct 30, 2018
@foosel foosel added this to the 1.3.10 milestone Oct 30, 2018
@DominikPalo
Copy link
Contributor Author

Thanks, but recently I've updated my OctopPrint to the version 1.3.10rc2 and I still can't see the current baudrate/port after connecting with the AUTO setting. According to the changelog, it should be part of 1.3.10rc1 or am I wrong?
octoprint

@foosel
Copy link
Member

foosel commented Nov 14, 2018

You aren't wrong and that should be implemented. The problem is that it works here, both of these were set to AUTO before connecting:

image

Does it work in safe mode? Have you tried clearing your browser's cache?

@foosel
Copy link
Member

foosel commented Nov 14, 2018

Ooooh, wait. Did that connection happen through auto connect on server startup or through a manual connect?

@DominikPalo
Copy link
Contributor Author

DominikPalo commented Nov 18, 2018

It was a manual connect. See my video (recorded in the incognito mode, so it can't be caused by the browser's cache) https://gyazo.com/d9114fd8ac759e6e09ca217da04b08c2 Also, I am able to replicate it on two different computers and browsers (Safari and Chrome),

@foosel foosel modified the milestones: 1.3.10, 1.3.11 Dec 10, 2018
@foosel foosel added unreproduced No reproduction in a dev setting yet, further analysis blocked by that triage This issue needs triage and removed done Done but not yet released labels Dec 10, 2018
@foosel
Copy link
Member

foosel commented Dec 10, 2018

This not working under 1.3.10 is still unreproduced. Marking as such.

@Edo78
Copy link

Edo78 commented Jan 21, 2019

I'm experiencing the same issue even in safe mode. I'm on OctoPrint 1.3.10 running on OctoPi 0.15.1

Can I provide you further information to help you?

@foosel
Copy link
Member

foosel commented Jan 28, 2019

@Edo78 exact steps with which you experience this issue. The more details the better. I still cannot reproduce this.

@Edo78
Copy link

Edo78 commented Jan 28, 2019

I did nothing special:

  • Downloaded octopi
  • flashed on the sd
  • configured the wifi
  • booted the Pi
  • if I remember correctly on the first login it tells me there's an update so I update
  • rebooted the Pi and reloaded in the browser
  • connected to the printer with AUTO/AUTO
  • keep seeing AUTO/AUTO since then

I even tried the incognito mode in chrome but I stile get AUTO/AUTO.

If I set the proper values then I see them, otherwise it's always been AUTO/AUTO

@foosel
Copy link
Member

foosel commented Mar 19, 2019

Now that was weird. I couldn't reproduce it at all - until today. Now I finally could reproduce it and looking at the code have no idea why it ever worked for me to begin with. I'm... very confused by this 🤨

In any case, I hope the above commit now fixes it for good - it does for me. Already pushed to maintenance, soon devel, to be part of 1.3.11.

@foosel foosel added bug Issue describes a bug done Done but not yet released and removed unreproduced No reproduction in a dev setting yet, further analysis blocked by that triage This issue needs triage request Feature request labels Mar 19, 2019
@GitIssueBot GitIssueBot added the request Feature request label Mar 19, 2019
@foosel foosel closed this as completed in bc66d29 May 14, 2019
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue describes a bug done Done but not yet released request Feature request
Projects
None yet
Development

No branches or pull requests

4 participants