potential problem with memory overflow of TxtAncs. #84

New issue

Closed

opened 2019-04-09 14:53:51 +01:00 by kieran-boyle · 2 comments

kieran-boyle commented

2019-04-09 14:53:51 +01:00

(Migrated from github.com)

It is possible that TxtAncs does not correctly get cleared when a new message is received.
ToDo.
When connected to network, monitor memory usage with the showRam function (found in swbbSlave)

It is possible that TxtAncs does not correctly get cleared when a new message is received. ToDo. When connected to network, monitor memory usage with the showRam function (found in swbbSlave)

Riolaurenti commented

2019-04-17 12:56:47 +01:00

(Migrated from github.com)

I think char array messages are stored in eeprom by fastLED text library.
eg, if you power down the arduino mid text array, when repowered it will continue where it left off.

From what I can tell, the behavior is ike that of a Queue, where if the character array has been interupted before the queue is finished popping its characters, the remainder will be added on to the start of the next message.
So again, if your text pattern is unfinished before you call another text pattern, same problem occurs.

There are a number of work around to this, I assume if you're working from code that already exists in a DV# repository, then we've lost a snippet of the char array management somewhere in translation.

Issue can be closed, methods to be explored over time.
Probably 2 mins with the header file.

I think char array messages are stored in eeprom by fastLED text library. eg, if you power down the arduino mid text array, when repowered it will continue where it left off. From what I can tell, the behavior is ike that of a Queue, where if the character array has been interupted before the queue is finished popping its characters, the remainder will be added on to the start of the next message. So again, if your text pattern is unfinished before you call another text pattern, same problem occurs. There are a number of work around to this, I assume if you're working from code that already exists in a DV# repository, then we've lost a snippet of the char array management somewhere in translation. Issue can be closed, methods to be explored over time. Probably 2 mins with the header file.

kieran-boyle commented

2019-06-03 13:43:24 +01:00

(Migrated from github.com)

Found the problem. String needs to start with , .
This issue does not present when over full network as messages is appended by CTL, and is cut correctly, however when debugging over serial it will cut at random places if there is no Comma at the start (just heads up if anyone runs into this issue and is as stumped as I was, I don't understand the reason that this is the case however)

Found the problem. String needs to start with , . This issue does not present when over full network as messages is appended by CTL, and is cut correctly, however when debugging over serial it will cut at random places if there is no Comma at the start (just heads up if anyone runs into this issue and is as stumped as I was, I don't understand the reason that this is the case however)