Feature #376
Need to integrate the configurator into the dSS
| Status: | Rejected | Start date: | 05/18/2010 | |
|---|---|---|---|---|
| Priority: | (P3) Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | dSS | |||
| Target version: | 0.8.0-rc1 | |||
| Severity: | Normal | |||
| Story points | - | |||
| Velocity based estimate | - |
Description
The configurator is a tool that's used to write the config block to a dSM. The dSM configuration must often be written when upgrading the firmware.
Currently, the configurator only runs on dSS10's, which makes the use of this device necessary.
This seems to be somewhat core technology that's critically necessary on the current dSS.
History
Updated by Roman Köhler over 1 year ago
To clarify:
the configurator is a application, which uses ds485 connectivity. on dss10 the ds485 is a seperate library and not a inseparably codeblock of a singular, monolithic dss-application.
Personally I don't think, that the core dSS need to have the capatility to configure the dSM beside the normal functions which are exposed throught the dSM-API... the config-block contains some measurement-calibration which is needed for the powermeasurement ...
I think, it would be wise to extract the dS485 protocol stack in a separate library or driver or somethink like that, so other application can utilize that connectivity. from the architectual view the whole "dSS-THING" will be also become a more modular and clearer structure ...
That singular configuration usecase, which is only be relevant on the production site of the dSM is nothing, that should concern the community, since we (aizo) will sell ready-calibrated and configured dSMs...
Updated by Miguel Rodriguez over 1 year ago
- Status changed from New to Rejected
This functionality is part of the production tool of dSM