ETSI's Bug Tracker - ASN.1 | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0006031 | ASN.1 | Base Spec | public | 18-04-2012 16:27 | 15-05-2012 10:43 |
| Reporter | Sebastian Muellers | ||||
| Assigned To | Andras Kovacs | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Platform | OS | OS Version | |||
| Product Version | |||||
| Target Version | Fixed in Version | v0.0.1 | |||
| Summary | 0006031: LightBar and SirenInUse in CAM | ||||
| Description | Dear all, While looking at the proposed CAM definition there is one Type called LightBarSirenInUse. This is used to encode together the state of the siren and light bar. Current definition: LightBarSirenInUse ::= BIT STRING { noActivity (0), lightBarAvailable (1), lightBarActivated (2), sirenAvailable (3), sirenActivated (4) } To me this is unclear and ambiguous. What is he purpose of the “noActivity†flag? What is the legal combinatyion of bits, what are the meaning of the combinations? I propose to reuse the old definition from ETSI TS 102 637-3 V1.1.1 (2010-09). In this document, there is a SimpleSystemState type that is used both for lightbar and for siren. I see no advantage in grouping these two together and I find the ENUMERATED type to bear more semantic information the BIT STRING. The encoded size (4 bits) is less than the proposal. New prosposal: Reuse the SimpleSystemState type from the old DENM document: SimpleSystemState ::= ENUMERATED { unavailable (0), -- not equipped or out of order disabled (1), -- switched off by user or due to driving situation, e.g. ACC below minimum speed enabled (2), -- switched on but no action, e.g. ESP in normal operation, limiter below limit speed engaged (3) -- switched on and in action, e.g. light bar flashing, limiter limiting speed } -- Please note that the comments apply the general use of the SimpleSystemState, above is given -- 4 examples: ACC, ESP, limiter, light bar. Each of the 4 states may not apply to all use of the type. Apply this to the CAM (and DENM if applicable): SpecialVehicleContainer ::= SEQUENCE { .... lightBar SimpleSystemState, siren SimpleSystemState, .... } | ||||
| Steps To Reproduce | |||||
| Additional Information | Dear Ola, I guess you refere to a ASN.1 document. Unfortunately have no editor for ASN.1. But in the latest excel sheet, which we discussed and agreed on at our last meeting in ETSI (ITSWG1(12)000023_CAM_message_list_v_38.xls), we spend only 2 bits for the LightBarSirenInUse. LightBarSireneInUse bit string, conditional (shall be present for specific vehicle types) bit 0: LightBar activated bit 1: Siren activated This bit sting provides everything what is needed. Best regards, Dieter Seeberger | ||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 18-04-2012 16:27 | Sebastian Muellers | New Issue | |||
| 19-04-2012 13:35 | Sebastian Muellers | Note Added: 0010561 | |||
| 25-04-2012 16:52 | Sebastian Muellers | Status | new => assigned | ||
| 25-04-2012 16:52 | Sebastian Muellers | Assigned To | => Andras Kovacs | ||
| 30-04-2012 18:49 | Andras Kovacs | Status | assigned => resolved | ||
| 30-04-2012 18:49 | Andras Kovacs | Resolution | open => fixed | ||
| 15-05-2012 10:43 | Sebastian Muellers | Status | resolved => closed | ||
| 15-05-2012 10:43 | Sebastian Muellers | Fixed in Version | => v0.0.1 | ||
| Notes | |||||
|
|
|||||
|
|
||||