Now I use dcmtk as a printer to recieve Siemens CT images,but the connection status of Siemens CT is not good,
so I checked the logs and found the connection aborted after NGet,But I didn't know why.
I actually never worked with dcmqrscp but for me it looks that the printer starts the association, sends the N-GET (and dcmqrscp responds successfully) but then no other message is received from the client. I.e. the client keeps the association open in order to use it later, maybe. Thus dcmqrscp runs into a timeout (timeout in non-blocking mode) while waiting for other DIMSE message (or the client ending the association).
Leaving the connection open for later (and thus potentially blocking it for other clients) is usually considered bad style.
You could try to define a longer timeout or switch to blocking mode (waiting "forever").
Actually I don't know whether this is possible in the dcmqrscp configuration file or whether it can only be done in code.
It could also be another error, e.g. client is crashing due to a software bug or there is an issue in dcmqrscp but I'd consider above scenario as the most likely one.
I actually never worked with dcmqrscp but for me it looks that the printer starts the association, sends the N-GET (and dcmqrscp responds successfully) but then no other message is received from the client. I.e. the client keeps the association open in order to use it later, maybe. Thus dcmqrscp runs into a timeout (timeout in non-blocking mode) while waiting for other DIMSE message (or the client ending the association).
Leaving the connection open for later (and thus potentially blocking it for other clients) is usually considered bad style.
You could try to define a longer timeout or switch to blocking mode (waiting "forever").
Actually I don't know whether this is possible in the dcmqrscp configuration file or whether it can only be done in code.
It could also be another error, e.g. client is crashing due to a software bug or there is an issue in dcmqrscp but I'd consider above scenario as the most likely one.
Best,
Michael
I changed the blocking mode,the log shows waiting forever,N-GET all the time.
I defined timeout 30s,40s,50s,no effort.
I connected to an other Siemens CT,it also had this problem.
Maybe this problem can only be solved in code.
Gavinzz01 wrote: ↑Mon, 2016-07-18, 14:08
Now I use dcmtk as a printer to recieve Siemens CT images,but the connection status of Siemens CT is not good,
so I checked the logs and found the connection aborted after NGet,But I didn't know why.
$dcmtk: dcmprscp v3.6.0 2011-01-06 $
2016-05-31 10:44:56
started
Using database in directory 'D:\DICOM\Database\'
Association Received (bogon:PR_CT76989 -> KKKK) 2016-06-30 10:45:06
====================== BEGIN A-ASSOCIATE-RQ =====================
Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.6.0
Our Implementation Version Name: OFFIS_DCMTK_360
Their Implementation Class UID: 1.3.12.2.1107.5.1.4
Their Implementation Version Name: SIEMENS_S5VC20A
Application Context Name: 1.2.840.10008.3.1.1.1
Calling Application Name: PR_CT76989
Called Application Name: KKKK
Responding Application Name:
Our Max PDU Receive Size: 32768
Their Max PDU Receive Size: 32768
Presentation Contexts:
Context ID: 1 (Proposed)
Abstract Syntax: =BasicGrayscalePrintManagementMetaSOPClass
Proposed SCP/SCU Role: Default
Accepted SCP/SCU Role: Default
Proposed Transfer Syntax(es):
=LittleEndianExplicit
=LittleEndianImplicit
=BigEndianExplicit
Context ID: 3 (Proposed)
Abstract Syntax: =PrintJobSOPClass
Proposed SCP/SCU Role: Default
Accepted SCP/SCU Role: Default
Proposed Transfer Syntax(es):
=LittleEndianExplicit
=LittleEndianImplicit
=BigEndianExplicit
Context ID: 5 (Proposed)
Abstract Syntax: =BasicColorPrintManagementMetaSOPClass
Proposed SCP/SCU Role: Default
Accepted SCP/SCU Role: Default
Proposed Transfer Syntax(es):
=LittleEndianExplicit
=LittleEndianImplicit
=BigEndianExplicit
Context ID: 7 (Proposed)
Abstract Syntax: =PresentationLUTSOPClass
Proposed SCP/SCU Role: Default
Accepted SCP/SCU Role: Default
Proposed Transfer Syntax(es):
=LittleEndianExplicit
=LittleEndianImplicit
=BigEndianExplicit
Requested Extended Negotiation: none
Accepted Extended Negotiation: none
Requested User Identity Negotiation: none
User Identity Negotiation Response: none
======================= END A-ASSOCIATE-RQ ======================
====================== BEGIN A-ASSOCIATE-AC =====================
Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.6.0
Our Implementation Version Name: OFFIS_DCMTK_360
Their Implementation Class UID: 1.3.12.2.1107.5.1.4
Their Implementation Version Name: SIEMENS_S5VC20A
Application Context Name: 1.2.840.10008.3.1.1.1
Calling Application Name: PR_CT76989
Called Application Name: KKKK
Responding Application Name: KKKK
Our Max PDU Receive Size: 32768
Their Max PDU Receive Size: 32768
Presentation Contexts:
Context ID: 1 (Accepted)
Abstract Syntax: =BasicGrayscalePrintManagementMetaSOPClass
Proposed SCP/SCU Role: Default
Accepted SCP/SCU Role: Default
Accepted Transfer Syntax: =LittleEndianImplicit
Context ID: 3 (Abstract Syntax Not Supported)
Abstract Syntax: =PrintJobSOPClass
Proposed SCP/SCU Role: Default
Accepted SCP/SCU Role: Default
Context ID: 5 (Abstract Syntax Not Supported)
Abstract Syntax: =BasicColorPrintManagementMetaSOPClass
Proposed SCP/SCU Role: Default
Accepted SCP/SCU Role: Default
Context ID: 7 (Accepted)
Abstract Syntax: =PresentationLUTSOPClass
Proposed SCP/SCU Role: Default
Accepted SCP/SCU Role: Default
Accepted Transfer Syntax: =LittleEndianImplicit
Requested Extended Negotiation: none
Accepted Extended Negotiation: none
Requested User Identity Negotiation: none
User Identity Negotiation Response: none
======================= END A-ASSOCIATE-AC ======================
Association Acknowledged (Max Send PDV: 32756)
===================== INCOMING DIMSE MESSAGE ====================
Message Type : N-GET RQ
Message ID : 59
Requested SOP Class UID : PrinterSOPClass
Requested SOP Instance UID : 1.2.840.10008.5.1.1.17
Data Set : none
Attribute Identifier List : none
======================= END DIMSE MESSAGE =======================
===================== OUTGOING DIMSE MESSAGE ====================
Message Type : N-GET RSP
Message ID Being Responded To : 59
Affected SOP Class UID : PrinterSOPClass
Affected SOP Instance UID : 1.2.840.10008.5.1.1.17
Data Set : present
DIMSE Status : 0x0000: Success
-----------------------------------------------------------------
# Dicom-Data-Set
# Used TransferSyntax: Unknown Transfer Syntax
(0008,0070) LO [KK] # 2, 1 Manufacturer
(0008,1090) LO [KK] # 10, 1 ManufacturerModelName
(0018,1000) LO [KK] # 10, 1 DeviceSerialNumber
(0018,1020) LO [V1.00] # 6, 1 SoftwareVersions
(0018,1200) DA [20160626] # 8, 1 DateOfLastCalibration
(0018,1201) TM [010101] # 6, 1 TimeOfLastCalibration
(2110,0010) CS [NORMAL] # 6, 1 PrinterStatus
(2110,0020) CS [NORMAL] # 6, 1 PrinterStatusInfo
(2110,0030) LO [KK] # 10, 1 PrinterName
======================= END DIMSE MESSAGE =======================
DIMSE Failure (aborting association):
0006:0207 DIMSE No data available (timeout in non-blocking mode)
hi,Gavinzz01.
i also has been in similar trouble when the siemens ct device print to my service.
so,do you have solve this problem? and how do you do?
i will be pleasure to receive your message.