@kl3m3n Excellent, I look forward to it!

@kl3m3n

Its not a critical thing, and there is ways to get around it. I just have setpoints that can be modified both at the device and via Bluetooth. I push change back to GUI-O app when the setpoint at the device changes. If you are changing settings on the app, it closes the window. This is just to keep setpoints/configuration up to date in the app.

At the end of the day its a minor inconvenience and something that would rarely happen, but can. Not some much as a wish, as an idea..

@kl3m3n Yes exactly. No changes to device firmware.

@kl3m3n

No problem,

Thank you for you great work!

@kl3m3n

My UID are generated automatically in the firmware, in the case it is "14" (coincidence I know). In the BLE Terminal app I can use:

@14 12345678901234/r/n and get success (14 characters from text input)

If I use:

@14 123456789012345/r/n I still get success from terminal app, but this will fail from GUI-O.

The output log is always blank, so I can't see what exactly GUI-O is sending in this case, but I did a lot of testing with firmware, and the device doesn't seem to get any message at all from GUI-O (when over 14 chars). I can comment out any processing and just spit out the UID (on the device) on every message and get nothing when over 14chars. 14 and under and works as expected. With Terminal app, functions as expected regardless of characters.

I could be missing something else, but at this point it appears to me to be a possible bug with specifically BLE on GUI-O?

I will try to explain this as an example

Lets say a device is publishing updates live at some frequency, or when the value changes, to a number field. This field is also a setpoint, so the user can make changes. If you trying to change the value, and an updates is published from the device. It closes the user input.

It might be an idea to disable field UI updates while editing the field. Could also notify user that the field has changed in the background.

Bluetooth Low Energy Device: When you try to send more than 14 characters from a text input to the remote device, the remote device does not appear to get any message. GUI-O app continues to get updates from the device, but can no longer send any updates back to the device. After 20 or 30 seconds, GUI-O comes up with "Low energy device error" and disconnects. 14 and under and behaves normally.

Using Ethernet connection to the Design Tool doesn't seem to have any issues.

I initially thought it was something with my device firmware, but testing the same function using the "Serial Bluetooth Terminal" app for Android, and can successfully set more than 14 characters. I tried to check the log files for GUI-O but the out_messages.log is always empty.

Thanks!

A setting to limit the number of characters entered on text inputs would be handy to give users the indication there is limited capacity.