Issue setting baud rate to 2400

[Brynod]

Hi all,
I have flashed ESP-Link to my wemos D1 mini and all is working fine on the larger part... however, if i try to change the baud rate to 2400 in the serial console (hoping to use this to montor my RS232 inverter) , this causes issues.

Firmware 2.2.3 simply wont set anything below 9600 and reports "error setting baud rate"
Firmware 3.0.14 will allow the change but then goes into a boot loop after power cycle
firmware 3.2.47 will allow the change but then goes into a boot loop after power cycle

is it possible to use ESP link at such a low baud rate? If so....does anyone know how to do this....or if this is even necessary? I am waiting for my MAX3232 adaptor to connect the inverter but just wanted to get everything ready in advance.

Thanks in advance!
Regards
Bryan

[Brynod]

NB: i have tried setting various different baud rates to gather as much info as possible, the message in the screenshot appears when trying to set to 2400 from any other baud rate in firmware 2.2.3

Trying this in any later firmware will allow the change but then just bootloops after power cycle and needs full reflash to get working again..

Thanks again for any help with this
Regards
Bryan

[adharyanto]

Hi, i have exactly the same issue...

My solution is:
I canceled to use Wemos D1 Mini (or any other ESP8266/ESP32) with the JeeLabs ESPLink software.
(I use this ESP8266-JeeLabs ESPLink for any other applications, works fine with baud rate 9600).

But for the inverter case instead, I use RS232-WiFi converter module, Elfin EW10, and it works fine.
It is a product of Hi-Flying, baud rate can be set to 2400, because the inverter only communicates with this rate.
This module has its own application to do the setting, called IOTService.
It is a relatively cheap module compared to other modules. You can search the product on the internet.

Regards,
Antonius

[uzi18]

Need to check this out - maybe fix is easy for that

[uzi18]

Code for all baudrates >300 looks the same

[adharyanto]

Code for all baudrates >300 looks the same

Hallo...

I have tried this way; firstly I set the JeeLabs ESPLink ESP8266 to 9600 or 115200, then connect to the Inverter, and of course it will not work because the Inverter works only on 2400. And then I changed the rate from 9600 or 115200 to 2400 (while it is still running and connected to the Inverter)... and it worked, but very slow and a lot of errors on my Inverter application program, (I built it using NodeRED). Then I monitored the stream of serial data (using Serial Monitor application), I could see the streaming data was not what I expected; many of the streaming data lengths were not the consistent, causing my NodeRED application program could not understand the data.

Moreover, after switching off the ESP8266-JeeLabs ESPLink (with the 2400 setting), and tried to switch on back again, it would not work. This means, JeeLabs ESPLink will work on 2400 only after changing from e.g. 9600 to 2400, but when I switch off the JeeLabs ESPLink, when it is set to 2400, and tried to switch on back again, it will not work.
Have you tried to switch off/on your JeeLabs ESPLink ESP8266/32 when it is set to 2400?

I suspect the inconsistent/too many error of the serial data streaming is caused by the conversion from RS232 to TTL, (using MAX3232), maybe the voltage level conversion is not good,.... I think I need to play/modify the capacitors of the MAX3232... just need some efforts & time...

Using the Hi-Flying Elfin EW10 work just fine, all the serial data stream exactly as I expected, and my NodeRED program can read them.

Regards,
Antonius

[uzi18]

@adharyanto so maybe there is a bug in hardware of esp8266 and workaround is set first 9600 and next desired baud rate?
if you use 32Mbit flash could prepare for you such modified version to test?

[adharyanto]

@adharyanto so maybe there is a bug in hardware of esp8266 and workaround is set first 9600 and next desired baud rate? if you use 32Mbit flash could prepare for you such modified version to test?

Hallo,

If there is a bug, the bug maybe is not in the ESP8266 hardware but maybe in the JeeLabs ESP-Link instead, because ESP8266 is running at 2400 on different software. JeeLabs ESP-Link works at 2400 but only the first time after changing from higher rate, after a power cycle (on/off), JeeLabs ESP-Link will not work/start.

