Getting only a single image in series retrieval (DCMTK, Siemens)

Ben Carruthers

unread,

Jun 25, 2004, 1:10:12 PM6/25/04

to

I am having trouble retrieving images from Siemens MagicView 300 (VA40A)
using the movescu utility in DCMTK. I supply the appropriate keys for a
series level retrieval and I am able to retrieve the first image in the
series, but after that something fails (fail to receive PDV command) and no
more images are retrieved.

I experienced a similar problem using the UC Davis toolkit with a new GE MR
scanner. Only the first image in the series was retrieved. I had no problems
with UC Davis and MagicView or with DCMTK and the new scanner.

I emailed OFFIS and Joerg Riesmeier suggested it might be a timing issue. I
tried calling movescu with the -dhl option (disable hostname lookup), but it
made no difference.

Any suggestions would be greatly appreciated.

Ben Carruthers

Joerg Riesmeier

unread,

Jun 28, 2004, 9:49:36 AM6/28/04

to

Ben Carruthers <ben...@hotmail.com> wrote:

> Any suggestions would be greatly appreciated.

it could also be a protocol violation. From the log you've provided:

DIMSE Command Received:
...
DIMSE Warning: (xxxx,xxxx): moveUser: Status Pending, but DataSetType!=NULL
DIMSE Warning: (xxxx,xxxx): Assuming NO response identifiers are present
Move Response 1: C-Move RSP: MsgID: 1 [Status=Pending]
AffectedSOPClassUID: =MOVEStudyRootQueryRetrieveInformationModel
Data Set: Present
NumberOfRemainingSubOperations: 20
NumberOfCompletedSubOperations: 1
NumberOfFailedSubOperations: 0
NumberOfWarningSubOperations: 0
DIMSE receiveCommand
DIMSE receiveCommand: 1 pdv's (14 bytes), presID=3
movescu: Move Failed:
0006:020d DIMSE Failed to receive message
0006:020f DIMSE: Command PDV Expected
...

The attribute Data Set Type (0000,0900) indicates that there is a dataset
but the receiver does not expect any and, therefore, ignores it.

Regards
Joerg Riesmeier
OFFIS

Ben Carruthers

unread,

Jun 28, 2004, 4:52:56 PM6/28/04

to

Thank you for your responses.

It's exactly that - the dataset is not expected. I solved the problem by
making a very small modification to dimmove.cxx. I added code to receive the
data set if it is present, even if it is not expected or supposed to be
present. It seems to be working fine now.

Ben Carruthers

"Joerg Riesmeier" <ne...@riesmeier.de> wrote in message
news:cbp7li$1...@news.Informatik.Uni-Oldenburg.DE...

Joerg Riesmeier

unread,

Jun 29, 2004, 4:42:48 AM6/29/04

to

Ben Carruthers <ben...@hotmail.com> wrote:

> I added code to receive the data set if it is present, even
> if it is not expected or supposed to be present.

I'm curious: what is the content of the dataset?

Regards,
Joerg Riesmeier
OFFIS

Ben Carruthers

unread,

Jun 30, 2004, 11:58:49 PM6/30/04

to

It's the image datasets containing pixel data.

Ben Carruthers

"Joerg Riesmeier" <ne...@riesmeier.de> wrote in message

news:cbra2a$n...@news.Informatik.Uni-Oldenburg.DE...

JAPS

unread,

Aug 5, 2004, 6:13:07 AM8/5/04

to

Hi there.

Could you please send me to my email the new 'dimmove.cc' or a patch to
the original one? I have exactly the same problem (at least, I think so).

I am using dcmtk 3.5.3 to retrieve images from a PACS and I only obtain
the first one from the study.

This is what I see when I try to retrieve the images:

**********************************************************************

[root@linuxFedora DICOM]# movescu -v -aec HNSQR -aet LFC1 -aem LFC1 +P
4006 -P -k 0008,0052=PATIENT -k 0010,0020=ABCDE 10.36.11.241 205

Requesting Association
Association Accepted (Max Send PDV: 16372)
================================
Sending query
Move SCU RQ: MsgID 1
Request:

# Dicom-Data-Set
# Used TransferSyntax: UnknownTransferSyntax
(0008,0052) CS [PATIENT] # 8, 1
QueryRetrieveLevel
(0010,0020) LO [ABCDE] # 6, 1 PatientID
Received C-Store RQ: MsgID: 1
AffectedSOPClassUID: =ComputedRadiographyImageStorage
AffectedSOPInstanceUID: 1.3.51.5146.1682.20040803.1090215.1
Priority: 0
Data Set: Present
Move Originator ID: 1
RECV:...........................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
....... Move Response 1: C-Move RSP: MsgID: 1 [Status=Pending]
AffectedSOPClassUID: =MOVEPatientRootQueryRetrieveInformationModel
Data Set: Not Present
NumberOfRemainingSubOperations: 1

NumberOfCompletedSubOperations: 1
NumberOfFailedSubOperations: 0
NumberOfWarningSubOperations: 0

DIMSE Warning: (,HNSQR): moveUser: Status Pending, but DataSetType!=NULL
DIMSE Warning: (,HNSQR): Assuming NO response identifiers are present
Move Response 2: C-Move RSP: MsgID: 1 [Status=Pending]
AffectedSOPClassUID: =MOVEPatientRootQueryRetrieveInformationModel
Data Set: Present
NumberOfRemainingSubOperations: 1

NumberOfCompletedSubOperations: 1
NumberOfFailedSubOperations: 0
NumberOfWarningSubOperations: 0

movescu: Move Failed:
0006:020d DIMSE Failed to receive message
0006:020f DIMSE: Command PDV Expected

movescu: SCU Failed:

0006:020d DIMSE Failed to receive message
0006:020f DIMSE: Command PDV Expected

Aborting Association

**********************************************************************