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

what speaks against console baudrate 9600? #1535

Closed
MaBecker opened this issue Oct 21, 2018 · 7 comments
Closed

what speaks against console baudrate 9600? #1535

MaBecker opened this issue Oct 21, 2018 · 7 comments
Labels
ESP8266 This is only a problem on ESP8266 devices question

Comments

@MaBecker
Copy link
Contributor

Is there any reason why we should stick with default_console_baudrate of 115200 for ESP8266_BOARD and ESP8266_4MB?

@MaBecker MaBecker added question ESP8266 This is only a problem on ESP8266 devices labels Oct 21, 2018
@gfwilliams
Copy link
Member

I'm biased, but apart from the existing documentation out there saying 115200 I don't see a reason.

I mean, even with all the docs out there people routinely forget to set the baud rate anyway, and it looks like many people use Telnet anyway, which is faster.

With the recent storage changes it should be trivial for more advanced users to do require("Storage").write('.boot0','Serial1.setup(115200,...)'); anyway if they really need it.

@MaBecker
Copy link
Contributor Author

@wilberforce and @jumjum123 what about ESP32 and baud 9600?

@Frida854
Copy link

What about PICO, it runs with 115200, even with latest version 2V00.
I'd be sad to let speed down.

@jumjum123
Copy link
Contributor

Looks like its grown the same way as ESP8266 ;-) Default from Espressif is 115200
AFAIK, we had to change default in menuconfig, ESP32.py and jshardwareUart.c
I would prefer to have higher speed, but thats my personal opinion only

May be we could add a command to save default rate for specific board somewhere in flash ?
Similiar to the option we have in ESP32 to switch Bluetooth or WiFi on/off
This would give anybody the option to use its own preferred baudrate

BTW, a quick search for 115200 in sources showed about 70 files

@MaBecker
Copy link
Contributor Author

Well, check CONSOLE log:

>>> Connecting...
Set Slow Write = true
[object Object]
Connected [object Object]
Received a prompt after sending newline... good!
>>> Sending...

even if Throttle Send is not set

bildschirmfoto 2018-10-22 um 21 55 14

@gfwilliams
Copy link
Member

Interesting about the other ESP8266 stuff - however I guess it's reasonable to assume that most users will go straight to using the IDE or CLI? If you're using your own stuff you're probably more likely to understand about the baud rate?

@Frida854 it's fine on all the Espruino boards like Pico/WiFi/Original. The USB goes straight into the microcontroller, so actually it doesn't matter what you set the baud rate to - it'll work at the same (high) speed through USB regardless. This only really applies to ESP8266/ESP32 that have a separate USB chip.

@MaBecker yes, the IDE does just turn on Slow Write regardless. I guess there could be an IDE option to fully force it not to be used BUT if you did that, you'd find that some uploads randomly failed.

115200 would be great if there was flow control - but as there isn't we've got to throttle on the IDE side - add to that all the confusion from the different baud rates and I'm more inclined to say 9600 is the best bet.

@gfwilliams
Copy link
Member

Looks to me like there isn't much opposition to choosing 9600 baud?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ESP8266 This is only a problem on ESP8266 devices question
Projects
None yet
Development

No branches or pull requests

4 participants