Project

General

Profile

Actions

Bug #5321

closed

sensor settings made by kepler user lost on SPAN restart

Added by Derik Barseghian over 13 years ago. Updated over 13 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
sensor-view
Target version:
Start date:
02/23/2011
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5321

Description

To start SPAN you

generate a config file from a CRBasic program:
./cr_parser.py conf/sq110_and_bps.CR8 span.cfg

and then start SPAN using it:
./cr1k_d CR800 span.cfg
./dcd_mgr span.cfg

Currently SPAN crashes periodically, requiring restart. Even if that weren't the case, we still need to function smoothly when the gumstix power cycles (thus restarting SPAN). If a user makes sensor changes via Kepler, and then SPAN is restarted, since the CRBasic program is never updated, the user sensor settings are lost.

Possible solutions, neither of which are currently supported afaik, seem to be:
1) download from the logger the CRBasic program whenever changes are made, thus keeping it in sync.
2) simply start SPAN without overwriting existing settings on the logger, e.g. with a mostly blank config.


Related issues

Blocked by Kepler - Bug #4763: create gui to access datalogger programNewDerik Barseghian02/05/2010

Actions
Actions

Also available in: Atom PDF