Skip to content
therealchalz edited this page Feb 28, 2013 · 3 revisions

TODO

  • Thorough testing of JAMOD serial operation - if the gnu.io/RXTX libraries don't cut it on both windows and linux then I'll try JSSC which I've had good success in Windows with.
  • More dataFunction options - it would be nice to have a raw expression data function that could be parsed and executed by Java Expression Parser
  • Review of error handling/exceptions, specifically for LookupTables. What should happen if a LUT is deleted while running? If it is changed?
  • Add an output module for a local SQL database for realtime values. This is what other applications, like web-based frontends etc, could access for realtime data

There are other things that should be part of the package, but I'm not sure if they should be rolled into the core application or should be part of a separate service.

  • Sending CSV files/Data to a remote server
  • Keeping an SSH tunnel alive for remote management and administration
  • Monitoring the health/status of the system and measurements, log issues as they arise (email alerts as well?) Track things like uptime for the application, system/computer, rtunnel, softlogger channels, etc.

Brainstorm of error conditions to monitor:

  • A device stops responding
  • A channel stops responding (ie: all devices on the same channel)
  • There is a problem with the config file (on bootup, since after it doesn't need it. Maybe a warning if during running there is a problem with it)
  • When it starts up (because this may mean that it had crashed, or power fail, etc)
  • Low disk space, out of disk space
  • Problems with output modules:
  • CSV module:
  • There is a problem with a lookup table; the output module should fail nicely in this case
  • Unable to send files to remote server
  • DB module:
  • Unable to contact database
  • Invalid schema format if configure to not alter tables

Clone this wiki locally