Equivalent findscu to what Orthanc is doing?

General
1

In Orthanc Explorer 2, I can go into DICOM Modalities, select my MR modality, and see all the studies that are on the scanner.

But if I do the same using findscu in a shell on the host that Orthanc is running on, setting the AEC to the same thing that’s in orthanc.json’s DicomAet, and setting the AET to the same thing that’s defined in DicomModalities, I get rejected.

E.g.:

micadmin@micvna ~ via 🐍 v3.11.2
❯ findscu -v -S -k "StudyDate=20250420-20250430" -aet MICVNA -aec PRISMA1 172.29.158.6 104
I: Requesting Association
I: Association Accepted (Max Send PDV: 131060)
I: Sending Find Request (MsgID 1)
I: Request Identifiers:
I:
I: # Dicom-Data-Set
I: # Used TransferSyntax: Little Endian Explicit
I: (0008,0020) DA [20250420-20250430]                      #  18, 1 StudyDate
I:
I: Received Final Find Response (Failed: UnableToProcess)
I: Releasing Association
E: Association Release Failed: 0006:0317 Peer aborted Association (or never connected)

Echo works fine.

micadmin@micvna ~ via 🐍 v3.11.2
✖2 ❯ echoscu -v -aet MICVNA -aec PRISMA1 172.29.158.6 104
I: Requesting Association
I: Association Accepted (Max Send PDV: 131060)
I: Sending Echo Request (MsgID 1)
I: Received Echo Response (Success)
I: Releasing Association

Can someone tell me what the equivalent findscu command would be to whatever Orthanc is doing that is succeeding?

2

Hi @ddrucker

As always, Orthanc logs might help you …

FYI, here’s a findscu command that works fine on my side and that mimics a C-Find from an AWS workstation.

findscu -S  -aec ORTHANC -aet AWS -k "QueryRetrieveLevel=Study" -k "StudyDate=20200205-20241231" -k "StudyTime" -k "AccessionNumber" -k "ModalitiesInStudy" -k "StationName" -k "StudyDescription" -k "PatientName" -k "PatientID" -k "PatientBirthDate" -k "PatientBirthTime" -k "PatientSex" -k "StudyInstanceUID" -k "StudyID" -k "NumberOfStudyRelatedInstances" -k "0008,0000"  -k "0010,0000"  -k "0020,0000" localhost 4242

HTH,

Alain.

3

Huh. That gives me a new error I’ve never seen before:

findscu -S  -aet MICVNA -aec PRISMA1 -k "QueryRetrieveLevel=Study" -k "StudyDate=20250425-20250501" -k "StudyTime" -k "AccessionNumber" -k "ModalitiesInStudy" -k "StationName" -k "StudyDescription" -k "PatientName" -k "PatientID" -k "PatientBirthDate" -k "PatientBirthTime" -k "PatientSex" -k "StudyInstanceUID" -k "StudyID" -k "NumberOfStudyRelatedInstances" -k "0008,0000"  -k "0010,0000"  -k "0020,0000" 172.29.158.6 104
E: Association Rejected:
E: Result: Rejected Transient, Source: Service Provider (Presentation Related)
E: Reason: Temporary Congestion

even though I still have no problems doing it from inside Orthanc.

4

That’s an Orthanc behind this IP/Port right ? Then, there should be logs from Orthanc no ?

5

No, that’s Siemens XA30 behind that IP/port.

6

Ok (slowly starting to understand what you are doing :wink: ).

If you start Orthanc with --trace-dicom, you’ll get the same output as the findscu -v. Hopefully, that will help you spot the difference.