I have tried several other Arduino codes, and testing them at 2400:

• some porting code made by "atadiat", it runs but serial data flow is not stable, my NodeRED program cannot read it
• example code from Arduino ide, esp8266wifi-WifiTelnetToSerial, it runs but again serial data flow is not stable, my NodeRED program cannot read it

I have checked my RS232-TTL voltage conversion, it is not very clean, little noise, but it is ok, data is translated correctly.
The problem i have now is the Flow Control of the serial data stream, i will need the code that has control on the serial data flow (Flow Control), and it must be a software controlled (Xon/Xoff), (not hardware controlled; RTS/CTS/DTR), because the Inverter has only limited communication cables (only VCC, Gnd, Tx, Rx).

So far, only the Hi-Flying Elfin-EW10 (RS232-Wifi module) gives me the solution. It converts the RS232 to WiFi flawlesly, and I can check & monitor the serial data coming very stable, and my NodeRED program can read it.

Regards,
Antonius

[adharyanto]

Hallo,

Just want to give you a little update: this morning I tried another code from Yuri-Rage_ESP-Serial-Bridge, using ESP32. For the same case as before, it is to connect to my Inverter via RS232-MAX3232-ESP32(WiFi)-NodeRED.

The serial communication works, (monitored via Serial Monitor application), but the incoming data (from ESP32 via WiFi to NodeRED) is not what I expected. The data is a "serial buffer" stream format, to be processed by the NodeRED, the problem is this serial buffer data coming in chunks of smaller data, (it is chopped into several smaller data), not the complete data sent in one piece, resulting NodeRED fails to read it. While the data sent by NodeRED via WiFi to ESP32-MAX3232-Inverter is fine, because the Inverter can read it and reply the correct answer.

Problem is the incoming data (answer from the Inverter) to the NodeRED, data is chopped into smaller data. This is actually the same problem as before, when using ESP8266 and other codes.

Compared to the data from the Hi-Flying Elfin EW10 module, it is really smooth, the data always comes completely (not chopped), and NoreRED can read it.

Regards,
Antonius

[uzi18]

@adharyanto You said maybe "esp-link code is with bug", but later you said about 2 arduino codes also works wrong.
So conclusion should be opposite - this is like hardware problem. Maybe on ESP32 it is resolved.
Will check this w Logic Analyzer on 2400

[adharyanto]

@adharyanto You said maybe "esp-link code is with bug", but later you said about 2 arduino codes also works wrong. So conclusion should be opposite - this is like hardware problem. Maybe on ESP32 it is resolved. Will check this w Logic Analyzer on 2400

Hallo,

I have tried 4 codes for my specific case/issue, (Inverter RS232-MAX3232-WiFi(ESP8266/32)-NodeRED, baud rate 2400):

• Code-1 = JeeLabs ESP-Link, using ESP8266
• Code-2 = by Atadiat, using ESP8266
• Code-3 = Arduino IDE, esp8266wifi-WifiTelnetToSerial, using ESP8266
• Code-4 = by Yuri-Rage_ESP-Serial-Bridge, using ESP32

Comparison result:

• Code-1 =
  • problem with baud rate 2400, after power cycle on/off ESP-Link wont work
  • JeeLabs ESP-Link only works on ESP8266 (does not work on ESP32)
  • incoming data is chopped, NodeRED cannot read it
• Code-2 =
  • no problem with baud rate 2400, after power cycle on/off it still works
  • works on ESP8266 and ESP32
  • incoming data is chopped, NodeRED cannot read it
• Code-3 =
  • no problem with baud rate 2400, after power cycle on/off it still works
  • works on ESP8266 and ESP32
  • incoming data is chopped, NodeRED cannot read it
• Code-4 =
  • no problem with baud rate 2400, after power cycle on/off it still works
  • works on ESP8266 and ESP32
  • incoming data is chopped, NodeRED cannot read it

