Hi. I'm wondering if anyone can advise please.
I normally avoid using strings but now it/they would make life a lot easier in a new project.
The device must stay running indefinitely as a data logger, no on off switch, no reset button. It is to collect data from a BLE module, store it in some I2C eeproms then when able send if via a WiFi module to a server on the internet.
I've settled on the Teensy-LC for now - power consumption is critical, but may have to upgrade to the Teensy-3.2 if code size becomes an issue etc.
The WiFi module is the ESP12S. It seems "reasonably reliable" (not had a problem with simple connect/disconnect over a few days but always paranoid about reliability) so far and I'm happy to reset it if there is an issue. It does not have to send data in real time. Since the logger is person carried, it won't be in WiFi range very often anyway and it is guaranteed to fail when signal strength is marginal etc. It will only bring up the module occasionally anyway (they sure are power hungry).
The BLE Module us the USR-IOT BLE-100.
My question is, is using Strings and supporting functions a "good idea" for a long term operation project. I've read how garbage collection and such can cause problems. Admittedly that was some time ago and with the conventional old ATMega based Arduinos. Some people seem to hate strings.
Using strings would make reading and deciding messages a lot easier but if there is a reliability issue, I'll ditch them and work it myself. It's just that I'd like to make that decision now instead of later down the track and ideally use other peoples experience as a guideline.
Thanks for any ideas or feedback - Richard
I normally avoid using strings but now it/they would make life a lot easier in a new project.
The device must stay running indefinitely as a data logger, no on off switch, no reset button. It is to collect data from a BLE module, store it in some I2C eeproms then when able send if via a WiFi module to a server on the internet.
I've settled on the Teensy-LC for now - power consumption is critical, but may have to upgrade to the Teensy-3.2 if code size becomes an issue etc.
The WiFi module is the ESP12S. It seems "reasonably reliable" (not had a problem with simple connect/disconnect over a few days but always paranoid about reliability) so far and I'm happy to reset it if there is an issue. It does not have to send data in real time. Since the logger is person carried, it won't be in WiFi range very often anyway and it is guaranteed to fail when signal strength is marginal etc. It will only bring up the module occasionally anyway (they sure are power hungry).
The BLE Module us the USR-IOT BLE-100.
My question is, is using Strings and supporting functions a "good idea" for a long term operation project. I've read how garbage collection and such can cause problems. Admittedly that was some time ago and with the conventional old ATMega based Arduinos. Some people seem to hate strings.
Using strings would make reading and deciding messages a lot easier but if there is a reliability issue, I'll ditch them and work it myself. It's just that I'd like to make that decision now instead of later down the track and ideally use other peoples experience as a guideline.
Thanks for any ideas or feedback - Richard