View Issue Details

IDProjectCategoryView StatusLast Update
000841210000-100: DevicesSpecpublic2024-10-14 12:00
ReporterRoman Sinawski Assigned ToUwe Thomas  
PrioritynormalSeveritytweakReproducibilityhave not tried
Status resolvedResolutionfixed 
Fixed in Version1.05 
Summary0008412: Contradiction between PrepareForUpdate and FileTransfer dependency?
Description

From Part 100 v 1.03.1, Table 69 – TemporaryFileTransferType Result Codes, "Bad_InvalidState" shall be returned "If the PrepareForUpdate is available, the UpdateBehavior requires preparation and the
PrepareForUpdate state machine is not in the state PreparedForUpdate."

We read this as an AND condition as follows: if there is the PrepareForUpdateStateMachine available AND the GetUpdateBehavior method returns "Need Preparation" BUT the state is not PreparedForUpdate, THEN return this error.

Is this the correct reading? If yes, then there is a contradiction between this and figure 35, where Loading.FileTransfer is done before the prepare activity.
Following table 69, GenerateFileForWrite (in order to do Loading.FileTransfer) cannot be called (returns an error) if the state is not PreparedForUpdate.

But in figure B.6, Loading.FileTransfer is (as in figure 35) done before PrepareForUpdate.Prepare().

TagsDI, Part 100

Activities

Uwe Thomas

2022-12-14 08:16

manager   ~0018317

The description of the result code in Table 69 is misleading: It only applies for Direct-Loading.
In case of Direct-Loading PrepareForUpdate must be called before the FileTransfer and only for this case the result code makes sense.
I suggest to change the description in Table 69:
"Bad_InvalidState" shall be returned "Direct-Loading only: If the PrepareForUpdate is available, the UpdateBehavior requires preparation and the
PrepareForUpdate state machine is not in the state PreparedForUpdate."

Uwe Thomas

2024-10-14 12:00

manager   ~0021887

changd description of result code:
Direct-Loading only: If the PrepareForUpdate is available, the UpdateBehavior requires preparation and the PrepareForUpdate state machine is not in the state PreparedForUpdate.

Issue History

Date Modified Username Field Change
2022-10-21 10:46 Roman Sinawski New Issue
2022-10-28 07:35 Roman Sinawski Tag Attached: Part 100
2022-10-28 07:35 Roman Sinawski Tag Attached: DI
2022-12-14 08:16 Uwe Thomas Note Added: 0018317
2024-05-14 13:49 Karl Deiretsbacher Assigned To => Uwe Thomas
2024-05-14 13:49 Karl Deiretsbacher Status new => assigned
2024-10-14 12:00 Uwe Thomas Status assigned => resolved
2024-10-14 12:00 Uwe Thomas Resolution open => fixed
2024-10-14 12:00 Uwe Thomas Fixed in Version => 1.05
2024-10-14 12:00 Uwe Thomas Note Added: 0021887