Looking at the above result, we can see that the JeeLabs ESP-Link is the inferior one compared to the other 3 codes.
JeeLabs ESP-Link has problem after power cycle on/off at 2400, the other 3 codes has no problem.
JeeLabs ESP-Link works only on ESP8266 (does not work on ESP32), the other 3 codes works on both ESP8266/ESP32 (use the right library).

So, at baud rate 2400, ONLY using JeeLabs ESP-Link has problem, while using the other 3 codes have no problem.
So, if there is a bug, the bug is NOT on the hardware (ESP8266/ESP32), but MAYBE in the JeeLabs ESP-Link.

Have you tried power cycle on/off using JeeLabs ESP-Link at 2400, and see what happen?

Anyway, the problem for my case (with this specific configuration) is the "Flow Control" of the incoming data, the data is not coming at one piece at one time, but rather it is chopped into several data, this causing my NodeRED fails to understand it.
If I compare to the incoming data from the Hi-Flying Elfin EW10 module, it comes in one piece at one time (not chopped), so my NodeRED can read, analyse, and parse it, to be displayed.

If there are some other codes with "Flow Control" capability, then I would like to try them.
So far, only the Hi-Flying Elfin EW10 gives me the solution, no alternative yet.

Regards,
Antonius

[adharyanto]

Forgot to mention, I also have tried the Tasmota, Serial/SerBr, the result is the same as the other 3 codes....

[uzi18]

@adharyanto have checked my build of esp-link (2.4.37) attached as archive in issue #543 (you did not mention firmware version of esp-link)
This one works correct with 115200 and 2400, no crash on reset, on power on etc. but first have disabled debug log on uart via Debug log subpage.
Is it possible to look at your nodered flow configuration?
Please also explain how do you connect to esp-link from network side like port number, etc.

[adharyanto]

@adharyanto have checked my build of esp-link (2.4.37) attached as archive in issue #543 (you did not mention firmware version of esp-link) This one works correct with 115200 and 2400, no crash on reset, on power on etc. but first have disabled debug log on uart via Debug log subpage. Is it possible to look at your nodered flow configuration? Please also explain how do you connect to esp-link from network side like port number, etc.

Hallo,

Thank you for your help....
I tried using (esp-link-v3.0.14-g963ffbb) and (esp-link-v3.2.47-g9c6530d), both have the same problem.
I have not tried using your recommendation (esp-link-v3.2.47.alpha.24-g74e2043-dirty-Lucjan.tgz), I will try after this.

I have re-flashed my ESP8266 with JeeLabs ESP-Link v3.0.14-g963ffbb, set the Baud: 2400, and switched the "UART debug log: off", and I can see improvement. Now JeeLabs ESP-Link works after power cycle off/on, one problem is solved.

But after testing it for the case = connecting Inverter RS232-MAX3232-ESP8266(JeeLabs ESP-Link)-WiFi-NodeRED, the incoming data is still chopped, coming not in one piece, but partially sent.

The situation is like this:

• My NodeRED can send several kinds of requests/interrogations/commands; (request for serial number, inverter type, parameter configuration, monitor measurement results, alarms, or sending commands to change parameters, etc.)
• Each time my NodeRED sending a request, the inverter will respond/reply the correct answer, and send to the NodeRED.
• Each answer from the Inverter have different length of data, depends on the type of answer need to be sent.
• One of the most important answer data is the "monitor measurement result". This data should be coming in 109 characters at once, (msg.payload.length = 110, measured by NodeRED).
• I program in NodeRED that every 3 seconds NodeRED sends this interrogation, and Inverter should reply also every 3 seconds.
• In NodeRED I use "tcp out node" for sending data, and "tcp in node" for receiving data. I use port-23 for this case.
• The payload type is "stream of Buffer payloads" to be processed further in NodeRED.

Using Hi-Flying Elfin EW10 RS232-Wifi module, I can see the data coming nicely like these below:

(000.0 00.0 220.6 50.0 0374 0219 008 446 28.00 031 100 0052 05.6 207.3 00.00 00000 10010110 00 00 01176 010ÕL
(000.0 00.0 220.6 50.0 0330 0202 007 445 28.00 031 100 0052 05.6 207.3 00.00 00000 10010110 00 00 01175 010dT
(000.0 00.0 219.1 50.0 0328 0203 007 445 28.00 031 100 0052 05.7 205.4 00.00 00000 10010110 00 00 01178 010[.
(000.0 00.0 219.4 50.0 0329 0214 007 446 28.00 031 100 0052 05.7 205.4 00.00 00000 10010110 00 00 01178 010.j
(000.0 00.0 220.0 50.0 0330 0197 007 445 28.00 031 100 0052 05.6 208.1 00.00 00000 10010110 00 00 01175 010P³
(000.0 00.0 220.1 50.0 0330 0207 007 445 28.00 031 100 0052 05.6 207.5 00.00 00000 10010110 00 00 01179 010.®
(000.0 00.0 219.9 50.0 0307 0192 007 447 28.00 032 100 0052 05.7 205.8 00.00 00000 10010110 00 00 01178 010Åë
(000.0 00.0 219.0 50.0 0328 0210 007 445 28.00 030 100 0052 05.7 204.6 00.00 00000 10010110 00 00 01170 010pÚ
(000.0 00.0 220.0 50.0 0330 0196 007 446 28.00 031 100 0052 05.5 208.7 00.00 00000 10010110 00 00 01166 010æˆ

Each line consist of 109 characters, the last 2 characters are the special ones, to indicate the complete data (for Flow Control).
This data showing the Voltage, Frequency, Power, Temperature, etc.....
Every 3 seconds, NodeRED receives this line (109 characters, or by NodeRED msg.payload.length = 110).
This is the flow of incoming data that I want to have, (every 3 seconds, one line with 109 characters at once, then followed by another line, another 109 char after 3 seconds, and so on...)
This way NodeRED will understand the data and can process further...

BUT, using the JeeLabs ESP-Link (even though UART debug log: off) or any other Codes I have tried, I can see the data coming like these below, (it is "chopped", sent partially):

first part:
(000.0 00.0 218.7 50.0 0328 0201 007 438 27.70 022 100 0051 04.0 214.0 00.00 000
followed by second part:
00 10010110 00 00 00867 010sx

Yes, total is 109 chars, (110 by NodeRED), but they are sent into two pieces (two parts)....
My NodeRED will always read this as msg.payload.length = 80, then followed by msg.payload.length = 30, this will not be processed by my NodeRED, because the incoming data will be processed only if msg.payload.length = 110.

I am still thinking of the "Flow Control" issue, that the JeeLabs ESP-Link (or any other Codes) should not send the data, should collect the data first into the buffer, and will send only until the data has those "last two special characters", this is used as the flow control. I am wondering if Elfin EW10 using this mechanism.... because I can see all the data (not only monitor measurement result) always sent with 2 special characters at the end.

Regards,
Antonius

[adharyanto]

Hallo,

I have just re-flashed the ESP8266 with (esp-link-v3.2.47.alpha.24-g74e2043-dirty-Lucjan), the result is exactly the same as (esp-link-v3.0.14-g963ffbb), no difference.
The incoming data for "monitor measurement result" is cut into two parts:

• msg.payload.length = 80 and msg.payload.length = 30, this can not be processed further in my NodeRED.
  The incoming data should not be cut, it should be in one piece, msg.payload.length = 110.

What is the buffer of ESP-Link, is it max can handle 80 characters only?

Regards,
Antonius

[uzi18]

@adharyanto please share your request and receiver part of code in node red - is it possible? option export of NodeRed flow?
Ok, I see now where is the problem. In fact esp-link has got 128 bytes buffer but for some reason triggers send at 80 chars.
... after a moment ...
Have found this 80 chars barrier, will increase it to eg. 115 chars , just need to check if I'm able to rebuild esp-link for you.