Skip to content
This repository has been archived by the owner on Mar 31, 2022. It is now read-only.

Autoconnect wrong baud rate #14

Open
3dbret opened this issue Sep 19, 2020 · 5 comments
Open

Autoconnect wrong baud rate #14

3dbret opened this issue Sep 19, 2020 · 5 comments
Labels
In the plan There are still some problems, and the future version is perfect

Comments

@3dbret
Copy link

3dbret commented Sep 19, 2020

As it is this will not work with an Artillery Sidewinder X1 or any other printer with a 250000 baud rate. This really needs to be a configuration option at install.

To fix:
change:
mainwindow.cpp: _ConnectJson.insert("baudrate",115200);
to this:
mainwindow.cpp: _ConnectJson.insert("baudrate",250000);
do a make clean; make; qmake OctoBTT.pro;

@bigtreetech
Copy link
Owner

In order to ensure the stability and anti-interference ability of the communication connection, it is recommended to use the intermediate 115200 Baud rate value. The default setting of the program is 115200 at present. More baud rate options and the communication mode of direct serial port will be obtained in future version updates.The make clean command can only work properly if it is run on the premise of existing compilation, otherwise the installation may be interrupted by unknown problems.Qmake octobtt.pro is required only if the list of items in the project file has changed, otherwise there is no sense in re-executing it.

@3dbret
Copy link
Author

3dbret commented Sep 19, 2020 via email

@bigtreetech
Copy link
Owner

Hello, you can modify the baud rate of the printer to 115200 so that OctoBTT can automatically connect to the printer.

@3dbret
Copy link
Author

3dbret commented Sep 21, 2020 via email

@bigtreetech bigtreetech added the In the plan There are still some problems, and the future version is perfect label Oct 23, 2020
@ftcorey3
Copy link

ftcorey3 commented Jun 9, 2021

Was this ever done, i have three printers that are affected by this bug. If you have not fixed it, can you post how a user can do this? this was marked in the plan more than 7 months ago

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
In the plan There are still some problems, and the future version is perfect
Projects
None yet
Development

No branches or pull requests

3 participants