Tengo el siguiente esquemático pero me genera el siguiente error, pareciera que en el ultimo índex el 5 leyera también el primero, ya intente modificar los tiempo del clock pero el error persiste, adjunto los prints de los errores
1 Like
Be sure to use println() at the end of each message to send from the sending device, to signal end of message.
Only use print() in the middle of a message.
Be sure not to println() in the middle of a message, or you will break it into two short messages and mess up the item count after you split the message in AI2.
Do not rely on timing for this, which is unreliable.
In the AI2 Designer, set the Delimiter attribute of the BlueTooth Client component to 10 to recognize the End of Line character.
Also, return data is not immediately available after sending a request,
you have to start a Clock Timer repeating and watch for its arrival in the Clock Timer event. The repeat rate of the Clock Timer should be faster than the transmission rate in the sending device, to not flood the AI2 buffers.
In your Clock Timer, you should check
Is the BlueTooth Client still Connected?
Is Bytes Available > 0?
IF Bytes Available > 0 THEN
set message var to BT.ReceiveText(-1)
This takes advantage of a special case in the ReceiveText block:
ReceiveText(numberOfBytes)
Receive text from the connected Bluetooth device. If numberOfBytes is less than 0, read until a delimiter byte value is received.
If you are sending multiple data values per message separated by | or comma, have your message split into a local or global variable for inspection before trying to select list items from it. Test if (length of list(split list result) >= expected list length) before doing any select list item operations, to avoid taking a long walk on a short pier. This bulletproofing is necessary in case your sending device sneaks in some commentary messages with the data values.
Some people send temperature and humidity in separate messages with distinctive prefixes like "t:" (for temperature) and "h:" (for humidity).
(That's YAML format.)
The AI2 Charts component can recognize these and graph them. See Bluetooth Client Polling Rate - #12 by ABG
To receive YAML format messages, test if the incoming message contains ':' . If true, split it at ':' into a list variable, and find the prefix in item 1 and the value in item 2.
Here is an updated blocks sample illustrating these ideas ...
Lo que entiendo es que debo primero armar la lista antes de mostrarla?
Lo que yo estoy enviando a través del bluetooth de la ESP32 es una cadena de texto separa por (
o (,), ya intente ambos.
Yo estoy enviando los datos tanto por serial y bluetooth; en el serial se ve bien, y en la APP, genera constantemente esos errores, aunque realmente en los 5 labels se muestran los ángulos; el error es en el ultimo.
Ya tengo el delimitador en 10; voy a ver tu forma para ver que tal, de igual forma quedo atento a comentarios muchas gracias.
También cabe recalcar que estoy enviando los datos cada 30ms, y los relojes en el app los deje configurados a 20ms.
I see your println() at the end of your print() sequence.
There is a limit to how long a single message in BlueTooth can be, called the MTU.
It might be necessary for you to switch to individually labelled values, one per message.
Some people send temperature and humidity in separate messages with distinctive prefixes like "t:" (for temperature) and "h:" (for humidity).
(That's YAML format.)
The AI2 Charts component can recognize these and graph them. See Bluetooth Client Polling Rate - #12 by ABG
To receive YAML format messages, test if the incoming message contains ':' . If true, split it at ':' into a list variable, and find the prefix in item 1 and the value in item 2.
This is a sample of how to receive messages that come individually labelled, like
t:98.6\n
h:20\n
BlueTooth_YAML_delimiter_sample.aia (3.5 KB)
