-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Reported baud rate not used until re-sent #9554
Comments
As designed. Once a configured use-case has been detected the correct baudrate will be set. Has anything to do with unwanted signals on GPIO1/3 where users have connected different hardware. |
Just for clarity:
|
In that case use a rule to set baudrate on reboot. Just for my understanding, if you say
how do you transmit it? Using the serial console, web console, serialsend... |
Changed management of serial baudrate (#9554)
The latest change solves at least the miscommunication of the current baudrate. To change the baudrate on restart use a rule like |
Web console serialsend, yes. |
I'm terribly glad it was not my imagination! Thank you.
Naturally. I shall add such a note to the documentation, too. Thanks again, folks! |
PROBLEM DESCRIPTION
A clear and concise description of what the problem is.
After a reboot, TASMOTA sends serial data (using the hardware port) at 115k regardless of the previously set baud rate. the previously set baud rate is reported, when TASMOTA is queried, however evidence suggests that this is not the rate being used.
Specifics:
When I reboot TASMOTA, I query the baud rate. I'm told it is 57600. When I send a byte, oscilloscope shows that the byte is about 75us long, suggesting a rate of about 115k.
I reset the baud rate to 57600, and resend the byte.
The byte is now about 150us long, suggesting a rate of about 57k6.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Read the Contributing Guide and Policy and the Code of Conduct
Searched the problem in issues
Searched the problem in the docs
Searched the problem in the forum
Searched the problem in the chat
Device used (e.g., Sonoff Basic): WEMOS D1
Tasmota binary firmware version number used: 8.5.1
Flashing tools used: esptool 2.6
[X Provide the output of command:
Backlog Template; Module; GPIO 255
:Configuration output here:
23:22:04 MQT: gen/stat/RESULT = {"NAME":"Generic","GPIO":[255,148,255,149,255,255,255,255,255,255,255,255,255],"FLAG":15,"BASE":18}
23:22:04 MQT: gen/stat/RESULT = {"Module":{"18":"Generic"}}
23:22:04 MQT: gen/stat/RESULT = {"GPIO0":{"0":"None"},"GPIO1":{"148":"Serial Tx"},"GPIO2":{"0":"None"},"GPIO3":{"149":"Serial Rx"},"GPIO4":{"21":"Relay1"},"GPIO5":{"0":"None"},"GPIO9":{"0":"None"},"GPIO10":{"0":"None"},"GPIO12":{"0":"None"},"GPIO13":{"0":"None"},"GPIO14":{"0":"None"},"GPIO15":{"0":"None"},"GPIO16":{"0":"None"}}
Rules output here:
STATUS 0 output here:
23:25:04 MQT: gen/stat/STATUS = {"Status":{"Module":18,"DeviceName":"Tasmota","FriendlyName":["gen"],"Topic":"gen","ButtonTopic":"0","Power":1,"PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":1,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0}}
23:25:04 MQT: gen/stat/STATUS1 = {"StatusPRM":{"Baudrate":57600,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota/release/tasmota.bin","RestartReason":"External System","Uptime":"0T00:08:39","StartupUTC":"2020-10-15T22:16:25","Sleep":50,"CfgHolder":4617,"BootCount":21,"BCResetTime":"2020-10-13T22:57:32","SaveCount":74,"SaveAddress":"FA000"}}
23:25:04 MQT: gen/stat/STATUS2 = {"StatusFWR":{"Version":"8.5.1(tasmota)","BuildDateTime":"2020-10-02T10:09:47","Boot":31,"Core":"2_7_4_1","SDK":"2.2.2-dev(38a443e)","CpuFrequency":80,"Hardware":"ESP8266EX","CR":"336/699"}}
23:25:04 MQT: gen/stat/STATUS3 = {"StatusLOG":{"SerialLog":0,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["Scrabo",""],"TelePeriod":300,"Resolution":"558180C0","SetOption":["00C08009","2805C8000100060000005A00000000000000","00800008","00006000","00000000"]}}
23:25:04 MQT: gen/stat/STATUS4 = {"StatusMEM":{"ProgramSize":596,"Free":404,"Heap":23,"ProgramFlashSize":1024,"FlashSize":4096,"FlashChipId":"164020","FlashFrequency":40,"FlashMode":3,"Features":["00000809","8FDAE797","04368001","000000CD","010013C0","C000F981","00004004","00000000"],"Drivers":"1,2,3,4,5,6,7,8,9,10,12,16,18,19,20,21,22,24,26,27,29,30,35,37","Sensors":"1,2,3,4,5,6"}}
23:25:04 MQT: gen/stat/STATUS5 = {"StatusNET":{"Hostname":"iotgen","IPAddress":"192.168.1.159","Gateway":"192.168.1.1","Subnetmask":"255.255.255.0","DNSServer":"192.168.1.1","Mac":"CC:50:E3:08:53:10","Webserver":2,"WifiConfig":4,"WifiPower":17.0}}
23:25:04 MQT: gen/stat/STATUS6 = {"StatusMQT":{"MqttHost":"192.168.1.111","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_085310","MqttUser":"device","MqttCount":1,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30}}
23:25:04 MQT: gen/stat/STATUS7 = {"StatusTIM":{"UTC":"2020-10-15T22:25:04","Local":"2020-10-15T23:25:04","StartDST":"2020-03-29T01:00:00","EndDST":"2020-10-25T02:00:00","Timezone":99,"Sunrise":"07:33","Sunset":"18:12"}}
23:25:04 MQT: gen/stat/STATUS10 = {"StatusSNS":{"Time":"2020-10-15T23:25:04"}}
23:25:04 MQT: gen/stat/STATUS11 = {"StatusSTS":{"Time":"2020-10-15T23:25:04","Uptime":"0T00:08:39","UptimeSec":519,"Heap":23,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"POWER":"ON","Wifi":{"AP":1,"SSId":"Scrabo","BSSId":"EC:BE:DD:37:EB:17","Channel":6,"RSSI":98,"Signal":-51,"LinkCount":1,"Downtime":"0T00:00:03"}}}
Console output here:
The text was updated successfully, but these errors were encountered: