-
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
Allow to send over serial a escape sequence of hexadecimal bytes #4947
Comments
Also, when this SetOption is Enable, trim 0xFF + 0xFF + 0xFF from SerialReceived data. |
Hi, This request is in an already open issue #3560 You already tag Theo there. Please, wait for his answer. May be he can came up with a more general solution for your request. Thanks |
ok @ascillato2, I think to open a 'Feature request' to better explain the case. Sorry for mistake ;) |
There is no mistake. No need to apologize. All the information related to that use case and the feature request has been very well explained in the referenced open issue. Anyway if you think that more information is needed to be added, please do. Let's wait for Theo's answer. Thanks for sharing your ideas and tests. Very appreciated |
As this is specific to NextIon it won't be implemented as a SetOption. You seem to have a workaround using Node-Red so apparently you are able to send three 0xFF via serial. What you actually need is a feature called escape sequence allowing to send escape chacaters like Backspace (\b). This is implemented but currently does not allow octal or hexadecimal input. I'll extend it with allowing to send hex values as \xFF or octal as \777 equal like C standard. |
Yes @arendst, you say good. And, thinking to other device as the SIM800/900 GSM module, multiple bytes. Thank you very much! |
Well 0D0A have always been available as \r\n. Look for Escape Sequences on google. |
Thank you! I go to read the code to understand better |
Latest additions allow to send hexadecimal bytes using escape sequence \x like in |
Thank you very much!!! |
For me this doesn't look right. I am sending
which translates to |
Hi @gitolicious, |
* Fix mDNS addService (arendst#4938, arendst#4951) * Add (S)SerialSend3 escape sequence \x to allow hexadecimal byte value (arendst#3560, arendst#4947) * Add SerialBridge command SSerialSend5 <hexdata>
Same issue from @gitolicious also in 6.5.9 core 2.4.2 |
SSerialsend3 does work (sended with first device):
Received (captured with second device in modus SSerialsend5) Serialsend3 does not work. Opened new issue #5760 |
Have you look for this feature in other issues and in the wiki?
Yes
Is your feature request related to a problem? Please describe.
Itead Nextion Display it's a very powerful and low cost HMI device, simple to programming with his free GUI editor.
https://www.itead.cc/display/nextion.html
The display interact with other devices trought simple serial communications.
Creating a very engaging and interactive user interface is really a breeze.
For example, to update the text showed in a TextBox (named "txtTemp") positioned in a specific page (named "page2") we have to send this simple comand:
page2.txtTemp.txt="Hello world"
Change a background color of this TextBox to Red:
page2.txtTemp.bco=63488
In conjuction with ESP8266/Tasmota can act as remote control console that fit at the place of wall switchs.
Can we use it to show data from other sources (sensors/switchs and so on...), send command to other device, set-up parameters) and offers a multipage interface (up to 255 pages) with unlimited possibility to expand Tasmota/ESP8266's ecosystem.
I tryed to use Nextion with Tasmota (receiving data it's from his very-very simple) but for send a command it's required that the string (plain text) are terminated with 3 '0xFF' bytes.
(page2.txtTemp.txt="Hello world" + 0xFF + 0xFF + 0xFF )
I don't find any simple solution to send thes 3 bytes over MQTT messages (without using other external software like NodeRed).
Describe the solution you'd like
I ask to Tasmota's Developers Team, to implement a new SetOption parameter to append thes 3 0xFF bytes to other commande bytes when serial data are sended wit
Describe alternatives you've considered
See this topic:
#3560 (comment)
Additional context
The display also offers 8 I / O pins.
Think a simple ESP-01 connected to Nextion... ;)
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: