Skip to content

Latest commit

 

History

History

issues

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Note

SECoP Issues have been replaced by the RFC process, which is described in RFC 1.

If there is renewed interest in one of the remaining open issues, please migrate to an RFC before restarting discussion.

SECoP Issues

The idea behind SECoP Issues is to document properly what was proposed, what was discussed, what was decided and why it was decided.

An issue might take different states:

(u) unspecified

a vague idea, but no proposal written down yet

(p) proposed

A proposal should contain the motivation. As long as nobody else joins into a discussion, the state remains proposed

(d) under discussion

This state is kept until there is a decision taken.

(f) finalizing

This state is kept until the specification change is agreed.

( ) closed

After a decision the state is closed. The issue is not deleted, even if the decision was to not follow further the proposal. This is helpful if somebody later rises a similar issue. However, it should be possible to reopen an issue, if new arguments arise.

Remark:

At the meeting in Lund (13th June 2018), it was agreed not to follow the proposal of creating a new state "extensible" for an issue containing an extensible list. Instead, an new issue should be created, containing the added elements. A full actual list should be added each time.

Issues List

SECoP Issue 1: About SECoP Issues
SECoP Issue 2: Equipment ID in Describing Message
SECoP Issue 3: Timestamp Format
SECoP Issue 4: The Timeout SEC Node Property
SECoP Issue 5: Definition of the term 'Qualifier'
SECoP Issue 6: Keep Alive
SECoP Issue 7: Time Synchronization
SECoP Issue 8: Groups and Hierarchy
SECoP Issue 9: Module Meaning
SECoP Issue 10: Character set for Names
SECoP Issue 11: Default parameters 'value' and 'target'
SECoP Issue 12: JSON values vs documents
SECoP Issue 13: Access Control
u SECoP Issue 14: Synchonisation of Hardware Modules on Different SEC Nodes
SECoP Issue 15: Support for Start/Stop/Pause/Shutdown Commands
SECoP Issue 16: wanted_target Parameter
SECoP Issue 17: Collect Use Cases for 'starting'
d SECoP Issue 18: Interface Classes
SECoP Issue 19: Set SEC Node clock over SECoP
u SECoP Issue 20: PID tables
SECoP Issue 21: Usage of JSON null
u SECoP Issue 22: Enable Module instead of Shutdown Command
SECoP Issue 23: Adjust Datatypes
SECoP Issue 24: Mix Commands within Parameters in the Description
SECoP Issue 25: Pong Format
SECoP Issue 26: More Module Meanings
d SECoP Issue 27: Proposals for Interface Classes
SECoP Issue 28: Clarify buffering mechanism
SECoP Issue 29: New messages for buffering
SECoP Issue 30: Clarify Message parsing
SECoP Issue 31: Clarify timing requirements of status updates
SECoP Issue 32: Clarify specification using RFC-style definitions
SECoP Issue 33: Include section about security and access control
SECoP Issue 34: Clarify 'do' message
SECoP Issue 35: Partial Structs
SECoP Issue 36: Dynamic units
SECoP Issue 37: Clarification of status
SECoP Issue 38: Extension mechanisms
p SECoP Issue 39: Use cases
p SECoP Issue 40: Finalise Specification
SECoP Issue 41: Handling of JSON-numbers
SECoP Issue 42: Requirements of datatypes
SECoP Issue 43: Parameters and units
SECoP Issue 44: Scaled integers
SECoP Issue 45: Async error updates
SECoP Issue 46: remote logging
SECoP Issue 47: Error classes
SECoP Issue 48: mode parameter
SECoP Issue 49: Precision of Floating Point Values
SECoP Issue 50: Reserved Names
SECoP Issue 51: No Restrictions on Datatype Nesting
SECoP Issue 52: Include Some Properties into Datatype
SECoP Issue 53: Custom Status Values
SECoP Issue 54: Splitting _update_ into two Message Types
SECoP Issue 55: Reformat Datatype description
SECoP Issue 56: Additional Busy States
SECoP Issue 58: use JSON key, value for describe message
SECoP Issue 59: set_mode and mode instead of some commands
u SECoP Issue 60: enhancements to the documentation
SECoP Issue 61: new predefined property implementation
u SECoP Issue 62: naming convention for related parameters
SECoP Issue 63: enumeration of floating point values
SECoP Issue 64: reading multiple parameters simultaneously
SECoP Issue 65: handling of coupled (sub)modules
SECoP Issue 66: force re-connect
f SECoP Issue 67: pid control parameters
SECoP Issue 68: transaction of multiple commands
f SECoP Issue 69: optional structs by default
u SECoP Issue 70: message is a JSON object
SECoP Issue 71: accessing sub items of parameters
SECoP Issue 72: features
p SECoP Issue 73: HasLimits and HasOffset
u SECoP Issue 74: Standardization of units
p SECoP Issue 75: New messages check and checked
p SECoP Issue 76: Interface for Measurable hardware
p SECoP Issue 77: predefined parameter name prefixes
p SECoP Issue 78: Interacting Modules - use case power supply
SECoP Issue 79: hints for readonly access
p SECoP Issue 80: issues with software ramp
p SECoP Issue 81: dynamic descriptive data
p SECoP Issue 82: Feature HasRamp