movescu.py v0.4.0 usage difficulties

19 views
Skip to first unread message

Normand Robert

unread,
Sep 26, 2023, 4:42:17 PM9/26/23
to pynetdicom
For a given same AGFA PACS system I can use both dcmtk findscu and pynetdicom findscu.py successfully. The parameters are identical for both. I can use dcmtk  movescu successfully but not pynetdicom movescu.py. Could someone comment on what I might be doing wrong?

findscu.py works:

python -m pynetdicom findscu -v -S -k QueryRetrieveLevel=SERIES -k SeriesInstanceUID="" -k PatientID=$MY_PATIENT_ID      138.218.233.66  11112 -aec ONDR01IDCSAS  -aet SRIHDIRS

#movescu.py version

python -m pynetdicom movescu -v 138.218.233.66 11112 --version
movescu.py v0.4.0

dcmtk movescu works:

movescu -v 138.218.233.66 11112 -aec ONDR01IDCSAS -aet SRIHDIRS --port 11112 -S -k QueryRetrieveLevel="SERIES" -k SeriesInstanceUID=$SERIES_INSTANCE_UID  -od ./incoming/

movescu.py does not work as expected

python -m pynetdicom movescu -v 138.218.233.66 11112 -aec ONDR01IDCSAS --store -aet SRIHDIRS -aem MOVESCU -S -od  ./incoming -k QueryRetrieveLevel="SERIES" -k SeriesInstanceUID=$SERIES_INSTANCE_UID
I: Requesting Association
I: Association Accepted
I: Sending Move Request: MsgID 1
I:
I: # Request Identifier
I: (0008,0052) CS [SERIES]                                 # 1 QueryRetrieveLevel
I: (0020,000E) UI [1.3.12.2.1107.5.1.4.73821.30000020070209574762400050885] # 1 SeriesInstanceUID
I:
I: Move SCP Result: 0xA801 (Failure)
I: Sub-Operations Remaining: 0, Completed: 0, Failed: 0, Warning: 0
I: Releasing Association





Normand Robert

unread,
Sep 27, 2023, 11:47:57 AM9/27/23
to pynetdicom
PLEASE REMOVE I still have issues but initial one above was also user error related.
Reply all
Reply to author
Forward
0 new messages